Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Commit158d071

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 parent3b80219 commit158d071

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
@@ -256,8 +256,7 @@ gmake prefix=/usr/local/pgsql.new install
256256
so you might want to set authentication to <literal>trust</> in
257257
<filename>pg_hba.conf</>, or if using <literal>md5</> authentication,
258258
use a <filename>~/.pgpass</> file (see <xref linkend="libpq-pgpass">)
259-
to avoid being prompted repeatedly for a password. Also make sure
260-
pg_upgrade is the only program that can connect to the clusters.
259+
to avoid being prompted repeatedly for a password.
261260
</para>
262261
</step>
263262

@@ -336,6 +335,9 @@ pg_upgrade.exe
336335

337336
<para>
338337
Obviously, no one should be accessing the clusters during the upgrade.
338+
Consider using a non-default port number, e.g. 50432, for old
339+
and new clusters to avoid unintended client connections during
340+
the upgrade.
339341
</para>
340342

341343
<para>

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp