| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Dave Page <dpage(at)pgadmin(dot)org>, Michael Gould <mgould(at)intermodalsoftwaresolutions(dot)net>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Full GUID support |
| Date: | 2011-07-08 13:50:44 |
| Message-ID: | 1310133044.16196.1.camel@vanquo.pezone.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On sön, 2011-07-03 at 17:02 -0400, 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.
There is a standard, and it defines four ways to create UUIDs. AFAIR,
no one has ever claimed that there is another recognized way that we
don't support. So I don't think that's really the argument. The
argument was that we don't want to bother.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Magnus Hagander | 2011-07-08 13:53:11 | Re: Old postgresql repository |
| Previous Message | Kevin Grittner | 2011-07-08 13:45:46 | Re: Re: [COMMITTERS] pgsql: Adjust OLDSERXID_MAX_PAGE based on BLCKSZ. |