Re: Fixed directory locations in installs - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: Fixed directory locations in installs
Date
Msg-id 200405022220.i42MKvu08871@candle.pha.pa.us
Whole thread Raw
In response to Re: Fixed directory locations in installs  (Peter Eisentraut <peter_e@gmx.net>)
Responses Re: Fixed directory locations in installs  (Andrew Dunstan <andrew@dunslane.net>)
List pgsql-hackers
Peter Eisentraut wrote:
> Magnus Hagander wrote:
> > To make it work more cross-platform, replace "that registry thing"
> > with "postgresql.conf". It's basically the same thing, except the
> > registry has a hierarchy model.
> 
> That only works as long as all the files we want to refer to are used by 
> the server.  But how will psql find /etc/psqlrc, how will libpq find 
> pg_service.conf, how will pg_dumpall find pg_dump, etc.?

Actually, postgresql.conf only works once they run initdb (and we have
PGDATA defined).  We still have the open issue of how initdb finds
postgresql.conf.sample unless we embed the file in the initdb binary
(double-yuck).

For pg_dump on Unix, we hopefully have it in our path, but on Win32, we
will not.

For Win32, we could use the registry.  For Unix, we can't use /etc
because we can't be sure we are root.  Can we create a dot-file in the
user's home directory during install?

--  Bruce Momjian                        |  http://candle.pha.pa.us pgman@candle.pha.pa.us               |  (610)
359-1001+  If your life is a hard drive,     |  13 Roberts Road +  Christ can be your backup.        |  Newtown Square,
Pennsylvania19073
 


pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: Fixed directory locations in installs
Next
From: Bruce Momjian
Date:
Subject: Re: SET WITHOUT CLUSTER patch