Re: BUG #17349: Function gen_random_uuid duplicates in pgcrypto and core - Mailing list pgsql-bugs

From Tom Lane
Subject Re: BUG #17349: Function gen_random_uuid duplicates in pgcrypto and core
Date
Msg-id 1905059.1640713316@sss.pgh.pa.us
Whole thread Raw
In response to BUG #17349: Function gen_random_uuid duplicates in pgcrypto and core  (PG Bug reporting form <noreply@postgresql.org>)
Responses Re: BUG #17349: Function gen_random_uuid duplicates in pgcrypto and core  (Andreas Dijkman <andreas.dijkman@cygnis.nl>)
List pgsql-bugs
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, the
> 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-c7d38fdae296%402ndquadrant.com#7ff316009e81aad797b6c0136251118c

            regards, tom lane



pgsql-bugs by date:

Previous
From: PG Bug reporting form
Date:
Subject: BUG #17349: Function gen_random_uuid duplicates in pgcrypto and core
Next
From: Mathias Kunter
Date:
Subject: Re: BUG #17347: pg_upgrade: analyze_new_cluster script analyzes wrong cluster