Re: VM corruption on standby

Tom Lane <tgl@sss.pgh.pa.us>

From: Tom Lane <tgl@sss.pgh.pa.us>

To: Alexander Korotkov <aekorotkov@gmail.com>

Cc: Kirill Reshke <reshkekirill@gmail.com>, Thomas Munro <thomas.munro@gmail.com>, Andrey Borodin <x4mmm@yandex-team.ru>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>, Melanie Plageman <melanieplageman@gmail.com>, Michael Paquier <michael@paquier.xyz>

Date: 2025-08-21T22:42:48Z

Lists: pgsql-hackers

Alexander Korotkov <aekorotkov@gmail.com> writes:
> On Tue, Aug 19, 2025 at 10:50 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> Therefore, I vote for reverting bc22dc0e0.  Hopefully only
>> temporarily, but it's too late to figure out another way for v18,
>> and I don't think that bc22dc0e0 is such an essential improvement
>> that we can't afford to give it up for v18.

> I'm OK about this.  Do you mind if I revert bc22dc0e0 myself?

Not at all, go for it.

> And let's retry it for v19.

+1

			regards, tom lane

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

Revert "Get rid of WALBufMappingLock"
- 2ce6abdf5085 18.0 landed
- c13070a27b63 19 (unreleased) landed
Get rid of WALBufMappingLock
- bc22dc0e0ddc 18.0 cited
Split WaitEventSet functions to separate source file
- 393e0d231405 18.0 cited
Add WL_EXIT_ON_PM_DEATH pseudo-event.
- cfdf4dc4fc96 12.0 cited