| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andres Freund <andres(at)2ndquadrant(dot)com> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, ronan(at)dunklau(dot)fr, David Rowley <dgrowleyml(at)gmail(dot)com>, Christoph Berg <cb(at)df7cb(dot)de>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>, Markus Wanner <markus(at)bluegap(dot)ch> |
| Subject: | Re: Hide 'Execution time' in EXPLAIN (COSTS OFF) |
| Date: | 2014-10-13 17:04:45 |
| Message-ID: | 8906.1413219885@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Andres Freund <andres(at)2ndquadrant(dot)com> writes:
> Well. Unless I miss something it doesn't resolve the problem that
> started this thread. Namely that it's currently impossible to write
> regression using EXPLAIN (ANALYZE, TIMING OFF. COSTS OFF). Which is
> worthwhile because it allows to tests some behaviour that's only visible
> in actually executed plans (like seing that a subtree wasn't executed).
TBH, I don't particularly care about that. A new flag for turning
"summary timing" off would answer the complaint with not too much
non-orthogonality ... but I really don't find this use case compelling
enough to justify adding a feature to EXPLAIN.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2014-10-13 17:44:43 | Re: Missing IPv6 for pgbuildfarm.org |
| Previous Message | Bruce Momjian | 2014-10-13 16:17:54 | Re: Code bug or doc bug? |