Re: Parsing config files in a directory - Mailing list pgsql-hackers

From Kevin Grittner
Subject Re: Parsing config files in a directory
Date
Msg-id 4AE81530020000250002C076@gw.wicourts.gov
Whole thread Raw
In response to Re: Parsing config files in a directory  (Alvaro Herrera <alvherre@commandprompt.com>)
Responses Re: Parsing config files in a directory
List pgsql-hackers
Alvaro Herrera <alvherre@commandprompt.com> wrote:
> Kevin Grittner wrote:
> 
>> But I think that's where the rub is -- when you
>> have more than one source for information, what's the precedence? 
> 
> This is not a problem nowadays because that info is in pg_settings.
> File name and line number.
I'm talking about how the decision should be made as to which takes
precedence.  It's fine to document which one *was* chosen, but that
doesn't eliminate the problem of conflicting settings making a mess. 
Someone else (Robert maybe?) gave an explicit example of how three
files could have overlapping settings.  Of course, *my* tool will name
its configuration file "        !.conf".
-Kevin


pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: Parsing config files in a directory
Next
From: Anders Steinlein
Date:
Subject: Show schema size with \dn+