Re: [PATCH] Implement uuid_version()
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Robert Haas <robertmhaas@gmail.com>
Cc: David Fetter <david@fetter.org>,
Jose Luis Tallon <jltallon@adv-solutions.net>,
pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2019-04-08T15:34:35Z
Lists: pgsql-hackers
Robert Haas <robertmhaas@gmail.com> writes: > My biggest gripe about uuid-ossp is that the name is stupid. I wish > we could see our way clear to renaming that extension to just 'uuid', > because as J.L. says, virtually nobody's actually compiling against > the OSSP library any more. +1 There's no ALTER EXTENSION RENAME, and I suppose there can't be because it would require editing/rewriting on-disk files that the server might not even have write permissions for. But your idea of an "update" script that effectively moves everything over into a new extension (that's physically installed but not present in current database) might work. Another way to approach it would be to have a script that belongs to the new extension and what you do is CREATE EXTENSION uuid FROM "uuid_ossp"; to perform the migration of the SQL objects. Either way, we'd be looking at providing two .so's for some period of time, but fortunately they're small. 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