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/ref/drop_opclass.sgml | 149 +++++++++++++++++++++++++++++++++++++ 1 file changed, 149 insertions(+) create mode 100644 doc/src/sgml/ref/drop_opclass.sgml (limited to 'doc/src/sgml/ref/drop_opclass.sgml') diff --git a/doc/src/sgml/ref/drop_opclass.sgml b/doc/src/sgml/ref/drop_opclass.sgml new file mode 100644 index 0000000..4cb4cc3 --- /dev/null +++ b/doc/src/sgml/ref/drop_opclass.sgml @@ -0,0 +1,149 @@ + + + + + DROP OPERATOR CLASS + + + + DROP OPERATOR CLASS + 7 + SQL - Language Statements + + + + DROP OPERATOR CLASS + remove an operator class + + + + +DROP OPERATOR CLASS [ IF EXISTS ] name USING index_method [ CASCADE | RESTRICT ] + + + + + Description + + + 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. + + + + + Parameters + + + + + IF EXISTS + + + Do not throw an error if the operator class does not exist. A notice is issued + in this case. + + + + + + name + + + The name (optionally schema-qualified) of an existing operator class. + + + + + + index_method + + + The name of the index access method the operator class is for. + + + + + + CASCADE + + + Automatically drop objects that depend on the operator class (such as + indexes), and in turn all objects that depend on those objects + (see ). + + + + + + RESTRICT + + + Refuse to drop the operator class if any objects depend on it. + This is the default. + + + + + + + + Notes + + + 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. + + + + + Examples + + + Remove the B-tree operator class widget_ops: + + +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. + + + + + Compatibility + + + There is no DROP OPERATOR CLASS statement in the + SQL standard. + + + + + See Also + + + + + + + + + -- cgit v1.2.3