diff options
author | Tom Lane <tgl@sss.pgh.pa.us> | 2014-04-16 20:48:51 -0400 |
---|---|---|
committer | Tom Lane <tgl@sss.pgh.pa.us> | 2014-04-16 20:48:59 -0400 |
commit | 5f86cbd714c9d43c0fbb43a7b172f77ebf429548 (patch) | |
tree | 9c201c8597d509e8992f027b6928c749d58469ce /src/backend/commands/explain.c | |
parent | e183d11262f4e04ce7f191a9655aeeaa4682a7f5 (diff) | |
download | postgresql-5f86cbd714c9d43c0fbb43a7b172f77ebf429548.tar.gz postgresql-5f86cbd714c9d43c0fbb43a7b172f77ebf429548.zip |
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.
Diffstat (limited to 'src/backend/commands/explain.c')
-rw-r--r-- | src/backend/commands/explain.c | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/src/backend/commands/explain.c b/src/backend/commands/explain.c index 08f3167f10d..1104cc36312 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); } |