From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
---|---|
To: | Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> |
Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, Andres Freund <andres(at)anarazel(dot)de>, Robert Haas <robertmhaas(at)gmail(dot)com>, David Fetter <david(at)fetter(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Jose Luis Tallon <jltallon(at)adv-solutions(dot)net> |
Subject: | Re: [PATCH] Implement uuid_version() |
Date: | 2019-07-02 07:26:16 |
Message-ID: | cb0540d0-0d18-922d-fd76-9225524bf715@2ndquadrant.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
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?
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Paquier | 2019-07-02 07:28:06 | Re: Cache lookup errors with functions manipulation object addresses |
Previous Message | Peter Eisentraut | 2019-07-02 07:19:22 | Re: Add parallelism and glibc dependent only options to reindexdb |