Re: BUG #15290: Stuck Parallel Index Scan query - Mailing list pgsql-bugs

From Thomas Munro
Subject Re: BUG #15290: Stuck Parallel Index Scan query
Date
Msg-id CAEepm=0wJF4OrQ-b=jVPzkc1iPFxBmLAkX5UCDr_D2Pdw1wZ3A@mail.gmail.com
Whole thread Raw
In response to Re: BUG #15290: Stuck Parallel Index Scan query  (Amit Kapila <amit.kapila16@gmail.com>)
List pgsql-bugs
On Wed, Jul 25, 2018 at 5:46 PM, Amit Kapila <amit.kapila16@gmail.com> wrote:
>> I think here we can release the current page lock
>> before calling _bt_parallel_seize as we don't need it to get the next
>> page.
>
> I have written a patch on the above lines and manually verified (by
> reproducing the issue via debugger) that it fixes the issue.  Thomas,
> Victor, is it possible for you guys to see if the attached fixes the
> issue for you?

The patch looks good to me.  It fixes the problem for my reproducer
(BTW that works better with an extra zero on the generate_series
number).

-- 
Thomas Munro
http://www.enterprisedb.com


pgsql-bugs by date:

Previous
From: Amit Kapila
Date:
Subject: Re: BUG #15290: Stuck Parallel Index Scan query
Next
From: Olav Gjerde
Date:
Subject: Re: BUG #15294: Phantom read in serializable transaction when yourename schema.