The problem I have with Bruce's scheme is that you could put your config
file where you want it and someone else puts one somewhere higher in the
search path and you have no idea what went wrong. It sounds to me like a
recipe for an SA's nightmare. Other people have claimed to speak from the SA
perspective - do they see this too?
andrew
----- Original Message -----
From: "Tom Lane" <tgl@sss.pgh.pa.us>
> Bruce Momjian <pgman@candle.pha.pa.us> writes:
> > I have a new idea. You know how we have search_path where you can
> > specify multiple schema names. What if we allow the config_dirs/-C to
> > specify multiple directories to search for config files. That way, we
> > can use only one variable, and we can allow people to place different
> > config files in different directories.
>
> Hm, a search path for config files? I could support that if it
> satisfies the folks who object to specifying config directories
> rather than file names.
>
> One thing that would have to be thought about is whether to re-search
> the path on each config file reload --- if you first find pg_hba.conf
> in, say, the third directory on the path, should you pay attention if
> one materializes in the second directory later? Or do you keep going
> back to the same well? I can see arguments either way.