public inbox for [email protected]
help / color / mirror / Atom feedFrom: Álvaro Herrera <[email protected]>
To: Matthias van de Meent <[email protected]>
Cc: Heikki Linnakangas <[email protected]>
Cc: Peter Geoghegan <[email protected]>
Cc: PostgreSQL Hackers <[email protected]>
Cc: Michail Nikolaev <[email protected]>
Subject: Re: [SP-]GiST IOS visibility bug (was: Why doens't GiST require super-exclusive lock)
Date: Tue, 3 Feb 2026 23:39:20 +0100
Message-ID: <[email protected]> (raw)
In-Reply-To: <CAEze2WgH13m=MDST58KLo-NkZpbwBEt4xNWcgtghWBwRj3J0+A@mail.gmail.com>
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/
view thread (3+ messages) latest in thread
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: [email protected]
Cc: [email protected], [email protected], [email protected], [email protected], [email protected], [email protected]
Subject: Re: [SP-]GiST IOS visibility bug (was: Why doens't GiST require super-exclusive lock)
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox