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

From Francisco Olarte Sanz
Subject Re: BUG #3965: UNIQUE constraint fails on long column values
Date
Msg-id 200802201221.03738.folarte@peoplecall.com
Whole thread Raw
In response to Re: BUG #3965: UNIQUE constraint fails on long column values  (Gregory Stark <stark@enterprisedb.com>)
Responses Re: BUG #3965: UNIQUE constraint fails on long column values  (Michael Fuhr <mike@fuhr.org>)
List pgsql-bugs
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:

The MD5 algorithm is designed to be quite fast on 32-bit machines. In
   addition, the MD5 algorithm does not require any large substitution
   tables; the algorithm can be coded quite compactly.

F.O.S.

pgsql-bugs by date:

Previous
From: "Heikki Linnakangas"
Date:
Subject: Re: GetNewOidWithIndex can cause infinite loop on user tables(not catalog).
Next
From: "Heikki Linnakangas"
Date:
Subject: Re: BUG #3965: UNIQUE constraint fails on long column values