* Bruno Wolff III ([EMAIL PROTECTED]) wrote: > Thinking about it some more, drops wouldn't be an issue since the owner > can always drop objects.
Right.
> Creating objects in particular schemas or databases is not something that
> all roles may be able to do.
Yeah, I'm not entirely sure what I think about this issue. If you're
not allowed to change ownership of objects and SET ROLE drops your
regular ROLE's privileges then the role which owns the object originally
(and which you're required to be in) must have had create access to that
schema at some point.
I can see requiring the role that's changing the ownership to have
create access to the schema in which the object that's being changed is
in.
Thanks,
Stephen
signature.asc
Description: Digital signature
