Re: UUID column as pimrary key? - Mailing list pgsql-general

From Jasen Betts
Subject Re: UUID column as pimrary key?
Date
Msg-id ig43a7$2qv$2@reversiblemaps.ath.cx
Whole thread Raw
In response to UUID column as pimrary key?  (Dennis Gearon <gearond@sbcglobal.net>)
Responses Re: UUID column as pimrary key?  (Scott Ribe <scott_ribe@elevated-dev.com>)
List pgsql-general
On 2011-01-05, Scott Ribe <scott_ribe@elevated-dev.com> wrote:
> On Jan 5, 2011, at 9:01 AM, Tom Lane wrote:
>
>> In practical use I think the odds of a collision are *far* higher than
>> you are suggesting, unless the UUID generation is being done with a lot
>> more care than is likely if the user takes these sorts of claims at face
>> value.
>
> Eh? The user taking such claims at face value has no bearing whatsoever on the quality of the UUID generation
algorithmprovided by the OS. So, unless we're talking about users coming up with their own algorithms, it seems
reasonableto assume that the generation is done with a great deal of care. (And if we are talking about users coming up
withtheir own algorithms, then all bets are off; feel free to assume the worst.) I know that is the case on OS X &
Linux.I would be shocked if it were not the case on Solaris. I would even be surprised if it were not the case on
Windows.


> The IETF Network Working Group designed UUIDs to ensure that their
> uniqueness guarantee would be strong enough that no application would
> need to worry about duplicates, ever. Claims that collisions are too
> likely to depend on UUIDs being unique really are claims that the IETF
> Network Working Group didn't know what it was doing, which I find a
> bit ridiculous.

Who was it that decided on 32 bits for IP addresses?

--
⚂⚃ 100% natural

pgsql-general by date:

Previous
From: Stuart Bishop
Date:
Subject: Re: UUID column as pimrary key?
Next
From: Sim Zacks
Date:
Subject: linux server configuration