Robert Haas wrote: > In this case, > I'll blame the fact that we allow a role to be dropped while there are > users connected using that role. That's about as sensible as allowing > a table to be dropped while there are users reading from it, or a > database to be dropped while there are users connected to it, both of > which we in fact prohibit. IOW, I'd say the problem is that we've > allowed the system state to become inconsistent and now we're sad > because stuff doesn't work. > > But since that's an established design fl^H^Hprinciple,
Actually, my first comment when Pavan mentioned this on IM was that we should look into fixing that problem sometime. It's not terribly urgent since it doesn't seem to hurt anything too badly, but it's still a bug. -- Álvaro Herrera https://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
