Alvaro Herrera <alvhe...@2ndquadrant.com> writes:
> I had a look at what it'd take to backpatch. For REASSIGN OWNED, you're
> right that it'd require some refactoring, and it's probably not
> worthwhile (the code is not really all that complicated). However, for
> DROP OWNED the proposed hunks apply fine. Only 8.3 needs a different
> patch, but it's only because whitespace is different.
> So what we would end up with, is that DROP OWNED works for shared
> objects (i.e. grants on tablespaces and databases are revoked), but
> REASSIGN OWNED does not; so you're forced to do ALTER
> DATABASE/TABLESPACE SET OWNER.
> Since it's the grants that are more likely to cause headaches than
> ownership when trying to drop users, I suggest that applying those
> patches is the most convenient. (We know that this is a real problem
> because of the bug reports we've gotten.)
Seems reasonable to me.
regards, tom lane
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
