| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
| Cc: | Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>, 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>, Jose Luis Tallon <jltallon(at)adv-solutions(dot)net> |
| Subject: | Re: [PATCH] Implement uuid_version() |
| Date: | 2019-07-02 15:09:17 |
| Message-ID: | 11633.1562080157@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2019-07-02 15:12:04 | Re: POC: converting Lists into arrays |
| Previous Message | Tom Lane | 2019-07-02 14:50:02 | Re: Hash join explain is broken |