mirror/postgresql
2
0
Fork 0
mirror of https://git.postgresql.org/git/postgresql.git synced 2024-12-21 08:29:39 +08:00
Code Issues Packages Projects Releases Wiki Activity

Update some ALTER USER cross-references to ALTER ROLE

Browse Source 
Greg Smith
This commit is contained in:
Alvaro Herrera 2011-05-02 13:40:24 -03:00
parent 4b08bf8ce7
commit 52897e54db
3 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -889,7 +889,7 @@ omicron bryanh guest1
each database user is stored in the <literal>pg_authid</> system
catalog. Passwords can be managed with the SQL commands
<xref linkend="sql-createuser"> and
<xref linkend="sql-alteruser">,
<xref linkend="sql-alterrole">,
e.g., <userinput>CREATE USER foo WITH PASSWORD 'secret'</userinput>.
If no password has been set up for a user, the stored password
is null and password authentication will always fail for that user.

6
doc/src/sgml/config.sgml
View File

@ -135,7 +135,7 @@ env PGOPTIONS='-c geqo=off' psql
Furthermore, it is possible to assign a set of parameter settings to
a user or a database. Whenever a session is started, the default
settings for the user and database involved are loaded. The
commands <xref linkend="sql-alteruser">
commands <xref linkend="sql-alterrole">
and <xref linkend="sql-alterdatabase">,
respectively, are used to configure these settings. Per-database
settings override anything received from the
@ -705,7 +705,7 @@ SET ENABLE_SEQSCAN TO OFF;
<para>
When a password is specified in <xref
linkend="sql-createuser"> or
<xref linkend="sql-alteruser">
<xref linkend="sql-alterrole">
without writing either <literal>ENCRYPTED</> or
<literal>UNENCRYPTED</>, this parameter determines whether the
password is to be encrypted. The default is <literal>on</>
@ -5205,7 +5205,7 @@ dynamic_library_path = 'C:\tools\postgresql;H:\my_project\lib;$libdir'
libraries to be loaded into specific sessions without an explicit
<command>LOAD</> command being given. For example, debugging could
be enabled for all sessions under a given user name by setting
this parameter with <command>ALTER USER SET</>.
this parameter with <command>ALTER ROLE SET</>.
</para>
<para>

2
doc/src/sgml/libpq.sgml
View File

@ -6387,7 +6387,7 @@ myEventProc(PGEventId evtId, void *evtInfo, void *passThrough)
<para>
The following environment variables can be used to specify default
behavior for each <productname>PostgreSQL</productname> session. (See
also the <xref linkend="sql-alteruser">
also the <xref linkend="sql-alterrole">
and <xref linkend="sql-alterdatabase">
commands for ways to set default behavior on a per-user or per-database
basis.)