> If you can suggest a plausible way that DROP USER is going to change the
> contents of other databases (which might well contain things owned by
> the target user), this might get onto the TODO list --- although I'd
> personally prefer RESTRICT/CASCADE options. So far, since no one has
> the foggiest idea how to implement cross-database removal, it's just
> been left as-is.
Ya ya. I had forgotten that aspect.
Chris
---------------------------(end of broadcast)---------------------------
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faqs/FAQ.html
