8000 Fix wording in pg_upgrade docs · postgrespro/postgres_cluster@499ae5f · GitHub
[go: up one dir, main page]
Skip to content

Commit 499ae5f

Browse files
mhagandermhagander
committed
Fix wording in pg_upgrade docs
Author: Daniel Gustafsson
1 parent 28d1c8c commit 499ae5f

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

‎src/bin/pg_upgrade/IMPLEMENTATION

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -71,8 +71,8 @@ performs a number of bookkeeping tasks required to 'sync up' the new
7171
cluster with the existing data.
7272

7373
First, pg_upgrade copies the commit status information and 'next
74-
transaction ID' from the old cluster to the new cluster. This is the
75-
steps ensures that the proper tuples are visible from the new cluster.
74+
transaction ID' from the old cluster to the new cluster. This step
75+
ensures that the proper tuples are visible from the new cluster.
7676
Remember, pg_upgrade does not export/import the content of user-defined
7777
tables so the transaction IDs in the new cluster must match the
7878
transaction IDs in the old data. pg_upgrade also copies the starting

0 commit comments

Comments
 (0)
0