DROP_TEXT_SEARCH_PARSER(7pg18)

💅 DROP TEXT SEARCH PARSER — the manual page, but make it make sense

okay bestie, so we're talking about DROP_TEXT_SEARCH_PARSER here, from the PostgreSQL 18.6 docs. Buckle up, it's actually not that deep, but it IS important. 🎀

---

✨ NAME ✨

DROP_TEXT_SEARCH_PARSER — remove a text search parser 💀✂️

---

🌸 SYNOPSIS 🌸

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

---

🦋 DESCRIPTION 🦋

So DROP TEXT SEARCH PARSER drops an existing text search parser. That's it, that's the whole vibe. It's giving "yeet that parser into the void." 🕳️✨

but fr fr, you must be a superuser to use this command. no superuser, no parser-dropping. that's the rule, no cap. 👑

---

💖 PARAMETERS 💖

• IF EXISTS — don't throw an error if the text search parser doesn't exist. instead, a notice is issued. so like, it's the "no worries if not!!" of flags. 🫶
• name — the name of an existing text search parser, optionally schema-qualified. lowkey important that it's existing, bestie. 🙈
• CASCADE — automatically drops objects that depend on the text search parser, and then in turn all the objects that depend on those objects (check Section 5.15 for the whole domino situation 🁢🁢🁢). it's the "and everything that came with it" button.
• RESTRICT — refuse to drop the text search parser if any objects depend on it. this is the default, so if you don't say anything, PostgreSQL is being cautious and protective of your stuff. main character energy honestly. 💅

---

🍓 EXAMPLES 🍓

Removing the text search parser my_parser:

DROP TEXT SEARCH PARSER my_parser;

heads up bestie: this command will not succeed if there are any existing text search configurations that use the parser. it's giving "you can't leave, you have responsibilities." 😭 add CASCADE to drop such configurations along with the parser. slay.

---

🌈 COMPATIBILITY 🌈

ngl there is no DROP TEXT SEARCH PARSER statement in the SQL standard. so this is a PostgreSQL exclusive, iykyk. ⭐

---

💜 SEE ALSO 💜

• ALTER TEXT SEARCH PARSER (ALTER_TEXT_SEARCH_PARSER(7)) 🔧
• CREATE TEXT SEARCH PARSER (CREATE_TEXT_SEARCH_PARSER(7)) 🏗️

---

okay that's the whole page, you ate that 🎀✨ this was PostgreSQL 18.6 documentation, dated 2026 — go drop some parsers responsibly, bestie, and remember: superuser only, RESTRICT by default, CASCADE when you're feeling brave. bye pookie 💖🦋