On Fri, Mar 18, 2011 at 4:55 PM, Stephen Rees <srees@xxxxxxxxxxx> wrote: > Robert, > > Thank you for reply. I had the wrong end of the stick regarding pg_dump and > hot-standby. > I will take a look at omnipitr, as you suggest. > > Per your comment >> >> You have to stop replay while you are doing the dumps like this > > how do I stop, then resume, replay with both the master and hot-standby > available throughout? > If you are using WAL file based replication, you need some logic in your restore script that will enable it to stop feeding xlog segments into the slave (think "if pause file exists, return, else cp xlog file"). This would leave the slave available, just with no updates coming in. If you are using streaming, I think it's much harder. There are some new function to pause and resume streaming WAL coming in 9.1, it might be possible to back-patch those, but we haven't looked at it yet. Robert Treat play: xzilla.net work: omniti.com hiring: l42.org/lg -- Sent via pgsql-admin mailing list (pgsql-admin@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin
