Re: VM corruption on standby

From: Kirill Reshke <reshkekirill(at)gmail(dot)com>
To: Aleksander Alekseev <aleksander(at)tigerdata(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Andrey Borodin <x4mmm(at)yandex-team(dot)ru>, Melanie Plageman <melanieplageman(at)gmail(dot)com>
Subject: Re: VM corruption on standby
Date: 2025-08-09 19:54:58
Message-ID: CALdSSPgTw+HMStedmQowp1xW_Mmb_w4qhTTj4PaqRG1Ec1=f5g@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, 7 Aug 2025 at 21:36, Aleksander Alekseev
<aleksander(at)tigerdata(dot)com> wrote:

> Perhaps there was a good
> reason to update the VM *before* creating WAL records I'm unaware of.

Looks like 503c730 intentionally does it this way; however, I have not
yet fully understood the reasoning behind it.

--
Best regards,
Kirill Reshke

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Aleksander Alekseev 2025-08-09 20:54:42 Re: VM corruption on standby
Previous Message Andrew Dunstan 2025-08-09 18:54:11 Re: Making type Datum be 8 bytes everywhere