Re: Parallel plans and "union all" subquery

Поиск
Список
Период
Сортировка
От Greg Nancarrow
Тема Re: Parallel plans and "union all" subquery
Дата
Msg-id CAJcOf-dAJL5o4c9aBpiR3c+gyK+AghPPZqvJayd=uWLi4K+YeQ@mail.gmail.com
обсуждение исходный текст
Ответ на Re: Parallel plans and "union all" subquery  (Luc Vlaming <luc@swarm64.com>)
Ответы Re: Parallel plans and "union all" subquery
Список pgsql-hackers
On Thu, Nov 26, 2020 at 6:11 PM Luc Vlaming <luc@swarm64.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



В списке pgsql-hackers по дате отправления:

Предыдущее
От: Bharath Rupireddy
Дата:
Сообщение: Re: Use standard SIGHUP and SIGTERM handlers in autoprewarm module
Следующее
От: Craig Ringer
Дата:
Сообщение: Re: POC: postgres_fdw insert batching