DROP_TEXT_SEARCH_PARSER(7)
๐ 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 ๐๐ฆ
๐ฆ where this page comes from
- alpine 3.23: postgresql18-doc 18.6-r0 ยท PostgreSQL
- alpine 3.24: postgresql18-doc 18.6-r0 ยท PostgreSQL
- arch rolling: postgresql 18.6-4 ยท PostgreSQL
- fedora 43: postgresql 18.6-1.fc43 ยท PostgreSQL
- fedora 43: postgresql 18.6-1.fc43 ยท PostgreSQL
- fedora 44: postgresql 18.6-1.fc44 ยท PostgreSQL
- fedora 44: postgresql 18.6-1.fc44 ยท PostgreSQL
- nixos 26.05: postgresql 18.6
- ubuntu resolute: postgresql-client-18 18.6-0ubuntu0.26.04.1 ยท PostgreSQL
- ubuntu stonking: postgresql-client-18 18.6-3build2 ยท PostgreSQL
- ๐ girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms