Commitf82d4d6

committed

Slightly correct context check for event triggers

The previous check for a "complete query" omitted the newPROCESS_UTILITY_QUERY_NONATOMIC value. This didn't actually make adifference in practice, because only CALL and SET from PL/pgSQL run inthis state, but it's more correct to include it anyway.Discussion:https://www.postgresql.org/message-id/4566041d-2567-74d2-d135-19ff6a20fe51%402ndquadrant.com

1 parentae30786 commitf82d4d6Copy full SHA for f82d4d6

File tree

-1

lines changed

-1

lines changed

Lines changed: 1 addition & 1 deletion

Original file line number	Diff line number	Diff line change
`@@ -943,7 +943,7 @@ ProcessUtilitySlow(ParseState *pstate,`
`943`	`943`	`{`
`944`	`944`	`Node*parsetree=pstmt->utilityStmt;`
`945`	`945`	`boolisTopLevel= (context==PROCESS_UTILITY_TOPLEVEL);`
`946`		`-boolisCompleteQuery= (context<=PROCESS_UTILITY_QUERY);`
	`946`	`+boolisCompleteQuery= (context!=PROCESS_UTILITY_SUBCOMMAND);`
`947`	`947`	`boolneedCleanup;`
`948`	`948`	`boolcommandCollected= false;`
`949`	`949`	`ObjectAddressaddress;`

Comments

(0)