DROP OPERATOR CLASS — remove an operator class
DROP OPERATOR CLASS [ IF EXISTS ]
index_method[ CASCADE | RESTRICT ]
DROP OPERATOR CLASS drops an existing operator class. To execute this command you must be the owner of the operator class.
DROP OPERATOR CLASS does not drop any of the operators or functions referenced by the class. If there are any indexes depending on the operator class, you will need to specify
CASCADE for the drop to complete.
Do not throw an error if the operator class does not exist. A notice is issued in this case.
The name (optionally schema-qualified) of an existing operator class.
The name of the index access method the operator class is for.
Automatically drop objects that depend on the operator class (such as indexes), and in turn all objects that depend on those objects (see Section 5.13).
Refuse to drop the operator class if any objects depend on it. This is the default.
DROP OPERATOR CLASS will not drop the operator family containing the class, even if there is nothing else left in the family (in particular, in the case where the family was implicitly created by
CREATE OPERATOR CLASS). An empty operator family is harmless, but for the sake of tidiness you might wish to remove the family with
DROP OPERATOR FAMILY; or perhaps better, use
DROP OPERATOR FAMILY in the first place.
Remove the B-tree operator class
DROP OPERATOR CLASS widget_ops USING btree;
This command will not succeed if there are any existing indexes that use the operator class. Add
CASCADE to drop such indexes along with the operator class.
There is no
DROP OPERATOR CLASS 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.