Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Skip to content

Commit 9f6aacd

Browse files
committed
Update password example.
1 parent 8ddb046 commit 9f6aacd

File tree

1 file changed

+7
-5
lines changed

1 file changed

+7
-5
lines changed

doc/src/sgml/ref/createuser.sgml

Lines changed: 7 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
<!--
2-
$PostgreSQL: pgsql/doc/src/sgml/ref/createuser.sgml,v 1.49 2007/06/21 10:43:09 petere Exp $
2+
$PostgreSQL: pgsql/doc/src/sgml/ref/createuser.sgml,v 1.50 2007/06/21 12:20:10 petere Exp $
33
PostgreSQL documentation
44
-->
55

@@ -378,12 +378,14 @@ PostgreSQL documentation
378378
<prompt>$ </prompt><userinput>createuser -P -s -e joe</userinput>
379379
<computeroutput>Enter password for new role: </computeroutput><userinput>xyzzy</userinput>
380380
<computeroutput>Enter it again: </computeroutput><userinput>xyzzy</userinput>
381-
<computeroutput>CREATE ROLE joe PASSWORD 'xyzzy' SUPERUSER CREATEDB CREATEROLE INHERIT LOGIN;</computeroutput>
381+
<computeroutput>CREATE ROLE joe PASSWORD 'md5b5f5ba1a423792b526f799ae4eb3d59e' SUPERUSER CREATEDB CREATEROLE INHERIT LOGIN;</computeroutput>
382382
</screen>
383383
In the above example, the new password isn't actually echoed when typed,
384-
but we show what was typed for clarity. However the password
385-
<emphasis>will</> appear in the echoed command, as illustrated &mdash;
386-
so you don't want to use <literal>-e</> when assigning a password, if
384+
but we show what was typed for clarity. As you see, the password is
385+
encrypted before it is sent to the client. If the option <option>--unencrypted</option>
386+
is used, the password <emphasis>will</> appear in the echoed command
387+
(and possibly also in the server log and elsewhere),
388+
so you don't want to use <option>-e</> in that case, if
387389
anyone else can see your screen.
388390
</para>
389391
</refsect1>

0 commit comments

Comments
 (0)