| From: | Stephen Frost <sfrost(at)snowman(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Peter Geoghegan <pg(at)heroku(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>, Robert Haas <rhaas(at)postgresql(dot)org> |
| Subject: | Re: [COMMITTERS] pgsql: Include planning time in EXPLAIN ANALYZE output. |
| Date: | 2014-02-04 00:13:46 |
| Message-ID: | 20140204001346.GS2921@tamriel.snowman.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
* Tom Lane (tgl(at)sss(dot)pgh(dot)pa(dot)us) wrote:
> 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".
Agreed.
Thanks,
Stephen
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2014-02-04 00:48:31 | pgsql: Fix lexing of U& sequences just before EOF. |
| Previous Message | Tom Lane | 2014-02-03 23:55:28 | Re: [COMMITTERS] pgsql: Include planning time in EXPLAIN ANALYZE output. |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gurjeet Singh | 2014-02-04 00:18:54 | Proposing pg_hibernate |
| Previous Message | Michael Paquier | 2014-02-04 00:04:46 | Re: should we add a XLogRecPtr/LSN SQL type? |