mirrors/postgres
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

doc: pg_upgrade, clarify standby servers must remain running

Browse Source 
Also mention that mismatching primary/standby LSNs should never
happen.

Reported-by: Nikolay Samokhvalov

Discussion: https://postgr.es/m/CAM527d8heqkjG5VrvjU3Xjsqxg41ufUyabD9QZccdAxnpbRH-Q@mail.gmail.com

Backpatch-through: 11
This commit is contained in:
Bruce Momjian 2023-09-26 18:54:10 -04:00
parent 15d5d7405d
commit b0d049e8fa
1 changed files with 2 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
doc/src/sgml/ref/pgupgrade.sgml
View File

@ -403,8 +403,8 @@ NET STOP postgresql-&majorversion;
</para>
<para>
Streaming replication and log-shipping standby servers can
remain running until a later step.
Streaming replication and log-shipping standby servers must be
running during this shutdown so they receive all changes.
</para>
</step>
@ -417,8 +417,6 @@ NET STOP postgresql-&majorversion;
servers are caught up by running <application>pg_controldata</application>
against the old primary and standby clusters. Verify that the
<quote>Latest checkpoint location</quote> 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, make sure <varname>wal_level</varname> is not set to
<literal>minimal</literal> in the <filename>postgresql.conf</filename> file on the
new primary cluster.