GRANT PRIVILEGE
GRANT
grants privileges on a database object. The PUBLIC
pseudo-role can
be used to indicate that the privileges should be granted to all roles
(including roles that might not exist yet).
Privileges are cumulative: revoking a privilege from PUBLIC
does not mean all
roles have lost that privilege, if certain roles were explicitly granted that
privilege.
Syntax
privilege
Field | Use |
---|---|
object_name | The object that privileges are being granted on. |
ALL object_type IN SCHEMA schema_name | The privilege will be granted on all objects of object_type in schema_name. |
ALL object_type IN DATABASE database_name | The privilege will be granted on all objects of object_type in database_name. |
ALL object_type | The privilege will be granted on all objects of object_type, excluding system objects. |
role_name | The role name that is gaining privileges. Use the PUBLIC pseudo-role to grant privileges to all roles. |
SELECT | Allows reading rows from an object. The abbreviation for this privilege is ‘r’ (read). |
INSERT | Allows inserting into an object. The abbreviation for this privilege is ‘a’ (append). |
UPDATE | Allows updating an object (requires SELECT if a read is necessary). The abbreviation for this privilege is ‘w’ (write). |
DELETE | Allows deleting from an object (requires SELECT if a read is necessary). The abbreviation for this privilege is ’d’. |
CREATE | Allows creating a new object within another object. The abbreviation for this privilege is ‘C’. |
USAGE | Allows using an object or looking up members of an object. The abbreviation for this privilege is ‘U’. |
CREATEROLE | Allows creating, altering, deleting roles and the ability to grant and revoke role membership. This privilege is very powerful. It allows roles to grant and revoke membership in other roles, even if it doesn’t have explicit membership in those roles. As a consequence, any role with this privilege can obtain the privileges of any other role in the system. The abbreviation for this privilege is ‘R’ (Role). |
CREATEDB | Allows creating databases. The abbreviation for this privilege is ‘B’ (dataBase). |
CREATECLUSTER | Allows creating clusters. The abbreviation for this privilege is ‘N’ (compute Node). |
CREATENETWORKPOLICY | Allows creating network policies. The abbreviation for this privilege is ‘P’ (newtwork Policy). |
ALL PRIVILEGES | All applicable privileges for the provided object type. |
GROUP | This is an optional keyword that has no effect but is part of the SQL standard. |
Details
The following table describes which privileges are applicable to which objects:
Object type | All privileges |
---|---|
SYSTEM |
RBN |
DATABASE |
UC |
SCHEMA |
UC |
TABLE |
arwd |
(VIEW ) |
r |
(MATERIALIZED VIEW ) |
r |
INDEX |
|
TYPE |
U |
(SOURCE ) |
r |
SINK |
|
CONNECTION |
U |
SECRET |
U |
CLUSTER |
UC |
Unlike PostgreSQL, UPDATE
and DELETE
always require SELECT
privileges on the object being
updated.
Compatibility
For PostgreSQL compatibility reasons, you must specify TABLE
as the object
type for sources, views, and materialized views, or omit the object type.
Examples
GRANT SELECT ON mv TO joe, mike;
GRANT USAGE, CREATE ON DATABASE materialize TO joe;
GRANT ALL ON CLUSTER dev TO joe;
GRANT CREATEDB ON SYSTEM TO joe;
Privileges
The privileges required to execute this statement are:
- Ownership of affected objects.
USAGE
privileges on the containing database if the affected object is a schema.USAGE
privileges on the containing schema if the affected object is namespaced by a schema.- superuser status if the privilege is a system privilege.
Useful views
mz_internal.mz_show_system_privileges
mz_internal.mz_show_my_system_privileges
mz_internal.mz_show_cluster_privileges
mz_internal.mz_show_my_cluster_privileges
mz_internal.mz_show_database_privileges
mz_internal.mz_show_my_database_privileges
mz_internal.mz_show_schema_privileges
mz_internal.mz_show_my_schema_privileges
mz_internal.mz_show_object_privileges
mz_internal.mz_show_my_object_privileges
mz_internal.mz_show_all_privileges
mz_internal.mz_show_all_my_privileges