On Thu, Jan 29, 2026 at 1:06 PM Andres Freund <[email protected]> wrote:
> Wonder if - independent of this
> issue - it could make sense to update the FSM during nbtree WAL recovery...

Maybe that would make sense. But I tend to think that we should have a
fully atomic, crash-safe approach to free space management.

Particularly in index AMs, where free space can only ever come in
BLCKSZ units -- the data structure/concurrency rules can be a lot
simpler if it only has to accommodate index AM requirements. Maybe the
WAL-logging could be built into existing index AM record types.

-- 
Peter Geoghegan


Reply via email to