Changes the definition of a text search dictionary.
ALTER TEXT SEARCH DICTIONARY <name> (
<option> [ = <value> ] [, ... ]
)
ALTER TEXT SEARCH DICTIONARY <name> RENAME TO <new_name>
ALTER TEXT SEARCH DICTIONARY <name> OWNER TO { <new_owner> | CURRENT_USER | SESSION_USER }
ALTER TEXT SEARCH DICTIONARY <name> SET SCHEMA <new_schema>
ALTER TEXT SEARCH DICTIONARY
changes the definition of a text search dictionary. You can change the dictionary's template-specific options, or change the dictionary's name or owner.
You must be the owner of the dictionary to use ALTER TEXT SEARCH DICTIONARY
.
Template-specific options can appear in any order.
The following example command changes the stop word list for a Snowball-based dictionary. Other parameters remain unchanged.
ALTER TEXT SEARCH DICTIONARY my_dict ( StopWords = newrussian );
The following example command changes the language option to dutch
, and removes the stop word option entirely:
ALTER TEXT SEARCH DICTIONARY my_dict ( language = dutch, StopWords );
The following example command "updates" the dictionary's definition without actually changing anything:
ALTER TEXT SEARCH DICTIONARY my_dict ( dummy );
(The reason this works is that the option removal code doesn't complain if there is no such option.) This trick is useful when changing configuration files for the dictionary: the ALTER
will force existing database sessions to re-read the configuration files, which they would otherwise never do if they had read them earlier.
There is no ALTER TEXT SEARCH DICTIONARY
statement in the SQL standard.
CREATE TEXT SEARCH DICTIONARY, DROP TEXT SEARCH DICTIONARY
Parent topic: SQL Commands