aboutsummaryrefslogtreecommitdiff
path: root/contrib/pg_stat_statements/pg_stat_statements.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2014-05-20 12:20:52 -0400
committerTom Lane <tgl@sss.pgh.pa.us>2014-05-20 12:20:52 -0400
commit0266a9c78139d0f0d64dc1c440e60b8f30172046 (patch)
tree063ac1c922f4ae0242d15b9a80b2d602f0cb52ed /contrib/pg_stat_statements/pg_stat_statements.c
parente0c04b7c3833c3874bf8ca91eb3a8ef45ac00ae4 (diff)
downloadpostgresql-0266a9c78139d0f0d64dc1c440e60b8f30172046.tar.gz
postgresql-0266a9c78139d0f0d64dc1c440e60b8f30172046.zip
Prevent auto_explain from changing the output of a user's EXPLAIN.
Commit af7914c6627bcf0b0ca614e9ce95d3f8056602bf, which introduced the EXPLAIN (TIMING) option, for some reason coded explain.c to look at planstate->instrument->need_timer rather than es->timing to decide whether to print timing info. However, the former flag might get set as a result of contrib/auto_explain wanting timing information. We certainly don't want activation of auto_explain to change user-visible statement behavior, so fix that. Also fix an independent bug introduced in the same patch: in the code path for a never-executed node with a machine-friendly output format, if timing was selected, it would fail to print the Actual Rows and Actual Loops items. Per bug #10404 from Tomonari Katsumata. Back-patch to 9.2 where the faulty code was introduced.
Diffstat (limited to 'contrib/pg_stat_statements/pg_stat_statements.c')
0 files changed, 0 insertions, 0 deletions