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

Commitee2f149

Browse files
committed
Clarify that the 'user' column still applies for 'trust'.
1 parent3761f96 commitee2f149

File tree

1 file changed

+4
-3
lines changed

1 file changed

+4
-3
lines changed

‎doc/src/sgml/client-auth.sgml

Lines changed: 4 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
<!--
2-
$PostgreSQL: pgsql/doc/src/sgml/client-auth.sgml,v 1.62 2003/12/13 23:59:06 neilc Exp $
2+
$PostgreSQL: pgsql/doc/src/sgml/client-auth.sgml,v 1.63 2004/01/26 05:35:15 momjian Exp $
33
-->
44

55
<chapter id="client-authentication">
@@ -535,8 +535,9 @@ local db1,db2,@demodbs all md5
535535
<para>
536536
When <literal>trust</> authentication is specified,
537537
<productname>PostgreSQL</productname> assumes that anyone who can
538-
connect to the server is authorized to access the database as
539-
whatever database user he specifies (including the database superuser).
538+
connect to the server is authorized to access the database with
539+
whatever database user they specify (including the database superuser).
540+
Of course, restrictions placed in the <literal>user</> column still apply.
540541
This method should only be used when there is adequate operating system-level
541542
protection on connections to the server.
542543
</para>

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp