| From: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
|---|---|
| To: | Ben Lancaster <benlancaster(at)holler(dot)co(dot)uk> |
| Cc: | pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: pg_archivecleanup with multiple slaves |
| Date: | 2011-05-20 15:30:35 |
| Message-ID: | BANLkTi=S7bm_2jQfhLZec1OXyUVSW8K7HQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
On Fri, May 20, 2011 at 7:59 PM, Ben Lancaster
<benlancaster(at)holler(dot)co(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tim Lewis | 2011-05-20 15:58:05 | Re: pg_archivecleanup with multiple slaves |
| Previous Message | Ben Lancaster | 2011-05-20 14:23:46 | Re: pg_archivecleanup with multiple slaves |