Re: [COMMITTERS] pgsql: Include planning time in EXPLAIN ANALYZE output.

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: [COMMITTERS] pgsql: Include planning time in EXPLAIN ANALYZE output.
Дата
Msg-id 18488.1397691358@sss.pgh.pa.us
обсуждение исходный текст
Ответ на Re: [COMMITTERS] pgsql: Include planning time in EXPLAIN ANALYZE output.  (Bruce Momjian <bruce@momjian.us>)
Ответы Re: [COMMITTERS] pgsql: Include planning time in EXPLAIN ANALYZE output.  (Oleg Bartunov <obartunov@gmail.com>)
Re: [COMMITTERS] pgsql: Include planning time in EXPLAIN ANALYZE output.  (Andreas Karlsson <andreas@proxel.se>)
Список pgsql-hackers
Bruce Momjian <bruce@momjian.us> writes:
> Where are we on this?  I still see:

>     test=> EXPLAIN ANALYZE SELECT 1;
>                                          QUERY PLAN
>     ------------------------------------------------------------------------------------
>      Result  (cost=0.00..0.01 rows=1 width=0) (actual time=0.001..0.001 rows=1 loops=1)
>      Planning time: 0.009 ms
> -->     Total runtime: 0.009 ms
>     (3 rows)

There seemed to be a clear majority of votes in favor of changing it to
say "Execution time".  Robert was arguing for no change, but I don't think
that's tenable in view of the fact that the addition of the "Planning
time" line is already a change, and one that makes the old wording
confusing.

I'll go change it.
        regards, tom lane



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

Предыдущее
От: Bruce Momjian
Дата:
Сообщение: Re: slow startup due to LWLockAssign() spinlock
Следующее
От: Bruce Momjian
Дата:
Сообщение: Re: Minor performance improvement in transition to external sort