rdelaage
/
postgresql
mirror of https://git.postgresql.org/git/postgresql.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

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.
This commit is contained in:
Noah Misch 2014-07-18 16:05:17 -04:00
parent 1567e659a8
commit 85f95739ec
1 changed files with 6 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -288,10 +288,9 @@ make prefix=/usr/local/pgsql.new install
<title>Adjust authentication</title>
<para>
<command>pg_upgrade</> will connect to the old and new servers several times,
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
<command>pg_upgrade</> will connect to the old and new servers several
times, so you might want to set authentication to <literal>peer</>
in <filename>pg_hba.conf</> or use a <filename>~/.pgpass</> file
(see <xref linkend="libpq-pgpass">).
</para>
</step>
@ -406,10 +405,9 @@ pg_upgrade.exe
<title>Restore <filename>pg_hba.conf</></title>
<para>
If you modified <filename>pg_hba.conf</> to use <literal>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. <filename>postgresql.conf</>.
If you modified <filename>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. <filename>postgresql.conf</>.
</para>
</step>