aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorBruce Momjian <bruce@momjian.us>2011-07-01 18:36:00 -0400
committerBruce Momjian <bruce@momjian.us>2011-07-01 18:36:00 -0400
commitcc81d9969c6ac32f8482b3fc1a1775d212222fa7 (patch)
treeb4730968cc372972f1993579bc06aa3e7a2e749d
parenta88f4496b75a756df371a405ce608ceb06c8fbd7 (diff)
downloadpostgresql-cc81d9969c6ac32f8482b3fc1a1775d212222fa7.tar.gz
postgresql-cc81d9969c6ac32f8482b3fc1a1775d212222fa7.zip
In the pg_upgrade docs, move 50432 port mention to the place where we
talk about client access.
-rw-r--r--doc/src/sgml/pgupgrade.sgml10
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>