Re: First draft of the PG 15 release notes - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: First draft of the PG 15 release notes
Date
Msg-id Yw++epcHZJuJ4Dx+@momjian.us
Whole thread Raw
In response to Re: First draft of the PG 15 release notes  (Peter Eisentraut <peter.eisentraut@enterprisedb.com>)
Responses Re: First draft of the PG 15 release notes
List pgsql-hackers
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


Attachment

pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: Avoid erroring out when unable to remove or parse logical rewrite files to save checkpoint work
Next
From: Tom Lane
Date:
Subject: Re: Bug fix. autovacuum.c do_worker_start() associates memory allocations with TopMemoryContext rather than 'Autovacuum start worker (tmp)'