Hi, How about the following two areas? step 3: wait until the failover is completed, the server is brought up after applying all WAL files available in the archive. Question 1: How to check if the failover is completed and the new Primary is ready? step 4: if the failover is done Question 2: Do I need to edit the new primary's postgresql.conf and restart postgresql? e.g. comment out the hot_standy = on thanks On 20 Sep 2013, at 4:39 AM, Michael Nolan wrote: > On 9/19/13, John R Pierce <pierce@xxxxxxxxxxxx> wrote: >> On 9/19/2013 1:29 PM, Vick Khera wrote: >>> >>> On Thu, Sep 19, 2013 at 11:31 AM, ascot.moss@xxxxxxxxx >>> <mailto:ascot.moss@xxxxxxxxx> <ascot.moss@xxxxxxxxx >>> <mailto:ascot.moss@xxxxxxxxx>> wrote: >>> >>> I use PG 9.2.4 with streaming replication. What will be the >>> manual procedure to failover from Primary to Standby and Set the >>> old Primary as a new standby? >>> >>> >>> From what I understand, you start over by setting up the old primary >>> as a new standby from scratch. >> >> if you use rsync for the base backup of new master to old, it should go >> fairly quickly as relatively few files should have changed assuming not >> much time has elapsed. > > Of course, before you do anything, you should spend some time figuring > out WHY the old master failed. There could be issues that need to be > resolved before putting it back online, and fixing them could affect > how much work you have to do to get the physical files back in sync. > -- > Mike Nolan > > > -- > Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) > To make changes to your subscription: > http://www.postgresql.org/mailpref/pgsql-general -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
