| From: | Peter Geoghegan <pg(at)heroku(dot)com> |
|---|---|
| To: | Robert Haas <rhaas(at)postgresql(dot)org> |
| Cc: | pgsql-committers(at)postgresql(dot)org |
| Subject: | Re: pgsql: Include planning time in EXPLAIN ANALYZE output. |
| Date: | 2014-02-02 11:44:12 |
| Message-ID: | CAM3SWZRXpGyz+L4OSYvhTPyf+9D5_3tO7jOxFxb4GekyHEhdJA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
On Wed, Jan 29, 2014 at 1:10 PM, Robert Haas <rhaas(at)postgresql(dot)org> wrote:
> Include planning time in EXPLAIN ANALYZE output.
Isn't it perhaps a little confusing that "Planning time" may well
exceed "Total runtime"? I'm aware that we aren't super clear on the
accounting here generally, as with pg_stat_statements, which doesn't
include planning time in total_time, while we aren't even explicit
about that in the documentation. But even still, seeing the two
side-by-side, with planning time > total runtime did give me pause.
--
Peter Geoghegan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2014-02-02 14:06:35 | Re: pgsql: Introduce replication slots. |
| Previous Message | Fujii Masao | 2014-02-02 05:44:51 | Re: pgsql: Introduce replication slots. |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Marko Kreen | 2014-02-02 12:16:21 | Re: SSL: better default ciphersuite |
| Previous Message | Ronan Dunklau | 2014-02-02 10:53:51 | Re: Triggers on foreign tables |