Re: Hash Function: MD5 or other? - Mailing list pgsql-general

From Tino Wildenhain
Subject Re: Hash Function: MD5 or other?
Date
Msg-id 1118738065.5605.43.camel@sabrina.peacock.de
Whole thread Raw
In response to Re: Hash Function: MD5 or other?  (Greg Stark <gsstark@mit.edu>)
List pgsql-general
Am Dienstag, den 14.06.2005, 02:40 -0400 schrieb Greg Stark:
> Shelby Cain <alyandon@yahoo.com> writes:
>
> > > My question is: is the builtin MD5 appropriate for this use or should I be
> > > using a function from pl/something? Figures on collision rates would be
> > > nice as well - the typical chunk of text is probably 1k-8k.
>
> Note that MD5 is slow and CPU-intensive. By design.
>
> If you want a quick way to find matching records then you might find something
> like CRC to be more useful. With MD5 it's supposed to be hard for someone to
> come up with inputs that hash to a target value, but if you're not too worried
> about people trying to do that then MD5 is probably overkill.
>
Sha1 is said to be faster.
(And less likely to collisions)
--
Tino Wildenhain <tino@wildenhain.de>


pgsql-general by date:

Previous
From: Devrim GUNDUZ
Date:
Subject: Re: postgresql rpms (7.4.2, 7.4.5, 7.4.8) for redhat 8.0
Next
From: Ioannis Theoharis
Date:
Subject: Re: suse 9.2