Tom Lane escribió:
It looks to me like DropOwnedObjects doesn't actually insist on
superuserness to do DROP OWNED, only ability to become the role,
which means that DROP OWNED BY is completely broken for privileges
if executed by a non-superuser; the only privileges it would remove
would be
Tom Lane escribió:
I believe the problem is that DROP OWNED for privileges is implemented
by calling REVOKE. As noted upthread, when a superuser does REVOKE,
it's executed as though the object owner did the REVOKE, so only
privileges granted directly by the object owner go away. In this
On 02/08/2013 09:09 AM, Tom Lane wrote:
Adrian Klaver adrian.kla...@gmail.com writes:
On 02/08/2013 08:14 AM, Tom Lane wrote:
Of course, postgres has other options besides that, of which DROP OWNED
BY ak02 is probably the most appropriate here. Or if you really want
to get rid of just that
On 02/08/2013 10:09 AM, Tom Lane wrote:
Adrian Klaver adrian.kla...@gmail.com writes:
I am not sure I am following. Are we talking two different cases here?
What I was pointing out was that the non-superuser case seems to be
broken almost completely, whereas the superuser case is only broken
