DROP_OPERATOR_FAMILY(7)

✨ DROP OPERATOR FAMILY ✨

okay bestie, welcome to DROP_OPERATOR_FAMILY, the PostgreSQL 18.6 page about yeeting an operator family out of existence 💅

---

🌸 NAME 🌸

DROP_OPERATOR_FAMILY — remove an operator family 🫶

---

🎀 SYNOPSIS 🎀

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

---

💖 DESCRIPTION 💖

So like, DROP OPERATOR FAMILY drops an existing operator family. Periodt. But heads up bestie — to run this command you must be the owner of the operator family. No ownership, no vibes, no drop. 🔥

And here's the tea 🍓: DROP OPERATOR FAMILY includes dropping any operator classes contained in the family, but it does not drop any of the operators or functions referenced by the family. Those stay exactly where they are. If there are any indexes depending on operator classes within the family, you will need to specify CASCADE for the drop to actually complete. Otherwise it's giving "no ❤️".

---

👑 PARAMETERS 👑

• IF EXISTS — Do not throw an error if the operator family does not exist. A notice is issued in this case. Like, it's not mad at you, it's just letting you know 💀
• name — The name (optionally schema-qualified) of an existing operator family.
• index_method — The name of the index access method the operator family is for.
• CASCADE — Automatically drop objects that depend on the operator family, and in turn all objects that depend on those objects (see Section 5.15). It's giving domino effect, and honestly? slay.
• RESTRICT — Refuse to drop the operator family if any objects depend on it. This is the default. It's the "actually, let's not" of the two.

---

🦋 EXAMPLES 🦋

Remove the B-tree operator family float_ops:

DROP OPERATOR FAMILY float_ops USING btree;

This command will not succeed if there are any existing indexes that use operator classes within the family. Add CASCADE to drop such indexes along with the operator family. 🔥

ngl this is the part where people get mad at the error message. it's not broken, bestie, you just gotta commit to the cascade 😭

---

🌈 COMPATIBILITY 🌈

There is no DROP OPERATOR FAMILY statement in the SQL standard. So it's giving very much "Postgres exclusive, iykyk" ✨

---

⭐ SEE ALSO ⭐

• ALTER OPERATOR FAMILY (ALTER_OPERATOR_FAMILY(7))
• CREATE OPERATOR FAMILY (CREATE_OPERATOR_FAMILY(7))
• ALTER OPERATOR CLASS (ALTER_OPERATOR_CLASS(7))
• CREATE OPERATOR CLASS (CREATE_OPERATOR_CLASS(7))
• DROP OPERATOR CLASS (DROP_OPERATOR_CLASS(7))

---

and that's the whole page, bestie — go forth and drop responsibly 🧚💜

This one's from PostgreSQL 18.6, dated 2026, and it's the DROP OPERATOR FAMILY(7) page. mwah 💋