drop_owned(7) [centos man page]

DROP 
OWNED(7)						  PostgreSQL 9.2.7 Documentation					     DROP OWNED(7)

NAME

       DROP_OWNED - remove database objects owned by a database role

SYNOPSIS

       DROP OWNED BY name [, ...] [ CASCADE | RESTRICT ]

DESCRIPTION

       DROP OWNED drops all the objects within 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 and on shared objects (databases, tablespaces) will also be revoked.

PARAMETERS

       name
	   The name of a role whose objects will be dropped, and whose privileges will be revoked.

       CASCADE
	   Automatically drop objects that depend on the affected objects.

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

NOTES

       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 might make the command recurse to objects owned by other users.

       The REASSIGN OWNED (REASSIGN_OWNED(7)) command is an alternative that reassigns the ownership of all the database objects owned by one or
       more roles.

       Databases and tablespaces owned by the role(s) will not be removed.

COMPATIBILITY

       The DROP OWNED statement is a PostgreSQL extension.

SEE ALSO

       REASSIGN OWNED (REASSIGN_OWNED(7)), DROP ROLE (DROP_ROLE(7))

PostgreSQL 9.2.7						    2014-02-17							     DROP OWNED(7)

DROP 
ROLE(7)							   SQL Commands 						      DROP ROLE(7)

NAME

       DROP ROLE - remove a database role

SYNOPSIS

       DROP ROLE [ IF EXISTS ] name [, ...]

DESCRIPTION

       DROP ROLE removes the specified role(s).  To drop a superuser role, you must be a superuser yourself; to drop non-superuser roles, you must
       have CREATEROLE privilege.

       A role cannot be removed if it is still referenced in any database of the cluster; an error will be raised if so. Before dropping the role,
       you must drop all the objects it owns (or reassign their ownership) and revoke any privileges the role has been granted. The REASSIGN OWNED
       [reassign_owned(7)] and DROP OWNED [drop_owned(7)] commands can be useful for this purpose.

       However, it is not necessary to remove role memberships involving the role; DROP ROLE automatically revokes any memberships of  the  target
       role in other roles, and of other roles in the target role.  The other roles are not dropped nor otherwise affected.

PARAMETERS

       IF EXISTS
	      Do not throw an error if the role does not exist. A notice is issued in this case.

       name   The name of the role to remove.

NOTES

       PostgreSQL  includes  a program dropuser [dropuser(1)] that has the same functionality as this command (in fact, it calls this command) but
       can be run from the command shell.

EXAMPLES

       To drop a role:

       DROP ROLE jonathan;

COMPATIBILITY

       The SQL standard defines DROP ROLE, but it allows only one role to be dropped at a time, and it specifies different privilege  requirements
       than PostgreSQL uses.

SEE ALSO

       CREATE ROLE [create_role(7)], ALTER ROLE [alter_role(7)], SET ROLE [set_role(7)]

SQL - Language Statements					    2010-05-14							      DROP ROLE(7)