Re: VM corruption on standby

From: Aleksander Alekseev <aleksander(at)tigerdata(dot)com>
To: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Cc: Andrey Borodin <x4mmm(at)yandex-team(dot)ru>, Melanie Plageman <melanieplageman(at)gmail(dot)com>
Subject: Re: VM corruption on standby
Date: 2025-08-07 14:14:00
Message-ID: CAJ7c6TNfsDjCvQdX7ey4YfB8=WkvTAB4TD7dE2S1WLekJQh3kA@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> > This is a tricky bug. Do you also have a proposal of a particular fix?
>
> 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).

I meant instance, not backend. Sorry for confusion.

> A draft patch is attached. It makes the test pass and doesn't seem to
> break any other tests.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2025-08-07 14:15:19 Re: headerscheck warnings with late-model gcc
Previous Message Aleksander Alekseev 2025-08-07 14:09:39 Re: VM corruption on standby