Help Center/ GaussDB/ Developer Guide(Distributed_2.x)/ SQL Reference/ SQL Syntax/ GRANT
Updated on 2024-10-14 GMT+08:00
View PDF
Share

GRANT

Function

GRANT grants permissions to roles and users.

GRANT is used in the following scenarios:

  • Granting system permissions to roles or users

    System permissions are also called user attributes, including SYSADMIN, CREATEDB, CREATEROLE, AUDITADMIN, MONADMIN, OPRADMIN, POLADMIN, INHERIT, REPLICATION, VCADMIN, and LOGIN.

    They can be specified only by the CREATE ROLE or ALTER ROLE statement. The SYSADMIN permissions can be granted and revoked using GRANT ALL PRIVILEGE and REVOKE ALL PRIVILEGE, respectively. System permissions cannot be inherited by a user from a role, and cannot be granted using PUBLIC.

  • Granting database object permissions to roles or users

    Grant permissions on a database object (table, view, column, database, function, schema, or tablespace) to a role or user.

    GRANT gives specific permissions on a database object to one or more roles. These permissions are added to those already granted, if any.

    The keyword PUBLIC indicates that the permissions are to be granted to all roles, including those that might be created later. PUBLIC can be thought of as an implicitly defined group that always includes all roles. Any particular role will have the sum of permissions granted directly to it, permissions granted to any role it is presently a member of, and permissions granted to PUBLIC.

    If WITH GRANT OPTION is specified, the recipient of the permission can in turn grant it to others. Without a grant option, the recipient cannot do that. This option cannot be granted to PUBLIC, which is a unique GaussDB attribute.

    GaussDB grants the permissions on certain types of objects to PUBLIC. By default, permissions on tables, columns, sequences, foreign data sources, foreign servers, schemas, and tablespaces are not granted to PUBLIC, but the following permissions are granted to PUBLIC: CONNECT and CREATE TEMP TABLE permissions on databases, EXECUTE permission on functions, and USAGE permission on languages and data types (including domains). An object owner can revoke the default permissions granted to PUBLIC and grant permissions to other users as needed. For security purposes, you are advised to create an object and set its permissions in the same transaction so that other users do not have time windows to use the object. In addition, you can restrict the permissions of the PUBLIC user group by referring to t"Permission Management" in Security Hardening Guide. These default permissions can be modified using the ALTER DEFAULT PRIVILEGES command.

    By default, an object owner has all permissions on the object. For security purposes, the owner can discard some permissions. However, the ALTER, DROP, COMMENT, INDEX, VACUUM, and re-grantable permissions of the object are inherent permissions implicitly owned by the owner.

  • Granting the permissions of one role or user to others

    Grant the permissions of one role or user to others. In this case, every role or user can be regarded as a set of one or more database permissions.

    If WITH ADMIN OPTION is specified, the recipients can in turn grant the permissions to other roles or users or revoke the permissions they have granted to other roles or users. If recipients' permissions are changed or revoked later, the grantees' permissions will also change.

    Database administrators can grant or revoke permissions for any roles or users. Roles with the CREATEROLE permission can grant or revoke permissions for non-admin roles.

  • Granting ANY permissions to roles or users

    Grant ANY permissions to a specified role or user. For details about the value range of the ANY permissions, see the syntax. If WITH ADMIN OPTION is specified, the grantee can grant the ANY permissions to or revoke them from other roles or users. The ANY permissions can be inherited by a role but cannot be granted to PUBLIC. An initial user and the system administrator when separation of duties is disabled can grant the ANY permissions to or revoke them from any role or user.

    Currently, the following ANY permissions are supported: CREATE ANY TABLE, ALTER ANY TABLE, DROP ANY TABLE, SELECT ANY TABLE, INSERT ANY TABLE, UPDATE ANY TABLE, DELETE ANY TABLE, CREATE ANY SEQUENCE, CREATE ANY INDEX, CREATE ANY FUNCTION, EXECUTE ANY FUNCTION, CREATE ANY PACKAGE, EXECUTE ANY PACKAGE, and CREATE ANY TYPE. For details about the ANY permission scope, see Table 1.

