On Thu, May 29, 2014 at 01:56:22PM -0400, Tom Lane wrote:
> Bruce Momjian <bruce@momjian.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.
Well, the only two I could think of were the pg_dump and backend mapping
changes; pretty hacky.
> > 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.
OK. I was just worried that users are now using a badly-named uuid-ossp
extension that isn't even using uuid-ossp in many cases. If we have a
long-term plan to fix this, then you are right that it isn't worth
worrying about it now.
-- Bruce Momjian <bruce@momjian.us> http://momjian.us EnterpriseDB
http://enterprisedb.com
+ Everyone has their own god. +