I'll consider this dead.
-----Original Message-----
From: Tom Lane [mailto:tgl@sss.pgh.pa.us]
Sent: Saturday, October 27, 2001 1:12 PM
To: Robert Dyas
Cc: pgsql-hackers@postgresql.org
Subject: Re: [HACKERS] consistent naming of components
"Robert Dyas" <rdyas@adelphia.net> writes:
> [ rename and move just about everything in sight ]
Sorry, but I don't think this is going to happen. We'd be breaking
a heck of a lot of user applications, startup scripts, etc to achieve
(IMHO) very little of value. Renaming psql->pgsql would alone break
more user scripts than I care to think about.
> change data location /var/lib/pgsql/data to /var/pgsql
> move .conf files from /var/lib/pgsql/data to /etc/pgsql
The present sources do not have any hardwired notion of where things
should go. If you care to install things in those directories, you
can --- but you won't get far insisting that everyone else should do
likewise. Preferred filesystem organization varies across platforms.
Even if it didn't, there are situations such as running multiple
postmasters (eg, setting up a test version) in which some instances
*must* have a nonstandard location.
You might possibly be able to talk the RPM maintainer into changing
his ideas of where the RPMs should install stuff --- but I believe
he thinks he's following the Linux filesystem layout standard
(FHS? forget what it's called exactly). In any case, breaking
backwards compatibility won't be an easy sell.
> Going a bit further in reorganization, if the config files always lived in
> an /etc/pgsql directory, then pgsqld (aka postmaster) could start with
zero
> parameters and zero environment variables (true?),
Again, see multiple-postmaster issue. AFAICT you are proposing to
remove flexibility that is *necessary* for some people. (Like me
... I currently have three postmasters of different vintages running
on this machine ...)
regards, tom lane
