diff options
| -rw-r--r-- | doc/src/sgml/pgupgrade.sgml | 10 |
1 files changed, 5 insertions, 5 deletions
diff --git a/doc/src/sgml/pgupgrade.sgml b/doc/src/sgml/pgupgrade.sgml index aa633e2d414..102ca526bb1 100644 --- a/doc/src/sgml/pgupgrade.sgml +++ b/doc/src/sgml/pgupgrade.sgml @@ -302,13 +302,11 @@ NET STOP pgsql-8.3 (<productname>PostgreSQL</> 8.3 and older used a different s copying), but you will not be able to access your old cluster once you start the new cluster after the upgrade. Link mode also requires that the old and new cluster data directories be in the - same file system. + same file system. See <literal>pg_upgrade --help</> for a full + list of options. </para> <para> - <application>pg_upgrade</> defaults to running servers on port - 50432 to avoid unintended client connections. See <literal>pg_upgrade - --help</> for a full list of options. </para> <para> @@ -339,7 +337,9 @@ pg_upgrade.exe </para> <para> - Obviously, no one should be accessing the clusters during the upgrade. + Obviously, no one should be accessing the clusters during the + upgrade. <application>pg_upgrade</> defaults to running servers + on port 50432 to avoid unintended client connections. </para> <para> |