aboutsummaryrefslogtreecommitdiff
path: root/contrib/btree_gist/btree_gist.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2014-04-16 20:48:51 -0400
committerTom Lane <tgl@sss.pgh.pa.us>2014-04-16 20:48:59 -0400
commit5f86cbd714c9d43c0fbb43a7b172f77ebf429548 (patch)
tree9c201c8597d509e8992f027b6928c749d58469ce /contrib/btree_gist/btree_gist.c
parente183d11262f4e04ce7f191a9655aeeaa4682a7f5 (diff)
downloadpostgresql-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 'contrib/btree_gist/btree_gist.c')
0 files changed, 0 insertions, 0 deletions