| From: | Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us>, Matthias van de Meent <boekewurm+postgres(at)gmail(dot)com> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: First draft of the PG 15 release notes |
| Date: | 2022-08-31 09:38:33 |
| Message-ID: | e5299b18-2069-a530-48c3-b824f6f9fd28@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | houzj.fnst@fujitsu.com | 2022-08-31 09:55:45 | RE: Perform streaming logical transactions by background workers and parallel apply |
| Previous Message | Peter Eisentraut | 2022-08-31 09:35:17 | Re: plpgsql-trigger.html: Format TG_ variables as table (patch) |