Feedback-ID: ie3de48e3:Fastmail
Date: Tue, 3 Feb 2026 23:39:20 +0100
From: =?utf-8?Q?=C3=81lvaro?= Herrera <alvherre@kurilemu.de>
To: Matthias van de Meent <boekewurm@gmail.com>
Cc: Heikki Linnakangas <hlinnaka@iki.fi>, Peter Geoghegan <pg@bowt.ie>, 
	PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>, Michail Nikolaev <michail.nikolaev@gmail.com>
Subject: Re: [SP-]GiST IOS visibility bug (was: Why doens't GiST require
 super-exclusive lock)
Message-ID: <202602032236.3kvssyb3duyu@alvherre.pgsql>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <CAEze2WgH13m=MDST58KLo-NkZpbwBEt4xNWcgtghWBwRj3J0+A@mail.gmail.com>
Archived-At: <https://www.postgresql.org/message-id/202602032236.3kvssyb3duyu%40alvherre.pgsql>
Precedence: bulk

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/