summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorBruce Momjian2020-06-30 15:55:53 +0000
committerBruce Momjian2020-06-30 15:55:53 +0000
commit2a06cb86dbacdf19a19d5bfd00d5156584f2188a (patch)
tree31f0deb4bcc6455f5584538bbc6b6e2f43f4d40d
parent9bae7e4cde7c9786ee61dac4a3e032b346350a88 (diff)
doc: change pg_upgrade wal_level to be not minimal
Previously it was specified to be only replica. Discussion: https://postgr.es/m/[email protected] Backpatch-through: 9.5
-rw-r--r--doc/src/sgml/ref/pgupgrade.sgml4
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/src/sgml/ref/pgupgrade.sgml b/doc/src/sgml/ref/pgupgrade.sgml
index 319d6132966..6779a5bddcf 100644
--- a/doc/src/sgml/ref/pgupgrade.sgml
+++ b/doc/src/sgml/ref/pgupgrade.sgml
@@ -360,8 +360,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>