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

From: solai v <solai(dot)cdac(at)gmail(dot)com>
To: Mihail Nikalayeu <mihailnikalayeu(at)gmail(dot)com>
Cc: Matthias van de Meent <boekewurm+postgres(at)gmail(dot)com>, Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, Peter Geoghegan <pg(at)bowt(dot)ie>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Álvaro Herrera <alvherre(at)kurilemu(dot)de>
Subject: Re: [SP-]GiST IOS visibility bug (was: Why doens't GiST require super-exclusive lock)
Date: 2026-08-04 03:50:59
Message-ID: CAF0whucM8F2X=+dqZ+R2FiXODQ6rdkRh0uQwKADZa5-BGQFg1g@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi Mikhail,
I tested the attached follow-up patch (nocfbot_spgistvischeckwrongtid.patch).
The patch applied cleanly on top of the v02 patch series. PostgreSQL
built successfully, and all regression tests passed .
I also verified that SP-GiST Index Only Scan continued to work
correctly after applying the patch and did not observe any build or
functional regressions during my testing.
I was not able to verify the reported stress-test failure because no
reproducer or stress-test framework was provided.

Regards,
Solai

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message solai v 2026-08-04 03:53:11 Re: XMLSerialize: version and explicit XML declaration
Previous Message Fujii Masao 2026-08-04 03:47:15 Re: data_checksums + debug_discard_caches = crash