BUG #7578: Not able to drop user if S/he has permission on tablespace

From: wheelly(at)gmail(dot)com
To: pgsql-bugs(at)postgresql(dot)org
Subject: BUG #7578: Not able to drop user if S/he has permission on tablespace
Date: 2012-10-02 08:49:27
Message-ID: E1TIyAR-0001qA-FF@wrigleys.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

The following bug has been logged on the website:

Bug reference: 7578
Logged by: Nikolay
Email address: wheelly(at)gmail(dot)com
PostgreSQL version: 9.1.4
Operating system: Linux version 3.2.0-3-amd64 (Debian 3.2.21-3)
Description:

Hello,

The bug is similar to existing bug "BUG #6116: Not able to drop user if S/he
has permission on tablespace".
http://archives.postgresql.org/pgsql-bugs/2011-07/msg00110.php

You wrote to mr. "tushar" <tushar(dot)qa(at)gmail(dot)com>:
------------------------------------------------------------------------
The "DROP OWNED BY" command only drops objects that are owned by a
user. It doesn't revoke privileges that user has granted: those
aren't considered dropable objects. So technically speaking all of
those commands are working just as expected.
------------------------------------------------------------------------

But documentation say reversal thing
(http://www.postgresql.org/docs/9.1/static/sql-drop-owned.html)
------------------------------------------------------------------------
DROP OWNED drops all the objects in the current database that are owned by
one of the specified roles.
Any privileges granted to the given roles on objects in the current database
will also be revoked.
------------------------------------------------------------------------

Where is a bug in PostgreSQL or in documentation?

Thank you,
Nikolay.

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Копыченко Павел 2012-10-02 09:51:14 Please could you provide more specific step by step instructions to build this driver psqlodbc-09.01.0200 under Windows.
Previous Message Heikki Linnakangas 2012-10-02 08:26:24 Re: BUG #7534: walreceiver takes long time to detect n/w breakdown