| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Stephen Frost <sfrost(at)snowman(dot)net>, Ashutosh Bapat <ashutosh(dot)bapat(at)enterprisedb(dot)com>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Reporting planning time with EXPLAIN |
| Date: | 2017-01-06 01:02:19 |
| Message-ID: | 20170106010219.na5hmc5c7hcudbz4@alap3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2016-12-28 10:29:48 -0500, Tom Lane wrote:
> 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.
I don't like this much - I'd like (as previously stated in [1]) to be
able to have an actual EXPLAIN ANALYZE (COSTS off, TIMING OFF) in tests
because that shows the number of loops, rechecks, etc.
Andres
[1] http://archives.postgresql.org/message-id/20140603180548.GU24145%40awork2.anarazel.de
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kouhei Kaigai | 2017-01-06 01:31:26 | T_Float morph to T_Integer after nodeRead |
| Previous Message | Jim Nasby | 2017-01-06 00:44:53 | Re: proposal: session server side variables |