| From: | "Armbrust, Daniel C(dot)" <Armbrust(dot)Daniel(at)mayo(dot)edu> |
|---|---|
| To: | pgadmin-support(at)postgresql(dot)org |
| Subject: | Re: Security settings |
| Date: | 2003-07-18 14:47:07 |
| Message-ID: | 818623B5FD23D51193200002B32C076106FE4E38@excsrv44.mayo.edu |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgadmin-support |
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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dave Page | 2003-07-18 15:01:42 | Re: Security settings |
| Previous Message | George T. Gibson | 2003-07-18 14:32:05 | Error on most recent slackware build |