Re: BUG #16792: silent corruption of GIN index resulting in SELECTs returning non-matching rows

From: Alexander Korotkov <aekorotkov(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, Pawel Kudzia <kudzia(at)gmail(dot)com>, PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: BUG #16792: silent corruption of GIN index resulting in SELECTs returning non-matching rows
Date: 2021-06-22 16:02:34
Message-ID: CAPpHfdsmWD_8Qn5CCNj4OPc4K4WubJCtnK3mN_dpYogEvZ60oA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Fri, Jun 18, 2021 at 12:55 AM Alexander Korotkov
<aekorotkov(at)gmail(dot)com> wrote:
> On Thu, Jun 17, 2021 at 10:49 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> > Anyway, I'm punting this to the code authors. I'd like to see
> > some comments clarifying what the API really is, not just a
> > quick-n-dirty code fix.
>
> Yep, I'm going to have a closer look at this tomorrow.

Sorry for the delay. I'm going to take a closer look in the next
couple of days.

------
Regards,
Alexander Korotkov

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Alexander Lakhin 2021-06-22 17:00:04 Re: BUG #17064: Parallel VACUUM operations cause the error "global/pg_filenode.map contains incorrect checksum"
Previous Message Alexander Korotkov 2021-06-22 16:01:36 Re: BUG #17066: Cache lookup failed when null (unknown) is passed as anycompatiblemultirange