DROP ROLE v16
DROP ROLE — Remove a database role.
DROP ROLE removes the specified role. To drop a superuser role, you must be a superuser. To drop non-superuser roles, you must have the
Before dropping the role, you must drop all the objects it owns or reassign their ownership and revoke any privileges the role was granted. You can't remove a role if any database of the cluster references it.
You don't need to remove role memberships involving the role.
DROP ROLE revokes any memberships of the target role in other roles and of other roles in the target role. The other roles aren't dropped or otherwise affected.
Alternatively, if the only objects owned by the role belong in a schema that's owned by the role and has the same name as the role, you can specify the
CASCADE option. In this case, the issuer of the
DROP ROLE name CASCADE command must be a superuser. The named role, the schema, and all objects in the schema are deleted.
The name of the role to remove.
Drops the schema owned by and with the same name as the role as long as there are no other dependencies on the role or the schema. All objects owned by the role belonging to the schema are also dropped.
This example drops a role: