CREATE_TEXT_SEARCH_CONFIGURATION(7pg14)

💅 CREATE_TEXT_SEARCH_CONFIGURATION — the PostgreSQL 14 glow-up (that's 7pg14, bestie, write it down)

okay so picture this: it's a 7pg14 manpage, the vibe is immaculate, and it's literally all about defining a brand-new text search configuration. no cap, it's giving "main character energy" for your search setup. let's get into it 🎀

---

✨ NAME ✨

CREATE_TEXT_SEARCH_CONFIGURATION — define a new text search configuration 💖

---

🦋 SYNOPSIS 🦋

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

---

🌸 DESCRIPTION 🌸

so CREATE TEXT SEARCH CONFIGURATION creates a new text search configuration. slay. a text search configuration specifies a text search parser (the thingy that can divide a string into tokens) plus dictionaries (the things that can be used to determine which tokens are of interest for searching). that's the whole squad right there 🫶

if you only specify the parser, then lowkey your new text search configuration initially has no mappings from token types to dictionaries, and therefore will ignore all words. 😭 like, every word. gone. subsequent ALTER TEXT SEARCH CONFIGURATION commands must be used to create mappings and make the configuration actually useful. alternatively — plot twist — you can just copy an existing text search configuration. iconic behaviour honestly.

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. no notes ✨

the user who defines a text search configuration becomes its owner. it's yours now, bestie, that's your baby 👑

refer to Chapter 12 for further information if you want the deep lore 📖

---

🧚 PARAMETERS 🧚

• name — the name of the text search configuration to be created. and yes, the name can be schema-qualified. go off 💅
• parser_name — the name of the text search parser to use for this configuration. this is the tokenizer bestie of your dreams.
• source_config — the name of an existing text search configuration to copy. copy-paste but make it fashion ✨

---

💀 NOTES 💀

the PARSER and COPY options are mutually exclusive, because when an existing configuration is copied, its parser selection is copied too. so like... pick one. not both. it's giving "you can't sit with both tables" 🙈

---

🌈 COMPATIBILITY 🌈

there is literally no CREATE TEXT SEARCH CONFIGURATION statement in the SQL standard. not a single one. we're built different, iykyk ⭐

---

🔥 SEE ALSO 🔥

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

go read those next, bestie, they're the sequel and the breakup arc 🦋

---

and that's the whole page!! ty for coming to my ted talk, this was PostgreSQL 14.24, dated 2026, and the title on the tin is CREATE_TEXT_SEARCH_CONFIGURATION(7) 💜 mwah 🎀