Commit9646d2f

committed

Use <substeps> in pg_upgrade's procedure

For clarity, so that the substeps are not numbered identically to theouter procedure's steps.Per report from Andy Colson inhttp://www.postgresql.org/message-id/55D789B5.7040308@squeakycode.net

1 parent123c9d2 commit9646d2fCopy full SHA for 9646d2f

File tree

-2

lines changed

-2

lines changed

Lines changed: 2 additions & 2 deletions

Original file line number	Diff line number	Diff line change
`@@ -407,7 +407,7 @@ pg_upgrade.exe`
`407`	`407`	`upgrade them (before starting any servers):`
`408`	`408`	`</para>`
`409`	`409`
`410`		`- <procedure>`
	`410`	`+ <substeps>`
`411`	`411`
`412`	`412`	`<step>`
`413`	`413`	`<title>Install the new PostgreSQL binaries on standby servers</title>`
`@@ -522,7 +522,7 @@ rsync --archive --delete --hard-links --size-only old_pgdata new_pgdata remote_d`
`522`	`522`	`</para>`
`523`	`523`	`</step>`
`524`	`524`
`525`		`- </procedure>`
	`525`	`+ </substeps>`
`526`	`526`
`527`	`527`	`</step>`
`528`	`528`

Comments

(0)