| 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 |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2008-02-20 16:04:45 | Re: BUG #3965: UNIQUE constraint fails on long column values |
| Previous Message | Alvaro Herrera | 2008-02-20 12:19:38 | Re: BUG #3972: ERROR: function 59015 returned NULL |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2008-02-20 16:04:45 | Re: BUG #3965: UNIQUE constraint fails on long column values |
| Previous Message | Gregory Stark | 2008-02-20 11:51:47 | Re: BUG #3965: UNIQUE constraint fails on long column values |