Re: Fix FSM range endpoint after relation extension

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Jingtang Zhang <mrdrivingduck(at)gmail(dot)com>
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Andres Freund <andres(at)anarazel(dot)de>, Melanie Plageman <melanieplageman(at)gmail(dot)com>
Subject: Re: Fix FSM range endpoint after relation extension
Date: 2026-07-15 01:10:58
Message-ID: albeIeDL1jglr4qc@paquier.xyz
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Jul 13, 2026 at 12:28:01PM +0800, Jingtang Zhang wrote:
> Just following up on this thread, since there hasn't been any feedback yet.
>
> The patches are unchanged since the original posting. The fix is a
> one-line correction to pass last_block + 1 as the exclusive endpoint
> to FreeSpaceMapVacuumRange(), and the second patch includes a focused
> test crossing an FSM leaf-page boundary.
>
> If the diagnosis and fix look reasonable, I would greatly appreciate
> a review.

Adding the related committers in CC is a good first step. Please also
make sure that this patch is registered in the commit fest, so as we
don't forget about it (aka there is a lot of traffic on this list, and
everybody is busy with their own things, so it may take time before
somebody is able to look back at what you have):
https://commitfest.postgresql.org/60/

Thanks,
--
Michael

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Hayato Kuroda (Fujitsu) 2026-07-15 01:31:43 RE: sequencesync worker race with REFRESH SEQUENCES
Previous Message Michael Paquier 2026-07-15 01:07:23 Re: equalPolicy() doesn't compare the permissive flag