Quick Links

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

From:	Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To:	pgsql-hackers(at)postgresql(dot)org, Peter Geoghegan <pg(at)heroku(dot)com>
Cc:	Robert Haas <rhaas(at)postgresql(dot)org>, pgsql-committers(at)postgresql(dot)org
Subject:	Re: [COMMITTERS] pgsql: Include planning time in EXPLAIN ANALYZE output.
Date:	2014-02-02 16:13:54
Message-ID:	8090.1391357634@sss.pgh.pa.us
Views:	Raw Message \| Whole Thread \| Download mbox \| Resend email
Thread:
Lists:	pgsql-committers pgsql-hackers

Peter Geoghegan <pg(at)heroku(dot)com> writes:
> On Wed, Jan 29, 2014 at 1:10 PM, Robert Haas <rhaas(at)postgresql(dot)org> wrote:
>> Include planning time in EXPLAIN ANALYZE output.

> Isn't it perhaps a little confusing that "Planning time" may well
> exceed "Total runtime"?

Perhaps s/Total runtime/Execution time/ ?

regards, tom lane

In response to

Re: pgsql: Include planning time in EXPLAIN ANALYZE output. at 2014-02-02 11:44:12 from Peter Geoghegan

Responses

Re: pgsql: Include planning time in EXPLAIN ANALYZE output. at 2014-02-02 20:44:50 from Peter Geoghegan
Re: [COMMITTERS] pgsql: Include planning time in EXPLAIN ANALYZE output. at 2014-02-03 12:15:32 from Robert Haas

Browse pgsql-committers by date

	From	Date	Subject
Next Message	Tom Lane	2014-02-02 17:51:21	pgsql: Clean up some sloppy coding in repl_gram.y.
Previous Message	Fujii Masao	2014-02-02 15:43:08	pgsql: Add primary_slotname to recovery.conf.sample.

Browse pgsql-hackers by date

	From	Date	Subject
Next Message	Andres Freund	2014-02-02 16:31:38	Re: mvcc catalo gsnapshots and TopTransactionContext
Previous Message	Tom Lane	2014-02-02 16:12:08	Re: [GENERAL] Insert result does not match record count