From: Bruce Momjian <bruce@momjian.us>
Date: Tue, 30 Jun 2020 15:55:52 +0000 (-0400)
Subject: doc: change pg_upgrade wal_level to be not minimal
X-Git-Tag: REL9_5_23~33
X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=41c0166317988d1eb0d8d445ff14574a1cbc2c1a;p=thirdparty%2Fpostgresql.git

doc: change pg_upgrade wal_level to be not minimal

Previously it was specified to be only replica.

Discussion: https://postgr.es/m/20200618180058.GK7349@momjian.us

Backpatch-through: 9.5
---

diff --git a/doc/src/sgml/ref/pgupgrade.sgml b/doc/src/sgml/ref/pgupgrade.sgml
index 6936941adbc..dc5fb35bb0d 100644
--- a/doc/src/sgml/ref/pgupgrade.sgml
+++ b/doc/src/sgml/ref/pgupgrade.sgml
@@ -330,8 +330,8 @@ NET STOP postgresql-9.0
      <quote>Latest checkpoint location</> values match in all clusters.
      (There will be a mismatch if old standby servers were shut down
      before the old primary or if the old standby servers are still running.)
-     Also, change <varname>wal_level</varname> to
-     <literal>hot_standby</> in the <filename>postgresql.conf</> file on the
+     Also, make sure <varname>wal_level</varname> is not set to 
+     <literal>minimal</literal> in the <filename>postgresql.conf</filename> file on the
      new primary cluster.
     </para>
    </step>