| From: | Francisco Olarte Sanz <folarte(at)peoplecall(dot)com> |
|---|---|
| To: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: BUG #3965: UNIQUE constraint fails on long column values |
| Date: | 2008-02-20 11:21:03 |
| Message-ID: | 200802201221.03738.folarte@peoplecall.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-docs |
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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2008-02-20 11:25:53 | Re: BUG #3965: UNIQUE constraint fails on long column values |
| Previous Message | Heikki Linnakangas | 2008-02-20 11:00:35 | Re: GetNewOidWithIndex can cause infinite loop on user tables(not catalog). |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2008-02-20 11:25:53 | Re: BUG #3965: UNIQUE constraint fails on long column values |
| Previous Message | Gregory Stark | 2008-02-20 09:26:35 | Re: BUG #3965: UNIQUE constraint fails on long column values |