From: David Johnston <polobo@yahoo.com>
To: pgsql-admin@postgresql.org
Subject: Re: How was I able to drop a role even though objects depend on it?
Date: Mon, 1 Jul 2013 09:46:04 -0700 (PDT)
Message-ID: <1372697164049-5762060.post@n5.nabble.com> (raw)
In-Reply-To: <59BF48FAC524384DA413D8F4F2E4BA6907D9A9DA@CINURCNA06.e2k.ad.ge.com>
References: <59BF48FAC524384DA413D8F4F2E4BA6907D9A9DA@CINURCNA06.e2k.ad.ge.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-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-...
Sent from the PostgreSQL - admin mailing list archive at Nabble.com.
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
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: pgsql-admin@postgresql.org
Cc: polobo@yahoo.com
Subject: Re: How was I able to drop a role even though objects depend on it?
In-Reply-To: <1372697164049-5762060.post@n5.nabble.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox