aboutsummaryrefslogtreecommitdiff
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
commitd02b38799d956ae6e8d600f081212448abe3f30e (patch)
treeb5d232b5d197fad5070ac1ef592aa8a17133a525
parent75c452a755a0c1e1500362b9bd7976a0be2588d2 (diff)
downloadpostgresql-d02b38799d956ae6e8d600f081212448abe3f30e.tar.gz
postgresql-d02b38799d956ae6e8d600f081212448abe3f30e.zip
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 09e1653c2c1..eed55dd6db4 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">