Precautions

  • It is not allowed to grant the ANY permissions to PUBLIC or revoke the ANY permissions from PUBLIC.
  • The ANY permissions are database permissions and are valid only for database objects that are granted with the permissions. For example, SELECT ANY TABLE only allows a user to view all user table data in the current database, but the user does not have the permission to view user tables in other databases.
  • Even if a user is granted with the ANY permissions, the user cannot perform INSERT, DELETE, UPDATE, or SELECT operations on the objects of private users.
  • The ANY permissions and the original permissions do not affect each other.
  • If a user is granted with the CREATE ANY TABLE permission, the owner of a table created in a schema with the same name as the user is the creator of the schema. When the user performs other operations on the table, the user needs to be granted with the corresponding operation permission.
  • Exercise caution when granting the CREATE ANY FUNMCTION permission to users to prevent other users from using SECURITY DEFINER functions for privilege escalation.

Syntax

  • Grant the table or view access permission to a user or role. 
    1
2
3
4
5
6
    		 
    GRANT { { SELECT | INSERT | UPDATE | DELETE | TRUNCATE | REFERENCES | TRIGGER | ALTER | DROP | COMMENT | INDEX | VACUUM } [, ...] 
      | ALL [ PRIVILEGES ] }
    ON { [ TABLE ] table_name [, ...]
       | ALL TABLES IN SCHEMA schema_name [, ...] }
    TO { [ GROUP ] role_name | PUBLIC } [, ...] 
    [ WITH GRANT OPTION ];
  • Grant the column access permission to a user or role. 
    1
2
3
4
5
    		 
    GRANT { {{ SELECT | INSERT | UPDATE | REFERENCES | COMMENT } ( column_name [, ...] )} [, ...] 
      | ALL [ PRIVILEGES ] ( column_name [, ...] ) }
    ON [ TABLE ] table_name [, ...]
    TO { [ GROUP ] role_name | PUBLIC } [, ...]
    [ WITH GRANT OPTION ];
  • Grant the sequence access permission to a specified user or role. 
    1
2
3
4
5
6
    		 
    GRANT { { SELECT | UPDATE | USAGE | ALTER | DROP | COMMENT } [, ...] 
      | ALL [ PRIVILEGES ] }
    ON { [ SEQUENCE ] sequence_name [, ...]
       | ALL SEQUENCES IN SCHEMA schema_name [, ...] }
    TO { [ GROUP ] role_name | PUBLIC } [, ...] 
    [ WITH GRANT OPTION ];
  • Grant the database access permission to a user or role. 
    1
2
3
4
5
    		 
    GRANT { { CREATE | CONNECT | TEMPORARY | TEMP | ALTER | DROP | COMMENT } [, ...]
      | ALL [ PRIVILEGES ] }
    ON DATABASE database_name [, ...]
    TO { [ GROUP ] role_name | PUBLIC } [, ...]
    [ WITH GRANT OPTION ];
  • Grant the domain access permission to a user or role. 
    1
2
3
4
    		 
    GRANT { USAGE | ALL [ PRIVILEGES ] }
    ON DOMAIN domain_name [, ...]
    TO { [ GROUP ] role_name | PUBLIC } [, ...]
    [ WITH GRANT OPTION ];

    In the current version, the domain access permission cannot be granted.

  • Grant the CMK access permission to a specified user or role. 
    1
