From d1073c3b4cc83bb9d25b0c0203adc74ca58ef866 Mon Sep 17 00:00:00 2001 From: Peter Eisentraut Date: Fri, 29 Aug 2025 10:18:10 +0200 Subject: [PATCH] doc PG 18 relnotes: Add migration note about tsearch Document the small migration hazard introduced in commit fb1a18810f0, as suggested there. Reviewed-by: Daniel Verite Reviewed-by: Heikki Linnakangas Discussion: https://www.postgresql.org/message-id/flat/653f3b84-fc87-45a7-9a0c-bfb4fcab3e7d%40eisentraut.org --- doc/src/sgml/release-18.sgml | 22 ++++++++++++++++++++++ 1 file changed, 22 insertions(+) diff --git a/doc/src/sgml/release-18.sgml b/doc/src/sgml/release-18.sgml index ce594b5b4ce..c3e318dab00 100644 --- a/doc/src/sgml/release-18.sgml +++ b/doc/src/sgml/release-18.sgml @@ -266,6 +266,28 @@ Author: Fujii Masao + + + + + 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. + + § + + +