Thank you. I made a mistake, our version is PostgreSQL 9.6.2 ________________________________ From: Ben Chobot <be...@silentmedia.com> Sent: Monday, March 4, 2019 5:08 PM To: Julie Nishimura Cc: pgsql-general@lists.postgresql.org Subject: Re: master-> 2 hot standbys
On Mar 4, 2019, at 1:59 PM, Julie Nishimura <juliez...@hotmail.com<mailto:juliez...@hotmail.com>> wrote: Hello, Our current master 9.2 has two active standbys. Can you please help me out with the right sequence of events if we would like to promote one of current standbys to master and convert master to standby? It depends on how you've set things up, of course, but generally you can run "pg_ctl promote" on one of your slaves. This will make that slave start a new timeline and begin to act as a master. To restore your old master to a standby, you will need to rebuild it with something like pg_basebackup, as I do not believe pg_replay is supported with 9.2. https://www.postgresql.org/docs/9.5/warm-standby-failover.html Terminating client connections on the old master to avoid splitbrain and then making those clients reconnect to your new master is left as an exercise to the reader - how you do it really depends on your environment - but be sure you do it right, because splitbrain is a real danger. In a similar vein, you don't want two masters trying to save the same wals to the same wal archive. Also, if your two slaves are using asynchronous replication, be aware that the slave you choose to become the new master has a chance to be behind the other slave in wal replay when you promote it, unless you take precautions. This would mean your other slave won't be able to sync up with the newly promoted master.
