Re: 9.2 Cascading replication after slave promotion

From: Gibheer <gibheer(at)zero-knowledge(dot)org>
To: Josh Berkus <josh(at)agliodbs(dot)com>
Cc: Stephen Frost <sfrost(at)snowman(dot)net>, Daniel Farina <daniel(at)heroku(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: 9.2 Cascading replication after slave promotion
Date: 2012-09-19 04:09:51
Message-ID: 20120919060951.18410d9b@linse.fritz.box
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, 14 Aug 2012 10:50:07 -0700
Josh Berkus <josh(at)agliodbs(dot)com> wrote:

>
> > Yeah, I think there's more people that agree with this use-case
> > than you seem to think.. That said, I appreciate that it's not a
> > trivial thing to support cleanly.
>
> Not trivial, no, but not major either. Really what needs to happen is
> for the timeline change record to get transmitted over the WAL stream.
>
> Hmmm. You know, I bet I could get stream-only remastering working in
> an unsafe way just by disabling the timeline checks. Time to test ...
>

Isn't that, what recovery_target_timeline in the recovery.conf already
does? It switches to the next timeline after a master migration. See
http://www.postgresql.org/docs/current/static/recovery-target-settings.html
for further information.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2012-09-19 06:05:38 Re: [ADMIN] pg_upgrade from 9.1.3 to 9.2 failed
Previous Message Tom Lane 2012-09-19 03:38:33 Re: WIP patch: add (PRE|POST)PROCESSOR options to COPY