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

Michail Nikolaev <michail.nikolaev@gmail.com>

From: Michail Nikolaev <michail.nikolaev@gmail.com>

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

Cc: Peter Geoghegan <pg@bowt.ie>, pgsql-hackers@lists.postgresql.org, hlinnaka@iki.fi, Tom Lane <tgl@sss.pgh.pa.us>, Andres Freund <andres@anarazel.de>, Tomas Vondra <tomas@vondra.me>

Date: 2025-02-08T13:46:00Z

Lists: pgsql-hackers

Attachments

v8-0002-Fix-index-only-scan-race-condition-in-GiST-implem.patch (application/octet-stream) patch v8-0002
v8-0003-Improve-buffer-handling-for-killed-items-in-GiST-.patch (application/octet-stream) patch v8-0003
v8-0004-Fix-index-only-scan-race-condition-in-SP-GiST-imp.patch (application/octet-stream) patch v8-0004
v8-0001-Tests-for-index-only-scan-race-condition-with-con.patch (application/octet-stream) patch v8-0001

Hello, everyone!

Just some commit messages + few cleanups.

Best regards,
Mikhail.

Commits

Standardize cleanup lock terminology.
- bcf60585e6e0 15.0 landed
Reduce pinning and buffer content locking for btree scans.
- 2ed5b87f96d4 9.5.0 cited