Re: Mysql -> Postgresql pitfalls

From: "scott(dot)marlowe" <scott(dot)marlowe(at)ihs(dot)com>
To: "Chad N(dot) Tindel" <chad(at)tindel(dot)net>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, <pgsql-docs(at)postgresql(dot)org>
Subject: Re: Mysql -> Postgresql pitfalls
Date: 2003-08-04 15:21:05
Message-ID: Pine.LNX.4.33.0308040920330.10259-100000@css120.ihs.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-docs

On Sat, 2 Aug 2003, Chad N. Tindel wrote:

> > > <RANT>As a programmer, I personally would never write code that kept
> > > people from running things as root. I mean, what is the point?
> >
> > If someone roots your box, it's not our fault. Simple as that.
>
> 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. But to do so, one has to know how to re-compile apache, which will
> exclude a lot of your basic garden variety administrators. Its very
> un-friendly programming.

So tell me, what does the sysadmin gain by running postgresql as root.
Seriously, what one advantage does he have? Besides allowing him to be
lazy, I can't think of one.

In response to

Browse pgsql-docs by date

  From Date Subject
Next Message scott.marlowe 2003-08-04 16:05:40 Re: truth table missing values
Previous Message scott.marlowe 2003-08-04 15:13:41 Re: Mysql -> Postgresql pitfalls