DROP_OPERATOR_CLASS(7pg17)

πŸ“¦ version 17.11, in opensuse-leap 16.0

πŸ’… DROP OPERATOR CLASS πŸ’…

okay bestie, welcome to DROP OPERATOR CLASS(7) from the PostgreSQL 17.11 Documentation β€” this is the page where operator classes get unalived (respectfully πŸ’€βœ¨). No cap, it's giving cleanup era.


✨ NAME ✨

DROP_OPERATOR_CLASS β€” remove an operator class. literally what it says on the tin, bestie πŸŽ€

🌸 SYNOPSIS 🌸

DROP OPERATOR CLASS [ IF EXISTS ] name USING index_method [ CASCADE | RESTRICT ]

πŸ¦‹ DESCRIPTION πŸ¦‹

okay so DROP OPERATOR CLASS drops an existing operator class. To execute this command you must be the owner of the operator class β€” owner energy only, iykyk πŸ‘‘.

DROP OPERATOR CLASS does not drop any of the operators or functions referenced by the class. not me checking twice 😭. 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. polite little heads-up ✨
  • 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 Section 5.15). full domino-effect slay πŸ”₯
  • RESTRICT β€” refuse to drop the operator class if any objects depend on it. This is the default. no impulsive deletes here πŸ™ˆ

🧚 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. bestie, tidy vibes only 🌈

⭐ 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. that's the whole plot twist 😭

πŸ’œ COMPATIBILITY πŸ’œ

There is no DROP OPERATOR CLASS statement in the SQL standard. not a standard girlie, and that's iconic πŸ’…

🫢 SEE ALSO 🫢


that's the whole page, bestie 🫢 β€” PostgreSQL 17.11, dated 2026, signing off with DROP OPERATOR CLASS(7) energy. mwah πŸ’–

πŸ“¦ where this page comes from