database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-07-28 23:42:10 +03:00
Code Activity

In pg_upgrade, document that link mode has to have data directories on

Browse Source 
the same file system, and that authentication should lock out normal
users.

Per suggestsion from #postgresql irc channel.

Backpatch to 9.0.
This commit is contained in:
Bruce Momjian
2011-06-14 18:14:56 -04:00
parent 5246386727
commit 6122849416
1 changed files with 7 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@ -239,7 +239,8 @@ 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.
to avoid being prompted repeatedly for a password. Also make sure
pg_upgrade is the only program that can connect to the clusters.
</para>
</step>
@ -278,9 +279,11 @@ NET STOP pgsql-8.3 (<productname>PostgreSQL</> 8.3 and older used a different s
data and executable (<filename>bin</>) directories. You can also specify separate
user and port values, and whether you want the data linked instead of
copied (the default). If you use linking, the migration will be much
faster (no data copying), but you will no longer be able to access your
old cluster once you start the new cluster after the upgrade. See
<literal>pg_upgrade --help</> for a full list of options.
faster (hard link data files rather than copying them), but you
will no longer be able to access your old cluster once you start
the new cluster after the upgrade. Link mode also requires that the
old and new cluster data directories be in the same file system.
See <literal>pg_upgrade --help</> for a full list of options.
</para>
<para>