aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorBruce Momjian <bruce@momjian.us>2018-08-25 13:35:14 -0400
committerBruce Momjian <bruce@momjian.us>2018-08-25 13:35:14 -0400
commit3e8382996ffaea16e4202172d32ca72b672056b4 (patch)
tree20a8ec18ec3320a5db1afd7df92f2a9b219cbf32
parent56c1d751cf16d7be72131085d70fb027f83d2e1a (diff)
downloadpostgresql-3e8382996ffaea16e4202172d32ca72b672056b4.tar.gz
postgresql-3e8382996ffaea16e4202172d32ca72b672056b4.zip
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
-rw-r--r--doc/src/sgml/ref/pgupgrade.sgml3
1 files changed, 2 insertions, 1 deletions
diff --git a/doc/src/sgml/ref/pgupgrade.sgml b/doc/src/sgml/ref/pgupgrade.sgml
index 6816abad489..ac3e08300da 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
<quote>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 <varname>wal_level</> to
+ before the old primary or if the old standby servers are still running.)
+ Also, change <varname>wal_level</varname> to
<literal>hot_standby</> in the <filename>postgresql.conf</> file on the
new primary cluster.
</para>