Re: Hide 'Execution time' in EXPLAIN (COSTS OFF) - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Hide 'Execution time' in EXPLAIN (COSTS OFF)
Date
Msg-id CA+TgmoZQKhMUReXtyD7FovOrx8N_7m5H=L5Q0u6ge_uyUqfFmg@mail.gmail.com
Whole thread Raw
In response to Re: Hide 'Execution time' in EXPLAIN (COSTS OFF)  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Hide 'Execution time' in EXPLAIN (COSTS OFF)  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: Hide 'Execution time' in EXPLAIN (COSTS OFF)  (Andres Freund <andres@2ndquadrant.com>)
List pgsql-hackers
On Tue, Jun 3, 2014 at 3:08 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Andres Freund <andres@2ndquadrant.com> writes:
>> In 9.4. COSTS OFF for EXPLAIN prevents 'Planning time' to be
>> printed. Should we perhaps do the same for 'Execution time'? That'd make
>> it possible to use EXPLAIN (ANALYZE, COSTS OFF, TIMING OFF) in
>> regression tests.
>
>> Currently the output for that is:
>> postgres=# EXPLAIN (ANALYZE, TIMING OFF, COSTS OFF) SELECT 1;
>>            QUERY PLAN
>> --------------------------------
>>  Result (actual rows=1 loops=1)
>>  Total runtime: 0.035 ms
>> (2 rows)
>
>> Leaving off the total runtime doesn't seem bad to me.
>
> It seems a little weird to call it a "cost" ... but maybe that
> ship has sailed given how we're treating the planning-time item.

Maybe we could make it be controlled by TIMING.  Seems like it fits
well-enough there.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: Hide 'Execution time' in EXPLAIN (COSTS OFF)
Next
From: Keith Fiske
Date:
Subject: Re: [BUGS] BUG #9652: inet types don't support min/max