ALTER_TEXT_SEARCH_PARSER(7pg17)

πŸ“¦ version 17.11, in opensuse-leap 16.0

πŸ’… ALTER TEXT SEARCH PARSER πŸ’…

okay bestie, real talk: this one's from the PostgreSQL 17 docs (the 7 manual, iykyk) and it's honestly a tiny little icon of a command. no cap, it does like two things total and both of them are "give it a different name." slay.


✨ 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 🌸

ALTER TEXT SEARCH PARSER changes the definition of a text search parser. literally that's the whole vibe πŸ’…

and like… currently, the only supported functionality is to change the parser's name. that's it. that's the feature set. she's minimal but she's iconic.

⚠️ heads up bestie: you must be a superuser to use ALTER TEXT SEARCH PARSER. no superuser, no slay. it's giving exclusive.

πŸŽ€ PARAMETERS πŸŽ€

  • name β€” the name (optionally schema-qualified) of an existing text search parser. like, the one you're about to mess with πŸ’–
  • new_name β€” the new name of the text search parser. glow-up name, basically ✨
  • new_schema β€” the new schema for the text search parser. moving her to a different neighborhood 🏑

🌈 COMPATIBILITY 🌈

there is no ALTER TEXT SEARCH PARSER statement in the SQL standard. not a single crumb. πŸ“ so if you're out here looking for it in the standard, don't bother β€” it's not there, fr fr.


πŸ‘‘ SEE ALSO πŸ‘‘


🫢 and that's the whole page, bestie. this masterpiece is PostgreSQL 17.11, dated 2026 β€” go forth and rename responsibly. periodt. πŸ’œπŸ§šβ€β™€οΈ

πŸ“¦ where this page comes from