From: Tom Lane <tgl@sss.pgh.pa.us>
To: andreas.dijkman@cygnis.nl
cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #17349: Function gen_random_uuid duplicates in pgcrypto and
 core
In-reply-to: <17349-24d61e214429e8c1@postgresql.org>
References: <17349-24d61e214429e8c1@postgresql.org>
Comments: In-reply-to PG Bug reporting form <noreply@postgresql.org>
	message dated "Tue, 28 Dec 2021 16:31:15 +0000"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <1905058.1640713316.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Tue, 28 Dec 2021 12:41:56 -0500
Message-ID: <1905059.1640713316@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/1905059.1640713316%40sss.pgh.pa.us>
Precedence: bulk

PG Bug reporting form <noreply@postgresql.org> writes:
> As stated in
> https://www.postgresql.org/docs/current/pgcrypto.html#id-1.11.7.35.10, t=
he
> function gen_random_uuid is now part of core PostgreSQL. Shouldn't this
> function be removed from the pgcrypto-extension as of PostgreSQL 13?

pg_crypto's gen_random_uuid() is now just a wrapper for the core function.
Taking it out entirely would save only a couple lines of code.

> If you install the pgcrypto-extension in the pg_catalog-schema (yes, I'm
> aware if installing it in public the error doesn't occur) you get an
> error:

The contrary side of that is that taking it out of the extension could
break applications that expect gen_random_uuid() to exist in the
extension's schema.  I don't think we consider installing extensions
in pg_catalog to be a supported case, anyway.

See previous discussion at

https://www.postgresql.org/message-id/flat/5b2c6230-e0b9-59a9-b945-c7d38fd=
ae296%402ndquadrant.com#7ff316009e81aad797b6c0136251118c

			regards, tom lane