Re: Cascading replication and recovery_target_timeline='latest' - Mailing list pgsql-hackers

From Heikki Linnakangas
Subject Re: Cascading replication and recovery_target_timeline='latest'
Date
Msg-id 50454DF6.4070400@iki.fi
Whole thread Raw
In response to Re: Cascading replication and recovery_target_timeline='latest'  (Heikki Linnakangas <hlinnaka@iki.fi>)
Responses Re: Cascading replication and recovery_target_timeline='latest'  (Heikki Linnakangas <hlinnaka@iki.fi>)
List pgsql-hackers
On 03.09.2012 16:26, Heikki Linnakangas wrote:
> On 03.09.2012 16:25, Fujii Masao wrote:
>> On Tue, Sep 4, 2012 at 7:07 AM, Heikki Linnakangas<hlinnaka@iki.fi>
>> wrote:
>>> Hmm, I was thinking that when walsender gets the position it can send
>>> the
>>> WAL up to, in GetStandbyFlushRecPtr(), it could atomically check the
>>> current
>>> recovery timeline. If it has changed, refuse to send the new WAL and
>>> terminate. That would be a fairly small change, it would just close the
>>> window between requesting walsenders to terminate and them actually
>>> terminating.
>>
>> Yeah, sounds good. Could you implement the patch? If you don't have time,
>> I will....
>
> I'll give it a shot..

So, this is what I came up with, please review.

- Heikki

Attachment

pgsql-hackers by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Re: Cascading replication and recovery_target_timeline='latest'
Next
From: Peter Eisentraut
Date:
Subject: Re: Is this non-volatile pointer access OK?