From: Bruce Momjian Date: Sat, 2 Jul 2011 03:09:13 +0000 (-0400) Subject: In pg_upgrade 9.0 and 9.1, document suggestion of using a non-default X-Git-Tag: REL9_1_BETA3~31 X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=158d071b28529509b0a77317a24ef55fb84480d9;p=postgresql In pg_upgrade 9.0 and 9.1, document suggestion of using a non-default port number to avoid unintended client connections. --- diff --git a/doc/src/sgml/pgupgrade.sgml b/doc/src/sgml/pgupgrade.sgml index b24c1e7b98..5d605e187e 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 trust in pg_hba.conf, or if using md5 authentication, use a ~/.pgpass file (see ) - 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. @@ -336,6 +335,9 @@ pg_upgrade.exe 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.