Re: initdb: Refactor PG_CMD_PUTS loops
От | Andrew Dunstan |
---|---|
Тема | Re: initdb: Refactor PG_CMD_PUTS loops |
Дата | |
Msg-id | 962a4a82-ec18-6a4f-7002-4edb2a47b94c@dunslane.net обсуждение исходный текст |
Ответ на | initdb: Refactor PG_CMD_PUTS loops (Peter Eisentraut <peter.eisentraut@enterprisedb.com>) |
Ответы |
Re: initdb: Refactor PG_CMD_PUTS loops
|
Список | pgsql-hackers |
On 2022-12-01 Th 05:02, Peter Eisentraut wrote: > 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(). This patch unwinds all that; it's > much simpler that way. Looks reasonable. (Most of this dates back to 2003/2004, the very early days of initdb.c.) cheers andrew -- Andrew Dunstan EDB: https://www.enterprisedb.com
В списке pgsql-hackers по дате отправления: