| From: | Victor Yegorov <vyegorov(at)gmail(dot)com> |
|---|---|
| To: | amit(dot)kapila16(at)gmail(dot)com |
| Cc: | thomas(dot)munro(at)enterprisedb(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #15290: Stuck Parallel Index Scan query |
| Date: | 2018-07-26 10:23:01 |
| Message-ID: | CAGnEbohuAs-vGjaKwm3F8mN9GCN6YaFJR=Nm4MB0UFEuE4gm4A@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
ср, 25 июл. 2018 г. в 8:46, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>:
> On Wed, Jul 25, 2018 at 8:43 AM, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
> wrote:
> > Well spotted. 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?
>
First, I failed to reproduce Thomas' case on the VM with just 1 core.
But it is reproduced just fine on an 8-core machine, make sure to warm up
the index first though.
Patch fixes the issue for me here.
--
Victor Yegorov
| From | Date | Subject | |
|---|---|---|---|
| Next Message | PG Bug reporting form | 2018-07-26 10:26:31 | BUG #15296: Not able to get query result "information_schema.constraint_column_usage" |
| Previous Message | Ze Victor Harry | 2018-07-26 10:17:39 | Fwd: mvn package not installing/error |