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

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

Per suggestsion from #postgresql irc channel.

Backpatch to 9.0.

diff --git a/doc/src/sgml/pgupgrade.sgml b/doc/src/sgml/pgupgrade.sgml
index 9f6f5db5d0b97ae9c1d265195c27d07cff3a03a6..bf5f40bf5ae0d585ae455e3b8f2fb00e48be6443 100644 (file)
--- a/doc/src/sgml/pgupgrade.sgml
+++ b/doc/src/sgml/pgupgrade.sgml
@@ -239,7 +239,8 @@ gmake prefix=/usr/local/pgsql.new install
      so you might want to set authentication to trust in
      pg_hba.conf, or if using md5 authentication,
      use a ~/.pgpass file (see )
-     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.
     
    
  
@@ -278,9 +279,11 @@ NET STOP pgsql-8.3  (PostgreSQL 8.3 and older used a different s
      data and executable (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
-     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 pg_upgrade --help for a full list of options.