DROP TEXT SEARCH CONFIGURATION
Read PG 18 manual ↗remove a text search configuration
Syntax
DROP TEXT SEARCH CONFIGURATION [ IF EXISTS ] name [ CASCADE | RESTRICT ]
Syntax diagrams
Read left to right. Branches are choices, bypasses are optional, loops repeat. Select an underlined parameter to open its rule.
Description
DROP TEXT SEARCH CONFIGURATION drops an existing text search configuration. To execute this command you must be the owner of the configuration.
Parameters
IF EXISTSDo not throw an error if the text search configuration does not exist. A notice is issued in this case.
nameThe name (optionally schema-qualified) of an existing text search configuration.
CASCADEAutomatically drop objects that depend on the text search configuration, and in turn all objects that depend on those objects (see Section 5.15).
RESTRICTRefuse to drop the text search configuration if any objects depend on it. This is the default.
Examples
Remove the text search configuration my_english:
DROP TEXT SEARCH CONFIGURATION my_english;
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.
See Also
ALTER TEXT SEARCH CONFIGURATION, CREATE TEXT SEARCH CONFIGURATIONVersion history 4
- PG 19 → 20changed
- PG 18 → 19changed
- PG 16 → 17changed
- PG 11 → 12changed
Related entries
Definition snapshot: 2026-09-14T13:14:25.700916+00:00@99e6866c · English manual source