Stephen Frost <sfr...@snowman.net> writes:
> * Ashutosh Bapat (ashutosh.ba...@enterprisedb.com) wrote:
>>> I am not sure whether using *summary* to print just planning time is a
>>> good idea. Another option could be SUMMARY_PLAN_TIME.
> Using 'summary' seems entirely reasonable to me,
I think it's an awful choice of name; it has nothing to do with either
the functionality or the printed name of the field. And I could imagine
future uses of "summary" to mean something much different, like say an
actual summary. (The dictionary meaning of "summary" is "a brief
restatement of the main points of something"; adding new information
is not even approximately within the meaning.)
How about just saying that the existing TIMING option turns this on,
if it's specified without ANALYZE? Right now that combination draws
an error:
regression=# explain (timing on) select 1;
ERROR: EXPLAIN option TIMING requires ANALYZE
so there's no existing usage that this would break.
regards, tom lane
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
