From 981e5acd24cc63fa4f27dac3b35e5d0bf3921efc Mon Sep 17 00:00:00 2001
From: Bruce Momjian <bruce@momjian.us>
Date: Thu, 6 Oct 2011 19:31:20 -0400
Subject: [PATCH] Move pg_upgrade doc mention of the port numbers to the same
 place.

---
 doc/src/sgml/pgupgrade.sgml | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/doc/src/sgml/pgupgrade.sgml b/doc/src/sgml/pgupgrade.sgml
index 9b0718df6b..0d084243a8 100644
--- a/doc/src/sgml/pgupgrade.sgml
+++ b/doc/src/sgml/pgupgrade.sgml
@@ -201,9 +201,7 @@ mv /usr/local/pgsql /usr/local/pgsql.old
     <title>Install the new PostgreSQL binaries</title>
 
     <para>
-     Install the new server's binaries and support files. You can use the
-     same port numbers for both clusters, typically 5432, because the old and
-     new clusters will not be running at the same time.
+     Install the new server's binaries and support files.
     </para>
 
     <para>
@@ -340,6 +338,8 @@ pg_upgrade.exe
      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.
+     You can use the same port numbers for both clusters because the
+     old and new clusters will not be running at the same time.
     </para>
 
     <para>
-- 
2.40.0