DROP_TEXT_SEARCH_CONFIGURATION(7pg16)

💅 NAME 💅

DROP_TEXT_SEARCH_CONFIGURATION — bestie, this is the command that removes a text search configuration. Manual page DROP_TEXT_SEARCH_CONFIGURATION(7pg16), straight from the PostgreSQL 16.15 docs. We love a cleanup moment. ✨

🦋 SYNOPSIS 🦋

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

🌸 DESCRIPTION 🌸

Okay so DROP TEXT SEARCH CONFIGURATION drops an existing text search configuration. To execute this command you must be the owner of the configuration. Owner energy only, no cap. 👑

🎀 PARAMETERS 🎀

• IF EXISTS — do not throw an error if the text search configuration does not exist. A notice is issued in this case. Lowkey forgiving. 🫶
• name — the name (optionally schema-qualified) of an existing text search configuration. Yes, schema-qualified is allowed. 💅
• CASCADE — automatically drop objects that depend on the text search configuration, and in turn all objects that depend on those objects (see Section 5.14). It's giving “clean up the whole friend group.” 🧹
• RESTRICT — refuse to drop the text search configuration if any objects depend on it. This is the default. It's the “nope, not touching that” setting. 🙈

🔥 EXAMPLES 🔥

Remove the text search configuration my_english:

DROP TEXT SEARCH CONFIGURATION my_english;

Heads up bestie: 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. 💀

🌈 COMPATIBILITY 🌈

There is no DROP TEXT SEARCH CONFIGURATION statement in the SQL standard. Periodt. 💅

👑 SEE ALSO 👑

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

💖 cute sign-off: source/version is PostgreSQL 16.15, dated 2026. Go forth and drop responsibly, bestie. 🎀🦋💜