postgres.git / summary / log / commit / refs

commit    d02b38799d956ae6e8d600f081212448abe3f30e
Author:   Bruce Momjian <bruce@momjian.us>
Date:     Tue Aug 02 21:13:10 2016 +0000

    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 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">


[parent: 75c452a755a0]