From: | Mark Kirkwood <mark(dot)kirkwood(at)catalyst(dot)net(dot)nz> |
---|---|
To: | Josh Berkus <josh(at)agliodbs(dot)com> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: 9.2 Cascading replication after slave promotion |
Date: | 2012-08-14 00:54:50 |
Message-ID: | 5029A1DA.9000906@catalyst.net.nz |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 14/08/12 12:32, Josh Berkus wrote:
> 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 ...
>
>
Make that 2 of us...
From | Date | Subject | |
---|---|---|---|
Next Message | Daniel Farina | 2012-08-14 01:47:40 | Re: 9.2 Cascading replication after slave promotion |
Previous Message | Josh Berkus | 2012-08-14 00:32:48 | Re: 9.2 Cascading replication after slave promotion |