Skip site navigation (1) Skip section navigation (2)

Re: BUG #3965: UNIQUE constraint fails on long column values

From: Michael Fuhr <mike(at)fuhr(dot)org>
To: Francisco Olarte Sanz <folarte(at)peoplecall(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #3965: UNIQUE constraint fails on long column values
Date: 2008-02-20 14:41:54
Message-ID: 20080220144153.GA72277@winnie.fuhr.org (view raw or flat)
Thread:
Lists: pgsql-bugspgsql-docs
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

In response to

Responses

pgsql-docs by date

Next:From: Tom LaneDate: 2008-02-20 16:04:45
Subject: Re: BUG #3965: UNIQUE constraint fails on long column values
Previous:From: Gregory StarkDate: 2008-02-20 11:51:47
Subject: Re: BUG #3965: UNIQUE constraint fails on long column values

pgsql-bugs by date

Next:From: Tom LaneDate: 2008-02-20 16:04:45
Subject: Re: BUG #3965: UNIQUE constraint fails on long column values
Previous:From: Alvaro HerreraDate: 2008-02-20 12:19:38
Subject: Re: BUG #3972: ERROR: function 59015 returned NULL

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group