On 7/2/19 10:03, Dave Page wrote:
> On Thu, Feb 7, 2019 at 8:26 AM Peter Eisentraut
> <peter.eisentraut@2ndquadrant.com> wrote:
>> I'm wondering whether we should phase out the use of the ossp-uuid
>> library? (not the uuid-ossp extension)
Hmm... FWIW, just get it in core altogether? Seems small and useful
enough... if it carries the opfamily with it, UUID would become really
convenient to use for distributed applications.
(being using that functionality for a while, already)
>> We have had preferred
>> alternatives for a while now, so it shouldn't be necessary to use this
>> anymore, except perhaps in some marginal circumstances? As we know,
>> ossp-uuid isn't maintained anymore, and a few weeks ago the website was
>> gone altogether, but it seems to be back now.
>>
>> I suggest we declare it deprecated in PG12 and remove it altogether in PG13.
> Much as I'd like to get rid of it, we don't have an alternative for
> Windows do we? The docs for 11 imply it's required for UUID support
> (though the wording isn't exactly clear, saying it's required for
> UUID-OSSP support!):
> https://www.postgresql.org/docs/11/install-windows-full.html#id-1.6.4.8.8
AFAIR, Windows has its own DCE/v4 UUID generation support. UUID v5 can
be generated using built-in crypto hashes. v1 are the ones (potentially)
more cumbersome to generate.... plus they are the least useful IMHO.
Just my .02€
Thanks,
/ J.L.
