database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-07-30 11:03:19 +03:00
Code Activity

Limit pg_upgrade authentication advice to always-secure techniques.

Browse Source 
~/.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 8a817785ad
commit 3f09bb8d27
1 changed files with 4 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@ -252,10 +252,9 @@ gmake 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>
@ -355,8 +354,7 @@ 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.
If you modified <filename>pg_hba.conf</>, restore its original settings.
</para>
</step>