| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Set arbitrary GUC options during initdb |
| Date: | 2023-01-27 15:29:37 |
| Message-ID: | CA+TgmoYjC9TcdtiqBg3GD9VmtOfPu8v_65q_S5gC7VUHNZxjSQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Jan 25, 2023 at 4:26 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2023-01-27 15:34:05 | Re: Set arbitrary GUC options during initdb |
| Previous Message | Peter Eisentraut | 2023-01-27 15:26:01 | Re: Named Operators |