Limit pg_upgrade authentication advice to always-secure techniques.

~/.pgpass is a sound choice everywhere, and "peer" authentication is
safe on every platform it supports.  Cease to recommend "trust"
authentication, the safety of which is deeply configuration-specific.
Back-patch to 9.0, where pg_upgrade was introduced.

diff --git a/doc/src/sgml/pgupgrade.sgml b/doc/src/sgml/pgupgrade.sgml
index afb2ff4fbb9cbf137d161422f4c44b493107ed40..b5267b69d82bf37b32b2e81223d6bba6650d5785 100644 (file)
--- a/doc/src/sgml/pgupgrade.sgml
+++ b/doc/src/sgml/pgupgrade.sgml
@@ -288,10 +288,9 @@ make prefix=/usr/local/pgsql.new install
     Adjust authentication
 
     
-     pg_upgrade will connect to the old and new servers several times,
-     so you might want to set authentication to trust
-     or peer in pg_hba.conf, or if using
-     md5 authentication, use a ~/.pgpass file
+     pg_upgrade will connect to the old and new servers several
+     times, so you might want to set authentication to peer
+     in pg_hba.conf or use a ~/.pgpass file
      (see ).
     
    
@@ -406,10 +405,9 @@ pg_upgrade.exe
     Restore <filename>pg_hba.conf</>
 
     
-     If you modified pg_hba.conf to use trust,
-     restore its original authentication settings.  It might also be
-     necessary to adjust other configurations files in the new cluster to
-     match the old cluster, e.g. postgresql.conf.
+     If you modified pg_hba.conf, restore its original settings.
+     It might also be necessary to adjust other configuration files in the new
+     cluster to match the old cluster, e.g. postgresql.conf.