Re: Runtime pruning problem

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: Runtime pruning problem
Дата
Msg-id 2018.1555473241@sss.pgh.pa.us
обсуждение исходный текст
Ответ на Re: Runtime pruning problem  (Amit Langote <Langote_Amit_f8@lab.ntt.co.jp>)
Ответы Re: Runtime pruning problem  (David Rowley <david.rowley@2ndquadrant.com>)
Список pgsql-hackers
Amit Langote <Langote_Amit_f8@lab.ntt.co.jp> writes:
> On 2019/04/17 11:29, David Rowley wrote:
>> Where do you think the output list for EXPLAIN VERBOSE should put the
>> output column list in this case? On the Append node, or just not show
>> them?

> Maybe, not show them?

Yeah, I think that seems like a reasonable idea.  If we show the tlist
for Append in this case, when we never do otherwise, that will be
confusing, and it could easily break plan-reading apps like depesz.com.

What I'm more worried about is whether this breaks any internal behavior
of explain.c, as the comment David quoted upthread seems to think.
If we need to have a tlist to reference, can we make that code look
to the pre-pruning plan tree, rather than the planstate tree?

            regards, tom lane



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

Предыдущее
От: Bruce Momjian
Дата:
Сообщение: log_planner_stats and prepared statements
Следующее
От: David Rowley
Дата:
Сообщение: Re: Runtime pruning problem