Tom Lane writes:
> 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.
One possibility would be to have an explicit "flush privileges" command
that you can run over a database to clean up after this. That might also
help to support grant options on groups, which suffer from a similar
can't-look-into-other-databases problem.
--
Peter Eisentraut [EMAIL PROTECTED]
---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match
