DROP_TEXT_SEARCH_CONFIGURATION(7pg18)

✨ DROP_TEXT_SEARCH_CONFIGURATION ✨

okay bestie, we're deep in the PostgreSQL 18.6 Documentation today and this one is literally about yeeting a text search configuration out of existence 💅 it's giving "cleanup era" fr fr

---

🌸 NAME 🌸

DROP_TEXT_SEARCH_CONFIGURATION — remove a text search configuration 🗑️✨

---

🎀 SYNOPSIS 🎀

DROP TEXT SEARCH CONFIGURATION [ IF EXISTS ] name [ CASCADE | RESTRICT ]

---

💖 DESCRIPTION 💖

So DROP TEXT SEARCH CONFIGURATION drops an existing text search configuration. That's it, that's the whole vibe. 💀

But — and this is the important part, no cap — to run this command you must be the owner of the configuration. Not your friend, not your coworker, you. The database does not care about your excuses 🫶

---

🦋 PARAMETERS 🦋

• IF EXISTS — do not throw an error if the text search configuration doesn't exist. Instead, a notice is issued in this case. So like, no dramatic meltdown, just a lil "hey btw it's not there" 🥲
• name — the name (optionally schema-qualified) of an existing text search configuration. Yes you can slide the schema in there if you need to, main character energy 🎀
• CASCADE — automatically drop objects that depend on the text search configuration, and in turn all objects that depend on those objects (see Section 5.15). It's giving domino effect, it's giving chain reaction 🔥
• RESTRICT — refuse to drop the text search configuration if any objects depend on it. This is the default. She's cautious, she's responsible, she said "nope not on my watch" 🧚

---

🌈 EXAMPLES 🌈

Remove the text search configuration my_english:

DROP TEXT SEARCH CONFIGURATION my_english;

And now the plot twist 😭 — this command will not succeed if there are any existing indexes that reference the configuration in to_tsvector calls. Add CASCADE to drop such indexes along with the text search configuration. So if it's refusing to cooperate, that's why, and now you know iykyk ✨

---

⭐ COMPATIBILITY ⭐

There is no DROP TEXT SEARCH CONFIGURATION statement in the SQL standard. PostgreSQL said "we're doing our own thing" and honestly? iconic 👑

---

👑 SEE ALSO 👑

• ALTER TEXT SEARCH CONFIGURATION (ALTER_TEXT_SEARCH_CONFIGURATION(7))
• CREATE TEXT SEARCH CONFIGURATION (CREATE_TEXT_SEARCH_CONFIGURATION(7))

---

and that's the whole page bestie 💜 this was PostgreSQL 18.6, dated 2026 — go forth and drop those configurations responsibly, mwah 🍓💖