Re: [PATCH] Implement uuid_version()
Alvaro Herrera <alvherre@2ndquadrant.com>
From: Alvaro Herrera <alvherre@2ndquadrant.com>
To: Jose Luis Tallon <jltallon@adv-solutions.net>
Cc: Fabien COELHO <coelho@cri.ensmp.fr>, Tom Lane <tgl@sss.pgh.pa.us>, pgsql-hackers <pgsql-hackers@postgresql.org>, Peter Eisentraut <peter.eisentraut@2ndquadrant.com>, Andres Freund <andres@anarazel.de>, Robert Haas <robertmhaas@gmail.com>, David Fetter <david@fetter.org>
Date: 2019-09-02T16:00:25Z
Lists: pgsql-hackers
On 2019-Jul-13, Jose Luis Tallon wrote: > Considering the later arguments on-list, I plan on submitting a more > elaborate patchset integrating the feedback received so far, and along the > following lines: > > - uuid type, v4 generation and uuid_version() in core > > - Provide a means to rename/supercede extensions keeping backwards > compatibility (i.e. uuid-ossp -> uuid, keep old code working) It is wholly unclear what this commitfest entry is all about; in the thread there's a mixture about a new uuid_version(), some new v4 stuff migrating from pgcrypto (which apparently was done), plus some kind of mechanism to allow upgrading extension names; all this stemming from feedback from the patch submitted in April. But there hasn't been a new patch in a long time, and there won't be a new patch version during the current commitfest. Therefore, I'm closing this entry as Returned with Feedback. The author(s) can create a new entry in a future commitfest once they have a new patch. I do suggest to keep such a patch restricted in scope. -- Álvaro Herrera https://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
Commits
-
Add gen_random_uuid function
- 5925e5549890 13.0 landed
-
Add a 64-bit hash function for type hstore.
- eb6f29141bed 12.0 cited