Description
DROP ROLE removes the specified role(s).
To drop a superuser role, you must be a superuser yourself;
to drop non-superuser roles, you must have CREATEROLE
privilege.
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.
However, it is not necessary to remove role memberships involving
the role; DROP ROLE automatically revokes any memberships
of the target role in other roles, and of other roles in the target role.
The other roles are not dropped nor otherwise affected.
Redwood compatible syntax to drop a role can be done making use of
the CASCADE clause.
Compatibility
The SQL standard defines DROP ROLE, but it allows
only one role to be dropped at a time, and it specifies different
privilege requirements than EnterpriseDB uses.