| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | Gregory Stark <stark(at)enterprisedb(dot)com> |
| Cc: | Magnus Hagander <magnus(at)hagander(dot)net>, Csaba Nagy <nagy(at)ecircle-ag(dot)com>, Aidan Van Dyk <aidan(at)highrise(dot)ca>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Permanent settings |
| Date: | 2008-02-19 17:19:16 |
| Message-ID: | 20080219171916.GG14892@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Gregory Stark wrote:
> The alternative is to have two files and read them both. Then if you change a
> variable which is overridden by the other source you can warn that the change
> is ineffective.
>
> I think on balance the include file method is so much simpler that I prefer it.
I think this is a good idea. I would suggest being able to query
exactly which config file a setting came from -- so you can see whether
it's the stock postgresql.conf, or the locally-modified
postgresql.local.conf.
--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2008-02-19 17:29:51 | Re: Severe regression in autoconf 2.61 |
| Previous Message | Tom Lane | 2008-02-19 17:11:05 | Re: Including PL/PgSQL by default |