diff options
| author | Peter Eisentraut | 2018-10-05 13:20:32 +0000 |
|---|---|---|
| committer | Peter Eisentraut | 2018-10-10 20:41:12 +0000 |
| commit | f82d4d666ff501382b92dfd80eaf1d459e6e84a3 (patch) | |
| tree | e20beec724e32cfcfa87cda4f5ee8131f5dc1ee8 | |
| parent | ae307861d89767991b71e97faa6e1812e5ab83f9 (diff) | |
Slightly correct context check for event triggers
The previous check for a "complete query" omitted the new
PROCESS_UTILITY_QUERY_NONATOMIC value. This didn't actually make a
difference in practice, because only CALL and SET from PL/pgSQL run in
this state, but it's more correct to include it anyway.
Discussion: https://www.postgresql.org/message-id/4566041d-2567-74d2-d135-19ff6a20fe51%402ndquadrant.com
| -rw-r--r-- | src/backend/tcop/utility.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/src/backend/tcop/utility.c b/src/backend/tcop/utility.c index 898091c45f..ede1621d3e 100644 --- a/src/backend/tcop/utility.c +++ b/src/backend/tcop/utility.c @@ -943,7 +943,7 @@ ProcessUtilitySlow(ParseState *pstate, { Node *parsetree = pstmt->utilityStmt; bool isTopLevel = (context == PROCESS_UTILITY_TOPLEVEL); - bool isCompleteQuery = (context <= PROCESS_UTILITY_QUERY); + bool isCompleteQuery = (context != PROCESS_UTILITY_SUBCOMMAND); bool needCleanup; bool commandCollected = false; ObjectAddress address; |