Matt Zagrabelny <mzagrabe@xxxxxxxxx> writes: > On Mon, Jun 24, 2024 at 7:03 PM Adrian Klaver <adrian.klaver@xxxxxxxxxxx> > wrote: >> "A role cannot be removed if it is still referenced in any database of >> the cluster; an error will be raised if so. Before dropping the role, >> you must drop all the objects it owns (or reassign their ownership) and >> revoke any privileges the role has been granted on other objects. The >> REASSIGN OWNED and DROP OWNED commands can be useful for this purpose; >> see Section 22.4 for more discussion." > Cool. I gave it a try, but came up with the same error: > test_db=# REASSIGN OWNED by legacy_owner TO new_owner; > REASSIGN OWNED > Time: 0.212 ms > test_db=# drop role legacy_owner; > ERROR: role "legacy_owner" cannot be dropped because some objects depend > on it You need to do DROP OWNED as well to get rid of those privileges. REASSIGN OWNED only changes the ownership of ownable objects. > I'd still like to see how to list the "privileges for schema > public", "\dn+ public" in psql would do that. regards, tom lane
