Failback with log shipping

Поиск
Список
Период
Сортировка
От Heikki Linnakangas
Тема Failback with log shipping
Дата
Msg-id 4BFFA1E3.1000808@enterprisedb.com
обсуждение исходный текст
Ответы Re: Failback with log shipping  (Dimitri Fontaine <dfontaine@hi-media.com>)
Re: Failback with log shipping  (Fujii Masao <masao.fujii@gmail.com>)
Список pgsql-hackers
At PGCon, several people asked me about restarting an old master as a 
standby after failover has happened. And it wasn't the first time people 
ask me about it, even before 9.0. We have no mention of that in the 
docs, which is a pretty serious oversight. What can we say about it?

I believe the current official policy is that you have to take a new 
base backup and restore from that. Rsync can be used to speed that up.

However, someone once asked me for a comment on a script he wrote to do 
that in a smarter way. I forget who and when and how exactly it worked, 
but it seems possible to do safely.

First of all, you have to shut down the master cleanly for this to work, 
otherwise there can be changes in the old master that never made it to 
the standby.

Assuming controlled shutdown and that the standby received all WAL from 
the old master before it was promoted, I think you can simply create a 
recovery.conf in the old master's data directory to turn it into a 
standby server, and restart. Am I missing something?

--   Heikki Linnakangas  EnterpriseDB   http://www.enterprisedb.com


В списке pgsql-hackers по дате отправления:

Предыдущее
От: Fujii Masao
Дата:
Сообщение: Re: Patch submission deadline for CommitFest 2010-07
Следующее
От: Robert Haas
Дата:
Сообщение: Re: Working with PostgreSQL enums in C code