ALTER_LANGUAGE(7)

💖 ALTER_LANGUAGE — bestie edition 💖

okay so this is the ALTER_LANGUAGE(7) page from the PostgreSQL 18.6 docs and honestly? it's a short one. we love a low-maintenance icon. ✨

---

🌸 NAME 🌸

ALTER_LANGUAGE — change the definition of a procedural language

like, you're editing a language's whole vibe. that's it. that's the job. 💅

---

✨ SYNOPSIS ✨

ALTER [ PROCEDURAL ] LANGUAGE name RENAME TO new_name
ALTER [ PROCEDURAL ] LANGUAGE name OWNER TO { new_owner | CURRENT_ROLE | CURRENT_USER | SESSION_USER }

look at her. two whole lines. no notes. 🎀

---

🦋 DESCRIPTION 🦋

so ALTER LANGUAGE changes the definition of a procedural language. that's the whole plot.

the only functionality here is renaming the language or assigning it a new owner. that's it. no secret extra features, no hidden menu. she does two things and she does them well. 👑

🚨 important bestie: you must be a superuser or the owner of the language to use ALTER LANGUAGE. no sneaking in. the vibe check is strict and the permissions are real.

---

💜 PARAMETERS 💜

• name — name of a language 🌈
• new_name — the new name of the language ✨ (glow-up name change, we support it)
• new_owner — the new owner of the language 👑 (passing the crown, iconic behaviour)

---

💀 COMPATIBILITY 💀

there is no ALTER LANGUAGE statement in the SQL standard. not a thing. doesn't exist. PostgreSQL said "we'll do it ourselves" and honestly? slay. 🫶

---

🌟 SEE ALSO 🌟

• CREATE LANGUAGE (CREATE_LANGUAGE(7)) 🌱 — making the language in the first place
• DROP LANGUAGE (DROP_LANGUAGE(7)) 💥 — yeeting it entirely

---

that's the whole page, bestie, you ate it. this was PostgreSQL 18.6 documentation, dated 2026, and ALTER_LANGUAGE(7) is officially understood. go rename something responsibly. 🎀💖✨🦋