Re: BUG #15290: Stuck Parallel Index Scan query

From: Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com>
To: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
Cc: Andres Freund <andres(at)anarazel(dot)de>, Victor Yegorov <vyegorov(at)gmail(dot)com>, PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: BUG #15290: Stuck Parallel Index Scan query
Date: 2018-07-25 09:55:57
Message-ID: CAEepm=0wJF4OrQ-b=jVPzkc1iPFxBmLAkX5UCDr_D2Pdw1wZ3A@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Wed, Jul 25, 2018 at 5:46 PM, Amit Kapila <amit(dot)kapila16(at)gmail(dot)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

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Olav Gjerde 2018-07-25 10:44:16 Re: BUG #15294: Phantom read in serializable transaction when you rename schema.
Previous Message Michael Paquier 2018-07-25 05:48:57 Re: LLVM jit and matview