table of contents
DROP OWNED(7) | PostgreSQL 17.2 Documentation | DROP OWNED(7) |
NAME¶
DROP_OWNED - remove database objects owned by a database role
SYNOPSIS¶
DROP OWNED BY { name | CURRENT_ROLE | CURRENT_USER | SESSION_USER } [, ...] [ CASCADE | RESTRICT ]
DESCRIPTION¶
DROP OWNED drops all the objects within the current database that are owned by one of the specified roles. Any privileges granted to the given roles on objects in the current database or on shared objects (databases, tablespaces, configuration parameters) will also be revoked.
PARAMETERS¶
name
CASCADE
RESTRICT
NOTES¶
DROP OWNED is often used to prepare for the removal of one or more roles. Because DROP OWNED only affects the objects in the current database, it is usually necessary to execute this command in each database that contains objects owned by a role that is to be removed.
Using the CASCADE option might make the command recurse to objects owned by other users.
The REASSIGN OWNED command is an alternative that reassigns the ownership of all the database objects owned by one or more roles. However, REASSIGN OWNED does not deal with privileges for other objects.
Databases and tablespaces owned by the role(s) will not be removed.
See Section 21.4 for more discussion.
COMPATIBILITY¶
The DROP OWNED command is a PostgreSQL extension.
SEE ALSO¶
REASSIGN OWNED (REASSIGN_OWNED(7)), DROP ROLE (DROP_ROLE(7))
2024 | PostgreSQL 17.2 |