Re: How can I build OSSP UUID support on Windows to avoid duplicate UUIDs?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "MauMau" <maumau307(at)gmail(dot)com>
Cc: "Alvaro Herrera" <alvherre(at)2ndquadrant(dot)com>, "Hiroshi Saito" <hiroshi(at)winpg(dot)jp>, "Dave Page" <dpage(at)pgadmin(dot)org>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: How can I build OSSP UUID support on Windows to avoid duplicate UUIDs?
Date: 2013-10-30 21:32:46
Message-ID: 6764.1383168766@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

"MauMau" <maumau307(at)gmail(dot)com> writes:
> From: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
>> Yeah, but what shall we replace it with? And can we preserve the
>> API contrib/uuid-ossp offers? (Maybe we shouldn't even try, but
>> just deprecate that module and start fresh.)

> Would it be welcomed in this community if a patch for built-in UUID
> generation functions are provided?

Based on what? The reason we've held this code at arms length (in a
contrib module) is exactly that we weren't too satisfied with the
portability or adequacy of the generation methods. Moving the functions
into core doesn't do anything to make that better; rather, it raises the
portability bar even higher, as well as making it almost impossible to
contemplate further API changes.

Note the lack of enthusiasm for taking on maintainership of the OSSP
code. Pushing it into core would mean that we're buying into that
maintainership, hook line and sinker. I don't think that such a
proposal would fly.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2013-10-31 01:26:31 Re: Something fishy happening on frogmouth
Previous Message Sergey Konoplev 2013-10-30 21:28:43 Re: [PATCH] Use MAP_HUGETLB where supported (v3)