relnotes: improve collation check and ICU items
authorBruce Momjian
Sat, 3 Sep 2022 01:47:30 +0000 (21:47 -0400)
committerBruce Momjian
Sat, 3 Sep 2022 01:47:55 +0000 (21:47 -0400)
Reported-by: Matthias van de Meent
Discussion: https://postgr.es/m/CAEze2WhrNAT2g8upDUhfqt1nWfV_JdUgXAQu7oT4rY2L68O-HQ@mail.gmail.com

Backpatch-through: 15 only

doc/src/sgml/release-15.sgml

index daec5711083b685eaab78e7a689298eff13c9531..d432c2db44c504ee8e3466af4aac15389c031869 100644 (file)
@@ -578,17 +578,17 @@ Author: Peter Eisentraut 
 
      
       
-       Record and check the collation of each 
+       Record and check the collation version of each 
        linkend="sql-createdatabase">database (Peter Eisentraut)
       
 
       
-       This is designed to detect collation
+       This is designed to detect collation version
        mismatches to avoid data corruption.  Function
        pg_database_collation_actual_version()
        reports the underlying operating system collation version, and
        ALTER DATABASE ...  REFRESH sets the database
-       to match the operating system collation version.  DETAILS?
+       to match the operating system collation version.
       
      
 
@@ -605,9 +605,11 @@ Author: Peter Eisentraut 
       
 
       
-       Previously, ICU collations could only be
-       specified in CREATE
-       COLLATION and used with the
+       Previously, only libc-based
+       collations could be set at the cluster and database levels.
+       ICU collations were previously limited
+       to CREATE
+       COLLATION and referenced by the
        COLLATE clause.