11<!--
2- $PostgreSQL: pgsql/doc/src/sgml/ref/drop_owned.sgml,v 1.1 2005/11/21 12:49:30 alvherre Exp $
2+ $PostgreSQL: pgsql/doc/src/sgml/ref/drop_owned.sgml,v 1.2 2006/04/02 04:02:40 neilc Exp $
33PostgreSQL documentation
44-->
55
@@ -20,44 +20,76 @@ PostgreSQL documentation
2020
2121 <refsynopsisdiv>
2222<synopsis>
23- DROP OWNED <replaceable class="PARAMETER">name</replaceable> [, ...] [ RESTRICT | CASCADE ]
23+ DROP OWNEDBY <replaceable class="PARAMETER">name</replaceable> [, ...] [ RESTRICT | CASCADE ]
2424</synopsis>
2525 </refsynopsisdiv>
2626
2727 <refsect1>
2828 <title>Description</title>
2929
3030 <para>
31- The <command>DROP OWNED</command>instructs thesystem to drop those
32- databaseobjects owned by one of thegiven roles which reside on the
33- current database. All privileges granted to the given roleswill also be
34- revoked.
31+ <command>DROP OWNED</command>drops all theobjects in the current
32+ databasethat are owned by one of thespecified roles. Any
33+ privileges granted to the given roleson objects in the current
34+ database will also be revoked.
3535 </para>
36+ </refsect1>
3637
37- <para>
38- If <literal>CASCADE</> is specified, <command>DROP OWNED</command>
39- will behave like a <command>DROP ... CASCADE</command> was issued
40- for each object, that is, objects dependent on the ones owned by the
41- given users will be dropped as well.
42- </para>
38+ <refsect1>
39+ <title>Parameters</title>
40+
41+ <variablelist>
42+ <varlistentry>
43+ <term><replaceable class="PARAMETER">name</replaceable></term>
44+ <listitem>
45+ <para>
46+ The name of a role whose objects will be dropped, and whose
47+ privileges will be revoked.
48+ </para>
49+ </listitem>
50+ </varlistentry>
51+
52+ <varlistentry>
53+ <term><literal>CASCADE</literal></term>
54+ <listitem>
55+ <para>
56+ Automatically drop objects that depend on the affected objects.
57+ </para>
58+ </listitem>
59+ </varlistentry>
60+
61+ <varlistentry>
62+ <term><literal>RESTRICT</literal></term>
63+ <listitem>
64+ <para>
65+ Refuse to drop the objects owned by a role if any other database
66+ objects depend on one of the affected objects. This is the default.
67+ </para>
68+ </listitem>
69+ </varlistentry>
70+ </variablelist>
4371 </refsect1>
4472
4573 <refsect1>
4674 <title>Notes</title>
4775 <para>
48- The <command>DROP OWNED</command> command is mostly used in preparation to
49- drop the roles. It may be necessary to issue the command in more than one
50- database.
76+ <command>DROP OWNED</command> is often used to prepare for the
77+ removal of one or more roles. Because <command>DROP OWNED</command>
78+ only affects the objects in the current database, it is usually
79+ necessary to execute this command in each database that contains
80+ objects owned by a role that is to be removed.
5181 </para>
5282
5383 <para>
54- Using the <literal>CASCADE</literal> option may make the command recurse to
55- objects owned by other users.
84+ Using the <literal>CASCADE</literal> option may make the command
85+ recurse to objects owned by other users.
5686 </para>
5787
5888 <para>
59- See the <command>REASSIGN OWNED</command> command for an alternative that
60- gives the objects away to another role.
89+ The <xref linkend="sql-reassign-owned"
90+ endterm="sql-reassign-owned-title"> command is an alternative that
91+ reassigns the ownership of all the database objects owned by one or
92+ more roles.
6193 </para>
6294 </refsect1>
6395