Re: Configurable path to look up dynamic libraries

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Tuesday 15 May 2001 14:44, Trond Eivind Glomsrød wrote:
> Tom Lane <tgl@sss.pgh.pa.us> writes:
> > Peter Eisentraut <peter_e@gmx.net> writes:
> > > Perhaps it would be good to make the empty path
> > > component equivalent to $libdir, e.g.,

> > Hmm, that would work, and also avoid having to figure out how to stuff
> > $PGLIB into postgresql.conf during initdb.

> While on the subject of postgresql conf... shouldn't it be in
> sysconfdir instead of the database directory? And there's no switch to
> the postmaster to tell it you've put it somewhere else either.

While I understand and, to an extent, agree with this sentiment, it would be 
unworkable at present unless the postgresql.conf file contained constructs 
that differentiated between multiple datadirs.  While the RPM currently 
doesn't support that possibility (not that it will never support such a 
possibility :-)), there are many who do use PostgreSQL with multiple 
postmasters and datadirs.

I personally wouldn't mind a construct similar to that of a webserver that 
supported multiple domain hosting -- you have a master config file or config 
file section that is in a standard place, and you have either a separate 
config file or config file section for each datadir -- in the case of the 
multiple config files, the master would point to each one.

BUT, given the current mindset in the postgresql.conf file, keeping it with 
the datadir is presently the only practical option.
- --
Lamar Owen
WGCR Internet Radio
1 Peter 4:11
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.4 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE7AXvy5kGGI8vV9eERAhS+AKDGhUchvGN5AEkBqE11wEq8xskrGwCgmIFs
FEDp+xn6e9rdVskMOlhtEKI=
=B0tI
-----END PGP SIGNATURE-----