Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> DHS Webmaster writes:
>> Are there any plans to handle these issues transparently when a user is
>> dropped?
> "Wishlist" maybe, but no concrete plans.
The reason it's difficult is that users span databases; when you drop a
user in database A, you have no way of seeing/removing references to him
that exist in databases B, C, ...
I'm not sure there's any really good answer to this short of changing
the way that users and databases work, which so far no one has wanted
to do.
regards, tom lane