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/schemacmds.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'src/backend/commands/schemacmds.c') diff --git a/src/backend/commands/schemacmds.c b/src/backend/commands/schemacmds.c index 21d7e608df..1d13ba0d30 100644 --- a/src/backend/commands/schemacmds.c +++ b/src/backend/commands/schemacmds.c @@ -151,10 +151,10 @@ CreateSchemaCommand(CreateSchemaStmt *stmt, const char *queryString) /* do this step */ ProcessUtility(stmt, queryString, + PROCESS_UTILITY_SUBCOMMAND, NULL, None_Receiver, - NULL, - PROCESS_UTILITY_SUBCOMMAND); + NULL); /* make sure later steps can see the object created here */ CommandCounterIncrement(); } -- cgit v1.2.1