Re: Permanent settings

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