bricklen <bricklen@gmail.com> 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@192.168.80.174:/WAL_Archive/ && rsync
> --bwlimit=1875 -az %p postgres@14.121.70.98:/WAL_Archive/
> The db is showing the change.
> SHOW archive_command:
> rsync -a %p postgres@192.168.80.174:/WAL_Archive/ && rsync
> --bwlimit=1875 -az %p postgres@14.121.70.98:/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.
If you kill -9 the archiver process, the postmaster will just start
a new one, but realize that that would result in two concurrent
rsync's. It might work ok to kill -9 the archiver and the current
rsync in the same command.
regards, tom lane
