From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Andres Freund <andres(at)2ndquadrant(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Hide 'Execution time' in EXPLAIN (COSTS OFF) |
Date: | 2014-06-03 19:40:27 |
Message-ID: | CA+TgmoZQKhMUReXtyD7FovOrx8N_7m5H=L5Q0u6ge_uyUqfFmg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, Jun 3, 2014 at 3:08 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Andres Freund <andres(at)2ndquadrant(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Keith Fiske | 2014-06-03 19:46:45 | Re: [HACKERS] BUG #9652: inet types don't support min/max |
Previous Message | Andres Freund | 2014-06-03 19:13:18 | Re: Hide 'Execution time' in EXPLAIN (COSTS OFF) |