In an attempt to throw the authorities off his trail, htomeh@firstam.com ("Tomeh, Husam") transmitted:
> I've seen book that prefer installing PostgreSQL as root and another one
> recommends otherwise by first creating a postgres account and then
> installing it as postgres. In the Oracle world, you don't use root to
> install the software. What is the best practice as far as PostgreSQL
> goes?
"Best practices" tend to vary.
If you are installing software using "package management" tools, then
it is mandatory that you install it as some form of "administrative"
user (e.g. - root) because typical package management tools require
root access.
(That's true whether we're talking about the RPM package manager that
Caldera paid RHAT to develop, dpkg used by Debian, BSD Ports, or
pkgadd used by sundry systems.)
I happen to do much of my work in "managed hosting" environments where
I may not even have root access. In those environments, the "best
practice" is the "mandatory practice" and is to get a postgres user
set up and to have that user install the software.
--
wm(X,Y):-write(X),write('@'),write(Y). wm('cbbrowne','acm.org').
http://www.ntlug.org/~cbbrowne/emacs.html
Rules of the Evil Overlord #94. "When arresting prisoners, my guards
will not allow them to stop and grab a useless trinket of purely
sentimental value." <http://www.eviloverlord.com/>
