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 6dafb404a1196dbbeba1af9164e6a154b3b5c2fd..d51146d641d81733a977975346d2005002eef0f6 100644 (file)
--- a/doc/src/sgml/ref/pgupgrade.sgml
+++ b/doc/src/sgml/ref/pgupgrade.sgml
@@ -326,7 +326,8 @@ NET STOP postgresql-&majorversion;
      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
      replica in the postgresql.conf file on the
      new primary cluster.