REASSIGN OWNED — change the ownership of database objects owned by a database role
REASSIGN OWNED BY {old_role | CURRENT_ROLE | CURRENT_USER | SESSION_USER } [, ...] TO {new_role | CURRENT_ROLE | CURRENT_USER | SESSION_USER }REASSIGN OWNED instructs the system to change the ownership of database objects owned by any of theold_roles tonew_role.
old_roleThe 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 tonew_role.
new_roleThe 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. BecauseREASSIGN 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 membership on both the source role(s) and the target role.
TheDROP OWNED command is an alternative that simply drops all the database objects owned by one or more roles.
TheREASSIGN OWNED command does not affect any privileges granted to theold_roles on objects that are not owned by them. Likewise, it does not affect default privileges created withALTER DEFAULT PRIVILEGES. UseDROP OWNED to revoke such privileges.
SeeSection 21.4 for more discussion.
TheREASSIGN OWNED command is aPostgreSQL extension.
If you see anything in the documentation that is not correct, does not match your experience with the particular feature or requires further clarification, please usethis form to report a documentation issue.