Skip to main content
Database Administrators

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

3
  • 1. yes correct 2. may be it is better not to automate that process. 3. so you need 2 slave and 1 master at least. because as you said sync. replication need at least 2 nodes to push commits sync. if it there is just one master node, you will not be able to commit.. Commented Jan 24, 2012 at 6:33
  • steps 4, 5, and 6 are not necessary on the new master because, well, you're replicating to begin with. Second, what if the master died and was offline - you would not be able to connect to it. Steps 4,5, & 6 are typically done on a new slave node joining the replication pool. Commented Mar 24, 2013 at 2:51
  • @Eric as I played with this, steps 4,5,6 are required to bring back the old master to working state. Making the standby new primary immediately makes new WAL entry, so it's now 1 entry ahead of the old master. Starting the old master in standy mode threw errors on me, so i did have to make steps 4,5,6 on the old master to sync it with the new master (by using pg_basebackup, which can stream the whole xlog from the new master - replaces steps 4,5,6 in postgres >= 9.1 I think). Am I correct or did I do something wrong and this shoudln't be necessary? Commented Nov 27, 2013 at 19:31