Supported Versions: Current (16) / 15 / 14 / 13 / 12
Development Versions: devel
Unsupported versions: 11 / 10 / 9.6 / 9.5 / 9.4 / 9.3 / 9.2 / 9.1 / 9.0 / 8.4 / 8.3 / 8.2
This documentation is for an unsupported version of PostgreSQL.
You may want to view the same page for the current version, or one of the other supported versions listed above instead.

REASSIGN OWNED

Name

REASSIGN OWNED -- change the ownership of database objects owned by a database role

Synopsis

REASSIGN OWNED BY old_role [, ...] TO new_role

Description

REASSIGN OWNED instructs the system to change the ownership of the database objects owned by one of the old_roles, to new_role.

Parameters

old_role

The name of a role. The ownership of all the objects in the current database owned by this role will be reassigned to new_role.

new_role

The name of the role that will be made the new owner of the affected objects.

Notes

REASSIGN OWNED is often used to prepare for the removal of one or more roles. Because REASSIGN 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.

REASSIGN OWNED requires privileges on both the source role(s) and the target role.

The DROP OWNED command is an alternative that drops all the database objects owned by one or more roles. Note also that DROP OWNED requires privileges only on the source role(s).

The REASSIGN OWNED command does not affect the privileges granted to the old_roles in objects that are not owned by them. Use DROP OWNED to revoke those privileges.

The REASSIGN OWNED command does not affect the ownership of any databases owned by the role. Use ALTER DATABASE to reassign that ownership.

Compatibility

The REASSIGN OWNED statement is a PostgreSQL extension.