Re: Thoughts on the location of configuration files

Please forget what I said here.  I see this thread was continued later
and a compromise was reached.

---------------------------------------------------------------------------

> > > Surely we can also add a -C option to override the sysconfdir just as -D
> > > overrides localstatedir.  Those that refuse to convert can also set -C
> > > equal to -D and have the old setup.  Or the user can only specify -C to
> > > point to the former -D and use the proposed 'datadir' parameter to find
> > > the data area.
> > 
> > I like this, but I'd prefer to have "-C" point to a specific
> > configuration file.
> 
> I understand the value of pointing to a specific configuration file, but
> we then would need to define the location of pg_hba.conf and others in
> that file, and it makes it hard to move that directory anywhere because
> the file paths have to be updated in the file.  Of course, we could
> default to look in the same directory as the config file, but that seems
> quite confusing.  Seems easier to just point to a directory and find all
> the stuff in there you want.
> 
> This does allow you to share postgresql.conf, pg_hba.conf, and
> pg_ident.conf with multiple servers if you override the port on
> postmaster startup for each server.  What it doesn't allow you to do is
> share only pg_hba.conf.  For that, you have to set up multiple
> directories and symlink the pg_hba.conf's together.

--  Bruce Momjian                        |  http://candle.pha.pa.us pgman@candle.pha.pa.us               |  (610)
853-3000+  If your life is a hard drive,     |  830 Blythe Avenue +  Christ can be your backup.        |  Drexel Hill,
Pennsylvania19026