Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1oTTvj-0007PH-Ky for pgsql-hackers@arkaria.postgresql.org; Wed, 31 Aug 2022 20:03:19 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1oTTvg-00056Q-Hv for pgsql-hackers@arkaria.postgresql.org; Wed, 31 Aug 2022 20:03:16 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1oTTvg-00056F-8S for pgsql-hackers@lists.postgresql.org; Wed, 31 Aug 2022 20:03:16 +0000 Received: from momjian.us ([72.94.173.45]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1oTTvZ-00005j-Iu for pgsql-hackers@postgresql.org; Wed, 31 Aug 2022 20:03:15 +0000 Received: from bruce by momjian.us with local (Exim 4.94.2) (envelope-from ) id 1oTTvX-001IC3-0S; Wed, 31 Aug 2022 16:03:07 -0400 Date: Wed, 31 Aug 2022 16:03:06 -0400 From: Bruce Momjian To: Peter Eisentraut Cc: Matthias van de Meent , PostgreSQL-development Subject: Re: First draft of the PG 15 release notes Message-ID: References: <20220706024557.GD2648447@rfd.leadboat.com> <20220710031941.GB2808420@rfd.leadboat.com> <20220712063132.GB2937407@rfd.leadboat.com> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="Lr2oxH851vHUzvpv" Content-Disposition: inline In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --Lr2oxH851vHUzvpv Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Wed, Aug 31, 2022 at 11:38:33AM +0200, Peter Eisentraut wrote: > On 30.08.22 22:42, Bruce Momjian wrote: > > Good question --- the full text is: > > > > > > > > Record and check the collation of each > linkend="sql-createdatabase">database (Peter Eisentraut) > > > > > > > > This is designed to detect collation > > 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? > > > > > > > > I just can't figure out what the user needs to understand about this, > > and I understand very little of it. > > We already had this feature for (schema-level) collations, now we have it on > the level of the database collation. Okay, I figured out the interplay between OS collation version support, collation libraries, and collation levels. Here is an updated patch for the release notes. -- Bruce Momjian https://momjian.us EDB https://enterprisedb.com Indecision is a decision. Inaction is an action. Mark Batterson --Lr2oxH851vHUzvpv Content-Type: text/x-diff; charset=us-ascii Content-Disposition: attachment; filename="REL_15_collation.diff" diff --git a/doc/src/sgml/release-15.sgml b/doc/src/sgml/release-15.sgml index e3ab13e53c..dca4550c03 100644 --- a/doc/src/sgml/release-15.sgml +++ b/doc/src/sgml/release-15.sgml @@ -578,17 +578,17 @@ Author: Peter Eisentraut - Record and check the collation of each 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. --Lr2oxH851vHUzvpv--