Horton

Re: [PATCH] Implement uuid_version()

Tom Lane <tgl@sss.pgh.pa.us>

View thread View on postgr.es
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Cc: Fabien COELHO <coelho@cri.ensmp.fr>, pgsql-hackers <pgsql-hackers@postgresql.org>, Andres Freund <andres@anarazel.de>, Robert Haas <robertmhaas@gmail.com>, David Fetter <david@fetter.org>, Jose Luis Tallon <jltallon@adv-solutions.net>
Date: 2019-07-02T15:09:17Z
Lists: pgsql-hackers 
Peter Eisentraut <peter.eisentraut@2ndquadrant.com> writes:
> On 2019-06-30 14:50, Fabien COELHO wrote:
>> I'm wondering whether pg_random_uuid() should be taken out of pgcrypto if 
>> it is available in core?

> That would probably require an extension version update dance in
> pgcrypto.  I'm not sure if it's worth that.  Thoughts?

We have some previous experience with this type of thing when we migrated
contrib/tsearch2 stuff into core.  I'm too caffeine-deprived to remember
exactly what we did or how well it worked.  But it seems advisable to go
study that history, because we could easily make things a mess for users
if we fail to consider their upgrade experience.

			regards, tom lane

Commits

  1. Add gen_random_uuid function

  2. Add a 64-bit hash function for type hstore.