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