| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us> |
| Cc: | Andres Freund <andres(at)2ndquadrant(dot)com>, Peter Eisentraut <peter_e(at)gmx(dot)net>, Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, "David E(dot) Wheeler" <david(at)justatheory(dot)com>, Matteo Beccati <php(at)beccati(dot)com>, pgsql-hackers list <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [PATCH] Replacement for OSSP-UUID for Linux and BSD |
| Date: | 2014-05-29 17:56:22 |
| Message-ID: | 13124.1401386182@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Bruce Momjian <bruce(at)momjian(dot)us> writes:
> One thing that concerns me is that we already had the problem that users
> creating the uuid-ossp extension had to double-quote the name because of
> the dash, and we have regularly questioned the viability of the
> uuid-ossp codebase.
> Now that we know we have to support alternatives, we are changing the
> build API to support those alternatives, but doing nothing to decouple
> the extension name from uuid-ossp and the dash issue.
Well, if you've got a proposal for how to rename the extension without
creating major compatibility problems, let's hear it.
> Seems this would be the logical time to just break compatibility and get
> a sane API for UUID generation.
Most people think the "sane API" would be to put the functionality in
core, and forget about any extension name at all. The compatibility
problems with that approach aren't exactly trivial either, but I suspect
that's where we'll end up in the long run. So I'm not that excited about
kluge solutions for renaming the extension.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2014-05-29 18:38:36 | Re: Odd uuid-ossp behavior on smew and shearwater |
| Previous Message | Bruce Momjian | 2014-05-29 17:42:48 | Re: recovery testing for beta |