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

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: [COMMITTERS] pgsql: Include planning time in EXPLAIN ANALYZE output.
Дата
Msg-id 24876.1391471728@sss.pgh.pa.us
обсуждение исходный текст
Ответ на Re: [COMMITTERS] pgsql: Include planning time in EXPLAIN ANALYZE output.  (Peter Geoghegan <pg@heroku.com>)
Ответы Re: [COMMITTERS] pgsql: Include planning time in EXPLAIN ANALYZE output.  (Stephen Frost <sfrost@snowman.net>)
Список pgsql-hackers
Peter Geoghegan <pg@heroku.com> writes:
> On Mon, Feb 3, 2014 at 4:15 AM, Robert Haas <robertmhaas@gmail.com> wrote:
>> I'm not really feeling a compelling need to change that.  We've been
>> displaying total runtime - described exactly that way - for many
>> releases and it's surely is confusing to the novice that the time
>> reported can be much less than the time reported by psql's \timing
>> option, usually because of planning time.

> I think that has a lot more to do with network roundtrip time and
> protocol/serialization overhead.

The problem I'm having with the way it stands now is that one would
reasonably expect that "Total time" is the total of all times counted
by EXPLAIN, including main plan execution time, trigger firing time,
and now planning time.  Since it is not, any longer, a total, I think
renaming it would be a good idea.  I'm not wedded to "execution time"
in particular, but I don't like "total".
        regards, tom lane



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

Предыдущее
От: Andres Freund
Дата:
Сообщение: Re: Re: Misaligned BufferDescriptors causing major performance problems on AMD
Следующее
От: Andres Freund
Дата:
Сообщение: Re: slow startup due to LWLockAssign() spinlock