PostgreSQL
Description
DROP EXTENSION removes extensions from the database. Dropping an extension causes its member objects, and other explicitly dependent routines (see ALTER ROUTINE, the `DEPENDS ON EXTENSION +`_`+extension_name`_ action), to be dropped as well.
You must own the extension to use DROP EXTENSION.
Parameters
IF EXISTS-
Do not throw an error if the extension does not exist. A notice is issued in this case.
- `name`
-
The name of an installed extension.
CASCADE-
Automatically drop objects that depend on the extension, and in turn all objects that depend on those objects (see Section 5.14).
RESTRICT-
This option prevents the specified extensions from being dropped if other objects, besides these extensions, their members, and their explicitly dependent routines, depend on them. This is the default.
Examples
To remove the extension hstore from the current database:
DROP EXTENSION hstore;This command will fail if any of hstore’s objects are in use in the database, for example if any tables have columns of the `hstore type. Add the CASCADE option to forcibly remove those dependent objects as well.
See Also
[.refentrytitle#CREATE EXTENSION], ALTER EXTENSION#
| Prev | Up | Next |
|---|---|---|
DROP EVENT TRIGGER |
DROP FOREIGN DATA WRAPPER |
Submit correction
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.
Copyright © 1996-2023 The PostgreSQL Global Development Group