diff options
| author | Tom Lane | 2014-04-17 00:48:51 +0000 |
|---|---|---|
| committer | Tom Lane | 2014-04-17 00:48:59 +0000 |
| commit | 5f86cbd714c9d43c0fbb43a7b172f77ebf429548 (patch) | |
| tree | 9c201c8597d509e8992f027b6928c749d58469ce /doc/src/sgml/ref/explain.sgml | |
| parent | e183d11262f4e04ce7f191a9655aeeaa4682a7f5 (diff) | |
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 'doc/src/sgml/ref/explain.sgml')
| -rw-r--r-- | doc/src/sgml/ref/explain.sgml | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/src/sgml/ref/explain.sgml b/doc/src/sgml/ref/explain.sgml index 04a78ee82ea..c4aa95f9302 100644 --- a/doc/src/sgml/ref/explain.sgml +++ b/doc/src/sgml/ref/explain.sgml @@ -408,7 +408,7 @@ EXPLAIN ANALYZE EXECUTE query(100, 200); -> Index Scan using test_pkey on test (cost=0.29..9.29 rows=50 width=8) (actual time=0.039..0.091 rows=99 loops=1) Index Cond: ((id > $1) AND (id < $2)) Planning time: 0.197 ms - Total runtime: 0.225 ms + Execution time: 0.225 ms (5 rows) </programlisting> </para> |