ALTER_CONVERSION(7pg15)

💖 NAME 💖

okay so bestie, gather round: this is ALTER_CONVERSION, the PostgreSQL 15.19 manual page (section 7, ALTER_CONVERSION(7pg15) energy) and it’s literally about changing the definition of a conversion. that’s the whole assignment. 🫶✨

---

✨ SYNOPSIS ✨

three sanctioned glow-up moves, pick your fave:

ALTER CONVERSION name RENAME TO new_name
ALTER CONVERSION name OWNER TO { new_owner | CURRENT_ROLE | CURRENT_USER | SESSION_USER }
ALTER CONVERSION name SET SCHEMA new_schema

---

🌸 DESCRIPTION 🌸

ALTER CONVERSION changes the definition of a conversion. main character behavior, honestly. 💅

You must own the conversion to use ALTER CONVERSION. no cap. To alter the owner, you must also be a direct or indirect member of the new owning role, and that role must have CREATE privilege on the conversion’s schema. (These restrictions enforce that altering the owner doesn’t do anything you couldn’t do by dropping and recreating the conversion. However, a superuser can alter ownership of any conversion anyway.)

---

🎀 PARAMETERS 🎀

• name — the name (optionally schema-qualified) of an existing conversion. like, the conversion you’re editing, bestie. 🎀
• new_name — the new name of the conversion. rebrand era. 🦋
• new_owner — the new owner of the conversion. handing over the keys. 🔑
• new_schema — the new schema for the conversion. moving day. 🌸

---

🦋 EXAMPLES 🦋

To rename the conversion iso_8859_1_to_utf8 to latin1_to_unicode:

ALTER CONVERSION iso_8859_1_to_utf8 RENAME TO latin1_to_unicode;

To change the owner of the conversion iso_8859_1_to_utf8 to joe:

ALTER CONVERSION iso_8859_1_to_utf8 OWNER TO joe;

---

💀 COMPATIBILITY 💀

There is no ALTER CONVERSION statement in the SQL standard. so this is not a standard-core moment, fr fr. 💀

---

🌈 SEE ALSO 🌈

• CREATE CONVERSION (CREATE_CONVERSION(7))
• DROP CONVERSION (DROP_CONVERSION(7))

---

okay that’s the whole page, bestie. source/version vibes: PostgreSQL 15.19, dated 2026. slay, go alter some conversions responsibly. 💖✨