| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Set arbitrary GUC options during initdb |
| Date: | 2023-01-27 16:35:48 |
| Message-ID: | 3337560.1674837348@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
"David G. Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> writes:
> On Fri, Jan 27, 2023 at 8:53 AM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> Anyway, it seems like I gotta work harder. I'll produce a
>> new patch.
> How about just adding a "section" to the end of the file as needed:
> # AdHoc Settings Specified During InitDB
> max_connections=75
> ...
Nah, I think that would be impossibly confusing. One way or another
the live setting has to be near where the GUC is documented.
We will have to do add-at-the-end for custom GUCs, of course,
but in that case there's no matching comment to confuse you.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Masahiko Sawada | 2023-01-27 16:36:26 | Re: Perform streaming logical transactions by background workers and parallel apply |
| Previous Message | Peter Geoghegan | 2023-01-27 16:22:23 | Re: New strategies for freezing, advancing relfrozenxid early |