On Fri, May 17, 2024 at 01:30:03PM -0700, Jeff Davis wrote: > On Thu, 2024-05-09 at 00:03 -0400, Bruce Momjian wrote: > > I have committed the first draft of the PG 17 release notes; you can > > see the results here: > > > > https://momjian.us/pgsql_docs/release-17.html > > For this item: > > Create a "builtin" collation provider similar to libc's C > locale (Jeff Davis) > > It uses a "C" locale which is identical but independent of > libc, but it allows the use of non-"C" collations like "en_US" > and "C.UTF-8" with the "C" locale, which libc does not. MORE? > > I suggest something more like: > > New, platform-independent "builtin" collation > provider. (Jeff Davis) > > Currently, it offers the "C" and "C.UTF-8" locales. The > "C.UTF-8" locale combines stable and fast code point order > collation with Unicode character semantics.
Okay, I went with the attached applied patch. Adjustments? -- Bruce Momjian <br...@momjian.us> https://momjian.us EDB https://enterprisedb.com Only you can decide what is important to you.
diff --git a/doc/src/sgml/release-17.sgml b/doc/src/sgml/release-17.sgml index 0bc1c9a14ad..5d2fcd7d7de 100644 --- a/doc/src/sgml/release-17.sgml +++ b/doc/src/sgml/release-17.sgml @@ -886,11 +886,11 @@ Author: Jeff Davis <jda...@postgresql.org> <listitem> <para> -Create a "builtin" collation provider similar to libc's C locale (Jeff Davis) +Create "builtin" collation provider similar to libc's C locale (Jeff Davis) </para> <para> -It uses a "C" locale which is identical but independent of libc, but it allows the use of non-"C" collations like "en_US" and "C.UTF-8" with the "C" locale, which libc does not. MORE? +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. </para> </listitem>
