DROP_CONVERSION(7)

💖 DROP_CONVERSION 💖

okay bestie, this is the DROP_CONVERSION page from the PostgreSQL 18.6 docs, and it's honestly a short one so we're gonna get through it together, no stress 🌸

---

✨ SYNOPSIS ✨

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

that's it. that's the whole thing. she's compact 👑

---

🦋 DESCRIPTION 🦋

so DROP CONVERSION removes a conversion that was previously defined. that's the whole job. she's a deleter, she's a closer, she's the "we don't need this anymore" friend 💅

⚠️ but listen — to be able to drop a conversion, you must own the conversion. no ownership, no dropping. that's the vibe check and you have to pass it 🫶

---

🎀 PARAMETERS 🎀

• IF EXISTS — do not throw an error if the conversion doesn't exist. instead, a notice gets issued in this case. it's giving "no big deal, moving on" 😌✨
• name — the name of the conversion. and yes, the conversion name can be schema-qualified, so go off with your myschema.myconversion energy 🌈
• CASCADE, RESTRICT — okay so these key words do not have any effect, because there are no dependencies on conversions. they're just here, hanging out, looking pretty, doing literally nothing 💀 iconic honestly

---

🌸 EXAMPLES 🌸

to drop the conversion named myname:

DROP CONVERSION myname;

boom. gone. slay ✨

---

💜 COMPATIBILITY 💜

so here's the tea ☕ — there is no DROP CONVERSION statement in the SQL standard. instead, the standard has a DROP TRANSLATION statement that goes along with the CREATE TRANSLATION statement, which is similar to the CREATE CONVERSION statement in PostgreSQL. so like, same energy, different name, iykyk 🙈

---

🧚 SEE ALSO 🧚

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

go read those too, they're the prequel and the glow-up 💖

---

okay that's the whole page bestie, you ate that 🍓💅

this has been PostgreSQL 18.6, dated 2026 — DROP CONVERSION(7) — mwah, take care of yourself, drink water, and don't drop conversions you don't own 🫶✨