Sorry, version: PostgreSQL 8.4.2 on x86_64-redhat-linux-gnu, compiled by GCC gcc (GCC) 4.1.2 20071124 (Red Hat 4.1.2-42), 64-bit
On Mon, May 10, 2010 at 5:01 PM, bricklen <brick...@gmail.com> wrote: > Hi, > > I'm stumped by an issue we are experiencing at the moment. We have > been successfully archiving logs to two standby sites for many months > now using the following command: > > rsync -a %p postg...@192.168.80.174:/WAL_Archive/ && rsync > --bwlimit=1250 -az %p postg...@14.121.70.98:/WAL_Archive/ > > 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 postg...@192.168.80.174:/WAL_Archive/ && rsync > --bwlimit=1875 -az %p postg...@14.121.70.98:/WAL_Archive/ > > > The db is showing the change. > SHOW archive_command: > rsync -a %p postg...@192.168.80.174:/WAL_Archive/ && rsync > --bwlimit=1875 -az %p postg...@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) > > ps aux | grep rsync > postgres 27704 0.0 0.0 63820 1068 ? S 16:55 0:00 sh -c > rsync -a pg_xlog/000000010000071700000070 > postg...@192.168.80.174:/WAL_Archive/ && rsync --bwlimit=1250 -az > pg_xlog/000000010000071700000070 postg...@14.121.70.98:/WAL_Archive/ > postgres 27714 37.2 0.0 68716 1612 ? S 16:55 0:01 rsync > --bwlimit=1250 -az pg_xlog/000000010000071700000070 > postg...@14.121.70.98:/WAL_Archive/ > postgres 27715 3.0 0.0 60764 5648 ? S 16:55 0:00 ssh > -l postgres 14.121.70.98 rsync --server -logDtprz --bwlimit=1250 . > /WAL_Archive/ > > > Thanks, > > bricklen > -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
