aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorHeikki Linnakangas <heikki.linnakangas@iki.fi>2014-08-25 19:13:24 +0300
committerHeikki Linnakangas <heikki.linnakangas@iki.fi>2014-08-25 19:13:24 +0300
commit3cd934f635699b7c8b0027be69fddfc36be6f9b8 (patch)
tree1ebda02f35729c234b75895258aeb8d8b70e80f9
parent73eba19aebe0101837668e39267469ca34373552 (diff)
downloadpostgresql-3cd934f635699b7c8b0027be69fddfc36be6f9b8.tar.gz
postgresql-3cd934f635699b7c8b0027be69fddfc36be6f9b8.zip
Don't track DEALLOCATE in pg_stat_statements.
We also don't track PREPARE, nor do we track planning time in general, so let's ignore DEALLOCATE as well for consistency. Backpatch to 9.4, but not further than that. Although it seems unlikely that anyone is relying on the current behavior, this is a behavioral change. Fabien Coelho
-rw-r--r--contrib/pg_stat_statements/pg_stat_statements.c5
1 files changed, 4 insertions, 1 deletions
diff --git a/contrib/pg_stat_statements/pg_stat_statements.c b/contrib/pg_stat_statements/pg_stat_statements.c
index 6beced0e7d9..799242ba6a7 100644
--- a/contrib/pg_stat_statements/pg_stat_statements.c
+++ b/contrib/pg_stat_statements/pg_stat_statements.c
@@ -954,10 +954,13 @@ pgss_ProcessUtility(Node *parsetree, const char *queryString,
* calculated from the query tree) would be used to accumulate costs of
* ensuing EXECUTEs. This would be confusing, and inconsistent with other
* cases where planning time is not included at all.
+ *
+ * Likewise, we don't track execution of DEALLOCATE.
*/
if (pgss_track_utility && pgss_enabled() &&
!IsA(parsetree, ExecuteStmt) &&
- !IsA(parsetree, PrepareStmt))
+ !IsA(parsetree, PrepareStmt) &&
+ !IsA(parsetree, DeallocateStmt))
{
instr_time start;
instr_time duration;