A newer version of this documentation is available. Use the version menu above to view the most up-to-date release of the Greenplum 6.x documentation.
Removes database objects owned by a database role.
DROP OWNED BY name [, ...] [CASCADE | RESTRICT]
DROP OWNED drops all the objects in 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) will also be revoked.
- The name of a role whose objects will be dropped, and whose privileges will be revoked.
- Automatically drop objects that depend on the affected objects.
- Refuse to drop the objects owned by a role if any other database objects depend on one of the affected objects. This is the default.
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 may 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.
Remove any database objects owned by the role named sally:
DROP OWNED BY sally;
The DROP OWNED command is a Greenplum Database extension.