DROP_CONVERSION(7pg16)

🌸 NAME 🌸

DROP_CONVERSION — remove a conversion

🎀 SYNOPSIS 🎀

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

✨ DESCRIPTION ✨

Okay bestie, listen up: DROP CONVERSION removes a conversion that was previously defined. That's literally the whole job. 💖

But important: to be able to drop a conversion, you must own the conversion. Ownership is the gatekeeping here, no cap. 🔑

💅 PARAMETERS 💅

• IF EXISTS — do not throw an error if the conversion does not exist. In that case, a notice is issued. So it's giving "gentle heads-up" instead of dramatic crash. 🫶
• name — the name of the conversion. The conversion name can be schema-qualified. Slay. 🦋
• CASCADE — this key word does not have any effect, since there are no dependencies on conversions. 💀
• RESTRICT — this key word also does not have any effect, since there are no dependencies on conversions. Same energy, zero effect. 💀

🌈 EXAMPLES 🌈

To drop the conversion named myname:

DROP CONVERSION myname;

Periodt. That's the example, and it ate. 🎀

🧚 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, and that is similar to the CREATE CONVERSION statement in PostgreSQL. So yeah — SQL standard is like "not here," but PostgreSQL has its own little translation-related situation. iykyk. 🌸

👑 SEE ALSO 👑

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

---

mwah 💋 this page is from the PostgreSQL 16.15 documentation, dated 2026, and the manual page is DROP CONVERSION(7). Go forth and drop responsibly, bestie. 🫶✨