I got the error figured out this morning... The clients were having issues, because
the user that was removed was the owner of the tables. So, the tables effectively had
no owner, causing pgadmin do have different issues in different versions.
I was able to get it fixed (only with the new pgadmin however - the old one barfed to
bad)
It does bring up what I would call a bug, however... Probably in the database,
however, and not the gui.
I would think that you should not be able to remove a user from a database if that
user owns tables.
Furthermore, if you remove a user, that user should have all of its security entries
removed from all tables.
Dan
ps - sorry for the private mail Dave, all of the other mailing lists I am on change
the Reply to to point back to the list, rather than the sender.
---------------------------(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
