Re: [COMMITTERS] pgsql: Include planning time in EXPLAIN ANALYZE output. - Mailing list pgsql-hackers

From Gavin Flower
Subject Re: [COMMITTERS] pgsql: Include planning time in EXPLAIN ANALYZE output.
Date
Msg-id 52EEB495.7040102@archidevsys.co.nz
Whole thread Raw
In response to Re: [COMMITTERS] pgsql: Include planning time in EXPLAIN ANALYZE output.  (Peter Geoghegan <pg@heroku.com>)
Responses Re: [COMMITTERS] pgsql: Include planning time in EXPLAIN ANALYZE output.  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On 03/02/14 09:44, Peter Geoghegan wrote:
> On Sun, Feb 2, 2014 at 8:13 AM, Tom Lane <tgl@sss.pgh.pa.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


pgsql-hackers by date:

Previous
From: Peter Geoghegan
Date:
Subject: Re: [COMMITTERS] pgsql: Include planning time in EXPLAIN ANALYZE output.
Next
From: Tom Lane
Date:
Subject: CacheInvalidateRelcache in btree is a crummy idea