database/postgres
database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-05-06 19:59:18 +03:00
Code

docs: Fix pg_upgrade standby server upgrade docs

Browse Source 
It was unsafe to instruct users to start/stop the server after
pg_upgrade was run but before the standby servers were rsync'ed.  The
new instructions avoid this.

RELEASE NOTES:  This fix should be mentioned in the minor release notes.

Reported-by: Dmitriy Sarafannikov and Sergey Burladyan

Discussion: https://postgr.es/m/87wp8o506b.fsf@seb.koffice.internal

Backpatch-through: 9.5, where standby server upgrade instructions first appeared
This commit is contained in:
Bruce Momjian 2017-06-15 12:30:02 -04:00
parent e3f87aae93
commit a0873fbabb
1 changed files with 15 additions and 18 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -317,15 +317,22 @@ NET STOP postgresql-9.0
</step> </step>
<step> <step>
<title>Verify standby servers</title> <title>Prepare for standby server upgrades</title>
<para> <para>
If you are upgrading Streaming Replication and Log-Shipping standby If you are upgrading standby servers (as outlined in section <xref
servers, verify that the old standby servers are caught up by running linkend="pgupgrade-step-replicas">), verify that the old standby
<application>pg_controldata</> against the old primary and standby servers are caught up by running <application>pg_controldata</>
clusters. Verify that the <quote>Latest checkpoint location</> against the old primary and standby clusters. Verify that the
values match in all clusters. (There will be a mismatch if old <quote>Latest checkpoint location</> values match in all clusters.
standby servers were shut down before the old primary.) (There will be a mismatch if old standby servers were shut down
before the old primary.)
</para>
<para>
Also, if upgrading standby servers, change <varname>wal_level</>
to <literal>replica</> in the <filename>postgresql.conf</> file on
the new master cluster.
</para> </para>
</step> </step>
@ -410,7 +417,7 @@ pg_upgrade.exe
</para> </para>
</step> </step>
<step> <step id="pgupgrade-step-replicas">
<title>Upgrade Streaming Replication and Log-Shipping standby servers</title> <title>Upgrade Streaming Replication and Log-Shipping standby servers</title>
<para> <para>
@ -471,16 +478,6 @@ pg_upgrade.exe
</para> </para>
</step> </step>
<step>
<title>Start and stop the new master cluster</title>
<para>
In the new master cluster, change <varname>wal_level</> to
<literal>replica</> in the <filename>postgresql.conf</> file
and then start and stop the cluster.
</para>
</step>
<step> <step>
<title>Run <application>rsync</></title> <title>Run <application>rsync</></title>