Re: [SP-]GiST IOS visibility bug (was: Why doens't GiST require super-exclusive lock) - Mailing list pgsql-hackers

From Álvaro Herrera
Subject Re: [SP-]GiST IOS visibility bug (was: Why doens't GiST require super-exclusive lock)
Date
Msg-id 202602032236.3kvssyb3duyu@alvherre.pgsql
Whole thread Raw
In response to [SP-]GiST IOS visibility bug (was: Why doens't GiST require super-exclusive lock)  (Matthias van de Meent <boekewurm@gmail.com>)
List pgsql-hackers
On 2025-Apr-25, Matthias van de Meent wrote:

> Hi,
> 
> In the original thread [0] we established that GIST and SP-GiST
> support index-only scans, but don't have sufficient interlocking to
> prevent dead tuples from being revived for their scan by vacuum.

Hello,

This commitfest entry
https://commitfest.postgresql.org/patch/5721/
is stale.  I would have brought it forward because it's tagged as a bug
fix, but the patches look a bit intimidating to consider it a
backpatchable bug fix.  So, what's the status here?

Thanks

-- 
Álvaro Herrera        Breisgau, Deutschland  —  https://www.EnterpriseDB.com/



pgsql-hackers by date:

Previous
From: Álvaro Herrera
Date:
Subject: Re: Orphaned users in PG16 and above can only be managed by Superusers
Next
From: Tom Lane
Date:
Subject: Re: PostgreSQL 19 on AIX?