Re: GUID for postgreSQL

From: Greg Stark <gsstark(at)mit(dot)edu>
To: "John D(dot) Burger" <john(at)mitre(dot)org>
Cc: Postgresql-General <pgsql-general(at)postgresql(dot)org>
Subject: Re: GUID for postgreSQL
Date: 2005-07-29 16:58:34
Message-ID: 87slxx7dmt.fsf@stark.xeocode.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general


"John D. Burger" <john(at)mitre(dot)org> writes:

> > If you use a large enough space for the number you can reduce that
> > probability of an accidental collision to much less than that of
> > catastrophic hardware failure at which point it isn't noticably better
> > than having no chance of collisions.
>
> I find the comparison unconvincing - if my hardware crashes, I know it and can
> decide how to recover. If two UIDs collide, my system may silently do
> something that may never be detected.

Alright, say the probability of a cosmic ray flipping one bit (if you're
picky, flipping two or three bits perfectly arranged so ECC ram doesn't detect
it). That would produce similarly subtle and unpredictable behaviour,
especially if it hit in a primary key.

Though I'm inclined to agree. They seem to be a fad with not much reason to
exist.

--
greg

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Bruno Wolff III 2005-07-29 17:13:17 Re: GUID for postgreSQL
Previous Message Greg Stark 2005-07-29 16:52:40 Re: Megabytes of stats saved after every connection