Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Commit9cef05e

Browse files
committed
Limit pg_upgrade authentication advice to always-secure techniques.
~/.pgpass is a sound choice everywhere, and "peer" authentication issafe 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.
1 parenta223b9e commit9cef05e

File tree

1 file changed

+6
-8
lines changed

1 file changed

+6
-8
lines changed

‎doc/src/sgml/pgupgrade.sgml

Lines changed: 6 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -280,10 +280,9 @@ gmake prefix=/usr/local/pgsql.new install
280280
<title>Adjust authentication</title>
281281

282282
<para>
283-
<command>pg_upgrade</> will connect to the old and new servers several times,
284-
so you might want to set authentication to <literal>trust</>
285-
or <literal>peer</> in <filename>pg_hba.conf</>, or if using
286-
<literal>md5</> authentication, use a <filename>~/.pgpass</> file
283+
<command>pg_upgrade</> will connect to the old and new servers several
284+
times, so you might want to set authentication to <literal>peer</>
285+
in <filename>pg_hba.conf</> or use a <filename>~/.pgpass</> file
287286
(see <xref linkend="libpq-pgpass">).
288287
</para>
289288
</step>
@@ -390,10 +389,9 @@ pg_upgrade.exe
390389
<title>Restore <filename>pg_hba.conf</></title>
391390

392391
<para>
393-
If you modified <filename>pg_hba.conf</> to use <literal>trust</>,
394-
restore its original authentication settings. It might also be
395-
necessary to adjust other configurations files in the new cluster to
396-
match the old cluster, e.g. <filename>postgresql.conf</>.
392+
If you modified <filename>pg_hba.conf</>, restore its original settings.
393+
It might also be necessary to adjust other configuration files in the new
394+
cluster to match the old cluster, e.g. <filename>postgresql.conf</>.
397395
</para>
398396
</step>
399397

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp