doc: change pg_upgrade wal_level to be not minimal
authorBruce Momjian <[email protected]>
Tue, 30 Jun 2020 15:55:53 +0000 (11:55 -0400)
committerBruce Momjian <[email protected]>
Tue, 30 Jun 2020 15:55:53 +0000 (11:55 -0400)
Previously it was specified to be only replica.

Discussion: https://postgr.es/m/20200618180058[email protected]

Backpatch-through: 9.5

doc/src/sgml/ref/pgupgrade.sgml

index e81f11d077839e38b5f7ad734b7eadbe3a2f2ceb..f4a64615f36e186741c5fd7a9f46b88c423c77c0 100644 (file)
@@ -359,8 +359,8 @@ NET STOP postgresql-&majorversion;
      <quote>Latest checkpoint location</quote> 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>replica</literal> in the <filename>postgresql.conf</filename> 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>