From: | Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> |
---|---|
To: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
Cc: | Jose Luis Tallon <jltallon(at)adv-solutions(dot)net>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, 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> |
Subject: | Re: [PATCH] Implement uuid_version() |
Date: | 2019-07-13 06:08:35 |
Message-ID: | alpine.DEB.2.21.1907130753320.8895@lancre |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hello Peter,
>>>> A possible option 3 is to keep the function in pgcrypto but change
>>>> its C code to call the core code.
>
> Updated patch with this change included.
Patch applies cleanly, compiles (both pg and pgcrypto). make check (global
and pgcrypto) ok. Doc generation ok. Minor comments:
About doc: I'd consider "generation" instead of "generating" as a
secondary index term.
> (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;
--
Fabien.
From | Date | Subject | |
---|---|---|---|
Next Message | Thomas Munro | 2019-07-13 06:29:16 | Re: Allow an alias to be attached directly to a JOIN ... USING |
Previous Message | Thomas Munro | 2019-07-13 05:57:24 | Re: Why is infinite_recurse test suddenly failing? |