Request a Demo
Home   >   mailing lists

Re: Buffer locking is special (hints, checksums, AIO writes) - Mailing list pgsql-hackers

From Peter Geoghegan
Subject Re: Buffer locking is special (hints, checksums, AIO writes)
Date
Msg-id CAH2-WznD08wju6qY5qnwcqS-k=vqMBs9QeUqtauTKs7TnECavQ@mail.gmail.com
Whole thread Raw
In response to Re: Buffer locking is special (hints, checksums, AIO writes)  (Andres Freund <andres@anarazel.de>)
Responses Re: Buffer locking is special (hints, checksums, AIO writes)
List pgsql-hackers
Tree view 
On Thu, Jan 29, 2026 at 1:06 PM Andres Freund <andres@anarazel.de> 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

pgsql-hackers by date:

Previous
From: Peter Geoghegan
Date:
Subject: Re: Buffer locking is special (hints, checksums, AIO writes)
Next
From: Robert Haas
Date:
Subject: more surprising enable_indexonlyscan behavior