From: | senthilnathan <senthilnathan(dot)t(at)gmail(dot)com> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Queries Regarding Postgresql Replication |
Date: | 2011-08-02 16:33:27 |
Message-ID: | 1312302807166-4659365.post@n5.nabble.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
*====> What is the procedure to make the failed master as working slave?*
Check whether the following steps works for you...
Assume the following is your use case.,
Master ----> Slave(Stand by..)
Master replicating to slave. At time when master failed, the slave takes
over as new master. Now your requirement to restart the failed master and
reconfigure the same as standby for the new master.
Stop the failed master.
1. Once the stand by taken over as master (once recovery.done and before any
new data inserted...), copy file pg_control (available under data/global/)
and the newly generated timeline history file available under archive folder
(e-g., file like 00000002.history)
2. Remove all files under pg_xlog directory and in archive folder in the
failed master . The above copied pg_control file, should be replaced in this
failed master under data/global/). The above copied history should be copied
in archive folder.
Reconfigure the recovery.conf to point the new master
Try starting the server..,(new standby) I hope it works !
- Senthil
--
View this message in context: http://postgresql.1045698.n5.nabble.com/Queries-Regarding-Postgresql-Replication-tp4372554p4659365.html
Sent from the PostgreSQL - general mailing list archive at Nabble.com.
From | Date | Subject | |
---|---|---|---|
Next Message | Scott Marlowe | 2011-08-02 17:55:13 | Re: 9.0 Streaming Replication Problem to two slaves |
Previous Message | senthilnathan | 2011-08-02 16:32:35 | Re: Queries Regarding Postgresql Replication |