| From: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
|---|---|
| To: | Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Robert Haas <robertmhaas(at)gmail(dot)com> |
| Subject: | Re: crashes due to setting max_parallel_workers=0 |
| Date: | 2017-03-25 04:56:54 |
| Message-ID: | CAA4eK1JGt79+6E0p1m2BcjeDQ3aeNnSCCk_GfewDKcL-AGFfow@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sat, Mar 25, 2017 at 7:40 AM, Tomas Vondra
<tomas(dot)vondra(at)2ndquadrant(dot)com> wrote:
> Hi,
>
> while working on a patch I ran into some crashes that seem to be caused by
> inconsistent handling of max_parallel_workers - queries still seem to be
> planned with parallel plans enabled, but then crash at execution.
>
> The attached script reproduces the issue on a simple query, causing crashed
> in GatherMerge, but I assume the issue is more general.
>
I could see other parallel plans like Gather also picked at
max_parallel_workers=0. I suspect multiple issues here and this needs
some investigation. I have added this to open items list.
--
With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Kapila | 2017-03-25 05:04:17 | Re: Problem in Parallel Bitmap Heap Scan? |
| Previous Message | Peter Eisentraut | 2017-03-25 04:52:17 | Re: Logical replication existing data copy |