Re: assorted documentation errors - Mailing list pgsql-bugs

FYI, this section of the patch was not applied.  It is part of other
work I am doing.


> Index: alter_user.sgml
> ===================================================================
> RCS file: /home/projects/pgsql/cvsroot/pgsql/doc/src/sgml/ref/alter_user.sgml,v
> retrieving revision 1.14
> diff -c -r1.14 alter_user.sgml
> *** alter_user.sgml    2001/07/10 22:09:27    1.14
> --- alter_user.sgml    2001/08/13 15:21:13
> ***************
> *** 27,33 ****
>
>   where <replaceable class="PARAMETER">option</replaceable> can be:
>
> !       PASSWORD '<replaceable class="PARAMETER">password</replaceable>'
>           | CREATEDB | NOCREATEDB
>           | CREATEUSER | NOCREATEUSER
>           | VALID UNTIL '<replaceable class="PARAMETER">abstime</replaceable>'
> --- 27,33 ----
>
>   where <replaceable class="PARAMETER">option</replaceable> can be:
>
> !       [ ENCRYPTED | UNENCRYPTED ] PASSWORD '<replaceable class="PARAMETER">password</replaceable>'
>           | CREATEDB | NOCREATEDB
>           | CREATEUSER | NOCREATEUSER
>           | VALID UNTIL '<replaceable class="PARAMETER">abstime</replaceable>'
> ***************
> *** 53,62 ****
>        </varlistentry>
>
>        <varlistentry>
> !       <term><replaceable class="PARAMETER">password</replaceable></term>
>         <listitem>
>          <para>
>       The new password to be used for this account.
>          </para>
>         </listitem>
>        </varlistentry>
> --- 53,65 ----
>        </varlistentry>
>
>        <varlistentry>
> !       <term><replaceable class="PARAMETER">[ encrypted | unencrypted ] password</replaceable></term>
>         <listitem>
>          <para>
>       The new password to be used for this account.
> +     <literal>Encrypted</literal>/ <literal>unencrypted</literal>
> +     controls whether the password is stored encrypted in the
> +     database.
>          </para>
>         </listitem>
>        </varlistentry>
> Index: create_user.sgml
> ===================================================================
> RCS file: /home/projects/pgsql/cvsroot/pgsql/doc/src/sgml/ref/create_user.sgml,v
> retrieving revision 1.17
> diff -c -r1.17 create_user.sgml
> *** create_user.sgml    2001/07/10 22:09:27    1.17
> --- create_user.sgml    2001/08/13 15:21:14
> ***************
> *** 28,34 ****
>   where <replaceable class="PARAMETER">option</replaceable> can be:
>
>         SYSID <replaceable class="PARAMETER">uid</replaceable>
> !         | PASSWORD '<replaceable class="PARAMETER">password</replaceable>'
>           | CREATEDB | NOCREATEDB
>           | CREATEUSER | NOCREATEUSER
>           | IN GROUP <replaceable class="PARAMETER">groupname</replaceable> [, ...]
> --- 28,34 ----
>   where <replaceable class="PARAMETER">option</replaceable> can be:
>
>         SYSID <replaceable class="PARAMETER">uid</replaceable>
> !         | [ ENCRYPTED | UNENCRYPTED ] PASSWORD '<replaceable class="PARAMETER">password</replaceable>'
>           | CREATEDB | NOCREATEDB
>           | CREATEUSER | NOCREATEUSER
>           | IN GROUP <replaceable class="PARAMETER">groupname</replaceable> [, ...]
> ***************
> *** 72,83 ****
>        </varlistentry>
>
>        <varlistentry>
> !       <term><replaceable class="parameter">password</replaceable></term>
>         <listitem>
>          <para>
>           Sets the user's password. If you do not plan to use password
>           authentication you can omit this option, otherwise the user
>           won't be able to connect to a password-authenticated server.
>           See the chapter on client authentication in the
>       <citetitle>Administrator's Guide</citetitle> for details on
>           how to set up authentication mechanisms.
> --- 72,90 ----
>        </varlistentry>
>
>        <varlistentry>
> !       <term><replaceable class="parameter">[ encrypted | unencrypted ] password</replaceable></term>
>         <listitem>
>          <para>
>           Sets the user's password. If you do not plan to use password
>           authentication you can omit this option, otherwise the user
>           won't be able to connect to a password-authenticated server.
> +     </para>
> +     <para>
> +     <literal>ENCRYPTED/UNENCRYPTED</literal> controls whether the
> +     password is stored encrypted in the database. Older clients may
> +     have trouble communicating using encrypted password storage.
> +     </para>
> +     <para>
>           See the chapter on client authentication in the
>       <citetitle>Administrator's Guide</citetitle> for details on
>           how to set up authentication mechanisms.

--
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026