This page in other versions: 9.1 / 9.2 / 9.3 / current (9.4)  |  Development versions: devel / 9.5  |  Unsupported versions: 8.2 / 8.3 / 8.4 / 9.0



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 the database objects owned by one of the old_roles, to new_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.


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 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.

The DROP OWNED command is an alternative that drops all the database objects owned by one or more roles.

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 statement is a PostgreSQL extension.


Sept. 4, 2010, 10:49 a.m.

You can't reassign 'postgres' objects to other user, because you will get the following error:

"ERROR: cannot drop objects owned by role postgres because they are required by the database system"

The system objects are affected by the command reassign.

Privacy Policy | About PostgreSQL
Copyright © 1996-2015 The PostgreSQL Global Development Group