Amit Kapila writes:
> On Fri, Nov 25, 2016 at 10:33 AM, Tom Lane wrote:
>> The impression I got in poking at this for a few minutes, before
>> going off to stuff myself with turkey, was that we were allowing
>> a SubqueryScanPath to mark itself as parallel-safe even though the
>> resulting plan n
On Fri, Nov 25, 2016 at 10:33 AM, Tom Lane wrote:
> Amit Kapila writes:
>> On Fri, Nov 25, 2016 at 3:26 AM, Andreas Seltenreich
>> wrote:
>>> just caught another InitPlan below Gather with the recent patches in
>>> (master as of 4cc6a3f). Recipe below.
>
>> I think this problem exists since co
Amit Kapila writes:
> On Fri, Nov 25, 2016 at 3:26 AM, Andreas Seltenreich
> wrote:
>> just caught another InitPlan below Gather with the recent patches in
>> (master as of 4cc6a3f). Recipe below.
> I think this problem exists since commit
> 110a6dbdebebac9401b43a8fc223e6ec43cd4d10 where we ha
On Fri, Nov 25, 2016 at 3:26 AM, Andreas Seltenreich wrote:
> Hi,
>
> just caught another InitPlan below Gather with the recent patches in
> (master as of 4cc6a3f). Recipe below.
>
I think this problem exists since commit
110a6dbdebebac9401b43a8fc223e6ec43cd4d10 where we have allowed
subqueries
Hi,
just caught another InitPlan below Gather with the recent patches in
(master as of 4cc6a3f). Recipe below.
regards,
andreas
set max_parallel_workers_per_gather = 2;
set min_parallel_relation_size = 0;
set parallel_setup_cost = 0;
set parallel_tuple_cost = 0;
explain select 1 from
public
On Mon, Nov 21, 2016 at 9:30 PM, Tom Lane wrote:
> Amit Kapila writes:
>> On Mon, Nov 21, 2016 at 6:10 PM, Amit Kapila wrote:
>>> 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
Amit Kapila writes:
> On Mon, Nov 21, 2016 at 6:10 PM, Amit Kapila wrote:
>> 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
On Mon, Nov 21, 2016 at 6:10 PM, Amit Kapila wrote:
> On Sun, Nov 20, 2016 at 10:43 PM, Andreas Seltenreich
> 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 no
On Sun, Nov 20, 2016 at 10:43 PM, Andreas Seltenreich
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
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.
regards,
Andreas
Gather (cost=1.64..84.29 rows=128 width=4)
Workers Planned: 1
Single Copy: true
-> L
10 matches
Mail list logo
