I don't actually use streaming replication, but what exactly is the problem with the hard link for each slave solution, and the slaves handling there own pg_archivecleanup?
On Fri, May 20, 2011 at 11:30 AM, Fujii Masao <masao.fu...@gmail.com> wrote: > On Fri, May 20, 2011 at 7:59 PM, Ben Lancaster > <benlancas...@holler.co.uk> wrote: > > The problem I have is that pg_archivecleanup (running on one of the > slaves) was removing WAL logs before the other slave had picked up the > changes, thus breaking replication for the second slave. As an interim fix, > I simply disabled the automatic cleanup and figured I'd worry about it > later. > > I'm afraid there is no clean solution. In order to address this > problem, we probably > should change the master for 9.2 so that it collects the information > about the cutoff > point from each standby and calls pg_archivecleanup. > > Regards, > > -- > Fujii Masao > NIPPON TELEGRAPH AND TELEPHONE CORPORATION > NTT Open Source Software Center > > -- > Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) > To make changes to your subscription: > http://www.postgresql.org/mailpref/pgsql-admin > -- Noodle Connecting People, Content & Capabilities within the Enterprise Toll Free: 866-258-6951 x 701 tim.le...@vialect.com http://www.vialect.com Noodle is a product of Vialect Inc Follow Noodle on Twitter http://www.twitter.com/noodle_news
