Re: Failover of a Hot standby setup with multiple standbys
От | Sergey Konoplev |
---|---|
Тема | Re: Failover of a Hot standby setup with multiple standbys |
Дата | |
Msg-id | CAL_0b1tA5ZQUw4zqn-oHHjD9AFxHuvbAwrJzDDRTROX7=gWzdA@mail.gmail.com обсуждение исходный текст |
Ответ на | Failover of a Hot standby setup with multiple standbys (Deepesh D <deep.d2010@gmail.com>) |
Список | pgsql-admin |
On Tue, Feb 28, 2012 at 4:05 PM, Deepesh D <deep.d2010@gmail.com> wrote: > Is it enough if I just change the 'primary_conninfo' and 'restore_command' > in both the slaves (S2,S3) to point to the new master S1? Once I had such experience on 9.0.x and here is the note I made for myself: To switch a replica to read from the new master after switching it over add the following instruction in the recovery.conf on the replica. recovery_target_timeline = 'latest' Then stop the service, resync the pg_xlog directory on the replica and start it. Note that the old master must be stopped before switching the new one over. It will prevent replicas from timeline divergence. ps. I tried to adjust the x..xx.history file to avoid re-syncing pg_xlog but without any success. pps. BTW I still wonder if it is possible to avoid the re-syncing. May be it could be done by setting restore_command? -- Sergey Konoplev Blog: http://gray-hemp.blogspot.com LinkedIn: http://ru.linkedin.com/in/grayhemp JID/GTalk: gray.ru@gmail.com Skype: gray-hemp
В списке pgsql-admin по дате отправления: