postgres.git / summary / log / commit / refs

commit    525ee8ff333d71fcf155833ea59a635f30b87fd1
Author:   Bruce Momjian <bruce@momjian.us>
Date:     Tue Jun 20 15:04:31 2017 +0000

    doc:  adjust wal_level pg_upgrade patch
    
    Since 9.5 has two WAL levels that apply to standby upgrades, archive and
    hot_standby, adjust the docs for that version to say, basically, "restore old
    cluster wal_level value in the new cluster".
    
    This is a follow-on patch to fd376afc9863dd8ea3eba95edfa79961173e706f.
    
    Backpatch-through: 9.5 only


 doc/src/sgml/ref/pgupgrade.sgml | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/doc/src/sgml/ref/pgupgrade.sgml b/doc/src/sgml/ref/pgupgrade.sgml
index 2269eb9d05b..3f2581e8527 100644
--- a/doc/src/sgml/ref/pgupgrade.sgml
+++ b/doc/src/sgml/ref/pgupgrade.sgml
@@ -331,8 +331,8 @@ NET STOP postgresql-9.0
 
     <para>
      Also, if upgrading standby servers, change <varname>wal_level</>
-     to <literal>replica</> in the <filename>postgresql.conf</> file on
-     the new master cluster.
+     in the <filename>postgresql.conf</> file on the new master cluster
+     to match the value you used in the old cluster.
     </para>
    </step>
 


[parent: 54d4d818ddab]