Re: [PATCH] Implement uuid_version() - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: [PATCH] Implement uuid_version()
Date
Msg-id 7ac17303-ee5b-0266-29db-a3ce3baa5283@2ndquadrant.com
Whole thread Raw
In response to Re: [PATCH] Implement uuid_version()  (Fabien COELHO <coelho@cri.ensmp.fr>)
Responses Re: [PATCH] Implement uuid_version()  (Fabien COELHO <coelho@cri.ensmp.fr>)
List 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



pgsql-hackers by date:

Previous
From: Joe Conway
Date:
Subject: Re: [Proposal] Table-level Transparent Data Encryption (TDE) and KeyManagement Service (KMS)
Next
From: Peter Eisentraut
Date:
Subject: Re: initdb recommendations