DROP DATABASE — remove a database
DROP DATABASE [ IF EXISTS ]
name[ [ WITH ] (
option[, ...] ) ] where
optioncan be: FORCE
DROP DATABASE 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. It cannot be executed while you are connected to the target database. (Connect to
postgres 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
FORCE option described below.
DROP DATABASE cannot be undone. Use it with care!
Do not throw an error if the database does not exist. A notice is issued in this case.
The name of the database to remove.
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.
This will fail if the current user has no permissions to terminate other connections. Required permissions are the same as with
pg_terminate_backend, described in Section 9.27.2. This will also fail if we are not able to terminate connections.
DROP DATABASE cannot be executed inside a transaction block.
This command cannot be executed while connected to the target database. Thus, it might be more convenient to use the program dropdb instead, which is a wrapper around this command.
There is no
DROP DATABASE statement in the SQL standard.
If you see anything in the documentation that is not correct, does not match your experience with the particular feature or requires further clarification, please use this form to report a documentation issue.