pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tim Lewis <Tim.Lewis@vialect.com>
To: Fujii Masao <masao.fujii@gmail.com>
Cc: Ben Lancaster <benlancaster@holler.co.uk>
Cc: pgsql-admin@postgresql.org
Subject: Re: pg_archivecleanup with multiple slaves
Date: Fri, 20 May 2011 11:58:05 -0400
Message-ID: <BANLkTin_7X-dfopa2qOzeFddEw4Pnm5OTA@mail.gmail.com> (raw)
In-Reply-To: <BANLkTi=S7bm_2jQfhLZec1OXyUVSW8K7HQ@mail.gmail.com>
References: <D1FBF69C-F380-4F16-AF57-20A32CB4850C@holler.co.uk>
	<BANLkTi=S7bm_2jQfhLZec1OXyUVSW8K7HQ@mail.gmail.com>

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.fujii@gmail.com> wrote:

> 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 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

view thread (7+ messages)  latest in thread

Message-ID: <BANLkTin_7X-dfopa2qOzeFddEw4Pnm5OTA@mail.gmail.com>
Permalink:  ../BANLkTin_7X-dfopa2qOzeFddEw4Pnm5OTA@mail.gmail.com/
Also on:    postgresql.org/message-id/BANLkTin_7X-dfopa2qOzeFddEw4Pnm5OTA@mail.gmail.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-admin@postgresql.org
  Cc: Tim.Lewis@vialect.com, masao.fujii@gmail.com, benlancaster@holler.co.uk
  Subject: Re: pg_archivecleanup with multiple slaves
  In-Reply-To: <BANLkTin_7X-dfopa2qOzeFddEw4Pnm5OTA@mail.gmail.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox