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

Поиск
Список
Период
Сортировка
От Francisco Olarte Sanz
Тема Re: BUG #3965: UNIQUE constraint fails on long column values
Дата
Msg-id 200802201221.03738.folarte@peoplecall.com
обсуждение исходный текст
Ответ на Re: BUG #3965: UNIQUE constraint fails on long column values  (Gregory Stark <stark@enterprisedb.com>)
Ответы Re: BUG #3965: UNIQUE constraint fails on long column values  (Michael Fuhr <mike@fuhr.org>)
Список 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 по дате отправления:

Предыдущее
От: "Heikki Linnakangas"
Дата:
Сообщение: Re: GetNewOidWithIndex can cause infinite loop on user tables(not catalog).
Следующее
От: "Heikki Linnakangas"
Дата:
Сообщение: Re: BUG #3965: UNIQUE constraint fails on long column values