From: Michael Paquier Date: Wed, 11 Oct 2023 04:54:33 +0000 (+0900) Subject: Improve some wording in pg_upgrade/IMPLEMENTATION X-Git-Tag: REL_17_BETA1~1704 X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=c7c801ef3ba067aedc0288c17fe463c4f42e5623;p=thirdparty%2Fpostgresql.git Improve some wording in pg_upgrade/IMPLEMENTATION Author: Gurjeet Singh Discussion: https://postgr.es/m/CABwTF4VFKtKrb78fBnMXwHvOu4a+-7y86siBSEety2knti2eGA@mail.gmail.com --- diff --git a/src/bin/pg_upgrade/IMPLEMENTATION b/src/bin/pg_upgrade/IMPLEMENTATION index 229399a45ae..f47deee90c1 100644 --- a/src/bin/pg_upgrade/IMPLEMENTATION +++ b/src/bin/pg_upgrade/IMPLEMENTATION @@ -48,9 +48,9 @@ HOW IT WORKS To use pg_upgrade during an upgrade, start by installing a fresh cluster using the newest version in a new directory. When you've finished installation, the new cluster will contain the new executables -and the usual template0, template1, and postgres, but no user-defined -tables. At this point, you can shut down the old and new postmasters and -invoke pg_upgrade. +and the usual template0, template1, and postgres databases, but no +user-defined tables. At this point, you can shut down the old and new +postmasters and invoke pg_upgrade. When pg_upgrade starts, it ensures that all required executables are present and contain the expected version numbers. The verification