Re: [PATCH] Implement uuid_version()
Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
From: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
To: Fabien COELHO <coelho@cri.ensmp.fr>
Cc: Jose Luis Tallon <jltallon@adv-solutions.net>,
Alvaro Herrera <alvherre@2ndquadrant.com>, Tom Lane <tgl@sss.pgh.pa.us>,
pgsql-hackers <pgsql-hackers@postgresql.org>,
Andres Freund <andres@anarazel.de>, Robert Haas <robertmhaas@gmail.com>,
David Fetter <david@fetter.org>
Date: 2019-07-13T12:36:54Z
Lists: pgsql-hackers
On 2019-07-13 08:08, Fabien COELHO wrote: > About doc: I'd consider "generation" instead of "generating" as a > secondary index term. We do use the "-ing" form for other secondary index terms. It's useful because the concatenation of primary and secondary term should usually make a phrase of some sort. The alternative would be "generation of", but that doesn't seem clearly better. >> (There is also precedent for redirecting the extension function to the >> internal one by changing the SQL-level function definition using CREATE >> OR REPLACE FUNCTION ... LANGUAGE INTERNAL. But that seems more >> complicated and would require a new extension version. It could maybe >> be included if the extension version is changed for other reasons.) > > What about avoiding a redirection with something like: > > Datum (* const pg_random_uuid)(PG_FUNCTION_ARGS) = gen_random_uuid; That seems very confusing. -- Peter Eisentraut http://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