From: Heikki Linnakangas <hlinnaka@iki.fi>
To: exclusion@gmail.com
To: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18129: GiST index produces incorrect query results
Date: Fri, 22 Sep 2023 16:43:06 +0300
Message-ID: <a278e3e4-f9e4-c2ce-1a2f-abb646fdcaa4@iki.fi> (raw)
In-Reply-To: <18129-caca016eaf0c3702@postgresql.org>
References: <18129-caca016eaf0c3702@postgresql.org>
On 22/09/2023 09:00, PG Bug reporting form wrote:
> First bad commit is 9155580fd, on which three different outcomes are
> possible: test passes/test fails/assertion fails.
> Assertion failures, that we had observed after 9155580fd, were fixed by
> a7ee7c851 and 741b88435, but apparently there is another defect induced
> by that gist implementation change.
I can reproduce this. I suspect something's still wrong with the LSN <->
NSN cross check, when the pages are WAL logged in physical order. Thanks
for the report, I'll take a look.
--
Heikki Linnakangas
Neon (https://neon.tech)
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: pgsql-bugs@postgresql.org
Cc: hlinnaka@iki.fi, exclusion@gmail.com, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18129: GiST index produces incorrect query results
In-Reply-To: <a278e3e4-f9e4-c2ce-1a2f-abb646fdcaa4@iki.fi>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox