Re: [HACKERS] Reporting planning time with EXPLAIN - Mailing list pgsql-hackers

From Andres Freund
Subject Re: [HACKERS] Reporting planning time with EXPLAIN
Date
Msg-id 20170106010219.na5hmc5c7hcudbz4@alap3.anarazel.de
Whole thread Raw
In response to Re: [HACKERS] Reporting planning time with EXPLAIN  (Tom Lane <tgl@sss.pgh.pa.us>)
List 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



pgsql-hackers by date:

Previous
From: Jim Nasby
Date:
Subject: Re: [HACKERS] proposal: session server side variables
Next
From: Kouhei Kaigai
Date:
Subject: [HACKERS] T_Float morph to T_Integer after nodeRead