Re: [PATCHES] Patch for UUID datatype (beta) - Mailing list pgsql-hackers

From Gregory Stark
Subject Re: [PATCHES] Patch for UUID datatype (beta)
Date
Msg-id 87k63y9af3.fsf@stark.xeocode.com
Whole thread Raw
In response to Re: [PATCHES] Patch for UUID datatype (beta)  (mark@mark.mielke.cc)
Responses Re: [PATCHES] Patch for UUID datatype (beta)
Re: [PATCHES] Patch for UUID datatype (beta)
List pgsql-hackers
mark@mark.mielke.cc writes:

> I have the impression I'm not being heard.
> 
> *I* control the MAC address assignment for all of *MY* units.

No, you're missing the point. How does that help *me* avoid collisions with
your UUIDs? UUIDs are supposed to be unique period, not just unique on your
database.

If all you want is unique number generation in your database then you can just
use sequences and they'll take a lot less space and perform much better.
(16-byte foreign keys throughout the whole database, *shudder*)

The reason to use UUIDs is when you want to have unique identifiers that you
can send outside the database and know they won't conflict with other unique
identifiers generated elsewhere.


Really this whole debate only reinforces the point that there isn't a single
way of doing UUID generation. There are multiple libraries out there each with
pros and cons. It makes more sense to have multiple pgfoundry UUID generating
modules.



-- 
greg



pgsql-hackers by date:

Previous
From: "Albe Laurenz"
Date:
Subject: 'configure --disable-shared' and 'make check'
Next
From: Jeremy Drake
Date:
Subject: Re: [PATCHES] Patch for UUID datatype (beta)