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

From Tom Lane
Subject Re: default opclass for jsonb (was Re: Call for GIST/GIN/SP-GIST opclass documentation)
Date
Msg-id 18360.1399633457@sss.pgh.pa.us
Whole thread Raw
In response to Re: default opclass for jsonb (was Re: Call for GIST/GIN/SP-GIST opclass documentation)  (Gavin Flower <GavinFlower@archidevsys.co.nz>)
Responses Re: default opclass for jsonb (was Re: Call for GIST/GIN/SP-GIST opclass documentation)
List pgsql-hackers
Gavin Flower <GavinFlower@archidevsys.co.nz> writes:
> On 09/05/14 15:34, Bruce Momjian wrote:
>> Looks good.  I was thinking the jsonb_ops name could remain unchanged
>> and the jsonb_hash_ops could be called jsonb_combo_ops as it combines
>> the key and value into a single index entry.

> If you have 'jsonb_combo_ops' - then surely 'jsonb_op' should be called 
> 'jsonb_xxx_ops', where the 'xxx' distinguishes that from 
> 'jsonb_combo_ops'?  I guess, if any appropriate wording of 'xxx' was too 
> cumbersome, then it would be worse.

Yeah, I'm disinclined to change the opclass names now.  It's not apparent
to me that "combo" is a better choice than "hash" for the second opclass.
        regards, tom lane



pgsql-hackers by date:

Previous
From: Thom Brown
Date:
Subject: Re: [WIP] showing index maintenance on EXPLAIN
Next
From: Michael Paquier
Date:
Subject: Cache lookup error when using jsonb, json_build_object and a WITH clause