From: | Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andres Freund <andres(at)anarazel(dot)de> |
Cc: | Andrew Dunstan <andrew(at)dunslane(dot)net>, Robert Haas <robertmhaas(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: initdb / bootstrap design |
Date: | 2022-02-21 12:49:09 |
Message-ID: | 03ed8a55-e50b-3186-f107-5722465c20bb@enterprisedb.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 20.02.22 01:39, Tom Lane wrote:
>> Hm, wouldn't it be less code to just use printf?
> Meh --- it'd be different from the way we do it in the rest
> of initdb, and it would not be "less code". Maybe it'd run
> a shade faster, but I refuse to believe that that'd be
> enough to matter.
There is a PG_CMD_PRINTF() that is used for that purpose.
From | Date | Subject | |
---|---|---|---|
Next Message | Noboru Saito | 2022-02-21 13:23:16 | Re: Separate the result of \watch for each query execution (psql) |
Previous Message | osumi.takamichi@fujitsu.com | 2022-02-21 12:44:04 | RE: Optionally automatically disable logical replication subscriptions on error |