From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | David Fetter <david(at)fetter(dot)org>, Jose Luis Tallon <jltallon(at)adv-solutions(dot)net>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: [PATCH] Implement uuid_version() |
Date: | 2019-04-08 15:34:35 |
Message-ID: | 32713.1554737675@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Robert Haas <robertmhaas(at)gmail(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Fabien COELHO | 2019-04-08 15:43:24 | pgbench - add option to show actual builtin script code |
Previous Message | Robert Haas | 2019-04-08 15:06:57 | Re: [PATCH] Implement uuid_version() |