diff options
Diffstat (limited to 'doc/src/sgml/textsearch.sgml')
| -rw-r--r-- | doc/src/sgml/textsearch.sgml | 19 |
1 files changed, 9 insertions, 10 deletions
diff --git a/doc/src/sgml/textsearch.sgml b/doc/src/sgml/textsearch.sgml index b3e4b8e9af7..1beebd21ee4 100644 --- a/doc/src/sgml/textsearch.sgml +++ b/doc/src/sgml/textsearch.sgml @@ -2132,9 +2132,7 @@ ALTER TEXT SEARCH CONFIGURATION astro_en end where it'd be useless. Filtering dictionaries are useful to partially normalize words to simplify the task of later dictionaries. For example, a filtering dictionary could be used to remove accents from accented - letters, as is done by the - <link linkend="unaccent"><filename>contrib/unaccent</></link> - extension module. + letters, as is done by the <xref linkend="unaccent"> module. </para> <sect2 id="textsearch-stopwords"> @@ -3367,8 +3365,8 @@ CREATE INDEX <replaceable>name</replaceable> ON <replaceable>table</replaceable> allows the implementation of very fast searches with online update. Partitioning can be done at the database level using table inheritance, or by distributing documents over - servers and collecting search results using the <filename>contrib/dblink</> - extension module. The latter is possible because ranking functions use + servers and collecting search results using the <xref linkend="dblink"> + module. The latter is possible because ranking functions use only local information. </para> @@ -3616,8 +3614,9 @@ Parser: "pg_catalog.default" <title>Migration from Pre-8.3 Text Search</title> <para> - Applications that used the <filename>contrib/tsearch2</> add-on module - for text searching will need some adjustments to work with the + Applications that use the <xref linkend="tsearch2"> + module for text searching will need some adjustments to work + with the built-in features: </para> @@ -3628,7 +3627,7 @@ Parser: "pg_catalog.default" argument lists, and all of them are now in the <literal>pg_catalog</> schema, whereas in a previous installation they would have been in <literal>public</> or another non-system schema. There is a new - version of <filename>contrib/tsearch2</> (see <xref linkend="tsearch2">) + version of <application>tsearch2</> that provides a compatibility layer to solve most problems in this area. </para> @@ -3636,11 +3635,11 @@ Parser: "pg_catalog.default" <listitem> <para> - The old <filename>contrib/tsearch2</> functions and other objects + The old <application>tsearch2</> functions and other objects <emphasis>must</> be suppressed when loading <application>pg_dump</> output from a pre-8.3 database. While many of them won't load anyway, a few will and then cause problems. One simple way to deal with this - is to load the new <filename>contrib/tsearch2</> module before restoring + is to load the new <application>tsearch2</> module before restoring the dump; then it will block the old objects from being loaded. </para> </listitem> |