Re: initdb: Refactor PG_CMD_PUTS loops - Mailing list pgsql-hackers

From Andrew Dunstan
Subject Re: initdb: Refactor PG_CMD_PUTS loops
Date
Msg-id 962a4a82-ec18-6a4f-7002-4edb2a47b94c@dunslane.net
Whole thread Raw
In response to initdb: Refactor PG_CMD_PUTS loops  (Peter Eisentraut <peter.eisentraut@enterprisedb.com>)
Responses Re: initdb: Refactor PG_CMD_PUTS loops  (Peter Eisentraut <peter.eisentraut@enterprisedb.com>)
List 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 by date:

Previous
From: Ranier Vilela
Date:
Subject: Re: Optimizing Node Files Support
Next
From: Israel Barth Rubio
Date:
Subject: Re: Add support for DEFAULT specification in COPY FROM