From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Andres Freund <andres(at)anarazel(dot)de> |
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:51:39 |
Message-ID: | 24212.1483667499@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Andres Freund <andres(at)anarazel(dot)de> writes:
> On 2016-12-28 10:29:48 -0500, Tom Lane wrote:
>> How about just saying that the existing TIMING option turns this on,
> 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.
Hmm ...
regression=# EXPLAIN (analyze, COSTS off, TIMING OFF) select * from tenk1;
QUERY PLAN
-----------------------------------------------
Seq Scan on tenk1 (actual rows=10000 loops=1)
Planning time: 1.075 ms
Execution time: 2.723 ms
(3 rows)
I see your point. OK, that's a use case not within the scope of the
original proposal, but it's a reasonable argument for having a SUMMARY OFF
option.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2017-01-06 02:02:32 | Re: T_Float morph to T_Integer after nodeRead |
Previous Message | Jim Nasby | 2017-01-06 01:37:24 | Re: DROP FUNCTION of multiple functions |