Adrian Klaver <adrian.klaver@gmail.com> 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 comman=
d
> >> 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=3D# revoke all on schema public from ak02 cascade;
> > REVOKE
> > db115150=3D# drop user ak02;
> > FEHLER: kann Rolle =C2=BBak02=C2=AB nicht l=C3=B6schen, weil andere Ob=
jekte davon abh=C3=A4ngen
> > DETAIL: Privilegien f=C3=BCr Schema public
> >
> >
> > Strange, isn't it?
>
> Well I got left is:
>
> REVOKE PUBLIC FROM ak02;
>
i think you mean:
db115150=3D# revoke all on schema public from ak02;
REVOKE
db115150=3D# drop user ak02;
FEHLER: kann Rolle =C2=BBak02=C2=AB nicht l=C3=B6schen, weil andere Objekt=
e davon abh=C3=A4ngen
DETAIL: Privilegien f=C3=BCr Schema public
