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/executor/functions.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'src/backend/executor/functions.c') diff --git a/src/backend/executor/functions.c b/src/backend/executor/functions.c index c908f34cfe4..dbb4805ae2c 100644 --- a/src/backend/executor/functions.c +++ b/src/backend/executor/functions.c @@ -831,10 +831,10 @@ postquel_getnext(execution_state *es, SQLFunctionCachePtr fcache) (Node *) es->qd->plannedstmt : es->qd->utilitystmt), fcache->src, + PROCESS_UTILITY_QUERY, es->qd->params, es->qd->dest, - NULL, - PROCESS_UTILITY_QUERY); + NULL); result = true; /* never stops early */ } else -- cgit v1.2.3