Re: VM corruption on standby
От | Andrey Borodin |
---|---|
Тема | Re: VM corruption on standby |
Дата | |
Msg-id | 59380CEA-503D-40F9-A239-DD29D1E466CF@yandex-team.ru обсуждение исходный текст |
Ответ на | Re: VM corruption on standby (Aleksander Alekseev <aleksander@tigerdata.com>) |
Ответы |
Re: VM corruption on standby
|
Список | pgsql-hackers |
> On 7 Aug 2025, at 17:09, Aleksander Alekseev <aleksander@tigerdata.com> wrote: > > If my understanding is correct, we should make a WAL record with the > XLH_LOCK_ALL_FROZEN_CLEARED flag *before* we modify the VM but within > the same critical section (in order to avoid race conditions within > the same backend). Well, the test passes because you moved injection point to a very safe position. I can't comment anything on other aspectsof moving visibilitymap_clear() around. The approach seems viable to me, but I'd like to have understanding why PD_ALL_VISIBLE in a heap page header did not savethe day before fixing anything. Best regards, Andrey Borodin.
В списке pgsql-hackers по дате отправления: