Commitd1073c3

committed

doc PG 18 relnotes: Add migration note about tsearch

Document the small migration hazard introduced in commitfb1a188,as suggested there.Reviewed-by: Daniel Verite <daniel@manitou-mail.org>Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>Discussion:https://www.postgresql.org/message-id/flat/653f3b84-fc87-45a7-9a0c-bfb4fcab3e7d%40eisentraut.org

1 parent58ea074 commitd1073c3Copy full SHA for d1073c3

File tree

+22

-0

lines changed

+22

-0

lines changed

Lines changed: 22 additions & 0 deletions

Original file line number	Diff line number	Diff line change
`@@ -266,6 +266,28 @@ Author: Fujii Masao <fujii@postgresql.org>`
`266`	`266`	`</para>`
`267`	`267`	`</listitem>`
`268`	`268`
	`269`	`+<!--`
	`270`	`+Author: Peter Eisentraut <peter@eisentraut.org>`
	`271`	`+2024-12-17 [fb1a18810f0] Remove ts_locale.c's lowerstr()`
	`272`	`+-->`
	`273`	`+`
	`274`	`+ <listitem>`
	`275`	`+ <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.`
	`286`	`+`
	`287`	`+ <ulink url="&commit_baseurl;fb1a18810f0">§</ulink>`
	`288`	`+ </para>`
	`289`	`+ </listitem>`
	`290`	`+`
`269`	`291`	`</itemizedlist>`
`270`	`292`
`271`	`293`	`</sect2>`

Comments

(0)