diff options
author | Peter Eisentraut <peter@eisentraut.org> | 2022-12-05 23:28:59 +0100 |
---|---|---|
committer | Peter Eisentraut <peter@eisentraut.org> | 2022-12-05 23:33:31 +0100 |
commit | 1bd47d0dca9f63dc26abc00d4912857440cd101c (patch) | |
tree | 06d34e57821d6b2df126e343b19ce244f994064f /src/backend/executor/nodeWindowAgg.c | |
parent | d69d01ba9d8d774487032459ebb83d2086715f01 (diff) | |
download | postgresql-1bd47d0dca9f63dc26abc00d4912857440cd101c.tar.gz postgresql-1bd47d0dca9f63dc26abc00d4912857440cd101c.zip |
initdb: Refactor PG_CMD_PUTS loops
Keeping the SQL commands that initdb runs in string arrays before
feeding them to PG_CMD_PUTS() seems unnecessarily verbose and
inflexible. In some cases, the array only has one member. In other
cases, one might want to use PG_CMD_PRINTF() instead, to parametrize a
command, but that would require breaking up the loop or using
workarounds like replace_token(). Unwind all that; it's much simpler
that way.
Reviewed-by: John Naylor <john.naylor@enterprisedb.com>
Reviewed-by: Andrew Dunstan <andrew@dunslane.net>
Discussion: https://www.postgresql.org/message-id/flat/2c50823b-f453-bb97-e38b-34751c51dcdf%40enterprisedb.com
Diffstat (limited to 'src/backend/executor/nodeWindowAgg.c')
0 files changed, 0 insertions, 0 deletions