| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Christoph Berg <cb(at)df7cb(dot)de>, Andres Freund <andres(at)2ndquadrant(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>, ronan(at)dunklau(dot)fr, Markus Wanner <markus(at)bluegap(dot)ch> |
| Subject: | Re: Hide 'Execution time' in EXPLAIN (COSTS OFF) |
| Date: | 2014-09-23 17:32:39 |
| Message-ID: | 15155.1411493559@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> On Sat, Sep 20, 2014 at 4:13 PM, Christoph Berg <cb(at)df7cb(dot)de> wrote:
>> Can we have "EXPLAIN (timing off)" in 9.4+ hide the "Planning time"
>> line? That would even be backwards compatible with 9.x where it would
>> be a no-op.
> I don't think that'll work becuase:
> /* check that timing is used with EXPLAIN ANALYZE */
> if (es.timing && !es.analyze)
> ereport(ERROR,
> (errcode(ERRCODE_INVALID_PARAMETER_VALUE),
> errmsg("EXPLAIN option TIMING
> requires ANALYZE")));
It looks to me like that would complain about EXPLAIN (TIMING ON),
not the case Christoph is suggesting. What he proposes seems a bit
odd and non-orthogonal, but we could make the code do it if we wanted.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2014-09-23 17:51:58 | Re: delta relations in AFTER triggers |
| Previous Message | Florian Weimer | 2014-09-23 17:15:25 | Re: [REVIEW] Re: Compression of full-page-writes |