| From: | Peter Geoghegan <pg(at)bowt(dot)ie> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Alexander Lakhin <exclusion(at)gmail(dot)com>, Chao Li <li(dot)evan(dot)chao(at)gmail(dot)com>, Kirill Reshke <reshkekirill(at)gmail(dot)com>, Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, Melanie Plageman <melanieplageman(at)gmail(dot)com>, Matthias van de Meent <boekewurm+postgres(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org, Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, Noah Misch <noah(at)leadboat(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
| Subject: | Re: Buffer locking is special (hints, checksums, AIO writes) |
| Date: | 2026-01-29 18:33:02 |
| Message-ID: | CAH2-WznD08wju6qY5qnwcqS-k=vqMBs9QeUqtauTKs7TnECavQ@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Jan 29, 2026 at 1:06 PM Andres Freund <andres(at)anarazel(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2026-01-29 18:45:21 | more surprising enable_indexonlyscan behavior |
| Previous Message | Peter Geoghegan | 2026-01-29 18:12:35 | Re: Buffer locking is special (hints, checksums, AIO writes) |