From f8db76e875099e5e49f5cd729a673e84c0b0471b Mon Sep 17 00:00:00 2001 From: Tom Lane Date: Sun, 28 Apr 2013 00:18:45 -0400 Subject: Editorialize a bit on new ProcessUtility() API. Choose a saner ordering of parameters (adding a new input param after the output params seemed a bit random), update the function's header comment to match reality (cmon folks, is this really that hard?), get rid of useless and sloppily-defined distinction between PROCESS_UTILITY_SUBCOMMAND and PROCESS_UTILITY_GENERATED. --- src/backend/commands/trigger.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) (limited to 'src/backend/commands/trigger.c') diff --git a/src/backend/commands/trigger.c b/src/backend/commands/trigger.c index bebb551f7fa..a0473498bd2 100644 --- a/src/backend/commands/trigger.c +++ b/src/backend/commands/trigger.c @@ -1014,7 +1014,8 @@ ConvertTriggerToFK(CreateTrigStmt *stmt, Oid funcoid) /* ... and execute it */ ProcessUtility((Node *) atstmt, "(generated ALTER TABLE ADD FOREIGN KEY command)", - NULL, None_Receiver, NULL, PROCESS_UTILITY_GENERATED); + PROCESS_UTILITY_SUBCOMMAND, NULL, + None_Receiver, NULL); /* Remove the matched item from the list */ info_list = list_delete_ptr(info_list, info); -- cgit v1.2.3