On Wed, Mar 2, 2016 at 5:43 PM, Valery Popov <v.po...@postgrespro.ru> wrote: > >>> <para> >>> <varname>db_user_namespace</> causes the client's and >>> server's user name representation to differ. >>> Authentication checks are always done with the server's user name >>> so authentication methods must be configured for the >>> server's user name, not the client's. Because >>> <literal>md5</> uses the user name as salt on both the >>> client and server, <literal>md5</> cannot be used with >>> <varname>db_user_namespace</>. >>> </para> > > Also in doc/src/sgml/ref/create_role.sgml is should be instead of > <term>PASSWORD VERIFIERS ( <replaceable > class="PARAMETER">verifier_type</replaceable> = '<replaceable > class="PARAMETER">password</replaceable>'</term> > like this > <term><literal>PASSWORD VERIFIERS</> ( <replaceable > class="PARAMETER">verifier_type</replaceable> = '<replaceable > class="PARAMETER">password</replaceable>'</term>
So the <literal> markup is missing. Thanks. I am taking note of it. -- Michael -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
