Re: Full GUID support

From: Magnus Hagander <magnus(at)hagander(dot)net>
To: Josh Berkus <josh(at)agliodbs(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Full GUID support
Date: 2011-07-11 14:20:18
Message-ID: CABUevEwGcgz4LJCmbgUp8visZfFvj7tddqdmRFarASt57Ta3OQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sun, Jul 10, 2011 at 20:59, Josh Berkus <josh(at)agliodbs(dot)com> wrote:
> On 7/3/11 2:02 PM, Tom Lane wrote:
>> Yeah.  If there were One True Way to create a UUID, I would probably
>> agree that we should push that functionality into core.  But there are
>> a lot of ways (and the reason for that is that they all suck in one
>> fashion or another :-().  Between that and the lack of portability of
>> many of the better ways, this is something I'm happy to keep at arm's
>> length.
>
> Also, I think that UUIDs fall into the class of "datatypes used by less
> than 10% of users" which should always remain extensions.  I'd consider
> CITEXT for core before UUID.

UUID *is* in core. It's just the generation functions that aren't.

--
 Magnus Hagander
 Me: http://www.hagander.net/
 Work: http://www.redpill-linpro.com/

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Christopher Browne 2011-07-11 14:21:54 Re: [HACKERS] Creating temp tables inside read only transactions
Previous Message Shigeru Hanada 2011-07-11 14:13:37 Re: per-column generic option