DROP_CONVERSION(7pg13)

okay so bestie, welcome to the DROP_CONVERSION(7) page from the PostgreSQL 13.23 Documentation — we’re talking about removing a conversion, and yes, it’s giving very specific permissions energy 💅

✨ NAME ✨

DROP_CONVERSION — remove a conversion 🎀

🦋 SYNOPSIS 🦋

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

🌸 DESCRIPTION 🌸

DROP CONVERSION removes a previously defined conversion. Lowkey important: to be able to drop a conversion, you must own the conversion. No ownership? No drop, bestie. Periodt. 👑

💖 PARAMETERS 💖

• IF EXISTS — do not throw an error if the conversion does not exist. In this case, a notice is issued. So it’s like, “okay, she’s not here, moving on” instead of a whole dramatic error 😭
• name — the name of the conversion. The conversion name can be schema-qualified, iykyk ✨
• CASCADE — these key words do not have any effect, since there are no dependencies on conversions. So she’s just there, vibing 🫶
• RESTRICT — same deal: these key words do not have any effect, since there are no dependencies on conversions. Iconic but functionally irrelevant 💀

🌈 EXAMPLES 🌈

To drop the conversion named myname:

DROP CONVERSION myname;

⭐ COMPATIBILITY ⭐

There is no DROP CONVERSION statement in the SQL standard, but a DROP TRANSLATION statement that goes along with the CREATE TRANSLATION statement that is similar to the CREATE CONVERSION statement in PostgreSQL. So yeah — PostgreSQL is doing its own cute thing here 🦋

👑 SEE ALSO 👑

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

mwah 💋 — this little manual moment comes from PostgreSQL 13.23, dated 2025, and the page is DROP CONVERSION(7). slay and stay schema-qualified, bestie 💜