agora inbox for [email protected]
help / color / mirror / Atom feedFrom: Adrian Klaver <[email protected]>
To: Andreas Kretschmer <[email protected]>
Cc: [email protected] <[email protected]>
Subject: Re: Bug, Feature, or what else?
Date: Fri, 08 Feb 2013 07:38:02 -0800
Message-ID: <[email protected]> (raw)
In-Reply-To: <609013460.25018.1360337038276.JavaMail.open-xchange@ox.ims-firmen.de>
References: <119745304.24731.1360333559327.JavaMail.open-xchange@ox.ims-firmen.de>
<[email protected]>
<1568445490.24920.1360335539088.JavaMail.open-xchange@ox.ims-firmen.de>
<[email protected]>
<609013460.25018.1360337038276.JavaMail.open-xchange@ox.ims-firmen.de>
List-Unsubscribe: <mailto:[email protected]?body=unsub%20pgsql-general>
On 02/08/2013 07:23 AM, Andreas Kretschmer wrote:
>
>
> Adrian Klaver <[email protected]> hat am 8. Februar 2013 um 16:19
> geschrieben:
>> On 02/08/2013 06:58 AM, Andreas Kretschmer wrote:
>>>
>>>>> How can i drop a user as SUPERUSER (!) with all privileges?
>>>>
>>>> I believe you will need to REVOKE ALL ON SCHEMA public FROM ak02.
>>>
>>>
>>> doesn't help:
>>>
>>> -bash-4.1$ psql -U postgres db115150
>>> psql (9.1.8)
>>> Type "help" for help.
>>>
>>> db115150=# begin;
>>> BEGIN
>>> 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
>>> db115150=#
>>>
>>>
>>
>> So what does \dn+ public show?
>
> db115150=# \dn+ public
> List of schemas
> Name | Owner | Access privileges | Description
> --------+----------+-----------------------------+------------------------
> public | postgres | postgres=UC/postgres +| standard public schema
> | | akretschmer01=U*C*/postgres+|
> | | ak02=UC/akretschmer01 |
> (1 row)
>
>
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;
--
Adrian Klaver
[email protected]
--
Sent via pgsql-general mailing list ([email protected])
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
view thread (23+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected]
Subject: Re: Bug, Feature, or what else?
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox