Re: 9.2 Cascading replication after slave promotion

From: Josh Berkus <josh(at)agliodbs(dot)com>
To: pgsql-hackers(at)postgresql(dot)org
Subject: Re: 9.2 Cascading replication after slave promotion
Date: 2012-08-14 00:32:48
Message-ID: 50299CB0.8060604@agliodbs.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Mark,

> Looking at the docs (section 25.2.6 paragraph 6) leads one to believe
> that downstream standbys can continue to receive and process wal merely
> by reconnecting after the cascading standby is promoted - but this does
> not seem to be the case (indeed the same paragraph notes that timelines
> now no longer match). It looks to me like the downstream guys all need
> to be rebuilt - or am I missing something?

Per discussion on this list (search for "remastering"), 9.2 still won't
allow standbies to point to a new master unless you are doing file-based
replication.

To date, I seem to be the only one convinced that this is an actual
deficiency ...

--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Mark Kirkwood 2012-08-14 00:54:50 Re: 9.2 Cascading replication after slave promotion
Previous Message Mark Kirkwood 2012-08-14 00:20:39 9.2 Cascading replication after slave promotion