| From: | David G Johnston <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: So why is EXPLAIN printing only *plan* time? |
| Date: | 2014-04-27 20:48:54 |
| Message-ID: | 1398631734166-5801674.post@n5.nabble.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Tom Lane-2 wrote
> Or we could add them into
> just the first planning-time printout, though that might also be
> misleading.
If you are going to show a number for these steps, which seems like a good
idea, then this seems like a reasonable option in the face of this
situation.
Basically two options:
1. Query overhead timing detailed separately
2. Query overhead included with first plans' planning time
An explain option: (OVERHEAD '[off?|detail|first]') would then give the user
the ability to choose between the two (not sure if off is worthwhile but
worth at least rejecting explicitly).
David J.
--
View this message in context: http://postgresql.1045698.n5.nabble.com/So-why-is-EXPLAIN-printing-only-plan-time-tp5801663p5801674.html
Sent from the PostgreSQL - hackers mailing list archive at Nabble.com.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2014-04-27 20:55:51 | Re: includedir_internal headers are not self-contained |
| Previous Message | Andres Freund | 2014-04-27 20:42:43 | Re: includedir_internal headers are not self-contained |