DROP_TEXT_SEARCH_CONFIGURATION(7pg14)

💖 NAME 💖

Okay so this is the DROP_TEXT_SEARCH_CONFIGURATION(7pg14) page from the PostgreSQL 14.24 docs, bestie — and it’s literally about how to remove a text search configuration. That’s the whole vibe. 🎀

✨ SYNOPSIS ✨

Here’s the exact shape of the command, no cap:

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

🦋 DESCRIPTION 🦋

DROP TEXT SEARCH CONFIGURATION drops an existing text search configuration. To execute this command you must be the owner of the configuration. Periodt. 💅

🌸 PARAMETERS 🌸

• IF EXISTS — Do not throw an error if the text search configuration does not exist. A notice is issued in this case — just a little FYI, not a whole meltdown. 🫶
• 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.14). Yes, it’s giving chain reaction. 🔥
• RESTRICT — Refuse to drop the text search configuration if any objects depend on it. This is the default. The safe default, periodt. 👑

🔥 EXAMPLES 🔥

Remove the text search configuration my_english:

DROP TEXT SEARCH CONFIGURATION my_english;

Ngl, 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. Sad but true. 😭

🫶 SEE ALSO 🫶

Go read these next, iykyk:

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

---

Later bestie — this page is from PostgreSQL 14.24, dated 2026. 💖✨