Re: Set arbitrary GUC options during initdb - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Set arbitrary GUC options during initdb
Date
Msg-id CA+TgmoYjC9TcdtiqBg3GD9VmtOfPu8v_65q_S5gC7VUHNZxjSQ@mail.gmail.com
Whole thread Raw
In response to Set arbitrary GUC options during initdb  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Wed, Jan 25, 2023 at 4:26 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
> So this invents an initdb switch "-c NAME=VALUE" just like the
> one that the server itself has long had.

HUGE +1 from me. This will, I think, be extremely convenient in many situations.

> The specified settings
> are applied on the command line of the initial probe calls
> (which happen before we've made any config files), and then they
> are added to postgresql.auto.conf, which causes them to take
> effect for the bootstrap backend runs as well as subsequent
> postmaster starts.

I agree with others that it would seem more natural to edit them in
postgresql.conf itself, but I also think it doesn't matter nearly as
much as getting the feature in some form.

-- 
Robert Haas
EDB: http://www.enterprisedb.com



pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: Named Operators
Next
From: Tom Lane
Date:
Subject: Re: Set arbitrary GUC options during initdb