Permalink
Browse files

pg_upgrade: document possible pg_hba.conf options

Previously, pg_upgrade docs recommended using .pgpass if using MD5
authentication to avoid being prompted for a password.  Turns out pg_ctl
never prompts for a password, so MD5 requires .pgpass --- document that.
Also recommend 'peer' for authentication too.
Backpatch back to 9.1.
  • Loading branch information...
1 parent f02b14f commit 886c05d8e8642572af25fee23f414bd31f2e7f3e @bmomjian bmomjian committed Jul 11, 2013
Showing with 4 additions and 4 deletions.
  1. +4 −4 doc/src/sgml/pgupgrade.sgml
View
8 doc/src/sgml/pgupgrade.sgml
@@ -287,10 +287,10 @@ gmake prefix=/usr/local/pgsql.new install
<para>
<command>pg_upgrade</> will connect to the old and new servers several times,
- 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.
+ so you might want to set authentication to <literal>trust</>
+ or <literal>peer</> in <filename>pg_hba.conf</>, or if using
+ <literal>md5</> authentication, use a <filename>~/.pgpass</> file
+ (see <xref linkend="libpq-pgpass">).
</para>
</step>

0 comments on commit 886c05d

Please sign in to comment.