summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorBruce Momjian <bruce@momjian.us>2011-07-01 23:09:14 -0400
committerBruce Momjian <bruce@momjian.us>2011-07-01 23:09:14 -0400
commit46242281b44c7546b321ba503b8d99cc299ca746 (patch)
treef2efda0902d5795671aa096172a03023bca79465
parentbbfcc71496051651accb71540130c6d36377a692 (diff)
In pg_upgrade 9.0 and 9.1, document suggestion of using a non-default
port number to avoid unintended client connections.
-rw-r--r--doc/src/sgml/pgupgrade.sgml6
1 files changed, 4 insertions, 2 deletions
diff --git a/doc/src/sgml/pgupgrade.sgml b/doc/src/sgml/pgupgrade.sgml
index 8e975d8e207..31f1c3d1d48 100644
--- a/doc/src/sgml/pgupgrade.sgml
+++ b/doc/src/sgml/pgupgrade.sgml
@@ -239,8 +239,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>
@@ -319,6 +318,9 @@ pg_upgrade.exe
<para>
Obviously, no one should be accessing the clusters during the migration.
+ 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>