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

From Dimitri Fontaine
Subject Re: Cascading replication and recovery_target_timeline='latest'
Date
Msg-id m2r4qiw1f4.fsf@2ndQuadrant.fr
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'  (Josh Berkus <josh@agliodbs.com>)
Re: Cascading replication and recovery_target_timeline='latest'  (Heikki Linnakangas <hlinnaka@iki.fi>)
List pgsql-hackers
Heikki Linnakangas <hlinnaka@iki.fi> writes:
> 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.

It looks to me like a bug fix that also applies to non cascading
situation. Is that right?

Regards,
-- 
Dimitri Fontaine
http://2ndQuadrant.fr     PostgreSQL : Expertise, Formation et Support



pgsql-hackers by date:

Previous
From: "Etsuro Fujita"
Date:
Subject: Minor document updates
Next
From: Amit Kapila
Date:
Subject: Re: Proof of concept: standalone backend with full FE/BE protocol