mirrors/postgres
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Clarify that the 'user' column still applies for 'trust'.

Browse Source
This commit is contained in:
Bruce Momjian 2004-01-26 05:35:15 +00:00
parent 3761f968c8
commit ee2f149d30
1 changed files with 4 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
doc/src/sgml/client-auth.sgml
View File

@ -1,5 +1,5 @@
<!-- <!--
$PostgreSQL: pgsql/doc/src/sgml/client-auth.sgml,v 1.62 2003/12/13 23:59:06 neilc Exp $ $PostgreSQL: pgsql/doc/src/sgml/client-auth.sgml,v 1.63 2004/01/26 05:35:15 momjian Exp $
--> -->
<chapter id="client-authentication"> <chapter id="client-authentication">
@ -535,8 +535,9 @@ local db1,db2,@demodbs all md5
<para> <para>
When <literal>trust</> authentication is specified, When <literal>trust</> authentication is specified,
<productname>PostgreSQL</productname> assumes that anyone who can <productname>PostgreSQL</productname> assumes that anyone who can
connect to the server is authorized to access the database as connect to the server is authorized to access the database with
whatever database user he specifies (including the database superuser). whatever database user they specify (including the database superuser).
Of course, restrictions placed in the <literal>user</> column still apply.
This method should only be used when there is adequate operating system-level This method should only be used when there is adequate operating system-level
protection on connections to the server. protection on connections to the server.
</para> </para>