From 5f86cbd714c9d43c0fbb43a7b172f77ebf429548 Mon Sep 17 00:00:00 2001 From: Tom Lane Date: Wed, 16 Apr 2014 20:48:51 -0400 Subject: Rename EXPLAIN ANALYZE's "total runtime" output to "execution time". Now that EXPLAIN also outputs a "planning time" measurement, the use of "total" here seems rather confusing: it sounds like it might include the planning time which of course it doesn't. Majority opinion was that "execution time" is a better label, so we'll call it that. This should be noted as a backwards incompatibility for tools that examine EXPLAIN ANALYZE output. In passing, I failed to resist the temptation to do a little editing on the materialized-view example affected by this change. --- src/backend/commands/explain.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'src/backend/commands/explain.c') diff --git a/src/backend/commands/explain.c b/src/backend/commands/explain.c index 08f3167f10..1104cc3631 100644 --- a/src/backend/commands/explain.c +++ b/src/backend/commands/explain.c @@ -508,7 +508,7 @@ ExplainOnePlan(PlannedStmt *plannedstmt, IntoClause *into, ExplainState *es, /* * Close down the query and free resources. Include time for this in the - * total runtime (although it should be pretty minimal). + * total execution time (although it should be pretty minimal). */ INSTR_TIME_SET_CURRENT(starttime); @@ -527,10 +527,10 @@ ExplainOnePlan(PlannedStmt *plannedstmt, IntoClause *into, ExplainState *es, if (es->analyze) { if (es->format == EXPLAIN_FORMAT_TEXT) - appendStringInfo(es->str, "Total runtime: %.3f ms\n", + appendStringInfo(es->str, "Execution time: %.3f ms\n", 1000.0 * totaltime); else - ExplainPropertyFloat("Total Runtime", 1000.0 * totaltime, + ExplainPropertyFloat("Execution Time", 1000.0 * totaltime, 3, es); } -- cgit v1.2.1