AW: [HACKERS] initdb problems on Solaris

From: Zeugswetter Andreas SB <ZeugswetterA(at)wien(dot)spardat(dot)at>
To: "'Tom Lane'" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "'Keith Parks'" <emkxp01(at)mtcc(dot)demon(dot)co(dot)uk>
Cc: "'hackers(at)postgreSQL(dot)org'" <hackers(at)postgreSQL(dot)org>
Subject: AW: [HACKERS] initdb problems on Solaris
Date: 2000-01-20 10:04:08
Message-ID: 219F68D65015D011A8E000006F8590C603FDC212@sdexcsrv1.f000.d0188.sd.spardat.at
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


> The postmaster and backend can and should refuse to run with an
> effective Unix userid of 0 (root), but that doesn't mean that
> a Postgres ID of 0 is insecure, does it?

The usual setup has the Postgres ID same as the unix id, thus
0 would be reserved for root.

I think this setup has the advatage, that we could someday issue
setuid() calls for "dba and untrusted stored procedures", which would
imho be a very handy feature.

Andreas

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2000-01-20 11:14:45 Re: AW: [HACKERS] initdb problems on Solaris
Previous Message Keith Parks 2000-01-20 08:39:03 Re: [HACKERS] initdb problems on Solaris