diff options
| author | Michael Paquier <michael@paquier.xyz> | 2023-10-11 13:54:33 +0900 |
|---|---|---|
| committer | Michael Paquier <michael@paquier.xyz> | 2023-10-11 13:54:33 +0900 |
| commit | c7c801ef3ba067aedc0288c17fe463c4f42e5623 (patch) | |
| tree | 3e80bf33f37a40f0f4cb9bbb669a238358b15a1b /src | |
| parent | 4800a5dfb4c46d22b5d05f16c615bea6ff24a2bb (diff) | |
| download | postgresql-c7c801ef3ba067aedc0288c17fe463c4f42e5623.tar.gz postgresql-c7c801ef3ba067aedc0288c17fe463c4f42e5623.zip | |
Improve some wording in pg_upgrade/IMPLEMENTATION
Author: Gurjeet Singh
Discussion: https://postgr.es/m/CABwTF4VFKtKrb78fBnMXwHvOu4a+-7y86siBSEety2knti2eGA@mail.gmail.com
Diffstat (limited to 'src')
| -rw-r--r-- | src/bin/pg_upgrade/IMPLEMENTATION | 6 |
1 files changed, 3 insertions, 3 deletions
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 |