Re: [HACKERS] Re: HISTORY for 6.5.2 - Mailing list pgsql-hackers

From Lamar Owen
Subject Re: [HACKERS] Re: HISTORY for 6.5.2
Date
Msg-id 99091915465201.00572@lowen.wgcr.org
Whole thread Raw
In response to Re: [HACKERS] Re: HISTORY for 6.5.2  (Thomas Lockhart <lockhart@alumni.caltech.edu>)
List pgsql-hackers
On Sun, 19 Sep 1999, Thomas Lockhart wrote:
> > Such as /usr/sbin on a Linux FSSTND-compliant system (such as RedHat).  In
> > fact, I may just do that with the RPM distribution (after consulting with RedHat
> > on the issue).  Thomas??  The same goes for the admin commands' man pages --
> > they should be in section 8 on the typical Linux box.
> 
> Man page sections can be reassigned for the next release. afaik
> /usr/sbin tends to contain programs executed by root, which is not
> usually the case for Postgres. Is there a precedent for other programs
> of this type in that directory?

The uucp programs uuxqt and uucico live in /usr/sbin (on RedHat 6).  They are
owned by and executed as user uucp. See other message for FHS quote re:
/usr/sbin.

> Underscores in program names suck. To paraphrase Ali, "no opinion,
> just fact" ;) 

I thought VACUUM sucked.... ;-P  In all seriousness, I totally agree -- either
replace the _ with -, or drop it altogether.

> If we are going to rename programs wholesale, let's do it for release
> 7.0, and if we must have "pg" in front of everything, then do it as,
> e.g. "pgcreateuser". We could rename "pg_dump" as "pgdump" at the same
> time.

Sounds good to me.

> btw, is it only me or do other people refer to this as "pig dump"?

Worse -- I see '/usr/lib/pgsql' and say "user-lib-pigsqueal."

So, with have a var-lib-pigsqueal, user-lib-pigsqueal, and a
user-local-pigsqueal.  Yuck.
> The docs don't claim to match the rpm (or any other real system; as
> the intro claims it is just used as an example). The docs *do* claim
> to know about what program you should run, so those names should never
> change unless done in the official distro.

Agreed.  Like I said, I'm just tossing some ideas -- if they make it in, Ok, if
not, Ok.  As far as I am concerned, it really doesn't matter -- RedHat has
never had a namespace conflict with the PostgreSQL executables residing in
/usr/bin.  The only advantage I see is removing certain admin commands from the
standard PATH.  Then, for user postgres, add to PATH the admin commands'
residence.  Make it part of the .profile for user postgres, give postgres a
different home (under RedHat, ~postgres is currently /var/lib/pgsql), and things
should work fine.

Lamar Owen
WGCR Internet Radio


pgsql-hackers by date:

Previous
From: Lamar Owen
Date:
Subject: Re: [HACKERS] Command Locations (was Re: HISTORY for 6.5....)
Next
From: Bruce Momjian
Date:
Subject: Re: [HACKERS] Command Locations (was Re: HISTORY for 6.5....)