>
> 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.
>
So a junior DBA goes to manage the db. Makes a change the
postgresql.conf file and bounces the db. The change doesn't stick.
That doesn't sound like fun and it also sounds like Oracle's spfile and
pfile.
Jon
