Re: 9.2 Cascading replication after slave promotion - Mailing list pgsql-hackers

From Josh Berkus
Subject Re: 9.2 Cascading replication after slave promotion
Date
Msg-id 50299CB0.8060604@agliodbs.com
Whole thread Raw
In response to 9.2 Cascading replication after slave promotion  (Mark Kirkwood <mark.kirkwood@catalyst.net.nz>)
Responses Re: 9.2 Cascading replication after slave promotion
Re: 9.2 Cascading replication after slave promotion
List 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



pgsql-hackers by date:

Previous
From: Mark Kirkwood
Date:
Subject: 9.2 Cascading replication after slave promotion
Next
From: Mark Kirkwood
Date:
Subject: Re: 9.2 Cascading replication after slave promotion