public inbox for [email protected]
help / color / mirror / Atom feedFrom: Peter Eisentraut <[email protected]>
To: Tom Lane <[email protected]>
To: [email protected]
Subject: Re: Set arbitrary GUC options during initdb
Date: Fri, 14 Apr 2023 10:29:53 +0200
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
<[email protected]>
On 27.01.23 15:48, Peter Eisentraut wrote:
> Btw., something that I have had in my notes for a while, but with this
> it would now be officially exposed: Not all options can be safely set
> during bootstrap. For example,
>
> initdb -D data -c track_commit_timestamp=on
>
> will fail an assertion. This might be an exception, or there might be
> others.
I ran a test across all changeable boolean parameters with initdb
setting it to the opposite of their default. The only one besides
track_commit_timestamp that caused initdb to not complete was
default_transaction_read_only, which is to be expected.
We should fix track_commit_timestamp, but it doesn't look like there is
wider impact. (Obviously, this tested only boolean settings. If
someone wants to fuzz-test the others ...)
view thread (3+ messages)
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected]
Subject: Re: Set arbitrary GUC options during initdb
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox