From a253a88594f6805168261ea1986df1cd6b9b25e0 Mon Sep 17 00:00:00 2001
From: Bruce Momjian <bruce@momjian.us>
Date: Tue, 2 Aug 2016 17:13:10 -0400
Subject: [PATCH] doc: OS collation changes can break indexes
Discussion: 20160702155517.GD18610@momjian.us
Reviewed-by: Christoph Berg
Backpatch-through: 9.1
---
doc/src/sgml/runtime.sgml | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/doc/src/sgml/runtime.sgml b/doc/src/sgml/runtime.sgml
index 4c5d748d0e4..310bf735fc3 100644
--- a/doc/src/sgml/runtime.sgml
+++ b/doc/src/sgml/runtime.sgml
@@ -188,8 +188,8 @@ postgres$ <userinput>initdb -D /usr/local/pgsql/data</userinput>
operating system's collation library for character set ordering.
This controls the ordering of keys stored in indexes. For this reason,
a cluster cannot switch to an incompatible collation library version,
- either through snapshot restore, binary streaming replication, or
- <application>pg_upgrade</> run.
+ either through snapshot restore, binary streaming replication, a
+ different operating system, or an operating system upgrade.
</para>
<sect2 id="creating-cluster-mount-points">
--
GitLab