Re: Set arbitrary GUC options during initdb

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 ...)