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

From Matthias van de Meent
Subject Re: [SP-]GiST IOS visibility bug (was: Why doens't GiST require super-exclusive lock)
Date
Msg-id CAEze2Wi1FhPC0zkR1pz+Bzzpy2b45PoJPET+RkJcXE8tT7dvkg@mail.gmail.com
Whole thread
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 Wed, 29 Jul 2026 at 19:02, Mihail Nikalayeu
<mihailnikalayeu@gmail.com> wrote:
>
> Hello!
>
> I am working on a stress-test framework and was trying to use it to
> reproduce this bug.
> It reproduced, but SP-GiST failed after the fix was applied.

> I haven't validated it carefully, sorry, but I think it will be helpful.

Yeah, that was me using the TID in the downlink-equivalent tuple,
rather than that of the leaf tuple, for the visibility check, and that
obviously will cause correctness issues.

Attached v3, which fixes that, and hopefully also fixes the
fallthrough compiler warning that cfbot has been reporting. Thanks for
the report!


Kind regards,

Matthias van de Meent
Databricks (https://www.databricks.com)

Attachment

pgsql-hackers by date:

Previous
From: Hannu Krosing
Date:
Subject: Re: WAL compression setting after PostgreSQL LZ4 default change
Next
From: Fujii Masao
Date:
Subject: Re: Checkpoint replication slots later