On Tue, May 11, 2010 at 9:50 AM, Tom Lane <tgl@xxxxxxxxxxxxx> wrote: > bricklen <bricklen@xxxxxxxxx> writes: >> Due to some heavy processing today, we have been falling behind on >> shipping log files (by about a 1000 logs or so), so wanted to up our >> bwlimit like so: > >> rsync -a %p postgres@xxxxxxxxxxxxxx:/WAL_Archive/ && rsync >> --bwlimit=1875 -az %p postgres@xxxxxxxxxxxx:/WAL_Archive/ > >> The db is showing the change. >> SHOW archive_command: >> rsync -a %p postgres@xxxxxxxxxxxxxx:/WAL_Archive/ && rsync >> --bwlimit=1875 -az %p postgres@xxxxxxxxxxxx:/WAL_Archive/ > >> Yet, the running processes never get above the original bwlimit of >> 1250. Have I missed a step? Would "kill -HUP <archiver pid>" help? >> (I'm leery of trying that untested though) > > A look at the code shows that the archiver only notices SIGHUP once > per outer loop, so the change would only take effect once you catch up, > which is not going to help much in this case. Possibly we should change > it to check for SIGHUP after each archive_command execution. +1 Here is the simple patch to do so. Regards, -- Fujii Masao NIPPON TELEGRAPH AND TELEPHONE CORPORATION NTT Open Source Software Center
Attachment:
pgarch_check_sighup_v1.patch
Description: Binary data
-- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
