ALTER_TEXT_SEARCH_PARSER(7)

✨ ALTER_TEXT_SEARCH_PARSER ✨

okay bestie, this one's from the PostgreSQL 18.6 Documentation and it's literally the glow-up page for your text search parsers 💅

---

🌸 NAME 🌸

ALTER_TEXT_SEARCH_PARSER — change the definition of a text search parser

---

🎀 SYNOPSIS 🎀

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

---

🦋 DESCRIPTION 🦋

So ALTER TEXT SEARCH PARSER changes the definition of a text search parser. That's the whole vibe.

Now, currently, the only supported functionality is to change the parser's name. That's it. That's the plot. Don't come in here expecting more, because rn there isn't more. 🙈

⚠️ bestie you must be a superuser to use ALTER TEXT SEARCH PARSER. No superuser, no parser renaming, no exceptions. it's giving exclusive 💀

---

💖 PARAMETERS 💖

• name — the name (optionally schema-qualified) of an existing text search parser. yes, you can qualify it with the schema, go off 👑
• new_name — the new name of the text search parser. the rebrand, the new era, the main character name change ✨
• new_schema — the new schema for the text search parser. moving it to a whole new neighborhood, we love a relocation 🏡

---

🌈 COMPATIBILITY 🌈

ngl there is no ALTER TEXT SEARCH PARSER statement in the SQL standard. not a thing. doesn't exist. this is a Postgres-exclusive situation, iykyk 🫶

---

⭐ SEE ALSO ⭐

• CREATE TEXT SEARCH PARSER (CREATE_TEXT_SEARCH_PARSER(7))
• DROP TEXT SEARCH PARSER (DROP_TEXT_SEARCH_PARSER(7))

---

and that's the whole page, bestie!! this iconic lil doc came to you straight from PostgreSQL 18.6, dated 2026, and fr fr it ate 💅✨ go rename something, you superuser you 👑