DROP_CONVERSION(7pg17)

πŸ“¦ version 17.11, in opensuse-leap 16.0

πŸ’… DROP_CONVERSION β€” like, the whole manual page, bestie

okay so this is the DROP_CONVERSION page from the PostgreSQL 17.11 docs, and honestly? She's short, she's sweet, she's giving "one job and she does it." Let's get into it ✨


πŸŽ€ NAME πŸŽ€

DROP_CONVERSION β€” remove a conversion. that's it. that's the vibe. πŸ’–

πŸ¦‹ SYNOPSIS πŸ¦‹

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

look at her. so clean. so unbothered. 🌸

✨ DESCRIPTION ✨

so DROP CONVERSION removes a conversion that was, like, previously defined. gone. deleted. no cap. πŸ’€

but here's the catch, and it's a real one: to be able to drop a conversion, you must own the conversion. own it. like legally. if it's not yours, this command is literally not gonna work for you, i don't make the rules 🫢

πŸ’… PARAMETERS πŸ’…

  • IF EXISTS β€” do not throw an error if the conversion doesn't exist. instead it just issues a notice, which is the polite way of being like "bestie… there was nothing there πŸ™ˆ"
  • name β€” the name of the conversion. and yes, the conversion name can be schema-qualified, so you can be all specific about it 🎯
  • CASCADE, RESTRICT β€” okay so these key words literally do not have any effect, because there are no dependencies on conversions. they're just here hanging out. main character energy with zero lines tho 😭

🌈 EXAMPLES 🌈

to drop the conversion named myname:

DROP CONVERSION myname;

slay. done. next πŸ’…

πŸ‘‘ COMPATIBILITY πŸ‘‘

so there is no DROP CONVERSION statement in the SQL standard. nope. not a thing. πŸ™ˆ

but there is a DROP TRANSLATION statement, and it 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 πŸ“


and that's the whole page!! 🧚 this little icon was brought to you by PostgreSQL 17.11, dated 2026 β€” drop a πŸ’œ for the docs team, fr fr 🫢✨

πŸ“¦ where this page comes from