From: McGehee, Robert <Robert.McGehee@geodecapital.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
To: Alvaro Herrera <alvherre@commandprompt.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: Unable to drop role
Date: Tue, 24 Aug 2010 09:25:30 -0400
Message-ID: <EEBC169715EB8C438D3C9283AF0F201C08DF4CAF@MSGBOSCLM2WIN.DMN1.FMR.COM> (raw)
References: <EEBC169715EB8C438D3C9283AF0F201C08DF4C41@MSGBOSCLM2WIN.DMN1.FMR.COM>
<16094.1282608675@sss.pgh.pa.us>
Thanks Tom and Alvaro for clearing up my confusion.
\l showed that a485099 had both (C)reate and (T)emporary access.
Revoking those allowed me to drop the role. Thanks for the help!
-----Original Message-----
From: Tom Lane [mailto:tgl@sss.pgh.pa.us]
Sent: Monday, August 23, 2010 8:11 PM
To: McGehee, Robert
Cc: pgsql-admin@postgresql.org
Subject: Re: [ADMIN] Unable to drop role
"McGehee, Robert" <Robert.McGehee@geodecapital.com> writes:
> template1=# DROP ROLE a485099;
> ERROR: role "a485099" cannot be dropped because some objects depend
on it
> DETAIL: access to database template1
> template1=# REVOKE CONNECT ON DATABASE template1 FROM a485099;
> REVOKE
CONNECT is not the only possible privilege. Try REVOKE ALL.
regards, tom lane
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: Robert.McGehee@geodecapital.com, tgl@sss.pgh.pa.us, alvherre@commandprompt.com
Subject: Re: Unable to drop role
In-Reply-To: <EEBC169715EB8C438D3C9283AF0F201C08DF4CAF@MSGBOSCLM2WIN.DMN1.FMR.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