| From: | Gavin Flower <GavinFlower(at)archidevsys(dot)co(dot)nz> |
|---|---|
| To: | Peter Geoghegan <pg(at)heroku(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-hackers(at)postgresql(dot)org, Robert Haas <rhaas(at)postgresql(dot)org>, pgsql-committers(at)postgresql(dot)org |
| Subject: | Re: [HACKERS] pgsql: Include planning time in EXPLAIN ANALYZE output. |
| Date: | 2014-02-02 21:11:49 |
| Message-ID: | 52EEB495.7040102@archidevsys.co.nz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
On 03/02/14 09:44, Peter Geoghegan wrote:
> On Sun, Feb 2, 2014 at 8:13 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> Perhaps s/Total runtime/Execution time/ ?
> +1
>
>
If the planning was ever made into a parallel process, then 'elapsed
time' would be less than the 'processor time'. So what does 'Execution
time' mean?
Can I assume:
'Total runtime' is 'elapsed time'
and
'Execution time' is 'processor time'.
In a parallel implementation, one would likely want both.
Possible this is not an issue now, and I'm thinking to far ahead!
Cheers,
Gavin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2014-02-02 21:53:12 | Re: [COMMITTERS] pgsql: Include planning time in EXPLAIN ANALYZE output. |
| Previous Message | Peter Geoghegan | 2014-02-02 20:44:50 | Re: pgsql: Include planning time in EXPLAIN ANALYZE output. |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2014-02-02 21:45:20 | CacheInvalidateRelcache in btree is a crummy idea |
| Previous Message | Peter Geoghegan | 2014-02-02 20:44:50 | Re: pgsql: Include planning time in EXPLAIN ANALYZE output. |