From: Bruce Momjian Date: Sat, 25 Aug 2018 17:35:14 +0000 (-0400) Subject: doc: "Latest checkpoint location" will not match in pg_upgrade X-Git-Tag: REL9_5_15~80 X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=3e8382996ffaea16e4202172d32ca72b672056b4;p=postgresql doc: "Latest checkpoint location" will not match in pg_upgrade Mention that "Latest checkpoint location" will not match in pg_upgrade if the standby server is still running during the upgrade, which is possible. "Match" text first appeared in PG 9.5. Reported-by: Paul Bonaud Discussion: https://postgr.es/m/c7268794-edb4-1772-3bfd-04c54585c24e@trainline.com Backpatch-through: 9.5 --- diff --git a/doc/src/sgml/ref/pgupgrade.sgml b/doc/src/sgml/ref/pgupgrade.sgml index 6816abad48..ac3e08300d 100644 --- a/doc/src/sgml/ref/pgupgrade.sgml +++ b/doc/src/sgml/ref/pgupgrade.sgml @@ -326,7 +326,8 @@ NET STOP postgresql-9.0 against the old primary and standby clusters. Verify that the Latest checkpoint location values match in all clusters. (There will be a mismatch if old standby servers were shut down - before the old primary.) Also, change wal_level to + before the old primary or if the old standby servers are still running.) + Also, change wal_level to hot_standby in the postgresql.conf file on the new primary cluster.