From: David Clarke <pigwin32@gmail.com>
To: Markus Schaber <schabi@logix-tt.com>
Cc: pgsql-sql@postgresql.org
Subject: Re: Alternative to serial primary key
Date: Thu, 6 Jul 2006 23:06:09 +1200
Message-ID: <12b7ac1e0607060406r16d03f74mfa303eec9ab4821f@mail.gmail.com> (raw)
In-Reply-To: <44ACEA1C.9030804@logix-tt.com>
References: <12b7ac1e0607060316ub7b5e21i5e8e3bef2504e02c@mail.gmail.com>
<44ACEA1C.9030804@logix-tt.com>
On 7/6/06, Markus Schaber <schabi@logix-tt.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.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: pigwin32@gmail.com, schabi@logix-tt.com
Subject: Re: Alternative to serial primary key
In-Reply-To: <12b7ac1e0607060406r16d03f74mfa303eec9ab4821f@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox