Commit54856eb

authored and

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 parentf0daa71 commit54856ebCopy full SHA for 54856eb

File tree

-4

lines changed

-4

lines changed

Lines changed: 2 additions & 4 deletions

Original file line number	Diff line number	Diff line change
`@@ -403,8 +403,8 @@ NET STOP postgresql-&majorversion;`
`403`	`403`	`</para>`
`404`	`404`
`405`	`405`	`<para>`
`406`		`- Streaming replication and log-shipping standby serverscan`
`407`		`-remainrunninguntil a later step.`
	`406`	`+ Streaming replication and log-shipping standby serversmust be`
	`407`	`+ runningduring this shutdown so they receive all changes.`
`408`	`408`	`</para>`
`409`	`409`	`</step>`
`410`	`410`
`@@ -417,8 +417,6 @@ NET STOP postgresql-&majorversion;`
`417`	`417`	`servers are caught up by running <application>pg_controldata</application>`
`418`	`418`	`against the old primary and standby clusters. Verify that the`
`419`	`419`	`<quote>Latest checkpoint location</quote> values match in all clusters.`
`420`		`- (There will be a mismatch if old standby servers were shut down`
`421`		`- before the old primary or if the old standby servers are still running.)`
`422`	`420`	`Also, make sure <varname>wal_level</varname> is not set to`
`423`	`421`	`<literal>minimal</literal> in the <filename>postgresql.conf</filename> file on the`
`424`	`422`	`new primary cluster.`

Comments

(0)