The DROP ROLE
statement removes one or more SQL roles.
The DROP ROLE
statement performs a schema change. For more information about how online schema changes work in CockroachDB, see Online Schema Changes.
DROP ROLE
is no longer an Enterprise feature and is now freely available in the core version of CockroachDB. Also, since the keywords ROLE
and USER
can now be used interchangeably in SQL statements for enhanced PostgreSQL compatibility, DROP ROLE
is now an alias for DROP USER
.
Considerations
- The
admin
role cannot be dropped, androot
must always be a member ofadmin
. - A role cannot be dropped if it has privileges. Use
REVOKE
to remove privileges. - Roles that own objects (such as databases, tables, schemas, and types) cannot be dropped until the ownership is transferred to another role.
Required privileges
Non-admin roles cannot drop admin roles. To drop non-admin roles, the role must be a member of the admin
role or have the CREATEROLE
parameter set.
Synopsis
Parameters
Parameter | Description |
---|---|
name |
The name of the role to remove. To remove multiple roles, use a comma-separate list of roles. You can use SHOW ROLES to find the names of roles. |
Example
In this example, first check a role's privileges. Then, revoke the role's privileges and remove the role.
> SHOW GRANTS ON documents FOR dev_ops;
+------------+--------+-----------+---------+------------+
| Database | Schema | Table | User | Privileges |
+------------+--------+-----------+---------+------------+
| jsonb_test | public | documents | dev_ops | INSERT |
+------------+--------+-----------+---------+------------+
> REVOKE INSERT ON documents FROM dev_ops;
> DROP ROLE dev_ops;