From 5e45211a64149b3c659b90ff2de6fa982a5a93ed Mon Sep 17 00:00:00 2001 From: Daniel Baumann Date: Sat, 4 May 2024 14:17:33 +0200 Subject: Adding upstream version 15.5. Signed-off-by: Daniel Baumann --- doc/src/sgml/html/manage-ag-dropdb.html | 28 ++++++++++++++++++++++++++++ 1 file changed, 28 insertions(+) create mode 100644 doc/src/sgml/html/manage-ag-dropdb.html (limited to 'doc/src/sgml/html/manage-ag-dropdb.html') diff --git a/doc/src/sgml/html/manage-ag-dropdb.html b/doc/src/sgml/html/manage-ag-dropdb.html new file mode 100644 index 0000000..55215da --- /dev/null +++ b/doc/src/sgml/html/manage-ag-dropdb.html @@ -0,0 +1,28 @@ + +23.5. Destroying a Database
23.5. Destroying a Database
Prev UpChapter 23. Managing DatabasesHome Next

23.5. Destroying a Database

+ Databases are destroyed with the command + DROP DATABASE: +

+DROP DATABASE name;
+

+ Only the owner of the database, or + a superuser, can drop a database. Dropping a database removes all objects + that were + contained within the database. The destruction of a database cannot + be undone. +

+ You cannot execute the DROP DATABASE command + while connected to the victim database. You can, however, be + connected to any other database, including the template1 + database. + template1 would be the only option for dropping the last user database of a + given cluster. +

+ For convenience, there is also a shell program to drop + databases, dropdb: +

+dropdb dbname
+

+ (Unlike createdb, it is not the default action to drop + the database with the current user name.) +

Prev Up Next
23.4. Database Configuration Home 23.6. Tablespaces
\ No newline at end of file -- cgit v1.2.3