Re: Inconsistent DB data in Streaming Replication

Поиск
Список
Период
Сортировка
От Fujii Masao
Тема Re: Inconsistent DB data in Streaming Replication
Дата
Msg-id CAHGQGwF-k7tt9Fj9PNrGzZvBW8MHm41Fu6WSLhGJXSuUAbeLoA@mail.gmail.com
обсуждение исходный текст
Ответ на Re: Inconsistent DB data in Streaming Replication  (Hannu Krosing <hannu@2ndQuadrant.com>)
Ответы Re: Inconsistent DB data in Streaming Replication  (Hannu Krosing <hannu@2ndQuadrant.com>)
Re: Inconsistent DB data in Streaming Replication  (Andres Freund <andres@2ndquadrant.com>)
Список pgsql-hackers
On Thu, Apr 11, 2013 at 10:25 PM, Hannu Krosing <hannu@2ndquadrant.com> wrote:
>
> You just shut down the old master and let the standby catch
> up (takas a few microseconds ;) ) before you promote it.
>
> After this you can start up the former master with recovery.conf
> and it will follow nicely.

No. When you shut down the old master, it might not have been
able to send all the WAL records to the standby. I have observed
this situation several times. So in your approach, new standby
might fail to catch up with the master nicely.

Regards,

--
Fujii Masao



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

Предыдущее
От: Tom Lane
Дата:
Сообщение: Analyzing bug 8049
Следующее
От: Fujii Masao
Дата:
Сообщение: Re: Inconsistent DB data in Streaming Replication