Re: pg_archivecleanup with multiple slaves - Mailing list pgsql-admin

From Fujii Masao
Subject Re: pg_archivecleanup with multiple slaves
Date
Msg-id BANLkTi=S7bm_2jQfhLZec1OXyUVSW8K7HQ@mail.gmail.com
Whole thread Raw
In response to pg_archivecleanup with multiple slaves  (Ben Lancaster <benlancaster@holler.co.uk>)
Responses Re: pg_archivecleanup with multiple slaves  (Tim Lewis <Tim.Lewis@vialect.com>)
List pgsql-admin
On Fri, May 20, 2011 at 7:59 PM, Ben Lancaster
<benlancaster@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
slavehad picked up the changes, thus breaking replication for the second slave. As an interim fix, I simply disabled
theautomatic 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

pgsql-admin by date:

Previous
From: Ben Lancaster
Date:
Subject: Re: pg_archivecleanup with multiple slaves
Next
From: Craig James
Date:
Subject: Who is causing all this i/o?