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.
Showing
- contrib/pg_stat_statements/pg_stat_statements.c 17 additions, 14 deletionscontrib/pg_stat_statements/pg_stat_statements.c
- contrib/sepgsql/hooks.c 8 additions, 6 deletionscontrib/sepgsql/hooks.c
- src/backend/commands/extension.c 2 additions, 2 deletionssrc/backend/commands/extension.c
- src/backend/commands/schemacmds.c 2 additions, 2 deletionssrc/backend/commands/schemacmds.c
- src/backend/commands/trigger.c 2 additions, 1 deletionsrc/backend/commands/trigger.c
- src/backend/executor/functions.c 2 additions, 2 deletionssrc/backend/executor/functions.c
- src/backend/executor/spi.c 2 additions, 2 deletionssrc/backend/executor/spi.c
- src/backend/tcop/pquery.c 2 additions, 3 deletionssrc/backend/tcop/pquery.c
- src/backend/tcop/utility.c 35 additions, 27 deletionssrc/backend/tcop/utility.c
- src/include/tcop/utility.h 8 additions, 9 deletionssrc/include/tcop/utility.h
Loading
Please register or sign in to comment