Streaming replication, master recycling

Поиск
Список
Период
Сортировка
От
Тема Streaming replication, master recycling
Дата
Msg-id 1462941074281.128157.22300@webmail6
обсуждение исходный текст
Ответы Re: Streaming replication, master recycling  (Venkata Balaji N <nag1010@gmail.com>)
Список pgsql-general
Hi All,

we are currently using streaming replication on multiple node pairs. We are seeing some issues, but I am mainly interrested in clarification.

When a failover occurs, we touch the trigger file, promoting the previous slave to master. That works perfectly.

For recycling the previous master, we create a recovery.conf (with recovery_target_timeline = 'latest') and *try* to start up. If postgresql starts up, we accept it as a new slave. If it does not, we proceed with a full basebackup.

This approach seems to work, but I have found indications that it can lead to database corruption: http://hlinnaka.iki.fi/presentations/NordicPGDay2015-pg_rewind.pdf

I am mainly seeking understanding of if and why this approach is a bad idea.

Thanks,
Fredrik Huitfeldt

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

Предыдущее
От: Sergey Konoplev
Дата:
Сообщение: Re: Increased I/O / Writes
Следующее
От: Niels Kristian Schjødt
Дата:
Сообщение: Lightest way of checking if postgresql is running at the other end of an ssh tunnel?