summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorBruce Momjian <bruce@momjian.us>2016-08-02 17:13:10 -0400
committerBruce Momjian <bruce@momjian.us>2016-08-02 17:13:10 -0400
commita6839bf0c61ccc8465ef438034312aff0a1d8a95 (patch)
treec5c9f5f471da700ba38cdcb4d8eeca72b87cbc56
parent6693c9d7bffbd8481b13ccad2d164d3f69398fa6 (diff)
doc: OS collation changes can break indexes
Discussion: 20160702155517.GD18610@momjian.us Reviewed-by: Christoph Berg Backpatch-through: 9.1
-rw-r--r--doc/src/sgml/runtime.sgml4
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/src/sgml/runtime.sgml b/doc/src/sgml/runtime.sgml
index 3616c160398..0cc62aeaf16 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">