Re: Fix for parallel BTree initialization bug

From: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
To: "Jameson, Hunter 'James'" <hunjmes(at)amazon(dot)com>
Cc: "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Fix for parallel BTree initialization bug
Date: 2020-09-09 13:14:08
Message-ID: CAA4eK1LNht44gB+7Ww07w8KLMOdw2dBrRvvgG=BtG8unnDw=jw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Sep 8, 2020 at 11:55 PM Jameson, Hunter 'James'
<hunjmes(at)amazon(dot)com> wrote:
>
> Hi, I ran across a small (but annoying) bug in initializing parallel BTree scans, which causes the parallel-scan state machine to get confused.
>
>
> To reproduce, you need a query that:
>
>
>
> 1. Executes parallel BTree index scan;
>
> 2. Has an IN-list of size > 1;
>
> 3. Has an additional index filter that makes it impossible to satisfy the
>
> first IN-list condition.
>
>
>
> (We encountered such a query, and therefore the bug, on a production instance.)
>
>

I think I can understand what you are pointing out here but it would
be great if you can have a reproducible test case because that will
make it apparent and we might want to include that in the regression
tests if possible.

--
With Regards,
Amit Kapila.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message osumi.takamichi@fujitsu.com 2020-09-09 13:28:12 RE: extension patch of CREATE OR REPLACE TRIGGER
Previous Message Alexey Kondratov 2020-09-09 13:03:45 Re: Allow CLUSTER, VACUUM FULL and REINDEX to change tablespace on the fly