Skip to content

Commit 4624228

Browse files
committed
In pg_upgrade 9.0 and 9.1, document suggestion of using a non-default
port number to avoid unintended client connections.
1 parent bbfcc71 commit 4624228

File tree

1 file changed

+4
-2
lines changed

1 file changed

+4
-2
lines changed

doc/src/sgml/pgupgrade.sgml

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -239,8 +239,7 @@ gmake prefix=/usr/local/pgsql.new install
239239
so you might want to set authentication to <literal>trust</> in
240240
<filename>pg_hba.conf</>, or if using <literal>md5</> authentication,
241241
use a <filename>~/.pgpass</> file (see <xref linkend="libpq-pgpass">)
242-
to avoid being prompted repeatedly for a password. Also make sure
243-
pg_upgrade is the only program that can connect to the clusters.
242+
to avoid being prompted repeatedly for a password.
244243
</para>
245244
</step>
246245

@@ -319,6 +318,9 @@ pg_upgrade.exe
319318

320319
<para>
321320
Obviously, no one should be accessing the clusters during the migration.
321+
Consider using a non-default port number, e.g. 50432, for old
322+
and new clusters to avoid unintended client connections during
323+
the upgrade.
322324
</para>
323325

324326
<para>

0 commit comments

Comments
 (0)