From 6efae5bf2a6bb0de31f53ecbe5dc52879fbc54c4 Mon Sep 17 00:00:00 2001 From: Tom Lane Date: Wed, 17 Oct 2007 01:01:28 +0000 Subject: Another round of editorialization on the text search documentation. Notably, standardize on using "token" for the strings output by a parser, while "lexeme" is reserved for the normalized strings produced by a dictionary. --- doc/src/sgml/ref/alter_tsdictionary.sgml | 17 ++++++++++++++++- 1 file changed, 16 insertions(+), 1 deletion(-) (limited to 'doc/src/sgml/ref') diff --git a/doc/src/sgml/ref/alter_tsdictionary.sgml b/doc/src/sgml/ref/alter_tsdictionary.sgml index a2929c70d12..69bc4298514 100644 --- a/doc/src/sgml/ref/alter_tsdictionary.sgml +++ b/doc/src/sgml/ref/alter_tsdictionary.sgml @@ -1,5 +1,5 @@ @@ -122,6 +122,21 @@ ALTER TEXT SEARCH DICTIONARY my_dict ( StopWords = newrussian ); 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. + -- cgit v1.2.3