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

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Ronan Dunklau <ronan(dot)dunklau(at)aiven(dot)io>
Cc: 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-03-01 09:12:43
Message-ID: ZeGcC5qMUXm791oc@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

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

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Alexey Ermakov 2024-03-01 09:50:35 Re: BUG #18349: ERROR: invalid DSA memory alloc request size 1811939328, CONTEXT: parallel worker
Previous Message Ronan Dunklau 2024-03-01 08:56:51 FSM Corruption (was: Could not read block at end of the relation)