| From: | Peter Geoghegan <pg(at)heroku(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "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-03 23:30:55 |
| Message-ID: | CAM3SWZTMzVsYi0yjYg_rnM_oKppPLKYpBMV+x9z-9Wb_jpeN1Q@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
On Mon, Feb 3, 2014 at 4:15 AM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> I'm not really feeling a compelling need to change that. We've been
> displaying total runtime - described exactly that way - for many
> releases and it's surely is confusing to the novice that the time
> reported can be much less than the time reported by psql's \timing
> option, usually because of planning time.
I think that has a lot more to do with network roundtrip time and
protocol/serialization overhead.
--
Peter Geoghegan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2014-02-03 23:55:28 | Re: [COMMITTERS] pgsql: Include planning time in EXPLAIN ANALYZE output. |
| Previous Message | Tom Lane | 2014-02-03 21:38:42 | Re: pgsql: Document a few more regression test hazards. |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2014-02-03 23:38:19 | Re: Re: Misaligned BufferDescriptors causing major performance problems on AMD |
| Previous Message | Peter Geoghegan | 2014-02-03 23:28:33 | Re: Wait free LW_SHARED acquisition - v0.2 |