@@ -273,16 +273,20 @@ Author: Peter Eisentraut <peter@eisentraut.org>
273273
274274 <listitem>
275275 <para>
276- The locale implementation underlying full-text search was improved. It
277- now observes the locale provider configured for the database for case
278- conversions. It was previously hardcoded to use libc. In database
279- clusters that use a locale provider other than libc (that is, ICU or
280- builtin) and where the locale configured through that locale provider
281- behaves differently from the LC_CTYPE setting configured for the database,
282- this could cause changes in behavior of some functions related to
283- full-text search as well as the pg_trgm extension. When upgrading such
284- database clusters using pg_upgrade, it is recommended to reindex all
285- indexes related to full-text search and pg_trgm after the upgrade.
276+ Change <link linkend="textsearch">full text search</link> to use the
277+ default collation provider of the cluster to read configuration files
278+ and dictionaries, rather than always using libc (Peter Eisentraut)
279+ </para>
280+
281+ <para>
282+ Clusters that default to non-libc collation providers (e.g., ICU,
283+ builtin) that behave differently than libc for characters processed
284+ by LC_CTYPE could observe changes in behavior of some full-text
285+ search functions, as well as the <xref linkend="pgtrgm"/> extension.
286+ When upgrading such clusters using <xref linkend="pgupgrade"/>, it
287+ is recommended to reindex all indexes related to full-text search
288+ and <application>pg_trgm</application> after the upgrade.
289+ (Peter Eisentraut)
286290 <ulink url="&commit_baseurl;fb1a18810f0">§</ulink>
287291 </para>
288292 </listitem>