DROP_TEXT_SEARCH_CONFIGURATION(7pg17)

okay bestie, this is the DROP TEXT SEARCH CONFIGURATION page straight out of the PostgreSQL 17.11 documentation, and it is lowkey the “yeet that text search configuration” command. no cap 💅

💖 NAME 💖

DROP_TEXT_SEARCH_CONFIGURATION — remove a text search configuration.

✨ SYNOPSIS ✨

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

🦋 DESCRIPTION 🦋

DROP TEXT SEARCH CONFIGURATION drops an existing text search configuration. tiny catch though: to execute this command you must be the owner of the configuration. owner energy required, periodt 👑

🎀 PARAMETERS 🎀

• IF EXISTS — do not throw an error if the text search configuration does not exist. a notice is issued in this case. so it’s like “bestie, it’s already gone” but in notice form 🫶
• name — the name (optionally schema-qualified) of an existing text search configuration.
• 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 ✨
• RESTRICT — refuse to drop the text search configuration if any objects depend on it. this is the default. so restrictive is the default vibe 🎀

🍓 EXAMPLES 🍓

remove the text search configuration my_english:

DROP TEXT SEARCH CONFIGURATION my_english;

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. like, the indexes are clingy, and CASCADE is the friend who helps you pack 😭💖

🌈 COMPATIBILITY 🌈

there is no DROP TEXT SEARCH CONFIGURATION statement in the SQL standard. not in the standard, no cap 💀

💜 SEE ALSO 💜

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

---

footer sign-off, bestie: PostgreSQL 17.11, 2026, and the DROP TEXT...IGURATION(7) tag. mwah 💋✨