Adrian Klaver <adrian.klaver@xxxxxxxxx> hat am 8. Februar 2013 um 16:48 geschrieben: > On 02/08/2013 07:45 AM, Andreas Kretschmer wrote: > > > >> > >> If I am following the Notes section correctly in: > >> > >> http://www.postgresql.org/docs/9.1/interactive/sql-revoke.html > >> > >> "If a superuser chooses to issue a GRANT or REVOKE command, the command > >> is performed as though it were issued by the owner of the affected > >> object. Since all privileges ultimately come from the object owner > >> (possibly indirectly via chains of grant options), it is possible for a > >> superuser to revoke all privileges, but this might require use of > >> CASCADE as stated above." > >> > >> > >> Try: > >> > >> revoke all on schema public from ak02 cascade; > > > > Yeah, i read that before, but doesn't help: > > > > > > > > db115150=# revoke all on schema public from ak02 cascade; > > REVOKE > > db115150=# drop user ak02; > > FEHLER: kann Rolle »ak02« nicht löschen, weil andere Objekte davon abhängen > > DETAIL: Privilegien für Schema public > > > > > > Strange, isn't it? > > Well I got left is: > > REVOKE PUBLIC FROM ak02; > i think you mean: db115150=# revoke all on schema public from ak02; REVOKE db115150=# drop user ak02; FEHLER: kann Rolle »ak02« nicht löschen, weil andere Objekte davon abhängen DETAIL: Privilegien für Schema public -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general