Re: Full GUID support

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Magnus Hagander <magnus(at)hagander(dot)net>, Josh Berkus <josh(at)agliodbs(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Full GUID support
Date: 2011-07-11 15:48:22
Message-ID: 1310399302.27274.4.camel@vanquo.pezone.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On mån, 2011-07-11 at 11:13 -0400, Tom Lane wrote:
> Magnus Hagander <magnus(at)hagander(dot)net> writes:
> > On Sun, Jul 10, 2011 at 20:59, Josh Berkus <josh(at)agliodbs(dot)com> wrote:
> >> 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.
>
> Remind me again *why* it's in core? Seems like something that ought to
> be an extension.

I think at the time, making something an add-on would have placed an
excessive burden on potential users. The claim was that most UUIDs are
generated by applications, so having the type in core would be
important, but having the generation functions not so much.

That said, there have been several proposals over the years to move a
few things out of the core into add-ons, and now that extension support
exists, we could potentially reopen that discussion.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Heikki Linnakangas 2011-07-11 15:58:05 Re: Select For Update and Left Outer Join
Previous Message Kevin Grittner 2011-07-11 15:44:17 Re: Select For Update and Left Outer Join