Re: print_path is missing GatherMerge and CustomScan support

Поиск
Список
Период
Сортировка
От Robert Haas
Тема Re: print_path is missing GatherMerge and CustomScan support
Дата
Msg-id CA+TgmoaDYiXj6mLZ0Cg3nN3yPgpjxQ+8sjanxRdKo1nTan9dXA@mail.gmail.com
обсуждение исходный текст
Ответ на Re: print_path is missing GatherMerge and CustomScan support  (Etsuro Fujita <fujita.etsuro@lab.ntt.co.jp>)
Ответы Re: print_path is missing GatherMerge and CustomScan support  (Etsuro Fujita <fujita.etsuro@lab.ntt.co.jp>)
Список pgsql-hackers
On Thu, Jul 26, 2018 at 1:14 AM, Etsuro Fujita
<fujita.etsuro@lab.ntt.co.jp> wrote:
> because we currently don't consider gathering partial child-scan or
> child-join paths.  I think we might consider that in future, though.

You generally want to put the Gather node as high up in the plan tree
as possible.  I think the only case in which this is beneficial is if
you can't put the Gather or Gather Merge node above the Append because
only some of the children are parallel-safe.  In that case, a separate
Gather per child can be better than no parallelism at all.  It's a
rare case, but it can happen. Actually, I thought we had code for this
already: see the end of apply_scanjoin_target_to_paths().

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company


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

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: 11beta crash/assert caused by parameter type changes
Следующее
От: Andres Freund
Дата:
Сообщение: Re: How can we submit code patches that implement our (pending)patents?