Re: BUG #8467: Slightly confusing pgcrypto example in docs - Mailing list pgsql-bugs

From Peter Eisentraut
Subject Re: BUG #8467: Slightly confusing pgcrypto example in docs
Date
Msg-id 1381450950.5264.3.camel@vanquo.pezone.net
Whole thread Raw
In response to Re: BUG #8467: Slightly confusing pgcrypto example in docs  (Bruce Momjian <bruce@momjian.us>)
Responses Re: BUG #8467: Slightly confusing pgcrypto example in docs  (Bruce Momjian <bruce@momjian.us>)
List pgsql-bugs
On Thu, 2013-10-10 at 19:14 -0400, Bruce Momjian wrote:
> > The changes shown below are incorrect, I think.
> >
> >
> > On 10/2/13 12:00 PM, Bruce Momjian wrote:
> > > *************** gen_salt(type text [, iter_count integer
> > > *** 353,359 ****
> > >          <entry>12 years</entry>
> > >         </row>
> > >         <row>
> > > !        <entry><literal>md5</></entry>
> > >          <entry>2345086</entry>
> > >          <entry>1 day</entry>
> > >          <entry>3 years</entry>
> > > --- 358,364 ----
> > >          <entry>12 years</entry>
> > >         </row>
> > >         <row>
> > > !        <entry><literal>md5 hash</></entry>
>
> Uh, the table already has a mention of md5 crypt above:
>
>        <entry><literal>crypt-md5</></entry>
>
> How can the later entry not be MD5 hash?

Because what you pass to the functions is 'md5', not 'md5 hash', which
is what the new text appears to indicate.

pgsql-bugs by date:

Previous
From: 'Bruce Momjian'
Date:
Subject: Re: BUG #8516: Calling VOLATILE from STABLE function
Next
From: Bruce Momjian
Date:
Subject: Re: BUG #8467: Slightly confusing pgcrypto example in docs