Re: Failover with a tertiary read-only secondary

bricklen <bricklen(at)gmail(dot)com> writes:

> On Fri, Mar 31, 2017 at 11:35 AM, Hammerman, Joseph <JosephHammerman(at)iheartmedia(dot)com> wrote:
>
> 1. Not a bad idea, but that only delays the necessity of a resync until the next failover…. Unless I’m missing something?
>
> I've used cascading replication extensively over the past few years and rarely had to resync a downstream replica. The several thousand Postgres clusters I'm
> administering now are almost exclusively set up with the primary replica streaming from the master and the master shipping WALs to the secondary replica in DR data
> centre, so I can't test any cascading replication promotions at the moment. My suggestion is to test your replication setup in a cascade and see what happens, I don't
> expect you'll need to resync. If you do, report back with how you've set up your replication settings.

Repointing tertiary standbys to a promoted peer should not be difficult
if same tertiary standby was at or trailing the log position when new
master promoted... and recovery.conf has recovery_target_timeline=latest.

Also, the new promoted master needs to have been already configured to
archive and wal_level set not minimal on promotion.

In other words, there shall be no break in the WAL stream in regards to
adequate wal level which depends on the tertiary standby's needs.

HTH

>

--
Jerry Sievers
Postgres DBA/Development Consulting
e: postgres(dot)consulting(at)comcast(dot)net
p: 312.241.7800