DROP_CONVERSION(7pg14)

🦋 DROP_CONVERSION(7pg14) — the manual page, but make it bestie 🦋

okay bestie, this is the DROP_CONVERSION page from the PostgreSQL 14.24 Documentation, and we're about to remove a conversion together. It's giving "cleanup era" ✨ no cap. Let's go.

✨ NAME ✨

DROP_CONVERSION — remove a conversion 💅

🫶 SYNOPSIS 🫶

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

🌸 DESCRIPTION 🌸

DROP CONVERSION removes a previously defined conversion. To be able to drop a conversion, you must own the conversion. That's the whole rule, bestie — ownership is the vibe check here 👑.

💅 PARAMETERS 💅

• IF EXISTS — do not throw an error if the conversion does not exist. A notice is issued in this case. So no dramatic crash, just a lil notice 🫶
• name — the name of the conversion. The conversion name can be schema-qualified ✨
• CASCADE — this key word does not have any effect, since there are no dependencies on conversions. Literally just vibes 💀
• RESTRICT — this key word does not have any effect either, since there are no dependencies on conversions. Same energy 🌸

🎀 EXAMPLES 🎀

To drop the conversion named myname:

DROP CONVERSION myname;

Slay, that's the example 🎀.

🦋 COMPATIBILITY 🦋

Real talk: 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. It's giving "same-ish family, different name" 😭.

🌈 SEE ALSO 🌈

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

---

that's the whole page, bestie 🫶 the footer vibe is PostgreSQL 14.24, 2026 — and this was DROP CONVERSION(7). go be iconic with your conversions 💖✨