From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Gavin Flower <GavinFlower(at)archidevsys(dot)co(dot)nz> |
Cc: | Peter Geoghegan <pg(at)heroku(dot)com>, pgsql-hackers(at)postgresql(dot)org, 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 21:53:12 |
Message-ID: | 28293.1391377992@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers pgsql-hackers |
Gavin Flower <GavinFlower(at)archidevsys(dot)co(dot)nz> writes:
> Can I assume:
> 'Total runtime' is 'elapsed time'
> and
> 'Execution time' is 'processor time'.
No. It's going to be elapsed time, either way.
> In a parallel implementation, one would likely want both.
When and if we have that, we can argue about what to measure.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2014-02-02 23:59:47 | pgsql: Switch in psql_scan() must cover all lexer states (except backsl |
Previous Message | Gavin Flower | 2014-02-02 21:11:49 | Re: [HACKERS] pgsql: Include planning time in EXPLAIN ANALYZE output. |
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2014-02-02 21:57:28 | Re: pg_basebackup and pg_stat_tmp directory |
Previous Message | Tom Lane | 2014-02-02 21:45:20 | CacheInvalidateRelcache in btree is a crummy idea |