Re: TODO item: set proper permissions on non-system schemas

From: Andrew - Supernews <andrew+nonews(at)supernews(dot)com>
To: pgsql-hackers(at)postgresql(dot)org
Subject: Re: TODO item: set proper permissions on non-system schemas
Date: 2005-09-01 17:51:52
Message-ID: slrndhefto.1vfu.andrew+nonews@trinity.supernews.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2005-09-01, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
>> Tom Lane wrote:
>>> Change the ownership of public in template1 to be a "dbadmin" group.
>>> Grant membership in "dbadmin" to all the DB owners. End of problem.
>
>> Won't that suddenly grant the owner of foo_db dbadmin rights in bar_db?
>> That seems to violate the principle of least surprise.
>
> I'm assuming here that the various dbowners aren't even allowed to
> connect to each others' databases.

Which implies either that you limit each dbowner to one db (in which case
why give them createdb privilege in the first place) or that you require
superuser intervention to modify pg_hba for each database created.

--
Andrew, Supernews
http://www.supernews.com - individual and corporate NNTP services

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2005-09-01 18:03:14 Re: Minimally avoiding Transaction Wraparound in VLDBs
Previous Message Tom Lane 2005-09-01 17:46:00 Re: Using multi-locale support in glibc