Re: Inconsistent DB data in Streaming Replication

Поиск
Список
Период
Сортировка
От Fujii Masao
Тема Re: Inconsistent DB data in Streaming Replication
Дата
Msg-id CAHGQGwH0f4Ww7GgH3NBRMUgrDqCGvgBqdq2ct6KYrfMOLEmNaA@mail.gmail.com
обсуждение исходный текст
Ответ на Re: Inconsistent DB data in Streaming Replication  (Shaun Thomas <sthomas@optionshouse.com>)
Ответы Re: Inconsistent DB data in Streaming Replication  (Shaun Thomas <sthomas@optionshouse.com>)
Список pgsql-hackers
On Wed, Apr 10, 2013 at 11:26 PM, Shaun Thomas <sthomas@optionshouse.com> wrote:
> On 04/10/2013 09:10 AM, Tom Lane wrote:
>
>> IOW, I wouldn't consider skipping the rsync even if I had a feature
>> like this.
>
>
> Totally. Out in the field, we consider the "old" database corrupt the moment
> we fail over.

Strange. If this is really true, shared disk failover solution is
fundamentally broken
because the standby needs to start up with the shared "corrupted"
database at the
failover. Also, we cannot trust the crash recovery at all if we adopt
the same logic
as you think. I think that there are the cases where we can replay and reuse the
old database even after PostgreSQL crashes.

Regards,

--
Fujii Masao



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

Предыдущее
От: Alvaro Herrera
Дата:
Сообщение: Re: Behaviour of bgworker with SIGHUP
Следующее
От: Shaun Thomas
Дата:
Сообщение: Re: Inconsistent DB data in Streaming Replication