| From: | "David Clarke" <pigwin32(at)gmail(dot)com> |
|---|---|
| To: | "Markus Schaber" <schabi(at)logix-tt(dot)com> |
| Cc: | pgsql-sql(at)postgresql(dot)org |
| Subject: | Re: Alternative to serial primary key |
| Date: | 2006-07-06 11:06:09 |
| Message-ID: | 12b7ac1e0607060406r16d03f74mfa303eec9ab4821f@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-sql |
On 7/6/06, Markus Schaber <schabi(at)logix-tt(dot)com> wrote:
> This is a good idea if you want to have taller indices, but you still
> need to re-check the "real" key due to hash collisions.
I am aware there are collisions with md5 but without any actual proof
I believe the risk to be very low with the data I'm storing which is a
kind of scrubbed free form residential address.
>
> If you've plenty of time to spend, you could also bring the hash index
> type back to life, which is currently deprecated according to the
> PostgreSQL docs...
Unfortunately with the meagre time I have available, the only dent I'm
likely to make is in the wall with my head.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Markus Schaber | 2006-07-06 11:10:55 | Re: Alternative to serial primary key |
| Previous Message | Markus Schaber | 2006-07-06 10:46:52 | Re: Alternative to serial primary key |