DROP_CONVERSION(7pg15)

✨ NAME ✨

okay bestie, meet DROP_CONVERSION — the PostgreSQL 15.19 manual page (you might see it as DROP_CONVERSION(7pg15)) that is literally about removing a conversion. It's giving cleanup era, and it's iconic for exactly one job: remove a conversion. 💅

---

🎀 SYNOPSIS 🎀

DROP CONVERSION [ IF EXISTS ] name [ CASCADE | RESTRICT ]

---

🦋 DESCRIPTION 🦋

okay so DROP CONVERSION removes a conversion that was previously defined. To be able to drop a conversion, you must own the conversion. That's the vibe check — no ownership, no drop, periodt. 👑

---

💖 PARAMETERS 💖

• IF EXISTS — do not throw an error if the conversion does not exist. In this case, a notice is issued. No dramatic error moment, just a lil heads-up. 🙈
• name — the name of the conversion. The conversion name can be schema-qualified. It's giving location-aware, iykyk. 📍
• CASCADE — this key word does not have any effect, since there are no dependencies on conversions. 💀
• RESTRICT — this key word does not have any effect, since there are no dependencies on conversions. 💀

---

🌸 EXAMPLES 🌸

To drop the conversion named myname, you literally just:

DROP CONVERSION myname;

slay, that's it. ✨

---

🌈 COMPATIBILITY 🌈

There is no DROP CONVERSION statement in the SQL standard, but there is a DROP TRANSLATION statement that goes along with the CREATE TRANSLATION statement that is similar to the CREATE CONVERSION statement in PostgreSQL. So bestie, it's a PostgreSQL-flavored situation. 🫶

---

⭐ SEE ALSO ⭐

• ALTER CONVERSION (ALTER_CONVERSION(7))
• CREATE CONVERSION (CREATE_CONVERSION(7))

---

🌈 source/version: PostgreSQL 15.19; date: 2026; manual page: DROP CONVERSION(7) — mwah, bestie 💋🫶