Improve some wording in pg_upgrade/IMPLEMENTATION

Author: Gurjeet Singh
Discussion: https://postgr.es/m/CABwTF4VFKtKrb78fBnMXwHvOu4a+-7y86siBSEety2knti2eGA@mail.gmail.com
This commit is contained in:
Michael Paquier 2023-10-11 13:54:33 +09:00
parent 4800a5dfb4
commit c7c801ef3b

View File

@ -48,9 +48,9 @@ HOW IT WORKS
To use pg_upgrade during an upgrade, start by installing a fresh To use pg_upgrade during an upgrade, start by installing a fresh
cluster using the newest version in a new directory. When you've cluster using the newest version in a new directory. When you've
finished installation, the new cluster will contain the new executables finished installation, the new cluster will contain the new executables
and the usual template0, template1, and postgres, but no user-defined and the usual template0, template1, and postgres databases, but no
tables. At this point, you can shut down the old and new postmasters and user-defined tables. At this point, you can shut down the old and new
invoke pg_upgrade. postmasters and invoke pg_upgrade.
When pg_upgrade starts, it ensures that all required executables are When pg_upgrade starts, it ensures that all required executables are
present and contain the expected version numbers. The verification present and contain the expected version numbers. The verification