Postgres Pro
Downloads
Home   >   mailing lists

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

From Michael Paquier
Subject Re: FSM Corruption (was: Could not read block at end of the relation)
Date
Msg-id ZeGcC5qMUXm791oc@paquier.xyz
Whole thread Raw
In response to FSM Corruption (was: Could not read block at end of the relation)  (Ronan Dunklau <ronan.dunklau@aiven.io>)
List pgsql-bugs
Tree view 
On Fri, Mar 01, 2024 at 09:56:51AM +0100, Ronan Dunklau wrote:
> In our case, we need to repair the FSM. The instructions on the wiki do work,
> but maybe we should add something like the attached patch (modeled after the
> same feature in pg_visibility) to make it possible to repair the FSM
> corruption online. What do you think about it ?

I vaguely recall that something like that has been suggested around
917dc7d2393c in the past.

> The investigation of the corruption is still ongoing.

Thanks!
--
Michael
Attachment

pgsql-bugs by date:

Previous
From: Ronan Dunklau
Date:
Subject: FSM Corruption (was: Could not read block at end of the relation)
Next
From: Alexey Ermakov
Date:
Subject: Re: BUG #18349: ERROR: invalid DSA memory alloc request size 1811939328, CONTEXT: parallel worker