MIME-Version: 1.0
In-Reply-To: <30137.1397057056@sss.pgh.pa.us>
References: <27299.1396989666@sss.pgh.pa.us>
 <CAM3SWZQGZyqSBzaFZ4gmtnQZpcXLE=ceUL_O29gtMgnP=AvC+g@mail.gmail.com>
 <28589.1396992841@sss.pgh.pa.us>
 <CAM3SWZRAxisGCdODhbgeiNL6tayqL18XMzun4W3xesASmKfwDA@mail.gmail.com>
 <29030.1396993582@sss.pgh.pa.us>
 <CAM3SWZQzOxmryVe_bdu9WhqbJTBoiqM7knvKm0oRYxvfsFnz7Q@mail.gmail.com>
 <534475B7.6020908@dunslane.net> <5344EAA4.1050605@vmware.com>
 <CA+TgmoZucoe-w5P_16A-gdfRBFCCu7PD17YO-KqrYPBhb5TxAA@mail.gmail.com>
 <30137.1397057056@sss.pgh.pa.us>
Date: Wed, 9 Apr 2014 09:51:43 -0700
Message-ID: 
 <CAM3SWZQ2Pd9d7Ae3BbjyqZ5=FD+3FMaNcer9bG=xHAufbsqdPA@mail.gmail.com>
Subject: Re: default opclass for jsonb (was Re: Call for
 GIST/GIN/SP-GIST opclass documentation)
From: Peter Geoghegan <pg@heroku.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Robert Haas <robertmhaas@gmail.com>,
 Heikki Linnakangas <hlinnakangas@vmware.com>,
 Andrew Dunstan <andrew@dunslane.net>,
 "pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>
Content-Type: text/plain; charset=UTF-8
Precedence: bulk
Sender: pgsql-hackers-owner@postgresql.org

On Wed, Apr 9, 2014 at 8:24 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> Maybe we should make *neither* of these the default opclass, and give
>> *neither* the name json_ops.
>
> There's definitely something to be said for that.  Default opclasses are
> sensible when there's basically only one behavior that's interesting for
> most people.  We can already see that that's not going to be the case
> for jsonb indexes, at least not with the currently available alternatives.

I've heard worse ideas.


-- 
Peter Geoghegan


-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers