Re: Fix FSM range endpoint after relation extension

From: Jingtang Zhang <mrdrivingduck(at)gmail(dot)com>
To: pgsql-hackers(at)lists(dot)postgresql(dot)org, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Cc: 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-13 04:28:01
Message-ID: CAPsk3_DBqL0r87cz-DJZA5GJDWkFA7OPUXp4B71=ZbNhfG=Ggw@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi hackers,

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.

---
Regards,
Jingtang

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Kapila 2026-07-13 04:43:43 Re: sequencesync worker race with REFRESH SEQUENCES
Previous Message Michael Paquier 2026-07-13 04:08:28 Re: Fix comment typo in canonicalize_path_enc()