Re: explain analyze output with parallel workers - question aboutmeaning of information for explain.depesz.com

Поиск
Список
Период
Сортировка
От Robert Haas
Тема Re: explain analyze output with parallel workers - question aboutmeaning of information for explain.depesz.com
Дата
Msg-id CA+TgmoYtMoOjygyGB-8f5qAacpup=iaHo8bXGmZ8NQQcVKnvNA@mail.gmail.com
обсуждение исходный текст
Ответ на Re: explain analyze output with parallel workers - question aboutmeaning of information for explain.depesz.com  (Amit Kapila <amit.kapila16@gmail.com>)
Ответы Re: explain analyze output with parallel workers - question aboutmeaning of information for explain.depesz.com  (Amit Kapila <amit.kapila16@gmail.com>)
Список pgsql-hackers
On Sat, Dec 2, 2017 at 8:04 AM, Amit Kapila <amit.kapila16@gmail.com> wrote:
> Attached patch contains regression test as well.  Note that I have
> carefully disabled all variable stats by using (analyze, timing off,
> summary off, costs off) and then selected parallel sequential scan on
> the right of join so that we have nloops and rows as variable stats
> and those should remain constant.

The regression test contains a whitespace error about which git diff
--check complains.

Also, looking at this again, shouldn't the reinitialization of the
instrumentation arrays happen in ExecParallelReinitialize rather than
ExecParallelFinish, so that we don't spend time doing it unless the
Gather is actually re-executed?

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


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

Предыдущее
От: Pantelis Theodosiou
Дата:
Сообщение: Re: [HACKERS] Secondary index access optimizations
Следующее
От: Robert Haas
Дата:
Сообщение: Re: [HACKERS] postgres_fdw super user checks