diff options
| author | Bruce Momjian | 2018-08-25 17:35:14 +0000 |
|---|---|---|
| committer | Bruce Momjian | 2018-08-25 17:35:14 +0000 |
| commit | 50ff8844bb3b32fbc2a4d1b2d4fe22b4e5efd779 (patch) | |
| tree | bb7f02a77a1700af3d1c3d90bcfa6e5af768c537 | |
| parent | a65f22fc6223117650fec31a3821f181f15d9366 (diff) | |
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.sgml | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/doc/src/sgml/ref/pgupgrade.sgml b/doc/src/sgml/ref/pgupgrade.sgml index fae32f95230..52f00bea787 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>replica</> in the <filename>postgresql.conf</> file on the new primary cluster. </para> |