Database security in a multi-user environment - Mailing list pgsql-general

From Thomas Yackel
Subject Database security in a multi-user environment
Date
Msg-id sbe147de.083@gwsmtp.ohsu.edu
Whole thread Raw
List pgsql-general
What is the proper method of setting up an environment that allows several database administrators to set up their own
databasesbut does not allow them to view the other DBAs users and passwords? 

For example, we are setting up postgres on a Solaris machine at my university.  I am a DBA (not the Solaris superuser)
whowants to be able to add/drop users, createlang, etc.  But there are others at my level who should not be able to
viewmy (and my users') passwords in the pg_shadow table, but should be able to have the same rights over the data under
theircontrol. 

Creating multiple databases doesn't allow this since a user is active across the entire database cluster.

Should we initdb several database clusters, one for each DBA?  What does this mean in terms of security and
performance? 


pgsql-general by date:

Previous
From: Tom Innes
Date:
Subject: Use of Serial Datatype and Sequence Issue
Next
From: Bruce Momjian
Date:
Subject: Re: Got error on CREATE TABLE AS (+Bug?)