| From: | Greg Stark <gsstark(at)mit(dot)edu> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Greg Smith <gsmith(at)gregsmith(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, 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:34:04 |
| Message-ID: | 407d949e0910261134n681ec167rfe5ebfa841a7f96b@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Oct 26, 2009 at 7:06 AM, Alvaro Herrera
<alvherre(at)commandprompt(dot)com> wrote:
> Maybe SET PERSISTENT needs to go back to postgresql.conf, add an
> automatic comment "# overridden in persistent.conf" and put a comment
> marker in front of the original line. That way the user is led to the
> actual authoritative source.
We cannot have automatic processes editing user configuration files.
What we could do is give a warning if you do set persistent and the
source of the current value is a postgresql.conf.
--
greg
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Greg Stark | 2009-10-26 18:36:54 | Re: Parsing config files in a directory |
| Previous Message | Greg Stark | 2009-10-26 18:15:06 | Re: Parsing config files in a directory |