Re: VM corruption on standby

From: Andrey Borodin <x4mmm(at)yandex-team(dot)ru>
To: Aleksander Alekseev <aleksander(at)tigerdata(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Melanie Plageman <melanieplageman(at)gmail(dot)com>
Subject: Re: VM corruption on standby
Date: 2025-08-10 06:56:28
Message-ID: 3FFBA27E-B096-4C57-9959-E93DB4EEA868@yandex-team.ru
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> On 9 Aug 2025, at 23:54, Aleksander Alekseev <aleksander(at)tigerdata(dot)com> wrote:
>
> IMHO: logging the changes first, then allowing to evict the page.

VM and BufferManager code does not allow flush of a buffer until changes are logged.
The problem is that our crash-exiting system destroys locks that protect buffer from being flushed.

Best regards, Andrey Borodin.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Alexander Lakhin 2025-08-10 07:00:00 Re: Test instability when pg_dump orders by OID
Previous Message Kirill Reshke 2025-08-10 05:45:15 Re: VM corruption on standby