Re: How was I able to drop a role even though objects depend on it? - Mailing list pgsql-admin

From David Johnston
Subject Re: How was I able to drop a role even though objects depend on it?
Date
Msg-id 1372697164049-5762060.post@n5.nabble.com
Whole thread Raw
In response to How was I able to drop a role even though objects depend on it?  ("Wojciechowski, Robert (GE Transportation)" <wojo@ge.com>)
Responses Re: How was I able to drop a role even though objects depend on it?  (Alvaro Herrera <alvherre@2ndquadrant.com>)
List pgsql-admin
Wojciechowski, Robert (GE Transportation) wrote
> [...] there is a database that shows this connect grant to a user that was
> known as foo1_userA (oid 3562339547): 3562339547=c/postgres

The main user dependent situation is having said user OWNER on a database
object.  Simply giving a user connect privileges on a database does not make
the database dependent upon said user and so removing said user remains
possible.

Either (or both) a more explicit description or a self-contained test case
is needed to figure out if you are simply mis-understanding the situation or
if there truly is a bug.  The sentence I quoted above leads me to think
operator-error.

David J.




--
View this message in context:
http://postgresql.1045698.n5.nabble.com/How-was-I-able-to-drop-a-role-even-though-objects-depend-on-it-tp5762049p5762060.html
Sent from the PostgreSQL - admin mailing list archive at Nabble.com.


pgsql-admin by date:

Previous
From: Marcos Cano
Date:
Subject: Re: pg_upgrade / postgis issue
Next
From: Megan
Date:
Subject: one client with multiple ssl cert connections to different databases