DROP_TEXT_SEARCH_PARSER(7pg17)

💅 DROP_TEXT_SEARCH_PARSER 💅

okay so bestie, welcome to the DROP_TEXT_SEARCH_PARSER page — straight out of the PostgreSQL 17.11 documentation and honestly? it's giving "short but iconic." this is the glow-up where we learn how to remove a text search parser that already exists. no cap, it's not a long read, but every word slays.

---

✨ NAME ✨

DROP_TEXT_SEARCH_PARSER — the command that removes a text search parser. that's it, that's the vibe. 🎀

---

🌸 SYNOPSIS 🌸

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

look at her. so clean. so structured. the brackets are basically optional accessories and we love an accessible queen. 💅

---

🦋 DESCRIPTION 🦋

DROP TEXT SEARCH PARSER drops an existing text search parser. simple. elegant. done. ✨

⚠️ okay but the plot twist: you must be a superuser to use this command. no superuser, no dropping. it's giving VIP access only. 👑

---

🎀 PARAMETERS 🎀

• IF EXISTS — use this when you're not tryna start drama. do not throw an error if the text search parser doesn't exist. instead, a notice is issued in this case. very "it's okay bestie, moving on." 🫶
• name — the name of an existing text search parser. and yes, it can be optionally schema-qualified, so go ahead and be specific. 🌈
• CASCADE — automatically drop objects that depend on the text search parser, and in turn all objects that depend on those objects (see Section 5.15). it's the domino effect, and honestly? kinda main character energy. 🔥
• RESTRICT — refuse to drop the text search parser if any objects depend on it. this is the default, so if you didn't pick anything, you got boundaries. 💀

---

💜 EXAMPLES 💜

here's how you remove the text search parser my_parser:

DROP TEXT SEARCH PARSER my_parser;

and listen — this command will not succeed if there are any existing text search configurations that use the parser. shade. 🙈

so if that's your situation, add CASCADE to drop such configurations along with the parser. problem solved, she ate. 💅✨

---

⭐ COMPATIBILITY ⭐

there is no DROP TEXT SEARCH PARSER statement in the SQL standard. so basically this is a PostgreSQL exclusive and we're not mad about it. periodt. 🌈

---

🧚 SEE ALSO 🧚

• ALTER TEXT SEARCH PARSER (ALTER_TEXT_SEARCH_PARSER(7))
• CREATE TEXT SEARCH PARSER (CREATE_TEXT_SEARCH_PARSER(7))

---

and that's the whole page, bestie! 💖 tysm for reading, mwah. this icon was brought to you by PostgreSQL 17.11, dated 2026 — DROP TEXT SEARCH PARSER(7), signing off. 🦋🌸🎀✨