From: Bruce Momjian <bruce@momjian.us>
To: Peter Eisentraut <peter.eisentraut@enterprisedb.com>
Cc: Matthias van de Meent <boekewurm+postgres@gmail.com>
Cc: PostgreSQL-development <pgsql-hackers@postgresql.org>
Subject: Re: First draft of the PG 15 release notes
Date: Wed, 31 Aug 2022 16:03:06 -0400
Message-ID: <Yw++epcHZJuJ4Dx+@momjian.us> (raw)
In-Reply-To: <e5299b18-2069-a530-48c3-b824f6f9fd28@enterprisedb.com>
References: <20220706024557.GD2648447@rfd.leadboat.com>
<YsWJ3XYbT7qMfpmy@momjian.us>
<20220710031941.GB2808420@rfd.leadboat.com>
<YsxSXWSS90Yzqqwv@momjian.us>
<20220712063132.GB2937407@rfd.leadboat.com>
<Ys3BqwfxDAwCDjES@momjian.us>
<YtmQbQtxP2H+irFa@momjian.us>
<CAEze2WhrNAT2g8upDUhfqt1nWfV_JdUgXAQu7oT4rY2L68O-HQ@mail.gmail.com>
<Yw52OMxLJ/KeGdeI@momjian.us>
<e5299b18-2069-a530-48c3-b824f6f9fd28@enterprisedb.com>
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:
> >
> > <listitem>
> > <para>
> > Record and check the collation of each <link
> > linkend="sql-createdatabase">database</link> (Peter Eisentraut)
> > </para>
> >
> > <para>
> > This is designed to detect collation
> > mismatches to avoid data corruption. Function
> > <function>pg_database_collation_actual_version()</function>
> > reports the underlying operating system collation version, and
> > <command>ALTER DATABASE ... REFRESH</command> sets the database
> > to match the operating system collation version. DETAILS?
> > </para>
> > </listitem>
> >
> > 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 <bruce@momjian.us> https://momjian.us
EDB https://enterprisedb.com
Indecision is a decision. Inaction is an action. Mark Batterson
Attachments:REL_15_collation.diff (text/x-diff, 1.7K) downloaddiff --git a/doc/src/sgml/release-15.sgml b/doc/src/sgml/release-15.sgmlindex e3ab13e53c..dca4550c03 100644--- a/doc/src/sgml/release-15.sgml+++ b/doc/src/sgml/release-15.sgml@@ -578,17 +578,17 @@ Author: Peter Eisentraut <peter@eisentraut.org>
<listitem>
<para>
- Record and check the collation of each <link+ Record and check the collation version of each <link
linkend="sql-createdatabase">database</link> (Peter Eisentraut)
</para>
<para>
- This is designed to detect collation+ This is designed to detect collation version
mismatches to avoid data corruption. Function
<function>pg_database_collation_actual_version()</function>
reports the underlying operating system collation version, and
<command>ALTER DATABASE ... REFRESH</command> sets the database
- to match the operating system collation version. DETAILS?+ to match the operating system collation version.
</para>
</listitem>
@@ -605,9 +605,11 @@ Author: Peter Eisentraut <peter@eisentraut.org>
</para>
<para>
- Previously, <acronym>ICU</acronym> collations could only be- specified in <link linkend="sql-createcollation"><command>CREATE- COLLATION</command></link> and used with the+ Previously, only <application>libc</application>-based+ collations could be set at the cluster and database levels.+ <acronym>ICU</acronym> collations were previously limited+ to <link linkend="sql-createcollation"><command>CREATE+ COLLATION</command></link> and referenced by the
<literal>COLLATE</literal> clause.
</para>
</listitem>
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: bruce@momjian.us, peter.eisentraut@enterprisedb.com, boekewurm+postgres@gmail.com
Subject: Re: First draft of the PG 15 release notes
In-Reply-To: <Yw++epcHZJuJ4Dx+@momjian.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox