Re: Unable to drop role

"McGehee, Robert" <Robert.McGehee@geodecapital.com> writes:
> 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!

I wonder whether Robert's confusion doesn't stem from a poor choice
of message wording:

>> template1=# DROP ROLE a485099;
>> ERROR:  role "a485099" cannot be dropped because some objects depend on it
>> DETAIL:  access to database template1

I can see how "access to" might be read as specifically meaning "CONNECT
privilege for".  Should we change this message from "access to whatever"
to "privileges for whatever", or some such wording?

            regards, tom lane