diff options
| author | Magnus Hagander <magnus@hagander.net> | 2017-05-05 12:42:21 +0200 |
|---|---|---|
| committer | Magnus Hagander <magnus@hagander.net> | 2017-05-05 12:42:21 +0200 |
| commit | 499ae5f5db99c84035e9951fd30e428adf0f40d2 (patch) | |
| tree | d11ae7e494f0702edb8685a875a34376fa519688 /src | |
| parent | 28d1c8ccc87128f9b0b937eae277473027c36b7e (diff) | |
| download | postgresql-499ae5f5db99c84035e9951fd30e428adf0f40d2.tar.gz postgresql-499ae5f5db99c84035e9951fd30e428adf0f40d2.zip | |
Fix wording in pg_upgrade docs
Author: Daniel Gustafsson
Diffstat (limited to 'src')
| -rw-r--r-- | src/bin/pg_upgrade/IMPLEMENTATION | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/src/bin/pg_upgrade/IMPLEMENTATION b/src/bin/pg_upgrade/IMPLEMENTATION index 9b5ff7295c1..69fcd70a7c5 100644 --- a/src/bin/pg_upgrade/IMPLEMENTATION +++ b/src/bin/pg_upgrade/IMPLEMENTATION @@ -71,8 +71,8 @@ performs a number of bookkeeping tasks required to 'sync up' the new cluster with the existing data. First, pg_upgrade copies the commit status information and 'next -transaction ID' from the old cluster to the new cluster. This is the -steps ensures that the proper tuples are visible from the new cluster. +transaction ID' from the old cluster to the new cluster. This step +ensures that the proper tuples are visible from the new cluster. Remember, pg_upgrade does not export/import the content of user-defined tables so the transaction IDs in the new cluster must match the transaction IDs in the old data. pg_upgrade also copies the starting |