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

From Peter Eisentraut
Subject Re: First draft of the PG 15 release notes
Date
Msg-id e5299b18-2069-a530-48c3-b824f6f9fd28@enterprisedb.com
Whole thread Raw
In response to Re: First draft of the PG 15 release notes  (Bruce Momjian <bruce@momjian.us>)
Responses Re: First draft of the PG 15 release notes
List pgsql-hackers
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.



pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: plpgsql-trigger.html: Format TG_ variables as table (patch)
Next
From: "houzj.fnst@fujitsu.com"
Date:
Subject: RE: Perform streaming logical transactions by background workers and parallel apply