doc: OS collation changes can break indexes

Discussion: 20160702155517.GD18610@momjian.us

Reviewed-by: Christoph Berg
Backpatch-through: 9.1

diff --git a/doc/src/sgml/runtime.sgml b/doc/src/sgml/runtime.sgml
index 4c5d748d0e4a0973e923abee589bd278aadc70da..310bf735fc376a314db5315f4c2a56d95abcc0a0 100644 (file)
--- 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">