From: Bruce Momjian Date: Tue, 30 Jun 2020 15:55:52 +0000 (-0400) Subject: doc: change pg_upgrade wal_level to be not minimal X-Git-Tag: REL_10_14~46 X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=d0a642fdc37066a4f29cd90c6027bc346702e830;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 b6ee0bcc7ba..72cb79a59e5 100644 --- a/doc/src/sgml/ref/pgupgrade.sgml +++ b/doc/src/sgml/ref/pgupgrade.sgml @@ -330,8 +330,8 @@ NET STOP postgresql-&majorversion; 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 wal_level to - replica in the postgresql.conf file on the + Also, make sure wal_level is not set to + minimal in the postgresql.conf file on the new primary cluster.