From: Bruce Momjian Date: Sat, 30 Aug 2025 21:52:06 +0000 (-0400) Subject: doc PG 18 relnotes: add attribution and rewrite text search item X-Git-Tag: REL_18_RC1~3 X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=a252ed7fba6667f913d74e72dd0af9c9b2c9b3d1;p=thirdparty%2Fpostgresql.git doc PG 18 relnotes: add attribution and rewrite text search item Discussion: https://postgr.es/m/aLMo7lJKg8bWUs3y@momjian.us Backpatch-through: 18 --- diff --git a/doc/src/sgml/release-18.sgml b/doc/src/sgml/release-18.sgml index 2deb5fdd328..d01686f9d07 100644 --- a/doc/src/sgml/release-18.sgml +++ b/doc/src/sgml/release-18.sgml @@ -273,16 +273,20 @@ Author: Peter Eisentraut - The locale implementation underlying full-text search was improved. It - now observes the locale provider configured for the database for case - conversions. It was previously hardcoded to use libc. In database - clusters that use a locale provider other than libc (that is, ICU or - builtin) and where the locale configured through that locale provider - behaves differently from the LC_CTYPE setting configured for the database, - this could cause changes in behavior of some functions related to - full-text search as well as the pg_trgm extension. When upgrading such - database clusters using pg_upgrade, it is recommended to reindex all - indexes related to full-text search and pg_trgm after the upgrade. + Change full text search to use the + default collation provider of the cluster to read configuration files + and dictionaries, rather than always using libc (Peter Eisentraut) + + + + Clusters that default to non-libc collation providers (e.g., ICU, + builtin) that behave differently than libc for characters processed + by LC_CTYPE could observe changes in behavior of some full-text + search functions, as well as the extension. + When upgrading such clusters using , it + is recommended to reindex all indexes related to full-text search + and pg_trgm after the upgrade. + (Peter Eisentraut) §