On Tue, Jun 3, 2014 at 3:08 PM, Tom Lane <t...@sss.pgh.pa.us> wrote: > Andres Freund <and...@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 -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers