Re: FSM Corruption (was: Could not read block at end of the relation)

From: Noah Misch <noah(at)leadboat(dot)com>
To: Ronan Dunklau <ronan(dot)dunklau(at)aiven(dot)io>
Cc: Michael Paquier <michael(at)paquier(dot)xyz>, pgsql-bugs <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: FSM Corruption (was: Could not read block at end of the relation)
Date: 2024-04-11 15:38:43
Message-ID: 20240411153843.20@rfd.leadboat.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Thu, Apr 11, 2024 at 09:36:50AM +0200, Ronan Dunklau wrote:
> Le dimanche 7 avril 2024, 00:30:37 CEST Noah Misch a écrit :
> > Your v3 has the right functionality. As further confirmation of the fix, I
> > tried reverting the non-test parts of commit 917dc7d "Fix WAL-logging of FSM
> > and VM truncation". That commit's 008_fsm_truncation.pl fails with 917dc7d
> > reverted from master, and adding this patch makes it pass again. I ran
> > pgindent and edited comments. I think the attached version is ready to go.
>
> Thank you Noah, the updated comments are much better. I think it should be
> backported at least to 16 since the chances of tripping on that behaviour are
> quite high here, but what about previous versions ?

It should be reachable in all branches, just needing concurrent extension lock
waiters to reach before v16. Hence, my plan is to back-patch it all the way.
It applies with negligible conflicts back to v12.

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Peter Geoghegan 2024-04-11 16:01:09 Re: FSM Corruption (was: Could not read block at end of the relation)
Previous Message Tom Lane 2024-04-11 14:13:15 Re: BUG #18422: Assert in expandTupleDesc() fails on row mismatch with additional SRF