From: | Adrian Klaver <adrian(dot)klaver(at)gmail(dot)com> |
---|---|
To: | Andreas Kretschmer <andreas(at)a-kretschmer(dot)de> |
Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Bug, Feature, or what else? |
Date: | 2013-02-08 15:48:47 |
Message-ID: | 51151E5F.70906@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
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;
>
>
> Andreas
>
>
--
Adrian Klaver
adrian(dot)klaver(at)gmail(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Marc Brazeau | 2013-02-08 15:51:39 | Re: pl/java for postgresql 9.2 |
Previous Message | Andreas Kretschmer | 2013-02-08 15:45:34 | Re: Bug, Feature, or what else? |
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2013-02-08 15:55:03 | Re: Vacuum/visibility is busted |
Previous Message | Andreas Kretschmer | 2013-02-08 15:45:34 | Re: Bug, Feature, or what else? |