Re: Parallel plans and "union all" subquery

From: Greg Nancarrow <gregn4422(at)gmail(dot)com>
To: Luc Vlaming <luc(at)swarm64(dot)com>
Cc: Phil Florent <philflorent(at)hotmail(dot)com>, "pgsql-hackers(at)lists(dot)postgresql(dot)org" <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Parallel plans and "union all" subquery
Date: 2020-11-27 03:14:48
Message-ID: CAJcOf-dAJL5o4c9aBpiR3c+gyK+AghPPZqvJayd=uWLi4K+YeQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Nov 26, 2020 at 6:11 PM Luc Vlaming <luc(at)swarm64(dot)com> wrote:
>
> If interesting I can make a draft of what this would look like if this
> makes it easier to discuss?
>

Sure, that would help clarify it.

I did debug this a bit, but it seems my gut feeling was wrong, even
though it knows a type coercion is required and can be done, the
parse/analyze code doesn't actually modify the nodes in place "for
fear of changing the semantics", so when the types don't exactly match
it's all left up to the planner, but for this parse tree it fails to
produce a parallel plan.

Regards,
Greg Nancarrow
Fujitsu Australia

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Craig Ringer 2020-11-27 03:56:15 Re: POC: postgres_fdw insert batching
Previous Message Bharath Rupireddy 2020-11-27 03:13:34 Re: Use standard SIGHUP and SIGTERM handlers in autoprewarm module