DROP USER

Description

Deletes a user and the schema with the same name as the user.

Precautions

• CASCADE is used to delete the objects (excluding databases) that depend on the user. CASCADE cannot delete locked objects unless the objects are unlocked or the processes locking the objects are killed.
• If the dependent objects are other databases or reside in other databases, manually delete them before deleting the user from the current database. DROP USER cannot delete objects across databases.
• Before deleting a user, you need to delete all the objects owned by the user and revoke the user's permissions on other objects. Alternatively, you can specify CASCADE to delete the objects owned by the user and the granted permissions.

Syntax

DROP USER [ IF EXISTS ] user_name [, ...] [ CASCADE | RESTRICT ];

Parameters

• IF EXISTS

  Reports a notice instead of an error if the specified user does not exist.

• user_name

  Specifies the name of the user to be deleted.

  Value range: an existing username

• CASCADE | RESTRICT
  • CASCADE: automatically deletes the objects that depend on the user.
  • RESTRICT: refuses to delete the user if any objects depend on it. This is the default action.
    

    In GaussDB, the enable_kill_query configuration parameter exists in the postgresql.conf file. This parameter affects CASCADE.

    • If enable_kill_query is on and CASCADE is used, the statement automatically kills the processes locking dependent objects and then deletes the specified user.
    • If enable_kill_query is off and CASCADE is used, the statement waits until the processes locking dependent objects stop and then deletes the specified user.

Examples

See Examples in section "CREATE USER."

Helpful Links

ALTER USER and CREATE USER