Peter Eisentraut wrote:
Tomeh, Husam wrote:
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?
The current recommendation, which is reflected in the installation
instructions, is to install the software as root and to use the
postgres user for the database files. The advice seen elsewhere in
this thread to use the postgres user also for the software files is
wrong.
If the user owns the catalog, there is no reason for that user to not
also own the files.
Sincerely,
Joshua D. Drake
--
Command Prompt, Inc., your source for PostgreSQL replication,
professional support, programming, managed services, shared
and dedicated hosting. Home of the Open Source Projects plPHP,
plPerlNG, pgManage, and pgPHPtoolkit.
Contact us now at: +1-503-667-4564 - http://www.commandprompt.com
begin:vcard
fn:Joshua D. Drake
n:Drake;Joshua D.
org:Command Prompt, Inc.
adr:;;PO Box 215;Cascade Locks;Oregon;97014;USA
email;internet:[EMAIL PROTECTED]
title:Consultant
tel;work:503-667-4564
tel;fax:503-210-0334
note:Command Prompt, Inc. is the largest and oldest US based commercial PostgreSQL support provider. We provide the only commercially viable integrated PostgreSQL replication solution, but also custom programming, and support. We authored the book Practical PostgreSQL, the procedural language plPHP, and adding trigger capability to plPerl.
x-mozilla-html:FALSE
url:http://www.commandprompt.com/
version:2.1
end:vcard
---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match
