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

From Greg Stark
Subject Re: default opclass for jsonb (was Re: Call for GIST/GIN/SP-GIST opclass documentation)
Date
Msg-id CAM-w4HOQ+ynm70Cgr4BwMqMc0jfL_8EZAwG2UD6r=EehjH3OOw@mail.gmail.com
Whole thread Raw
In response to Re: default opclass for jsonb (was Re: Call for GIST/GIN/SP-GIST opclass documentation)  (Bruce Momjian <bruce@momjian.us>)
Responses Re: default opclass for jsonb (was Re: Call for GIST/GIN/SP-GIST opclass documentation)
List pgsql-hackers
On Fri, May 9, 2014 at 2:53 PM, Bruce Momjian <bruce@momjian.us> wrote:
> Well, if we are optionally hashing json_ops for long strings, what does
> jsonb_hash_ops do uniquely with hashing?  Does it always hash, while
> json_ops optionally hashes?  Is that the distinguishing characteristic?
> It seemed the _content_ of the indexed value was more important, rather
> than the storage method.
>
> Should jsonb_hash_ops do only optional hashing too for long strings?


Well the question seems to me to be that if we're always doing recheck
then what advantage is there to not hashing everything?

-- 
greg



pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: default opclass for jsonb (was Re: Call for GIST/GIN/SP-GIST opclass documentation)
Next
From: Andrew Dunstan
Date:
Subject: Re: Cache lookup error when using jsonb, json_build_object and a WITH clause