Re: IRe: BUG #16792: silent corruption of GIN index resulting in SELECTs returning non-matching rows - Mailing list pgsql-bugs

From Alexander Korotkov
Subject Re: IRe: BUG #16792: silent corruption of GIN index resulting in SELECTs returning non-matching rows
Date
Msg-id CAPpHfdtbgMKfxOMhrMBOs-bv=xppOb5uOyRkUtaqmgbEk6c8eA@mail.gmail.com
Whole thread Raw
In response to Re: IRe: BUG #16792: silent corruption of GIN index resulting in SELECTs returning non-matching rows  (Alexander Korotkov <aekorotkov@gmail.com>)
Responses Re: IRe: BUG #16792: silent corruption of GIN index resulting in SELECTs returning non-matching rows  (Pawel Kudzia <kudzia@gmail.com>)
Re: IRe: BUG #16792: silent corruption of GIN index resulting in SELECTs returning non-matching rows  (Peter Geoghegan <pg@bowt.ie>)
List pgsql-bugs
On Fri, Jun 25, 2021 at 11:48 PM Alexander Korotkov
<aekorotkov@gmail.com> wrote:
> Do you think it also worth checking whether bug persists when set
> fastupdate = off.  Then we could localize whether bug is related to
> pending lists.

I still think this is worth checking.  Despite the pending list wasn't
involved in the index scan with wrong results, the bug could be
related to insertion to the pending list.  Or it could be related to
moving entries from the pending list to the posting list/tree.

------
Regards,
Alexander Korotkov



pgsql-bugs by date:

Previous
From: Domingo Alvarez Duarte
Date:
Subject: Re: BUG #17109: Fail to evaluate boolean expression properly
Next
From: PG Bug reporting form
Date:
Subject: BUG #17110: [FEATURE REQUEST] Log all plans for a query instead of just showing the most optimal plan