2005-11-21 13:49:33 +01:00
|
|
|
<!--
|
2010-09-20 22:08:53 +02:00
|
|
|
doc/src/sgml/ref/drop_owned.sgml
|
2005-11-21 13:49:33 +01:00
|
|
|
PostgreSQL documentation
|
|
|
|
-->
|
|
|
|
|
2017-10-20 03:16:39 +02:00
|
|
|
<refentry id="sql-drop-owned">
|
2014-02-24 03:25:35 +01:00
|
|
|
<indexterm zone="sql-drop-owned">
|
|
|
|
<primary>DROP OWNED</primary>
|
|
|
|
</indexterm>
|
|
|
|
|
2005-11-21 13:49:33 +01:00
|
|
|
<refmeta>
|
2010-04-03 09:23:02 +02:00
|
|
|
<refentrytitle>DROP OWNED</refentrytitle>
|
2008-11-14 11:22:48 +01:00
|
|
|
<manvolnum>7</manvolnum>
|
2005-11-21 13:49:33 +01:00
|
|
|
<refmiscinfo>SQL - Language Statements</refmiscinfo>
|
|
|
|
</refmeta>
|
|
|
|
|
|
|
|
<refnamediv>
|
|
|
|
<refname>DROP OWNED</refname>
|
|
|
|
<refpurpose>remove database objects owned by a database role</refpurpose>
|
|
|
|
</refnamediv>
|
|
|
|
|
|
|
|
<refsynopsisdiv>
|
|
|
|
<synopsis>
|
2020-09-17 11:39:28 +02:00
|
|
|
DROP OWNED BY { <replaceable class="parameter">name</replaceable> | CURRENT_ROLE | CURRENT_USER | SESSION_USER } [, ...] [ CASCADE | RESTRICT ]
|
2005-11-21 13:49:33 +01:00
|
|
|
</synopsis>
|
|
|
|
</refsynopsisdiv>
|
|
|
|
|
|
|
|
<refsect1>
|
|
|
|
<title>Description</title>
|
|
|
|
|
|
|
|
<para>
|
2013-01-28 21:46:47 +01:00
|
|
|
<command>DROP OWNED</command> drops all the objects within the current
|
2006-04-02 06:02:40 +02:00
|
|
|
database that are owned by one of the specified roles. Any
|
|
|
|
privileges granted to the given roles on objects in the current
|
2019-03-25 22:18:05 +01:00
|
|
|
database or on shared objects (databases, tablespaces) will also be
|
2013-01-28 21:46:47 +01:00
|
|
|
revoked.
|
2005-11-21 13:49:33 +01:00
|
|
|
</para>
|
2006-04-02 06:02:40 +02:00
|
|
|
</refsect1>
|
2005-11-21 13:49:33 +01:00
|
|
|
|
2006-04-02 06:02:40 +02:00
|
|
|
<refsect1>
|
|
|
|
<title>Parameters</title>
|
|
|
|
|
|
|
|
<variablelist>
|
|
|
|
<varlistentry>
|
2017-10-09 04:00:57 +02:00
|
|
|
<term><replaceable class="parameter">name</replaceable></term>
|
2006-04-02 06:02:40 +02:00
|
|
|
<listitem>
|
|
|
|
<para>
|
|
|
|
The name of a role whose objects will be dropped, and whose
|
|
|
|
privileges will be revoked.
|
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
|
|
|
<varlistentry>
|
|
|
|
<term><literal>CASCADE</literal></term>
|
|
|
|
<listitem>
|
|
|
|
<para>
|
2016-08-13 00:45:18 +02:00
|
|
|
Automatically drop objects that depend on the affected objects,
|
|
|
|
and in turn all objects that depend on those objects
|
2017-11-23 15:39:47 +01:00
|
|
|
(see <xref linkend="ddl-depend"/>).
|
2006-04-02 06:02:40 +02:00
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
|
|
|
<varlistentry>
|
|
|
|
<term><literal>RESTRICT</literal></term>
|
|
|
|
<listitem>
|
|
|
|
<para>
|
|
|
|
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.
|
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
</variablelist>
|
2005-11-21 13:49:33 +01:00
|
|
|
</refsect1>
|
|
|
|
|
|
|
|
<refsect1>
|
|
|
|
<title>Notes</title>
|
|
|
|
<para>
|
2006-04-02 06:02:40 +02:00
|
|
|
<command>DROP OWNED</command> is often used to prepare for the
|
|
|
|
removal of one or more roles. Because <command>DROP OWNED</command>
|
|
|
|
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.
|
2005-11-21 13:49:33 +01:00
|
|
|
</para>
|
|
|
|
|
|
|
|
<para>
|
Update reference documentation on may/can/might:
Standard English uses "may", "can", and "might" in different ways:
may - permission, "You may borrow my rake."
can - ability, "I can lift that log."
might - possibility, "It might rain today."
Unfortunately, in conversational English, their use is often mixed, as
in, "You may use this variable to do X", when in fact, "can" is a better
choice. Similarly, "It may crash" is better stated, "It might crash".
2007-02-01 00:26:05 +01:00
|
|
|
Using the <literal>CASCADE</literal> option might make the command
|
2006-04-02 06:02:40 +02:00
|
|
|
recurse to objects owned by other users.
|
2005-11-21 13:49:33 +01:00
|
|
|
</para>
|
|
|
|
|
|
|
|
<para>
|
Improve <xref> vs. <command> formatting in the documentation
SQL commands are generally marked up as <command>, except when a link
to a reference page is used using <xref>. But the latter doesn't
create monospace markup, so this looks strange especially when a
paragraph contains a mix of links and non-links.
We considered putting <command> in the <refentrytitle> on the target
side, but that creates some formatting side effects elsewhere.
Generally, it seems safer to solve this on the link source side.
We can't put the <xref> inside the <command>; the DTD doesn't allow
this. DocBook 5 would allow the <command> to have the linkend
attribute itself, but we are not there yet.
So to solve this for now, convert the <xref>s to <link> plus
<command>. This gives the correct look and also gives some more
flexibility what we can put into the link text (e.g., subcommands or
other clauses). In the future, these could then be converted to
DocBook 5 style.
I haven't converted absolutely all xrefs to SQL command reference
pages, only those where we care about the appearance of the link text
or where it was otherwise appropriate to make the appearance match a
bit better. Also in some cases, the links where repetitive, so in
those cases the links where just removed and replaced by a plain
<command>. In cases where we just want the link and don't
specifically care about the generated link text (typically phrased
"for further information see <xref ...>") the xref is kept.
Reported-by: Dagfinn Ilmari Mannsåker <ilmari@ilmari.org>
Discussion: https://www.postgresql.org/message-id/flat/87o8pco34z.fsf@wibble.ilmari.org
2020-10-03 16:16:51 +02:00
|
|
|
The <link linkend="sql-reassign-owned"><command>REASSIGN OWNED</command></link> command is an alternative that
|
2006-04-02 06:02:40 +02:00
|
|
|
reassigns the ownership of all the database objects owned by one or
|
2017-10-09 03:44:17 +02:00
|
|
|
more roles. However, <command>REASSIGN OWNED</command> does not deal with
|
2015-10-07 22:12:05 +02:00
|
|
|
privileges for other objects.
|
2005-11-21 13:49:33 +01:00
|
|
|
</para>
|
2010-04-02 19:29:22 +02:00
|
|
|
|
|
|
|
<para>
|
2013-01-28 21:46:47 +01:00
|
|
|
Databases and tablespaces owned by the role(s) will not be removed.
|
2010-04-02 19:29:22 +02:00
|
|
|
</para>
|
2015-10-07 22:12:05 +02:00
|
|
|
|
|
|
|
<para>
|
2017-11-23 15:39:47 +01:00
|
|
|
See <xref linkend="role-removal"/> for more discussion.
|
2015-10-07 22:12:05 +02:00
|
|
|
</para>
|
2005-11-21 13:49:33 +01:00
|
|
|
</refsect1>
|
|
|
|
|
|
|
|
<refsect1>
|
|
|
|
<title>Compatibility</title>
|
|
|
|
|
|
|
|
<para>
|
2015-10-07 22:12:05 +02:00
|
|
|
The <command>DROP OWNED</command> command is a
|
2005-11-21 13:49:33 +01:00
|
|
|
<productname>PostgreSQL</productname> extension.
|
|
|
|
</para>
|
|
|
|
</refsect1>
|
|
|
|
|
|
|
|
<refsect1>
|
|
|
|
<title>See Also</title>
|
|
|
|
|
|
|
|
<simplelist type="inline">
|
2017-11-23 15:39:47 +01:00
|
|
|
<member><xref linkend="sql-reassign-owned"/></member>
|
|
|
|
<member><xref linkend="sql-droprole"/></member>
|
2005-11-21 13:49:33 +01:00
|
|
|
</simplelist>
|
|
|
|
</refsect1>
|
|
|
|
|
|
|
|
</refentry>
|