postgres.git / summary / log / commit / refs

commit    158d071b28529509b0a77317a24ef55fb84480d9
Author:   Bruce Momjian <bruce@momjian.us>
Date:     Sat Jul 02 03:09:13 2011 +0000
First released in: 9.0.5, 9.1.0

    In pg_upgrade 9.0 and 9.1, document suggestion of using a non-default
    port number to avoid unintended client connections.


 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 b24c1e7b981..5d605e187e8 100644
--- a/doc/src/sgml/pgupgrade.sgml
+++ b/doc/src/sgml/pgupgrade.sgml
@@ -256,8 +256,7 @@ gmake prefix=/usr/local/pgsql.new install
      so you might want to set authentication to <literal>trust</> in
      <filename>pg_hba.conf</>, or if using <literal>md5</> authentication,
      use a <filename>~/.pgpass</> file (see <xref linkend="libpq-pgpass">)
-     to avoid being prompted repeatedly for a password.  Also make sure
-     pg_upgrade is the only program that can connect to the clusters.
+     to avoid being prompted repeatedly for a password.
     </para>
    </step>
 
@@ -336,6 +335,9 @@ pg_upgrade.exe
 
     <para>
      Obviously, no one should be accessing the clusters during the upgrade.
+     Consider using a non-default port number, e.g.  50432, for old
+     and new clusters to avoid unintended client connections during
+     the upgrade.
     </para>
 
     <para>


[parent: 3b80219e96f2]