User Management

You can use CREATE USER and ALTER USER to create and manage database users.

In the non-separation-of-permission mode, a GaussDB(DWS) user account can be created and deleted only by a system administrator or a security administrator with the CREATEROLE attribute.
In separation-of-permission mode, a user account can be created only by a security administrator.

Creating a User

The CREATE USER statement is used to create a GaussDB (DWS) user. After creating a user, you can use the user to connect to the database.

Create common user u1 and assign the CREATEDB attribute to the user.
To create the system administrator mydbadmin, you need to specify the SYSADMIN parameter.
View the created user in the PG_USER view.
To view user attributes, query the system catalog PG_AUTHID.

Altering User Attributes

The ALTER USER statement is used to alter user attributes, such as changing user passwords or permissions.

Example:

Rename user u1 to u2.
Grant the CREATEROLE permission to user u1:
For details about how to change the user password, see Setting and Changing a Password.

Locking a User

The ACCOUNT LOCK | ACCOUNT UNLOCK parameter in the statement is used to lock or unlock a user. A locked user cannot log in to the system. If an account is stolen or illegally accessed, the administrator can manually lock the account. After the account is secured, the administrator can manually unlock the account.

Example:

To lock user u1, run the following command:
To unlock user u1, run the following command:

Deleting a User

The DROP USER statement is used to delete one or more GaussDB(DWS) users. An administrator can delete an account that is no longer used. Deleted users cannot be restored.

If multiple users are deleted at the same time, separate them with commas (,).
After a user is deleted successfully, all the permissions of the user are also deleted.
When an account to be deleted is in the active state, it is deleted after the session is disconnected.
When CASCADE is specified in the DROP USER statement, objects such as tables that depend on the user will be deleted. That is, the objects whose owner is the user are deleted, and the authorizations of other objects to the user are also deleted.

Example: