On Dec 18, 2011, at 4:41 AM, Magnus Hagander wrote:
> We can hopefully get around this for the extensions in contrib (and
> reasonably well has already), but few large companies are going to be
> happy to go to pgxn and download an extension that has a single
> maintainer (not "the team", and in most cases not even "a team"),
> usually no defined lifecycle, no support, etc. (I'm pretty sure you
> won't get support included for random pgxn modules when you buy a
> contract from EDB, or CMD, or us, or PGX, or anybody really - wheras
> if it the datatype is in core, you *will* get this)
I support having a JSON type in core, but question the assertions here. *Some* organizations won’t use PGXN, usually
becausethey require things through a different ecosystem (RPMs, .debs, StackBuilder, etc.). But many others will. There
area *lot* of companies out there that use CPAN, easy_install, and Gem. The same sorts of places will use PGXN.
Oh, and at PGX, we’ll happily provide support for random modules, so long as you pay for our time. We’re not picky (and
happyto send improvements back upstream), though we might recommend you switch to something better. But such
evaluationsare based on quality, not simply on what ecosystem it came from.
> If we can find a way to have a stable part in core and then have
> addons that can provide these "tons of interesting features" (which I
> agree there are) until such time that they can be considered stable
> enough for core, I think that's the best compromise.
+1, though I think the core type will at least need some basic operators and indexing support.
Best,
David