|
578 | 578 |
|
579 | 579 | <listitem>
|
580 | 580 | <para>
|
581 |
| - Record and check the collation of each <link |
| 581 | + Record and check the collation version of each <link |
582 | 582 | linkend="sql-createdatabase">database</link> (Peter Eisentraut)
|
583 | 583 | </para>
|
584 | 584 |
|
585 | 585 | <para>
|
586 |
| - This is designed to detect collation |
| 586 | + This is designed to detect collation version |
587 | 587 | mismatches to avoid data corruption. Function
|
588 | 588 | <function>pg_database_collation_actual_version()</function>
|
589 | 589 | reports the underlying operating system collation version, and
|
590 | 590 | <command>ALTER DATABASE ... REFRESH</command> sets the database
|
591 |
| - to match the operating system collation version. DETAILS? |
| 591 | + to match the operating system collation version. |
592 | 592 | </para>
|
593 | 593 | </listitem>
|
594 | 594 |
|
|
605 | 605 | </para>
|
606 | 606 |
|
607 | 607 | <para>
|
608 |
| - Previously, <acronym>ICU</acronym> collations could only be |
609 |
| - specified in <link linkend="sql-createcollation"><command>CREATE |
610 |
| - COLLATION</command></link> and used with the |
| 608 | + Previously, only <application>libc</application>-based |
| 609 | + collations could be set at the cluster and database levels. |
| 610 | + <acronym>ICU</acronym> collations were previously limited |
| 611 | + to <link linkend="sql-createcollation"><command>CREATE |
| 612 | + COLLATION</command></link> and referenced by the |
611 | 613 | <literal>COLLATE</literal> clause.
|
612 | 614 | </para>
|
613 | 615 | </listitem>
|
|
0 commit comments