Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Skip to content

Commit a0873fb

Browse files
committed
docs: Fix pg_upgrade standby server upgrade docs
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
1 parent e3f87aa commit a0873fb

File tree

1 file changed

+15
-18
lines changed

1 file changed

+15
-18
lines changed

doc/src/sgml/ref/pgupgrade.sgml

+15-18
Original file line numberDiff line numberDiff line change
@@ -317,15 +317,22 @@ NET STOP postgresql-9.0
317317
</step>
318318

319319
<step>
320-
<title>Verify standby servers</title>
320+
<title>Prepare for standby server upgrades</title>
321321

322322
<para>
323-
If you are upgrading Streaming Replication and Log-Shipping standby
324-
servers, verify that the old standby servers are caught up by running
325-
<application>pg_controldata</> against the old primary and standby
326-
clusters. Verify that the <quote>Latest checkpoint location</>
327-
values match in all clusters. (There will be a mismatch if old
328-
standby servers were shut down before the old primary.)
323+
If you are upgrading standby servers (as outlined in section <xref
324+
linkend="pgupgrade-step-replicas">), verify that the old standby
325+
servers are caught up by running <application>pg_controldata</>
326+
against the old primary and standby clusters. Verify that the
327+
<quote>Latest checkpoint location</> values match in all clusters.
328+
(There will be a mismatch if old standby servers were shut down
329+
before the old primary.)
330+
</para>
331+
332+
<para>
333+
Also, if upgrading standby servers, change <varname>wal_level</>
334+
to <literal>replica</> in the <filename>postgresql.conf</> file on
335+
the new master cluster.
329336
</para>
330337
</step>
331338

@@ -410,7 +417,7 @@ pg_upgrade.exe
410417
</para>
411418
</step>
412419

413-
<step>
420+
<step id="pgupgrade-step-replicas">
414421
<title>Upgrade Streaming Replication and Log-Shipping standby servers</title>
415422

416423
<para>
@@ -471,16 +478,6 @@ pg_upgrade.exe
471478
</para>
472479
</step>
473480

474-
<step>
475-
<title>Start and stop the new master cluster</title>
476-
477-
<para>
478-
In the new master cluster, change <varname>wal_level</> to
479-
<literal>replica</> in the <filename>postgresql.conf</> file
480-
and then start and stop the cluster.
481-
</para>
482-
</step>
483-
484481
<step>
485482
<title>Run <application>rsync</></title>
486483

0 commit comments

Comments
 (0)