Re: [PATCH] Implement uuid_version()
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Alvaro Herrera <alvherre@2ndquadrant.com>
Cc: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>,
Jose Luis Tallon <jltallon@adv-solutions.net>,
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>
Date: 2019-07-05T14:27:32Z
Lists: pgsql-hackers
Alvaro Herrera <alvherre@2ndquadrant.com> writes: > On 2019-Jul-05, Peter Eisentraut wrote: >> (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. > One issue with this approach is that it forces the internal function to > remain unchanged forever. That seems OK in this particular case. No, what it's establishing is that the extension and core functions will do the same thing forevermore. Seems to me that's what we want here. >> It could maybe be included if the extension version is changed for >> other reasons.) > Maybe add a comment in the control file (?) so that we remember to do it > then. I'm not terribly excited about that --- we'd still need to keep the C function redirection in place in the .so file, for benefit of people who hadn't done ALTER EXTENSION UPGRADE. regards, tom lane
Commits
-
Add gen_random_uuid function
- 5925e5549890 13.0 landed
-
Add a 64-bit hash function for type hstore.
- eb6f29141bed 12.0 cited