2
3
4
    		 
    GRANT { { USAGE | DROP } [, ...] | ALL [ PRIVILEGES ] }
    ON { CLIENT_MASTER_KEY client_master_key 
    TO { [ GROUP ] role_name | PUBLIC } [, ...] 
    [ WITH GRANT OPTION ];
  • Grant the column encryption key (CEK) access permission to a specified user or role. 
    1
2
3
4
    		 
    GRANT { { USAGE | DROP } [, ...]| ALL [ PRIVILEGES ] }
    ON { COLUMN_ENCRYPTION_KEY column_encryption_key 
    TO { [ GROUP ] role_name | PUBLIC } [, ...] 
    [ WITH GRANT OPTION ];
  • Grant the foreign data source access permission to a user or role. 
    1
2
3
4
    		 
    GRANT { USAGE | ALL [ PRIVILEGES ] }
    ON FOREIGN DATA WRAPPER fdw_name [, ...]
    TO { [ GROUP ] role_name | PUBLIC } [, ...]
    [ WITH GRANT OPTION ];
  • Grant the foreign server access permission to a user or role. 
    1
2
3
4
    		 
    GRANT { { USAGE | ALTER | DROP | COMMENT } [, ...] | ALL [ PRIVILEGES ] }
    ON FOREIGN SERVER server_name [, ...]
    TO { [ GROUP ] role_name | PUBLIC } [, ...]
    [ WITH GRANT OPTION ];
  • Grant the function access permission to a user or role. 
    1
2
3
4
5
    		 
    GRANT { { EXECUTE | ALTER | DROP | COMMENT } [, ...] | ALL [ PRIVILEGES ] }
    ON { FUNCTION {function_name ( [ {[ argmode ] [ arg_name ] arg_type} [, ...] ] )} [, ...]
       | ALL FUNCTIONS IN SCHEMA schema_name [, ...] }
    TO { [ GROUP ] role_name | PUBLIC } [, ...]
    [ WITH GRANT OPTION ];
  • Grant the procedural procedure access permission to a user or role. 
    1
2
3
4
    		 
    GRANT { { EXECUTE | ALTER | DROP | COMMENT } [, ...] | ALL [ PRIVILEGES ] }
    ON { PROCEDURE {proc_name ( [ {[ argmode ] [ arg_name ] arg_type} [, ...] ] )} [, ...]
    TO { [ GROUP ] role_name | PUBLIC } [, ...]
    [ WITH GRANT OPTION ];
  • Grant the procedural language access permission to a user or role. 
    1
2
3
4
    		 
    GRANT { USAGE | ALL [ PRIVILEGES ] }
    ON LANGUAGE lang_name [, ...]
    TO { [ GROUP ] role_name | PUBLIC } [, ...]
    [ WITH GRANT OPTION ];

    In the current version, all users can create C functions, whereas only users with the sysadmin permission can create Java and internal functions.

    • When a user with the sysadmin permission grants the permission for creating C functions to others, the user must specify a recipient and cannot use GRANT USAGE ON LANGUAGE C TO PUBLIC.
    • When a user with the sysadmin permission grants the permission for creating C functions to others, the user cannot specify WITH GRANT OPTION.
  • Grant the sub-cluster access permission to a user or role. 
    1
2
3
4
    		 
    GRANT { { CREATE | USAGE | COMPUTE | ALTER | DROP } [, ...] | ALL [ PRIVILEGES ] }
    ON NODE GROUP group_name [, ...]
    TO { [ GROUP ] role_name | PUBLIC } [, ...]
    [ WITH GRANT OPTION ];

    When the create permission of a sub-cluster is granted to a specified user or role, the usage and compute permissions are granted to the specified user or role by default.

  • Grant the schema access permission to a user or role. 
    1
2
3
4
    		 
    GRANT { { CREATE | USAGE | ALTER | DROP | COMMENT } [, ...] | ALL [ PRIVILEGES ] }
    ON SCHEMA schema_name [, ...]
    TO { [ GROUP ] role_name | PUBLIC } [, ...]
    [ WITH GRANT OPTION ];

    When you grant table or view permissions to other users, you also need to grant the USAGE permission on the schema that the tables and views belong to. Without the USAGE permission, the users with table or view permissions can only see the object names, but cannot access them.

  • Grant the large object access permission to a specified user or role. 
    1
2
3
4
    		 
    GRANT { { SELECT | UPDATE } [, ...] | ALL [ PRIVILEGES ] }
    ON LARGE OBJECT loid [, ...]
    TO { [ GROUP ] role_name | PUBLIC } [, ...]
    [ WITH GRANT OPTION ];

    In the current version, the large object access permission cannot be granted.

  • Grant the tablespace access permission to a user or role. 
    1
2
3
4
    		 
    GRANT { { CREATE | ALTER | DROP | COMMENT } [, ...] | ALL [ PRIVILEGES ] }
    ON TABLESPACE tablespace_name [, ...]
    TO { [ GROUP ] role_name | PUBLIC } [, ...]
    [ WITH GRANT OPTION ];
  • Grant the type access permission to a user or role. 
    1
2
3
4
    		 
    GRANT { { USAGE | ALTER | DROP | COMMENT } [, ...] | ALL [ PRIVILEGES ] }
    ON TYPE type_name [, ...]
    TO { [ GROUP ] role_name | PUBLIC } [, ...]
    [ WITH GRANT OPTION ];

    In the current version, the type access permission cannot be granted.

  • Grant the data source permission to a role. 
    1
2
3
4
    		 
    GRANT { USAGE | ALL [PRIVILEGES]}
   ON DATA SOURCE src_name [, ...]
   TO { [GROUP] role_name | PUBLIC } [, ...]
   [WITH GRANT OPTION];
  • Grant the directory permission to a role. 
    1
2
3
4
    		 
    GRANT { { READ | WRITE | ALTER | DROP } [, ...] | ALL [PRIVILEGES] }
   ON DIRECTORY directory_name [, ...]
   TO { [GROUP] role_name | PUBLIC } [, ...]
   [WITH GRANT OPTION];
  • Grant the package permission to a role. 
    1
2
3
4
    		 
    GRANT { { EXECUTE | ALTER | DROP | COMMENT } [, ...] | ALL [PRIVILEGES] }
   ON PACKAGE package_name [, ...]
   TO { [GROUP] role_name | PUBLIC } [, ...]
   [WITH GRANT OPTION];

    In the current version, the package access permission cannot be granted.

  • Grant a role's permissions to another user or role. 
    1
2
3
    		 
    GRANT role_name [, ...]
   TO role_name [, ...]
   [ WITH ADMIN OPTION ];
  • Grant the sysadmin permission to a role. 
    1
2
    		 
    GRANT ALL { PRIVILEGES | PRIVILEGE }
   TO role_name;
  • Grant the ANY permissions to another user or role. 
    1
2
3
4
5
    		 
    GRANT { CREATE ANY TABLE | ALTER ANY TABLE | DROP ANY TABLE | SELECT ANY TABLE | INSERT ANY TABLE | UPDATE ANY TABLE |
  DELETE ANY TABLE | CREATE ANY SEQUENCE | CREATE ANY INDEX | CREATE ANY FUNCTION | EXECUTE ANY FUNCTION |
  CREATE ANY PACKAGE | EXECUTE ANY PACKAGE | CREATE ANY TYPE } [, ...]
  TO [ GROUP ] role_name [, ...]
  [ WITH ADMIN OPTION ];

    In the current version, the package access permission cannot be granted.

Parameter Description

The possible permissions are:

  • SELECT

    Allows SELECT from any table, view, or sequence.

  • INSERT

    Allows INSERT of a new row into a table.

  • UPDATE

    Allows UPDATE of any column of a table. SELECT ... FOR UPDATE and SELECT ... FOR SHARE also require this permission on at least one column, in addition to the SELECT permission.

  • DELETE

    Allows DELETE of a row from a table.

  • TRUNCATE

    Allows TRUNCATE on a table.

  • REFERENCES

    Allows creation of a foreign key constraint referencing a table. This permission is required on both referencing and referenced tables.

  • TRIGGER

    Allows the creation of a trigger on the specified table.

  • CREATE
    • For databases, allows new schemas to be created within the database.
    • For schemas, allows new objects to be created within the schema. To rename an existing object, you must own the object and have the CREATE permission on the schema of the object.
    • For tablespaces, allows tables to be created within the tablespace, and allows databases and schemas to be created that have the tablespace as their default tablespace.
    • For sub-clusters, allows tables to be created within the sub-cluster.
  • CONNECT

    Allows the grantee to connect to the database.

  • EXECUTE

    Allows calling a function, including use of any operators that are implemented on top of the function.

  • USAGE
    • For procedural languages, allows use of the language for the creation of functions in that language.
    • For schemas, allows access to objects contained in the schema. Without this permission, it is still possible to see the object names.
    • For sequences, allows use of the nextval function.
    • For sub-clusters, allows users who can access objects contained in the schema to access tables in the sub-cluster.
    • For data sources, specifies access permissions or is used as ALL PRIVILEGES.
    • For a key object, USAGE is the permission to use the key.
  • COMPUTE

    For computing sub-clusters, allows users to perform elastic computing in the sub-cluster that they have the compute permission on.

  • ALTER

    Allows users to modify the attributes of a specified object, excluding the owner and schema of the object.

  • DROP

    Allows users to delete specified objects.

  • COMMENT

    Allows users to define or modify comments of a specified object.

  • INDEX

    Allows users to create indexes on specified tables, manage indexes on the tables, and perform REINDEX and CLUSTER operations on the tables.

  • VACUUM

    Allows users to perform ANALYZE and VACUUM operations on specified tables.

  • ALL PRIVILEGES

    Grants all available permissions to a user or role at a time. Only a system administrator has the GRANT ALL PRIVILEGES permission.

GRANT parameters are as follows:

  • role_name

    Specifies the username.

  • table_name

    Specifies the table name.

  • column_name

    Specifies the column name.

  • schema_name

    Specifies the schema name.

  • database_name

    Specifies the database name.

  • function_name

    Specifies the function name.

  • sequence_name

    Specifies the sequence name.

  • domain_name

    Specifies the domain type name.

  • fdw_name

    Specifies the foreign data wrapper name.

  • lang_name

    Specifies the language name.

  • type_name

    Specifies the type name.

  • group_name

    Specifies the sub-cluster name.

  • src_name

    Specifies the data source name.

  • argmode

    Specifies the parameter mode.

    Value range: a string. It must comply with the naming convention.

  • arg_name

    Specifies the parameter name.

    Value range: a string. It must comply with the naming convention.

  • arg_type

    Specifies the parameter type.

    Value range: a string. It must comply with the naming convention.

  • loid

    Specifies the identifier of the large object that includes this page.

    Value range: a string. It must comply with the identifier naming convention.

  • tablespace_name

    Specifies the tablespace name.

  • client_master_key

    Name of the CMK.

    Value range: a string. It must comply with the identifier naming convention.

  • column_encryption_key

    Name of the column encryption key.

    Value range: a string. It must comply with the identifier naming convention.

  • directory_name

    Specifies the directory name.

    Value range: a string. It must comply with the identifier naming convention.

  • WITH GRANT OPTION

    If WITH GRANT OPTION is specified, the recipient of the permission can in turn grant it to others. Without a grant option, the recipient cannot do that. Grant options cannot be granted to PUBLIC.

When a non-owner of an object attempts to GRANT permissions on the object:

  • The statement will fail outright if the user has no permissions whatsoever on the object.
  • As long as some permission is available, the statement will proceed, but it will grant only those permissions for which the user has grant options.
  • The GRANT ALL PRIVILEGES forms will issue a warning message if no grant options are held, while the other forms will issue a warning if grant options for any of the permissions specifically named in the statement are not held.

Database administrators can access all objects, regardless of object permission settings. It is unwise to operate as a system administrator except when necessary.

  • WITH ADMIN OPTION

    If WITH ADMIN OPTION is specified for a role, the grantee can grant the role to other roles or users or revoke the role from other roles or users.

    For the ANY permissions, if WITH ADMIN OPTION is specified, the grantee can grant the ANY permissions to or revoke them from other roles or users.

Table 1 ANY permissions

Permission

Description

CREATE ANY TABLE

Users can create tables or views in the public and user schemas. The users must be granted with the permission to create sequences to create a table that contains serial columns.

ALTER ANY TABLE

Users' ALTER permission on tables or views in the public and user schemas. If the users want to modify the unique index of a table to add a primary key constraint or unique constraint to the table, the users must be granted with the index permission on the table.

DROP ANY TABLE

Users' DROP permission on tables or views in the public and user schemas.

SELECT ANY TABLE

Users' SELECT permission on tables or views in the public and user schemas, which is still subject to row-level access control.

UPDATE ANY TABLE

Users' UPDATE permission on tables or views in the public and user schemas, which is still subject to row-level access control.

INSERT ANY TABLE

Users' INSERT permission on tables or views in the public and user schemas.

DELETE ANY TABLE

Users' DELETE permission on tables or views in the public and user schemas, which is still subject to row-level access control.

CREATE ANY FUNCTION

Users can create functions or stored procedures in the user schemas.

EXECUTE ANY FUNCTION

Users' EXECUTE permission on functions or stored procedures in the public and user schemas.

CREATE ANY PACKAGE

In the current version, the package access permission cannot be granted.

EXECUTE ANY PACKAGE

In the current version, the package access permission cannot be granted.

CREATE ANY TYPE

Users can create types in the public and user schemas.

CREATE ANY SEQUENCE

Users can create sequences in the public and user schemas.

CREATE ANY INDEX

Users can create indexes in the public and user schemas. The users must be granted with the permission to create tablespaces to create a partitioned table index in a tablespace.

If a user is granted with any ANY permission, the user has the USAGE permission on the public and user schemas but does not have the USAGE permission on the system schemas except public listed in Table 1.

Examples

Example: Granting system permissions to a user or role

Create the joe user and grant the sysadmin permission to it.

1
2
 
openGauss=# CREATE USER joe PASSWORD 'xxxxxxxxxx';
openGauss=# GRANT ALL PRIVILEGES TO joe;

Then joe has the sysadmin permission.

Example: Granting object permissions to a user or role

  1. Revoke the sysadmin permission from the joe user. Grant the usage permission of the tpcds schema and all permissions on the tpcds.reason table to joe. 
    1
2
3
    		 
    openGauss=# REVOKE ALL PRIVILEGES FROM joe;
openGauss=# GRANT USAGE ON SCHEMA tpcds TO joe;
openGauss=# GRANT ALL PRIVILEGES ON tpcds.reason TO joe;

    Then joe has all permissions on the tpcds.reason table, including create, retrieve, update, and delete.

  2. Grant the retrieve permission of r_reason_sk, r_reason_id, and r_reason_desc columns and the update permission of the r_reason_desc column in the tpcds.reason table to joe. 
    1
    		 
    openGauss=# GRANT select (r_reason_sk,r_reason_id,r_reason_desc),update (r_reason_desc) ON tpcds.reason TO joe;

    Then joe has the retrieve permission of r_reason_sk and r_reason_id columns in the tpcds.reason table. To enable joe to grant these permissions to other users, execute the following statement:

    1
    		 
    openGauss=# GRANT select (r_reason_sk, r_reason_id) ON tpcds.reason TO joe WITH GRANT OPTION;

    Grant the connection and schema creation permissions of the postgres database to joe, and allow joe to grant these permissions to other users.

    1
    		 
    openGauss=# GRANT create,connect on database postgres TO joe WITH GRANT OPTION;

    Create the tpcds_manager role, grant the access and object creation permissions of the tpcds schema to tpcds_manager, but do not allow tpcds_manager to grant these permissions to others.

    1
2
    		 
    openGauss=# CREATE ROLE tpcds_manager PASSWORD 'xxxxxxxxxx';
openGauss=# GRANT USAGE,CREATE ON SCHEMA tpcds TO tpcds_manager;

    Grant all permissions on the tpcds_tbspc tablespace to joe, but do not allow joe to grant these permissions to others.

    1
2
    		 
    openGauss=# CREATE TABLESPACE tpcds_tbspc RELATIVE LOCATION 'tablespace/tablespace_1';
openGauss=# GRANT ALL ON TABLESPACE tpcds_tbspc TO joe;

Example: Granting the permissions of one user or role to others

  1. Create the manager role, grant joe's permissions to manager, and allow manager to grant these permissions to others. 
    1
2
    		 
    openGauss=# CREATE ROLE manager PASSWORD 'xxxxxxxxxxx';
openGauss=# GRANT joe TO manager WITH ADMIN OPTION;
  2. Create the senior_manager user and grant manager's permissions to it. 
    1
2
    		 
    openGauss=# CREATE ROLE senior_manager PASSWORD 'xxxxxxxxxxx';
openGauss=# GRANT manager TO senior_manager;
  3. Revoke permissions and delete users. 
    1
2
3
    		 
    openGauss=# REVOKE manager FROM joe;
openGauss=# REVOKE senior_manager FROM manager;
openGauss=# DROP USER manager;

Example: Granting the CMK or CEK permission to other user or role

  1. Connect to an encrypted database. 
    1
2
3
4
5
6
7
8
    		 
    gsql -p 57101 postgres -r -C
openGauss=# \! gs_ktool -g
GENERATE
1
openGauss=#  CREATE CLIENT MASTER KEY MyCMK1 WITH ( KEY_STORE = gs_ktool , KEY_PATH = "gs_ktool/1" , ALGORITHM = AES_256_CBC);
CREATE CLIENT MASTER KEY
openGauss=# CREATE COLUMN ENCRYPTION KEY MyCEK1 WITH VALUES (CLIENT_MASTER_KEY = MyCMK1, ALGORITHM = AEAD_AES_256_CBC_HMAC_SHA256);
CREATE COLUMN ENCRYPTION KEY
  2. Create a role newuser and grant the key permission to newuser. 
    1
2
3
4
5
6
7
8
    		 
    openGauss=# CREATE USER newuser PASSWORD 'xxxxxxxxx';
CREATE ROLE
openGauss=# GRANT ALL ON SCHEMA public TO newuser;
GRANT
openGauss=# GRANT USAGE ON COLUMN_ENCRYPTION_KEY MyCEK1 to newuser;
GRANT
openGauss=# GRANT USAGE ON CLIENT_MASTER_KEY MyCMK1 to newuser;
GRANT
  3. Set the user to connect to a database and use a CEK to create an encrypted table. 
     1
 2
 3
 4
 5
 6
 7
 8
 9
10
    		 
    openGauss=# SET SESSION AUTHORIZATION newuser PASSWORD 'xxxxxxxxx';
openGauss=>  CREATE TABLE acltest1 (x int, x2 varchar(50) ENCRYPTED WITH (COLUMN_ENCRYPTION_KEY = MyCEK1, ENCRYPTION_TYPE = DETERMINISTIC));
NOTICE:  The 'DISTRIBUTE BY' clause is not specified. Using 'x' as the distribution column by default.
HINT:  Please use 'DISTRIBUTE BY' clause to specify suitable data distribution column.
CREATE TABLE
openGauss=> SELECT has_cek_privilege('newuser', 'MyCEK1', 'USAGE');
 has_cek_privilege
-------------------
 t
(1 row)
  4. Revoke permissions and delete users. 
    1
2
3
4
5
6
7
8
    		 
    openGauss=# REVOKE USAGE ON COLUMN_ENCRYPTION_KEY MyCEK1 FROM newuser;
openGauss=# REVOKE USAGE ON CLIENT_MASTER_KEY MyCMK1 FROM newuser;
openGauss=# DROP TABLE newuser.acltest1;
openGauss=# DROP COLUMN ENCRYPTION KEY MyCEK1;
openGauss=# DROP CLIENT MASTER KEY MyCMK1;
openGauss=# DROP SCHEMA IF EXISTS newuser CASCADE;
openGauss=# REVOKE ALL ON SCHEMA public FROM newuser;
openGauss=# DROP ROLE IF EXISTS newuser;

Example: Revoking permissions and deleting roles and users

1
2
3
4
5
6
7
8
 
openGauss=# REVOKE ALL PRIVILEGES ON tpcds.reason FROM joe;
openGauss=# REVOKE ALL PRIVILEGES ON SCHEMA tpcds FROM joe;
openGauss=# REVOKE ALL ON TABLESPACE tpcds_tbspc FROM joe;
openGauss=# DROP TABLESPACE tpcds_tbspc;
openGauss=# REVOKE USAGE,CREATE ON SCHEMA tpcds FROM tpcds_manager;
openGauss=# DROP ROLE tpcds_manager;
openGauss=# DROP ROLE senior_manager;
openGauss=# DROP USER joe CASCADE;

Helpful Links

REVOKE and ALTER DEFAULT PRIVILEGES

Parent topic: SQL Syntax