Horton

Introduce the 'force' option for the Drop Database command.

Amit Kapila <akapila@postgresql.org>

View on postgr.es
Commit: 1379fd537f9fc7941c8acff8c879ce3636dbdb77
Author: Amit Kapila <akapila@postgresql.org>
Date: 2019-11-13T02:55:33Z
Releases: 13.0 
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

Files

PathChange+/−
doc/src/sgml/ref/drop_database.sgml modified +29 −4
src/backend/commands/dbcommands.c modified +33 −1
src/backend/nodes/copyfuncs.c modified +1 −0
src/backend/nodes/equalfuncs.c modified +1 −0
src/backend/parser/gram.y modified +42 −1
src/backend/storage/ipc/procarray.c modified +114 −0
src/backend/tcop/utility.c modified +3 −7
src/bin/psql/tab-complete.c modified +4 −0
src/include/commands/dbcommands.h modified +2 −1
src/include/nodes/parsenodes.h modified +1 −0
src/include/storage/procarray.h modified +1 −0
src/test/regress/expected/drop_if_exists.out modified +10 −0
src/test/regress/sql/drop_if_exists.sql modified +7 −0

Documentation touched

Discussion