DROP_OPERATOR_CLASS(7pg18)

💖 DROP_OPERATOR_CLASS 💖

okay bestie, gather round, because we're about to talk about PostgreSQL 18.6 and the lil command that yeets an operator class into the void. it's giving "spring cleaning but for your database" energy and honestly? we love to see it. 🧹✨

---

✨ NAME ✨

DROP_OPERATOR_CLASS — remove an operator class 💅

---

🌸 SYNOPSIS 🌸

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

---

🦋 DESCRIPTION 🦋

DROP OPERATOR CLASS drops an existing operator class. periodt. but lowkey there's a catch: to run this command you must be the owner of the operator class. no ownership, no dropping, sorry babe. 💀

also, important: DROP OPERATOR CLASS does not drop any of the operators or functions referenced by the class. it's just out here removing the class itself, minding its own business, not touching the ops or the functions. 🙈

and if there are any indexes depending on the operator class? you're gonna need to specify CASCADE for the drop to actually complete. no CASCADE, no completion. that's just the vibe check. 🫶

---

🎀 PARAMETERS 🎀

• IF EXISTS — do not throw an error if the operator class does not exist. a notice is issued in this case. it's like "eh, she's not here, moving on." 😌
• name — the name (optionally schema-qualified) of an existing operator class. yes, you can give it the whole address if you're feeling fancy. 🏠
• index_method — the name of the index access method the operator class is for. like btree and friends, iykyk. 🌈
• 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). it's the domino effect, bestie. one falls, they all fall. 🁳💥
• RESTRICT — refuse to drop the operator class if any objects depend on it. this is the default. she's cautious, she's careful, she's not about to cause chaos. 👑

---

👑 NOTES 👑

so here's the tea: 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, fr fr. but if you're a tidy queen and it's bugging you, you might wish to remove the family with DROP OPERATOR FAMILY; or perhaps better, use DROP OPERATOR FAMILY in the first place. main character foresight, honestly. 🧚✨

---

🌸 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. go on, hit it with the CASCADE, you know you want to. 💅

---

💜 COMPATIBILITY 💜

there is no DROP OPERATOR CLASS statement in the SQL standard. it's simply not a thing there. we're built different. ⭐

---

🌈 SEE ALSO 🌈

• ALTER OPERATOR CLASS (ALTER_OPERATOR_CLASS(7))
• CREATE OPERATOR CLASS (CREATE_OPERATOR_CLASS(7))
• DROP OPERATOR FAMILY (DROP_OPERATOR_FAMILY(7))

---

and that's the whole page, bestie!! this was PostgreSQL 18.6, dated 2026, brought to you by the DROP OPERATOR CLASS(7) manual page itself. now go forth and drop responsibly, and remember: you're the owner or you're not doing it at all. mwah 💖🦋🎀