CREATE_TEXT_SEARCH_PARSER(7pg17)

🌸 NAME 🌸

CREATE_TEXT_SEARCH_PARSER — define a new text search parser

okay bestie, welcome to the CREATE_TEXT_SEARCH_PARSER(7pg17) page 💅 this is the PostgreSQL 17.11 Documentation moment where we learn how to make a brand-new text search parser. iconic behavior, honestly.

---

✨ SYNOPSIS ✨

CREATE TEXT SEARCH PARSER name (
    START = start_function ,
    GETTOKEN = gettoken_function ,
    END = end_function ,
    LEXTYPES = lextypes_function
    [, HEADLINE = headline_function ]
)

---

🦋 DESCRIPTION 🦋

So CREATE TEXT SEARCH PARSER creates a new text search parser. A text search parser defines a method for splitting a text string into tokens and assigning types (categories) to the tokens. it's literally the tokenizer vibe-setter 🎀

A parser is not particularly useful by itself, but must be bound into a text search configuration along with some text search dictionaries to be used for searching. so like… it needs its little configuration friend group to actually do anything 🫶

If a schema name is given then the text search parser is created in the specified schema. Otherwise it is created in the current schema. no cap.

🚨 superuser check, bestie: You must be a superuser to use CREATE TEXT SEARCH PARSER. (This restriction is made because an erroneous text search parser definition could confuse or even crash the server.) and we do not want the server catching strays 😭

Refer to Chapter 12 for further information. that's the deep lore iykyk.

---

💖 PARAMETERS 💖

• name — The name of the text search parser to be created. The name can be schema-qualified. so you can drop it in a schema if you need to 💫
• start_function — The name of the start function for the parser.
• gettoken_function — The name of the get-next-token function for the parser.
• end_function — The name of the end function for the parser.
• lextypes_function — The name of the lextypes function for the parser (a function that returns information about the set of token types it produces).
• headline_function — The name of the headline function for the parser (a function that summarizes a set of tokens).

The function names can be schema-qualified if necessary. Argument types are not given, since the argument list for each type of function is predetermined. All except the headline function are required. yes, headline_function is the optional little bonus star ⭐

The arguments can appear in any order, not only the one shown above. so feel free to switch up the lineup — no need to copy the synopsis like it's a group photo 🧚

---

🌈 COMPATIBILITY 🌈

There is no CREATE TEXT SEARCH PARSER statement in the SQL standard. it's giving PostgreSQL-specific main character energy 👑

---

🔥 SEE ALSO 🔥

• ALTER TEXT SEARCH PARSER (ALTER_TEXT_SEARCH_PARSER(7))
• DROP TEXT SEARCH PARSER (DROP_TEXT_SEARCH_PARSER(7))

---

and that's the page, bestie 💜 brought to you by PostgreSQL 17.11, dated 2026. slay responsibly 🫶✨