DROP_TEXT_SEARCH_PARSER(7pg15)

💅 DROP TEXT SEARCH PARSER (7pg15) 💅

okay so bestie. you're reading the PostgreSQL 15.19 docs, page DROP_TEXT_SEARCH_PARSER(7), and honestly? this one is short and sweet — a little baby command with a big "i'm the main character" energy. let's get into it 🫶

---

✨ NAME ✨

DROP_TEXT_SEARCH_PARSER — remove a text search parser. that's it. that's the whole vibe. bye parser 👋

---

🌸 SYNOPSIS 🌸

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

look at that. clean. iconic. no cap ✨

---

💖 DESCRIPTION 💖

DROP TEXT SEARCH PARSER drops an existing text search parser. literally just yeets it out of existence 🕳️

but hold up — you must be a superuser to use this command. no superuser, no drop. that's the rule, bestie, and it's not negotiable 💅

---

🎀 PARAMETERS 🎀

• IF EXISTS — do not throw an error if the text search parser does not exist. instead, a notice is issued in this case. so like, it'll gently tell you "hey, that thing wasn't there" instead of full-on screaming at you. very demure, very mindful 🙈
• name — the name (optionally schema-qualified) of an existing text search parser. yes, you can schema-qualify it. yes, you're fancy for doing so 🎀
• CASCADE — automatically drop objects that depend on the text search parser, and in turn all objects that depend on those objects (see Section 5.14). chain reaction. domino effect. it's giving "burn it all down" 🔥
• RESTRICT — refuse to drop the text search parser if any objects depend on it. this is the default. so the safety is on unless you say otherwise 🛡️

---

🦋 EXAMPLES 🦋

remove the text search parser my_parser:

DROP TEXT SEARCH PARSER my_parser;

and here's the tea ☕ — this command will not succeed if there are any existing text search configurations that use the parser. add CASCADE to drop such configurations along with the parser. iykyk 💀

---

🌈 COMPATIBILITY 🌈

there is no DROP TEXT SEARCH PARSER statement in the SQL standard. so like... this is a PostgreSQL original. exclusive behavior only. 💅✨

---

⭐ SEE ALSO ⭐

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

go click those if you want the full lore 🧚

---

and that's the whole page, bestie, you ate that 🍓 PostgreSQL 15.19, dated 2026 — written from the DROP TEXT SEARCH PARSER(7) page, which is genuinely a mouthful to say out loud tbh. now go drop some parsers (responsibly, with RESTRICT on by default) 👑💜