Re: Why doesn't GiST VACUUM require a super-exclusive lock, like nbtree VACUUM?

Matthias van de Meent <boekewurm+postgres@gmail.com>

From: Matthias van de Meent <boekewurm+postgres@gmail.com>

To: Heikki Linnakangas <hlinnaka@iki.fi>, Peter Geoghegan <pg@bowt.ie>

Cc: vignesh C <vignesh21@gmail.com>, Michail Nikolaev <michail.nikolaev@gmail.com>, pgsql-hackers@lists.postgresql.org, Tom Lane <tgl@sss.pgh.pa.us>, Andres Freund <andres@anarazel.de>, Tomas Vondra <tomas@vondra.me>

Date: 2025-12-24T11:54:48Z

Lists: pgsql-hackers

Attachments

v14-0007-nbtree-Reduce-Index-Only-Scan-pin-duration.patch (application/octet-stream)
v14-0008-Test-for-IOS-Vacuum-race-conditions-in-index-AMs.patch (application/octet-stream)
v14-0004-IOS-Support-tableAM-powered-prechecked-visibilit.patch (application/octet-stream)
v14-0005-GIST-Fix-visibility-issues-in-IOS.patch (application/octet-stream)
v14-0006-SP-GIST-Fix-visibility-issues-in-IOS.patch (application/octet-stream)
v14-0002-pg_visibility-vectorize-collect_visibility_data.patch (application/octet-stream)
v14-0001-Add-vectorized-API-for-visibility-map-lookup.patch (application/octet-stream)
v14-0003-TableAM-Support-AM-specific-fast-visibility-test.patch (application/octet-stream)

On Mon, 22 Dec 2025 at 23:23, Matthias van de Meent
<boekewurm+postgres@gmail.com> wrote:
>
> On Thu, 24 Apr 2025 at 22:46, Matthias van de Meent
> <boekewurm+postgres@gmail.com> wrote:
> >
> > On Fri, 21 Mar 2025 at 17:14, Matthias van de Meent
> > <boekewurm+postgres@gmail.com> wrote:
> > > Attached is v10, which polishes the previous patches, and adds a patch
> > > for nbtree to use the new visibility checking strategy so that it too
> > > can release its index pages much earlier, and adds a similar
> > > visibility check test to nbtree.
> >
> > And here's v12. v11 (skipped) would've been a rebase, but after
> > finishing the rebase I noticed a severe regression in btree's IOS with
> > the new code, so v12 here applies some optimizations which reduce the
> > overhead of the new code.
>
> Here's v13, which moves the changes around a bit:

CFBot reported failures, which appeared to be due to an oversight in
patch 0001, where visibilitymap_get_status was missing a static
modifier to accompany its inline nature.

Apart from that fix v14 is identical to v13.

Kind regards,

Matthias van de Meent