X-Original-To: pgsql-docs-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [64.117.224.130]) by svr1.postgresql.org (Postfix) with ESMTP id BFC81D1CA0F for ; Mon, 4 Aug 2003 17:28:26 +0000 (GMT) Received: from svr1.postgresql.org ([64.117.224.193]) by localhost (neptune.hub.org [64.117.224.130]) (amavisd-new, port 10024) with ESMTP id 30771-05 for ; Mon, 4 Aug 2003 14:27:10 -0300 (ADT) Received: from mail.pari.edu (mail.pari.edu [206.74.232.230]) by svr1.postgresql.org (Postfix) with ESMTP id 55930D1CA05 for ; Mon, 4 Aug 2003 14:28:08 -0300 (ADT) Received: from 192.168.1.176 ([192.168.1.176]) by mail.pari.edu (8.11.6/8.11.6) with ESMTP id h74HKc009960; Mon, 4 Aug 2003 13:20:38 -0400 From: Lamar Owen Organization: Pisgah Astronomical Research Institute To: "Chad N. Tindel" , Tom Lane Subject: Re: Mysql -> Postgresql pitfalls Date: Mon, 4 Aug 2003 13:27:59 -0400 User-Agent: KMail/1.5 Cc: pgsql-docs@postgresql.org References: <20030801163555.GA32496@calma.pair.com> <18494.1059792541@sss.pgh.pa.us> <20030802170410.GA12300@calma.pair.com> In-Reply-To: <20030802170410.GA12300@calma.pair.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200308041327.59825.lowen@pari.edu> X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200308/24 X-Sequence-Number: 1884 On Saturday 02 August 2003 13:04, Chad N. Tindel wrote: > I didn't say "require them to run as a non-root user". I said "Give them > the choice to decide what is correct for their environment". In the case > of apache, there are many internal webservers that are not exposed to the > threat of the public internet; for such servers, it may be appropriate to > run apache as root because it simplifies the administration and automation > of tasks. It also simplifies a bug in apache crashing your box and scribbling all over your disk. Apache does have bugs, you know. (as do MySQL and PostgreSQL, but that's another story). The postmaster will not run as root. That is just the way it is, and has been, for quite some time. It is foolish to run an RDBMS server (or any other server that doesn't need root's permissions) as root when it is not necessary. It is lazy to run things as root to 'simplify' administration; properly administering a box isn't that hard, and user protections and permissions should be used to their intended effect in the course of routine administration. That's just basic Unix sysadmin practice that is well accepted by the vast majority of sysadmins. We just encourage the best practice in a more direct way than other servers, that's all. As to the subject matter of this thread, there are a great number of educational opportunities in such a migration/pitfalls document. The MySQL 'way' and the PostgreSQL 'way' are very different, and at points don't even have a common frame of reference. This issue is one of them; a thorough explanation, written in a direct non-condescending style, of why postmaster won't run as root would be a nice addition. -- Lamar Owen Director of Information Technology Pisgah Astronomical Research Institute