CREATE_TEXT_SEARCH_CONFIGURATION(7pg17)

💖 CREATE_TEXT_SEARCH_CONFIGURATION 💖

okay bestie, welcome to the 7pg17 manual page for CREATE_TEXT_SEARCH_CONFIGURATION — PostgreSQL 17.11 documentation, and yes we're gonna make text search configs make sense. 🫶

---

🌸 NAME 🌸

CREATE_TEXT_SEARCH_CONFIGURATION — define a new text search configuration. That's it, that's the name, no cap. 💅

✨ SYNOPSIS ✨

CREATE TEXT SEARCH CONFIGURATION name (
    PARSER = parser_name |
    COPY = source_config
)

🦋 DESCRIPTION 🦋

So CREATE TEXT SEARCH CONFIGURATION literally creates a new text search configuration. A text search configuration is the whole setup: it specifies a text search parser that can divide a string into tokens, plus dictionaries that can be used to determine which tokens are of interest for searching. It's giving "tokenizer meets dictionary gatekeeping" energy, and honestly? iconic. 💅

If you only specify the parser, then the new text search configuration initially has no mappings from token types to dictionaries, and therefore will ignore all words. Yep, all of them. 😭 Subsequent ALTER TEXT SEARCH CONFIGURATION commands must be used to create mappings to make the configuration useful. Alternatively, an existing text search configuration can be copied. Copy-paste slay. 📋✨

If a schema name is given then the text search configuration is created in the specified schema. Otherwise it is created in the current schema. Lowkey important, bestie. 🫶

The user who defines a text search configuration becomes its owner. Main character energy, fr fr. 👑

Refer to Chapter 12 for further information. That's the deep lore — go read it. 📖

🎀 PARAMETERS 🎀

• name — the name of the text search configuration to be created. The name can be schema-qualified. 🏷️
• parser_name — the name of the text search parser to use for this configuration. 🔍
• source_config — the name of an existing text search configuration to copy. 📋

💜 NOTES 💜

The PARSER and COPY options are mutually exclusive, because when an existing configuration is copied, its parser selection is copied too. So don't try to do both, bestie — that's not a vibe. 🚫💀

🌈 COMPATIBILITY 🌈

There is no CREATE TEXT SEARCH CONFIGURATION statement in the SQL standard. Not a single one. 💀

🔥 SEE ALSO 🔥

• ALTER TEXT SEARCH CONFIGURATION (ALTER_TEXT_SEARCH_CONFIGURATION(7)) 🌸
• DROP TEXT SEARCH CONFIGURATION (DROP_TEXT_SEARCH_CONFIGURATION(7)) 🦋

---

that's the whole page, bestie. xoxo, PostgreSQL 17.11 documentation from 2026, page CREATE TE...IGURATION(7) 💅✨