Received: from maia.hub.org (maia-3.hub.org [200.46.204.243]) by mail.postgresql.org (Postfix) with ESMTP id 61D56B5DC33 for ; Fri, 20 May 2011 12:58:21 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.243]) (amavisd-maia, port 10024) with ESMTP id 52363-05 for ; Fri, 20 May 2011 15:58:13 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from cp996.blacksun.ca (69-27-99-6.blacksun.ca [69.27.99.6]) by mail.postgresql.org (Postfix) with ESMTP id A681BB5DC31 for ; Fri, 20 May 2011 12:58:13 -0300 (ADT) Received: from mail-iw0-f174.google.com ([209.85.214.174]) by cp996.blacksun.ca with esmtpsa (TLSv1:RC4-SHA:128) (Exim 4.69) (envelope-from ) id 1QNS5X-00083z-38 for pgsql-admin@postgresql.org; Fri, 20 May 2011 09:58:07 -0600 Received: by iwn34 with SMTP id 34so3133616iwn.19 for ; Fri, 20 May 2011 08:58:05 -0700 (PDT) MIME-Version: 1.0 Received: by 10.231.210.148 with SMTP id gk20mr3226525ibb.110.1305907085822; Fri, 20 May 2011 08:58:05 -0700 (PDT) Received: by 10.231.25.80 with HTTP; Fri, 20 May 2011 08:58:05 -0700 (PDT) In-Reply-To: References: Date: Fri, 20 May 2011 11:58:05 -0400 Message-ID: Subject: Re: pg_archivecleanup with multiple slaves From: Tim Lewis To: Fujii Masao Cc: Ben Lancaster , pgsql-admin@postgresql.org Content-Type: multipart/alternative; boundary=0016e68dea50f5cd2504a3b72fa7 X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - cp996.blacksun.ca X-AntiAbuse: Original Domain - postgresql.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - vialect.com X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-0.917 tagged_above=-10 required=5 tests=BAYES_00=-1.9, HTML_MESSAGE=0.001, RDNS_DYNAMIC=0.982 X-Spam-Level: X-Archive-Number: 201105/149 X-Sequence-Number: 37586 --0016e68dea50f5cd2504a3b72fa7 Content-Type: text/plain; charset=ISO-8859-1 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 wrote: > On Fri, May 20, 2011 at 7:59 PM, Ben Lancaster > 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.Lewis@vialect.com http://www.vialect.com Noodle is a product of Vialect Inc Follow Noodle on Twitter http://www.twitter.com/noodle_news --0016e68dea50f5cd2504a3b72fa7 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable I don't actually use streaming replication, but what exactly is the pro= blem with the hard link for each slave solution, and the slaves handling th= ere own pg_archivecleanup?

On Fri, May 20= , 2011 at 11:30 AM, Fujii Masao <masao.fujii@gmail.com> wrote:
On Fri, May 20, 2011 at 7= :59 PM, Ben Lancaster
<benlancaster@holler.co.uk<= /a>> 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= 9;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



--
=

Noodle
Connecting=A0People, Content & Capabilities=A0within the=A0Enterprise


Toll Free:=A0866-258-6951=A0x 701
Tim.Lew= is@vialect.com
http://www.vialect.com

Noodle is a product of Vialect Inc

Follow Noodle on Twitter
<= a href=3D"http://www.twitter.com/noodle_news" style=3D"color:rgb(17, 65, 11= 2)" target=3D"_blank">http://www.twitter.com/noodle_news
 --0016e68dea50f5cd2504a3b72fa7--