Clarify some behaviours of REASSIGN OWNED and DROP OWNED BY.

This commit is contained in:
Simon Riggs 2010-04-02 17:29:22 +00:00
parent 33065ef8bc
commit 3e754a89ea
2 changed files with 14 additions and 3 deletions

View file

@ -1,5 +1,5 @@
<!--
$PostgreSQL: pgsql/doc/src/sgml/ref/drop_owned.sgml,v 1.6 2008/11/14 10:22:46 petere Exp $
$PostgreSQL: pgsql/doc/src/sgml/ref/drop_owned.sgml,v 1.7 2010/04/02 17:29:22 sriggs Exp $
PostgreSQL documentation
-->
@ -92,6 +92,10 @@ DROP OWNED BY <replaceable class="PARAMETER">name</replaceable> [, ...] [ CASCAD
reassigns the ownership of all the database objects owned by one or
more roles.
</para>
<para>
Databases owned by the role(s) will not be removed.
</para>
</refsect1>
<refsect1>

View file

@ -1,5 +1,5 @@
<!--
$PostgreSQL: pgsql/doc/src/sgml/ref/reassign_owned.sgml,v 1.4 2008/11/14 10:22:47 petere Exp $
$PostgreSQL: pgsql/doc/src/sgml/ref/reassign_owned.sgml,v 1.5 2010/04/02 17:29:22 sriggs Exp $
PostgreSQL documentation
-->
@ -73,10 +73,17 @@ REASSIGN OWNED BY <replaceable class="PARAMETER">old_role</replaceable> [, ...]
that contains objects owned by a role that is to be removed.
</para>
<para>
<command>REASSIGN OWNED</command> requires privileges on both the
source role(s) and the target role.
</para>
<para>
The <xref linkend="sql-drop-owned"
endterm="sql-drop-owned-title"> command is an alternative that
drops all the database objects owned by one or more roles.
drops all the database objects owned by one or more roles. Note
also that <command>DROP OWNED</command> requires privileges only
on the source role(s).
</para>
<para>