| From: | Alexander Korotkov <aekorotkov(at)gmail(dot)com> |
|---|---|
| To: | Heikki Linnakangas <hlinnaka(at)iki(dot)fi> |
| Cc: | Pawel Kudzia <kudzia(at)gmail(dot)com>, PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Subject: | Re: IRe: BUG #16792: silent corruption of GIN index resulting in SELECTs returning non-matching rows |
| Date: | 2021-07-15 10:56:13 |
| Message-ID: | CAPpHfdtbgMKfxOMhrMBOs-bv=xppOb5uOyRkUtaqmgbEk6c8eA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Fri, Jun 25, 2021 at 11:48 PM Alexander Korotkov
<aekorotkov(at)gmail(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | PG Bug reporting form | 2021-07-15 11:58:12 | BUG #17110: [FEATURE REQUEST] Log all plans for a query instead of just showing the most optimal plan |
| Previous Message | Domingo Alvarez Duarte | 2021-07-15 10:48:28 | Re: BUG #17109: Fail to evaluate boolean expression properly |