pg.ddx.io  pgsql-committers@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Melanie Plageman <melanieplageman@gmail.com>
To: pgsql-committers@lists.postgresql.org
Subject: pgsql: Detect and fix visibility map corruption in more cases
Date: Sun, 22 Mar 2026 15:55:45 +0000
Message-ID: <E1w4L9U-000xFD-0p@gemulon.postgresql.org> (raw)

Detect and fix visibility map corruption in more cases

Move VM corruption detection and repair into heap page pruning. This
allows VM repair during on-access pruning, not only during vacuum.

Also, expand corruption detection to cover pages marked all-visible that
contain dead tuples and tuples inserted or deleted by in-progress
transactions, rather than only all-visible pages with LP_DEAD items.

Pinning the correct VM page before on-access pruning is cheap when
compared to the cost of actually pruning. The vmbuffer is saved in the
scan descriptor, so a query should only need to pin each VM page once,
and a single VM page covers a large number of heap pages.

Author: Melanie Plageman <melanieplageman@gmail.com>
Reviewed-by: Andres Freund <andres@anarazel.de>
Reviewed-by: Chao Li <li.evan.chao@gmail.com>
Reviewed-by: Kirill Reshke <reshkekirill@gmail.com>
Discussion: https://postgr.es/m/bqc4kh5midfn44gnjiqez3bjqv4zogydguvdn446riw45jcf3y%404ez66il7ebvk

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/4f7ecca84ddacbce27bdff3b78981a2bd9c9b242

Modified Files
--------------
src/backend/access/heap/pruneheap.c  | 221 ++++++++++++++++++++++++++++++++---
src/backend/access/heap/vacuumlazy.c |  89 +-------------
src/include/access/heapam.h          |  12 ++
src/tools/pgindent/typedefs.list     |   1 +
4 files changed, 221 insertions(+), 102 deletions(-)



Message-ID: <E1w4L9U-000xFD-0p@gemulon.postgresql.org>
Permalink:  ../E1w4L9U-000xFD-0p@gemulon.postgresql.org/
Also on:    postgresql.org/message-id/E1w4L9U-000xFD-0p@gemulon.postgresql.org

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-committers@postgresql.org
  Cc: melanieplageman@gmail.com, pgsql-committers@lists.postgresql.org
  Subject: Re: pgsql: Detect and fix visibility map corruption in more cases
  In-Reply-To: <E1w4L9U-000xFD-0p@gemulon.postgresql.org>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox