Re: Default permissisons from schemas - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Default permissisons from schemas
Date
Msg-id 10308.1169530085@sss.pgh.pa.us
Whole thread Raw
In response to Default permissisons from schemas  (Stephen Frost <sfrost@snowman.net>)
Responses Re: Default permissisons from schemas  (Stephen Frost <sfrost@snowman.net>)
List pgsql-hackers
Stephen Frost <sfrost@snowman.net> writes:
>   Following up on my reply to Joshua, what I'd like to propose is, for
>   comments and suggestions:

>   ALTER SCHEMA name [ [ WITH ] [ DEFAULT ] option [ ... ] ]

>   where option can be:

>     { GRANT { { SELECT | INSERT | UPDATE | DELETE | RULE | REFERENCES | TRI=
> GGER | EXECUTE }=20
>       [,...] | ALL [ PRIVILEGES ] }=20
>       TO { role | PUBLIC } [, ...] [ WITH GRANT OPTION ]=20
>     } [, ...]

>     OWNER role

This seems to ignore the problem that different types of objects have
different privileges.  E.g., if I want to grant USAGE on all sequences
that doesn't necessarily mean I want to grant USAGE on all languages.

>   When not-null the 'nspdefowner' would be the owner of all
>   objects created in the schema.

Whoa.  You are going to allow people to create objects owned by someone
else?  I don't think so ... most Unix systems have forbidden object
give-away for years, for very good reasons.
        regards, tom lane


pgsql-hackers by date:

Previous
From: "Joshua D. Drake"
Date:
Subject: Re: Updateable cursors
Next
From: Lukas Kahwe Smith
Date:
Subject: Re: Updateable cursors