X-Original-To: pgsql-sql-postgresql.org@postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id 759E79FA147 for ; Thu, 6 Jul 2006 08:06:20 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 07657-06 for ; Thu, 6 Jul 2006 08:06:12 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey- Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.169]) by postgresql.org (Postfix) with ESMTP id 0013F9FA0EC for ; Thu, 6 Jul 2006 08:06:11 -0300 (ADT) Received: by ug-out-1314.google.com with SMTP id a2so2621692ugf for ; Thu, 06 Jul 2006 04:06:10 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=LFwSJ3QrxOJrTPLRes/MoMLFzNztE4qeh0tbkp5UMnH8Nj0hyt+R6NkoXpIvn59ub+OeAKwpfzWgSNN8AijZD9Zb6enqNEmS94WVtTcmavy40kmiKKdltOFepgMG490Qfu25xnIZYckY1Jm36jLfVsPmIA73fdDBUB/p4hXe4uo= Received: by 10.66.220.17 with SMTP id s17mr566427ugg; Thu, 06 Jul 2006 04:06:10 -0700 (PDT) Received: by 10.67.23.14 with HTTP; Thu, 6 Jul 2006 04:06:09 -0700 (PDT) Message-ID: <12b7ac1e0607060406r16d03f74mfa303eec9ab4821f@mail.gmail.com> Date: Thu, 6 Jul 2006 23:06:09 +1200 From: "David Clarke" To: "Markus Schaber" Subject: Re: Alternative to serial primary key Cc: pgsql-sql@postgresql.org In-Reply-To: <44ACEA1C.9030804@logix-tt.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <12b7ac1e0607060316ub7b5e21i5e8e3bef2504e02c@mail.gmail.com> <44ACEA1C.9030804@logix-tt.com> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200607/56 X-Sequence-Number: 25630 On 7/6/06, Markus Schaber 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.