Re: PATCH: standby crashed when replay block which truncated instandby but failed to truncate in master node

Поиск
Список
Период
Сортировка
От Michael Paquier
Тема Re: PATCH: standby crashed when replay block which truncated instandby but failed to truncate in master node
Дата
Msg-id 20190925032403.GF1815@paquier.xyz
обсуждение исходный текст
Ответ на Re: PATCH: standby crashed when replay block which truncated instandby but failed to truncate in master node  (Kyotaro Horiguchi <horikyota.ntt@gmail.com>)
Ответы Re: PATCH: standby crashed when replay block which truncated instandby but failed to truncate in master node  (Kyotaro Horiguchi <horikyota.ntt@gmail.com>)
Список pgsql-hackers
On Tue, Sep 24, 2019 at 02:48:16PM +0900, Kyotaro Horiguchi wrote:
> Of course I found no *explicit* ones. But I found one
> ereport(DEBUG1 in register_dirty_segment. So it will work at
> least for the case where fsync request queue is full.

Exactly.  I have not checked the patch in details, but I think that
we should not rely on the assumption that no code paths in this area do
not check after CHECK_FOR_INTERRUPTS() as smgrtruncate() does much
more than just the physical segment truncation.
--
Michael

Вложения

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

Предыдущее
От: Michael Paquier
Дата:
Сообщение: Re: [PATCH] src/test/modules/dummy_index -- way to test reloptionsfrom inside of access method
Следующее
От: Amit Kapila
Дата:
Сообщение: Re: range test for hash index?