Commit499ae5f

committed

Fix wording in pg_upgrade docs

Author: Daniel Gustafsson

1 parent28d1c8c commit499ae5fCopy full SHA for 499ae5f

File tree

-2

lines changed

-2

lines changed

Lines changed: 2 additions & 2 deletions

Original file line number	Diff line number	Diff line change
`@@ -71,8 +71,8 @@ performs a number of bookkeeping tasks required to 'sync up' the new`
`71`	`71`	`cluster with the existing data.`
`72`	`72`
`73`	`73`	`First, pg_upgrade copies the commit status information and 'next`
`74`		`-transaction ID' from the old cluster to the new cluster. Thisis the`
`75`		`-stepsensures that the proper tuples are visible from the new cluster.`
	`74`	`+transaction ID' from the old cluster to the new cluster. Thisstep`
	`75`	`+ensures that the proper tuples are visible from the new cluster.`
`76`	`76`	`Remember, pg_upgrade does not export/import the content of user-defined`
`77`	`77`	`tables so the transaction IDs in the new cluster must match the`
`78`	`78`	`transaction IDs in the old data. pg_upgrade also copies the starting`

Comments

(0)