| From: | Greg Stark <gsstark(at)mit(dot)edu> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Robert Haas <robertmhaas(at)gmail(dot)com>, Greg Smith <gsmith(at)gregsmith(dot)com>, Magnus Hagander <magnus(at)hagander(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Parsing config files in a directory |
| Date: | 2009-10-26 18:36:54 |
| Message-ID: | 407d949e0910261136v452ce840qc311ad8e5b7e9fc9@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Oct 26, 2009 at 7:25 AM, Alvaro Herrera
<alvherre(at)commandprompt(dot)com> wrote:
> I agree, except that some things are defined in postgresql.conf by
> initdb and you probably want to be able to change them by SET PERSISTENT
> anyway (e.g. lc_messages, listen_addresses, shared_buffers)
These things should go into a postgresql.d/00initdb-defaults.conf file
instead. Otherwise tools wouldn't be able to tune them at all without
user intervention.
--
greg
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joshua D. Drake | 2009-10-26 18:43:17 | Re: Parsing config files in a directory |
| Previous Message | Greg Stark | 2009-10-26 18:34:04 | Re: Parsing config files in a directory |