alter_text_search_dictionary(7)

NAME#

ALTER_TEXT_SEARCH_DICTIONARY - change the definition of a text search dictionary

SYNOPSIS#

ALTER TEXT SEARCH DICTIONARY \nname\n (
\n
    \noption\n [ = \nvalue\n ] [, ... ]
)
ALTER TEXT SEARCH DICTIONARY \nname\n RENAME TO \nnew_name\n
ALTER TEXT SEARCH DICTIONARY \nname\n OWNER TO { \nnew_owner\n | CURRENT_ROLE | CURRENT_USER | SESSION_USER }
ALTER TEXT SEARCH DICTIONARY \nname\n SET SCHEMA \nnew_schema

DESCRIPTION#

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.

PARAMETERS#

name

option

value

new_name

new_owner

new_schema

Template-specific options can appear in any order.

EXAMPLES#

The following example command changes the stopword 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 stopword 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 otherwise they would never do if they had read them earlier.

COMPATIBILITY#

There is no ALTER TEXT SEARCH DICTIONARY statement in the SQL standard.

SEE ALSO#

CREATE TEXT SEARCH DICTIONARY (CREATE_TEXT_SEARCH_DICTIONARY(7)), DROP TEXT SEARCH DICTIONARY (DROP_TEXT_SEARCH_DICTIONARY(7))