Supported Versions: Current (16) / 15 / 14 / 13 / 12
Development Versions: 17 / 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 -- change the ownership of database objects owned by a database role


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


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



The name of a role. The ownership of all the objects within the current database, and of all shared objects (databases, tablespaces), owned by this role will be reassigned to new_role.


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


REASSIGN OWNED is often used to prepare for the removal of one or more roles. Because REASSIGN OWNED does not affect objects within other databases, 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 simply drops all the database objects owned by one or more roles.

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

See Section 20.4 for more discussion.


The REASSIGN OWNED command is a PostgreSQL extension.