postgres.git / summary / log / commit / refs

commit    f789909b59c59a33e34feac3bed2c86f18159122
Author:   Bruce Momjian <bruce@momjian.us>
Date:     Fri Aug 31 20:55:49 2012 +0000

    In pg_upgade, document that the port numbers must be different when
    checking an old running server.


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

diff --git a/doc/src/sgml/pgupgrade.sgml b/doc/src/sgml/pgupgrade.sgml
index fcbe551e764..b62aba26418 100644
--- a/doc/src/sgml/pgupgrade.sgml
+++ b/doc/src/sgml/pgupgrade.sgml
@@ -367,8 +367,10 @@ 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.
+     You can use the same port number for both clusters when doing an
+     upgrade because the old and new clusters will not be running at the
+     same time.  However, when checking an old running server, the old
+     and new port numbers must be different.
     </para>
 
     <para>


[parent: 58a031f920c2]