diff options
| author | Amit Kapila <akapila@postgresql.org> | 2019-11-12 11:06:13 +0530 |
|---|---|---|
| committer | Amit Kapila <akapila@postgresql.org> | 2019-11-13 08:25:33 +0530 |
| commit | 1379fd537f9fc7941c8acff8c879ce3636dbdb77 (patch) | |
| tree | 7f74fd3cf0367c76ee511c14949c96e740a25916 /doc/src | |
| parent | 112caf9039f4c8fb286bb610461ced8253313e9f (diff) | |
| download | postgresql-1379fd537f9fc7941c8acff8c879ce3636dbdb77.tar.gz postgresql-1379fd537f9fc7941c8acff8c879ce3636dbdb77.zip | |
Introduce the 'force' option for the Drop Database command.
This new option terminates the other sessions connected to the target
database and then drop it. To terminate other sessions, the current user
must have desired permissions (same as pg_terminate_backend()). We don't
allow to terminate the sessions if prepared transactions, active logical
replication slots or subscriptions are present in the target database.
Author: Pavel Stehule with changes by me
Reviewed-by: Dilip Kumar, Vignesh C, Ibrar Ahmed, Anthony Nowocien,
Ryan Lambert and Amit Kapila
Discussion: https://postgr.es/m/CAP_rwwmLJJbn70vLOZFpxGw3XD7nLB_7+NKz46H5EOO2k5H7OQ@mail.gmail.com
Diffstat (limited to 'doc/src')
| -rw-r--r-- | doc/src/sgml/ref/drop_database.sgml | 33 |
1 files changed, 29 insertions, 4 deletions
diff --git a/doc/src/sgml/ref/drop_database.sgml b/doc/src/sgml/ref/drop_database.sgml index 3ac06c984a3..cef1b904219 100644 --- a/doc/src/sgml/ref/drop_database.sgml +++ b/doc/src/sgml/ref/drop_database.sgml @@ -21,7 +21,11 @@ PostgreSQL documentation <refsynopsisdiv> <synopsis> -DROP DATABASE [ IF EXISTS ] <replaceable class="parameter">name</replaceable> +DROP DATABASE [ IF EXISTS ] <replaceable class="parameter">name</replaceable> [ [ WITH ] ( <replaceable class="parameter">option</replaceable> [, ...] ) ] + +<phrase>where <replaceable class="parameter">option</replaceable> can be:</phrase> + + FORCE </synopsis> </refsynopsisdiv> @@ -32,9 +36,11 @@ DROP DATABASE [ IF EXISTS ] <replaceable class="parameter">name</replaceable> <command>DROP DATABASE</command> drops a database. It removes the catalog entries for the database and deletes the directory containing the data. It can only be executed by the database owner. - Also, it cannot be executed while you or anyone else are connected - to the target database. (Connect to <literal>postgres</literal> or any - other database to issue this command.) + It cannot be executed while you are connected to the target database. + (Connect to <literal>postgres</literal> or any other database to issue this + command.) + Also, if anyone else is connected to the target database, this command will + fail unless you use the <literal>FORCE</literal> option described below. </para> <para> @@ -64,6 +70,25 @@ DROP DATABASE [ IF EXISTS ] <replaceable class="parameter">name</replaceable> </para> </listitem> </varlistentry> + + <varlistentry> + <term><literal>FORCE</literal></term> + <listitem> + <para> + Attempt to terminate all existing connections to the target database. + It doesn't terminate if prepared transactions, active logical replication + slots or subscriptions are present in the target database. + </para> + <para> + This will fail if the current user has no permissions to terminate other + connections. Required permissions are the same as with + <literal>pg_terminate_backend</literal>, described in + <xref linkend="functions-admin-signal"/>. This will also fail if we + are not able to terminate connections. + </para> + </listitem> + </varlistentry> + </variablelist> </refsect1> |