You signed in with another tab or window.Reload to refresh your session.You signed out in another tab or window.Reload to refresh your session.You switched accounts on another tab or window.Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: doc/src/sgml/ref/alter_collation.sgml
+6-6Lines changed: 6 additions & 6 deletions
Original file line number
Diff line number
Diff line change
@@ -92,7 +92,7 @@ ALTER COLLATION <replaceable>name</replaceable> SET SCHEMA <replaceable>new_sche
92
92
<term><literal>REFRESH VERSION</literal></term>
93
93
<listitem>
94
94
<para>
95
-
Updated the collation version.
95
+
Update the collation's version.
96
96
See <xref linkend="sql-altercollation-notes"
97
97
endterm="sql-altercollation-notes-title"> below.
98
98
</para>
@@ -107,16 +107,16 @@ ALTER COLLATION <replaceable>name</replaceable> SET SCHEMA <replaceable>new_sche
107
107
<para>
108
108
When using collations provided by the ICU library, the ICU-specific version
109
109
of the collator is recorded in the system catalog when the collation object
110
-
is created. When the collation isthenused, the current version is
110
+
is created. When the collation is used, the current version is
111
111
checked against the recorded version, and a warning is issued when there is
112
112
a mismatch, for example:
113
113
<screen>
114
-
WARNING:ICU collator version mismatch
115
-
DETAIL: The database was created using version 1.2.3.4, thelibrary provides version 2.3.4.5.
116
-
HINT: Rebuild all objects affected by this collation and run ALTER COLLATION pg_catalog."xx-x-icu" REFRESH VERSION, or build PostgreSQL with the rightversion of ICU.
114
+
WARNING:collation "xx-x-icu" has version mismatch
115
+
DETAIL: Thecollation in thedatabase was created using version 1.2.3.4,buttheoperating system provides version 2.3.4.5.
116
+
HINT: Rebuild all objects affected by this collation and run ALTER COLLATION pg_catalog."xx-x-icu" REFRESH VERSION, or build PostgreSQL with the rightlibrary version.
117
117
</screen>
118
118
A change in collation definitions can lead to corrupt indexes and other
119
-
problemswhere the database system relies on stored objects having a
119
+
problemsbecause the database system relies on stored objects having a
120
120
certain sort order. Generally, this should be avoided, but it can happen
121
121
in legitimate circumstances, such as when
122
122
using <command>pg_upgrade</command> to upgrade to server binaries linked