Re: default opclass for jsonb (was Re: Call for GIST/GIN/SP-GIST opclass documentation)

Tom Lane wrote:

> > On Wed, Apr 9, 2014 at 2:37 AM, Heikki Linnakangas
> > <hlinnakangas@vmware.com> wrote:
> >> Both of the operator classes are actually much less flexible than I'd like.
> 
> > Maybe we should make *neither* of these the default opclass, and give
> > *neither* the name json_ops.

+1.  I was thinking the same thing after reading Heikki's rant.

> One other point here is that non-default opclasses can't be used in
> UNIQUE/PRIMARY KEY/EXCLUDE constraints, because there's no place to
> specify an opclass name in those syntaxes.  UNIQUE/PRIMARY KEY don't
> matter here since these aren't btree opclasses, but is there a
> use-case for EXCLUDE with any of the supported jsonb operators?

That sounds like an oversight that could better be fixed in EXCLUDE, no?

-- 
Álvaro Herrera                http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services