Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1s9ucc-005xcP-1X for pgsql-hackers@arkaria.postgresql.org; Wed, 22 May 2024 22:39:47 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1s9ucc-004ehS-0D for pgsql-hackers@arkaria.postgresql.org; Wed, 22 May 2024 22:39:46 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1s9ucb-004ehK-MX for pgsql-hackers@lists.postgresql.org; Wed, 22 May 2024 22:39:45 +0000 Received: from momjian.us ([72.94.173.45]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1s9ucY-000H0b-Ov for pgsql-hackers@postgresql.org; Wed, 22 May 2024 22:39:45 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=momjian.us; s=2024011501; h=In-Reply-To:Content-Transfer-Encoding:Content-Type: MIME-Version:References:Message-ID:Subject:Cc:To:From:Date:Sender:Reply-To: Content-ID:Content-Description; bh=mL4biGUtthB/mDdwKlcCB9Deu17evFMOCq79plZi7nU=; b=SqaGrDHaNzQzMYATEDPme5knU+ BLY+t3h2ijwDYvbs3x4D3ApeE7OKkP3KHJKLOAvX1Umt4EA+99QKr3mZCl4jCG2ac2NURYqXh0Hbm BNEmaY3NnRl1IA2wl3pMruskSyQ/AhRatgjx208Hk5lBsEThkty7AG2mNzZUjPsdJP72iwNcUenDU kmZCBy0NrCzmqYKGQKviZNnH4VgAmNI1FNuIHPbVQEktu2pp2NKUjtamutt4q8pXrojTCo9/Kzzhh /Rb1eDiDcJFuhL0nReQIQNqzVj58QTbz0ncllThMZ9J0/Bz7p+qu1ebPqhDVtjqGDm1hwFn3dlNKQ 5H440tuw==; Received: from bruce by momjian.us with local (Exim 4.96) (envelope-from ) id 1s9ucX-000vny-2K; Wed, 22 May 2024 18:39:41 -0400 Date: Wed, 22 May 2024 18:39:41 -0400 From: Bruce Momjian To: Jeff Davis Cc: PostgreSQL-development Subject: Re: First draft of PG 17 release notes Message-ID: References: <92e039f6fabc3567169e95e12b39a04c00f8503b.camel@j-davis.com> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="6q/rC1Yg7bnwJ2a5" Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <92e039f6fabc3567169e95e12b39a04c00f8503b.camel@j-davis.com> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --6q/rC1Yg7bnwJ2a5 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit On Mon, May 20, 2024 at 11:48:09AM -0700, Jeff Davis wrote: > On Sat, 2024-05-18 at 17:51 -0400, Bruce Momjian wrote: > > Okay, I went with the attached applied patch.  Adjustments? > > I think it should have more emphasis on the actual new feature: a > platform-independent builtin collation provider and the C.UTF-8 locale. > > The user can look at the documentation for comparison with libc. Okay, changed with the attached applied patch. -- Bruce Momjian https://momjian.us EDB https://enterprisedb.com Only you can decide what is important to you. --6q/rC1Yg7bnwJ2a5 Content-Type: text/x-diff; charset=us-ascii Content-Disposition: attachment; filename="master.diff" diff --git a/doc/src/sgml/release-17.sgml b/doc/src/sgml/release-17.sgml index 3025f31f8a0..e381dbe5d96 100644 --- a/doc/src/sgml/release-17.sgml +++ b/doc/src/sgml/release-17.sgml @@ -885,11 +885,11 @@ Author: Jeff Davis -Create "builtin" collation provider similar to libc's C locale (Jeff Davis) +Add a builtin platform-independent collation provider (Jeff Davis) -While its C locale is similar but independent of libc, its C.UTF-8 locale sorts by Unicode code points and has Unicode-based case folding. +This supports "C" and "C.UTF-8" collations. --6q/rC1Yg7bnwJ2a5--