database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-07-21 16:02:15 +03:00
Code Activity

In pg_upgrade 9.0 and 9.1, document suggestion of using a non-default

Browse Source 
port number to avoid unintended client connections.
This commit is contained in:
Bruce Momjian
2011-07-01 23:09:14 -04:00
parent bbfcc71496
commit 46242281b4
1 changed files with 4 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
doc/src/sgml/pgupgrade.sgml
View File

@ -239,8 +239,7 @@ gmake prefix=/usr/local/pgsql.new install
so you might want to set authentication to <literal>trust</> in so you might want to set authentication to <literal>trust</> in
<filename>pg_hba.conf</>, or if using <literal>md5</> authentication, <filename>pg_hba.conf</>, or if using <literal>md5</> authentication,
use a <filename>~/.pgpass</> file (see <xref linkend="libpq-pgpass">) use a <filename>~/.pgpass</> file (see <xref linkend="libpq-pgpass">)
to avoid being prompted repeatedly for a password. Also make sure to avoid being prompted repeatedly for a password.
pg_upgrade is the only program that can connect to the clusters.
</para> </para>
</step> </step>
@ -319,6 +318,9 @@ pg_upgrade.exe
<para> <para>
Obviously, no one should be accessing the clusters during the migration. 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>
<para> <para>