Commit29dec9f

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 parent3a9a1b8 commit29dec9fCopy full SHA for 29dec9f

File tree

-4

lines changed

-4

lines changed

Lines changed: 2 additions & 4 deletions

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

Comments

(0)