| From: | Andrew Sullivan <ajs(at)crankycanuck(dot)ca> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: UUID column as pimrary key? |
| Date: | 2011-01-06 03:26:50 |
| Message-ID: | 20110106032648.GB25891@shinkuro.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Wed, Jan 05, 2011 at 07:44:29PM -0700, Scott Ribe wrote:
> In order for a collision to matter, really in order for there to *be* a collision, the duplicate pair has to be collected in one place.
Not at the time of generation, though. They only have to end up in
the same place at once. For most cases, the value of the data
compared to the improbably low liklihood of collision means that you
deal with this case by saying, "Yuck. Well, someone loses." But if
the data is valuable enough (say, unique identifiers for nuclear
warheads), that's just not an acceptable trade-off.
A
--
Andrew Sullivan
ajs(at)crankycanuck(dot)ca
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Sullivan | 2011-01-06 05:30:45 | Re: UUID column as pimrary key? |
| Previous Message | Gordon Shannon | 2011-01-06 03:26:39 | walreceiver getting bad data? |