| From: | Melanie Plageman <melanieplageman(at)gmail(dot)com> |
|---|---|
| To: | pgsql-committers(at)lists(dot)postgresql(dot)org |
| Subject: | pgsql: Make on-access pruning pin visibility map before locking heap pa |
| Date: | 2026-09-12 00:39:56 |
| Message-ID: | E1x5Bmd-00000004VRD-1Adc@gemulon.postgresql.org |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers |
Make on-access pruning pin visibility map before locking heap page
b46e1e54d078 pinned the VM after acquiring a cleanup lock on the heap
page when on-access pruning. This was not correct, as pinning the VM may
require I/O. Pin the VM before acquiring the lock. This could mean
occasional unneeded pinning when the buffer is under contention, but
that should be rare.
Reported-by: Melanie Plageman <melanieplageman(at)gmail(dot)com>
Reviewed-by: Chao Li <li(dot)evan(dot)chao(at)gmail(dot)com>
Discussion: https://postgr.es/m/CAAKRu_aR6e2mNVo-DNHDUfBE5i0cbE4%3Du%3D_Qi9%2Bv573qiGtBig%40mail.gmail.com
Backpatch-through: 19
Branch
------
master
Details
-------
https://git.postgresql.org/pg/commitdiff/512d3e8919b649d36a6f246c657c8b8df7536e8a
Modified Files
--------------
src/backend/access/heap/pruneheap.c | 11 ++++++++---
1 file changed, 8 insertions(+), 3 deletions(-)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Melanie Plageman | 2026-09-12 00:42:38 | pgsql: Make on-access pruning pin visibility map before locking heap pa |
| Previous Message | Michael Paquier | 2026-09-12 00:04:38 | pgsql: doc: Fix output column name for pg_stat_get_backend_subxact() |