Re: FSM Corruption (was: Could not read block at end of the relation) - Mailing list pgsql-bugs

From Noah Misch
Subject Re: FSM Corruption (was: Could not read block at end of the relation)
Date
Msg-id 20240411153843.20@rfd.leadboat.com
Whole thread Raw
In response to Re: FSM Corruption (was: Could not read block at end of the relation)  (Ronan Dunklau <ronan.dunklau@aiven.io>)
Responses Re: FSM Corruption (was: Could not read block at end of the relation)
List 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.



pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: BUG #18422: Assert in expandTupleDesc() fails on row mismatch with additional SRF
Next
From: Peter Geoghegan
Date:
Subject: Re: FSM Corruption (was: Could not read block at end of the relation)