ALTER_TEXT_SEARCH_PARSER(7pg16)

✨ NAME ✨

okay so bestie, welcome to the ALTER_TEXT_SEARCH_PARSER(7pg16) page 💅 — we're talking about ALTER_TEXT_SEARCH_PARSER, the statement that changes the definition of a text search parser. Yes, the parser itself. It's giving “definition makeover,” but make it official. 🎀

📜 SYNOPSIS 📜

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

🌸 DESCRIPTION 🌸

ALTER TEXT SEARCH PARSER changes the definition of a text search parser. Currently, the only supported functionality is to change the parser's name. Lowkey iconic, highkey niche, and we're obsessed with the specificity. ✨

🚨 Superuser check: you must be a superuser to use ALTER TEXT SEARCH PARSER. No cap. If you're not a superuser, this is not your moment. 💀

🎀 PARAMETERS 🎀

• name — the name (optionally schema-qualified) of an existing text search parser. That's the parser you're about to alter, bestie. 🦋
• new_name — the new name of the text search parser. Slay, new identity. 💖
• new_schema — the new schema for the text search parser. Moving it into a new schema era. 🌈

💫 COMPATIBILITY 💫

There is no ALTER TEXT SEARCH PARSER statement in the SQL standard. So if the SQL standard says otherwise, bestie, it did not. 🙈

🔗 SEE ALSO 🔗

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

🫶 This page is PostgreSQL 16.15, dated 2026 — that's the source/version and date vibe, and that's the cute little curtsy at the end. Bye bestie! 💖✨