Re: [sqlsmith] Failed assertion in parallel worker in ExecInitSubPlan - Mailing list pgsql-hackers

From Amit Kapila
Subject Re: [sqlsmith] Failed assertion in parallel worker in ExecInitSubPlan
Date
Msg-id CAA4eK1KHO2bVkeiDuRmruwZs-VqNRmqRmiVcN6PRfW1HpgPrpg@mail.gmail.com
Whole thread Raw
In response to [sqlsmith] Failed assertion in parallel worker in ExecInitSubPlan  (Andreas Seltenreich <seltenreich@gmx.de>)
Responses Re: [sqlsmith] Failed assertion in parallel worker in ExecInitSubPlan
List pgsql-hackers
On Sun, Nov 20, 2016 at 10:43 PM, Andreas Seltenreich
<seltenreich@gmx.de> wrote:
> Hi,
>
> the query below triggers a parallel worker assertion for me when run on
> the regression database of master as of 0832f2d.  The plan sports a
> couple of InitPlan nodes below Gather.
>

I think the reason of this issue is that in some cases where subplan
is at some node other than top_plan node, we allow them to be executed
in the worker in force_parallel_mode.  It seems to me that the
problematic code is below check in standard_planner()

if (force_parallel_mode != FORCE_PARALLEL_OFF &&
best_path->parallel_safe &&
top_plan->initPlan == NIL)

Here instead of checking whether top_plan has initPlan, it should
check whether initPlan is present anywhere in plan tree.  I think one
simple way could be to check *glob->subplans* instead of
top_plan->initPlan, another possibility is to traverse the whole tree
to see if initPlan is present.

-- 
With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com



pgsql-hackers by date:

Previous
From: Etsuro Fujita
Date:
Subject: Re: Push down more full joins in postgres_fdw
Next
From: Amit Kapila
Date:
Subject: Re: Remove the comment on the countereffectiveness of large shared_buffers on Windows