ALTER_TEXT_SEARCH_PARSER(7pg15)

💅 ALTER_TEXT_SEARCH_PARSER 💅

okay so bestie, welcome to the ALTER TEXT SEARCH PARSER page from the PostgreSQL 15.19 docs (it's a section 7 manual page, iykyk) — the glow-up page for your text search parsers ✨

---

🌸 NAME 🌸

ALTER_TEXT_SEARCH_PARSER — literally the command that changes the definition of a text search parser. that's the whole vibe 🫶

---

🎀 SYNOPSIS 🎀

ALTER TEXT SEARCH PARSER name RENAME TO new_name
ALTER TEXT SEARCH PARSER name SET SCHEMA new_schema

two whole moods, pick your fighter 💖

---

✨ DESCRIPTION ✨

so ALTER TEXT SEARCH PARSER changes the definition of a text search parser. iconic behavior honestly.

Currently, the only supported functionality is changing the parser's name — like, that's the only thing it does rn, no cap. not me expecting more 💀

🚨 vibe check / big important thing: you must be a superuser to use ALTER TEXT SEARCH PARSER. no superuser, no parser glow-up. periodt 👑

---

🦋 PARAMETERS 🦋

• name — the name of an existing text search parser. it's optionally schema-qualified, so you can be all fancy and precise about it if you want 💅
• new_name — the new name of the text search parser. congrats on the rebrand bestie 🎀
• new_schema — the new schema for the text search parser. moving neighborhoods fr fr 🏡

---

🌈 COMPATIBILITY 🌈

ngl there is no ALTER TEXT SEARCH PARSER statement in the SQL standard. not a single one. it's giving PostgreSQL-exclusive main character energy 👑

---

🌟 SEE ALSO 🌟

• CREATE TEXT SEARCH PARSER (CREATE_TEXT_SEARCH_PARSER(7)) — for when you want to make one in the first place
• DROP TEXT SEARCH PARSER (DROP_TEXT_SEARCH_PARSER(7)) — for when it's time to say bye 🥲

---

and that's the page! mwah 💋 — brought to you by PostgreSQL 15.19, dated 2026, filed under ALTER TEX...CH PARSER(7) (yes the header really does truncate it like that, she's shy 🙈). go alter those parsers, you absolute icon 🧚‍♀️💜