Re: BUG #18129: GiST index produces incorrect query results

From: Heikki Linnakangas <hlinnaka(at)iki(dot)fi>
To: exclusion(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #18129: GiST index produces incorrect query results
Date: 2023-09-22 13:43:06
Message-ID: a278e3e4-f9e4-c2ce-1a2f-abb646fdcaa4@iki.fi
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

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)

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2023-09-22 17:48:59 Re: BUG #18080: to_tsvector fails for long text input
Previous Message Aleš Zelený 2023-09-22 12:56:57 Re: Invalid dump file after drop of role that previously created extension containing a table.