Re: BUG #3965: UNIQUE constraint fails on long column values - Mailing list pgsql-bugs

From Michael Fuhr
Subject Re: BUG #3965: UNIQUE constraint fails on long column values
Date
Msg-id 20080220144153.GA72277@winnie.fuhr.org
Whole thread Raw
In response to Re: BUG #3965: UNIQUE constraint fails on long column values  (Francisco Olarte Sanz <folarte@peoplecall.com>)
Responses Re: BUG #3965: UNIQUE constraint fails on long column values
List pgsql-bugs
On Wed, Feb 20, 2008 at 12:21:03PM +0100, Francisco Olarte Sanz wrote:
> On Wednesday 20 February 2008, Gregory Stark wrote:
>
> > Unless you need cryptographic security I would not suggest using MD5. MD5
> > is intentionally designed to take a substantial amount of CPU resources to
> > calculate.
>
> I thought it was the exact opposite, quoting from RFC1321:

And if you *do* need cryptographic security then don't use MD5, and
consider using SHA-256 instead of SHA-1.  See RFC 4270 for discussion.

ftp://ftp.rfc-editor.org/in-notes/rfc4270.txt

--
Michael Fuhr

pgsql-bugs by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: BUG #3972: ERROR: function 59015 returned NULL
Next
From: Tom Lane
Date:
Subject: Re: BUG #3965: UNIQUE constraint fails on long column values