Commitb21ec20

committed

doc: pg_upgrade, clarify standby servers must remain running

Also mention that mismatching primary/standby LSNs should neverhappen.Reported-by: Nikolay SamokhvalovDiscussion:https://postgr.es/m/CAM527d8heqkjG5VrvjU3Xjsqxg41ufUyabD9QZccdAxnpbRH-Q@mail.gmail.comBackpatch-through: 11

1 parent17cd48d commitb21ec20Copy full SHA for b21ec20

File tree

-4

lines changed

-4

lines changed

Lines changed: 2 additions & 4 deletions

Original file line number	Diff line number	Diff line change
`@@ -380,8 +380,8 @@ NET STOP postgresql-&majorversion;`
`380`	`380`	`</para>`
`381`	`381`
`382`	`382`	`<para>`
`383`		`- Streaming replication and log-shipping standby serverscan`
`384`		`-remainrunninguntil a later step.`
	`383`	`+ Streaming replication and log-shipping standby serversmust be`
	`384`	`+ runningduring this shutdown so they receive all changes.`
`385`	`385`	`</para>`
`386`	`386`	`</step>`
`387`	`387`
`@@ -394,8 +394,6 @@ NET STOP postgresql-&majorversion;`
`394`	`394`	`servers are caught up by running <application>pg_controldata</application>`
`395`	`395`	`against the old primary and standby clusters. Verify that the`
`396`	`396`	`<quote>Latest checkpoint location</quote> values match in all clusters.`
`397`		`- (There will be a mismatch if old standby servers were shut down`
`398`		`- before the old primary or if the old standby servers are still running.)`
`399`	`397`	`Also, make sure <varname>wal_level</varname> is not set to`
`400`	`398`	`<literal>minimal</literal> in the <filename>postgresql.conf</filename> file on the`
`401`	`399`	`new primary cluster.`

Comments

(0)