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 15:34:56 |
Message-ID: | slrndhe7t0.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 - Supernews <andrew+nonews(at)supernews(dot)com> writes:
>> On 2005-09-01, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>>> There is some merit in the thought that the DB owner should be able to
>>> grant and revoke access on the public schema, but that no longer
>>> requires ownership, only membership in an appropriate role.
>
>> How would that work without superuser intervention, given that the
>> ownership of public would be the same in all databases regardless of
>> who created them?
>
> Change the ownership of public in template1 to be a "dbadmin" group.
> Grant membership in "dbadmin" to all the DB owners. End of problem.
Only if all db owners are equivalent.
--
Andrew, Supernews
http://www.supernews.com - individual and corporate NNTP services
From | Date | Subject | |
---|---|---|---|
Next Message | Matt Miller | 2005-09-01 15:36:12 | PG_PAGE_LAYOUT_VERSION - Should be Documented as 3? |
Previous Message | Simon Riggs | 2005-09-01 15:34:09 | Re: Remove xmin and cmin from frozen tuples |