database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-07-20 05:03:10 +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 b8c24f7ab8
commit ec66f1adbf
1 changed files with 5 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@ -235,11 +235,10 @@ gmake prefix=/usr/local/pgsql.new install
<title>Adjust authentication</title> <title>Adjust authentication</title>
<para> <para>
<command>pg_upgrade</> will connect to the old and new servers several times, <command>pg_upgrade</> will connect to the old and new servers several
so you might want to set authentication to <literal>trust</> in times, so you might want to set <literal>local</> Unix-domain socket
<filename>pg_hba.conf</>, or if using <literal>md5</> authentication, authentication to <literal>ident</> in <filename>pg_hba.conf</> or use
use a <filename>~/.pgpass</> file (see <xref linkend="libpq-pgpass">) a <filename>~/.pgpass</> file (see <xref linkend="libpq-pgpass">).
to avoid being prompted repeatedly for a password.
</para> </para>
</step> </step>
@ -338,8 +337,7 @@ pg_upgrade.exe
<title>Restore <filename>pg_hba.conf</></title> <title>Restore <filename>pg_hba.conf</></title>
<para> <para>
If you modified <filename>pg_hba.conf</> to use <literal>trust</>, If you modified <filename>pg_hba.conf</>, restore its original settings.
restore its original authentication settings.
</para> </para>
</step> </step>