MIME-Version: 1.0
Reply-To: obartunov@gmail.com
In-Reply-To: <536E9386.6050701@dunslane.net>
References: <16769.1399407530@sss.pgh.pa.us>
 <20140506212020.GK30817@momjian.us>
 <57E8AA44-F816-45F2-BB61-5A854FFB0A97@justatheory.com>
 <28554.1399414853@sss.pgh.pa.us>
 <20140508134701.GO30817@momjian.us> <5819.1399558614@sss.pgh.pa.us>
 <1888.1399588751@sss.pgh.pa.us> <20140509033405.GA23254@momjian.us>
 <536C550F.50108@archidevsys.co.nz> <18360.1399633457@sss.pgh.pa.us>
 <20140509135336.GC23254@momjian.us>
 <CAM-w4HOQ+ynm70Cgr4BwMqMc0jfL_8EZAwG2UD6r=EehjH3OOw@mail.gmail.com>
 <28961.1399668272@sss.pgh.pa.us> <536E8F3A.40706@vmware.com>
 <536E9386.6050701@dunslane.net>
From: Oleg Bartunov <obartunov@gmail.com>
Date: Sun, 11 May 2014 01:03:24 +0400
Message-ID: 
 <CAF4Au4wVcdsGLQOnzib3NoiJPF7seC9ydR4e6XVV_9D0WUgNWA@mail.gmail.com>
Subject: Re: default opclass for jsonb (was Re: Call for
 GIST/GIN/SP-GIST opclass documentation)
To: Andrew Dunstan <andrew@dunslane.net>
Cc: Heikki Linnakangas <hlinnakangas@vmware.com>,
 Tom Lane <tgl@sss.pgh.pa.us>,
 Greg Stark <stark@mit.edu>, Bruce Momjian <bruce@momjian.us>,
 Gavin Flower <GavinFlower@archidevsys.co.nz>,
 "David E. Wheeler" <david@justatheory.com>,
 Robert Haas <robertmhaas@gmail.com>, Peter Geoghegan <pg@heroku.com>,
 "pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>
Content-Type: text/plain; charset=UTF-8
Precedence: bulk
Sender: pgsql-hackers-owner@postgresql.org

+1
but  bit confused with json instead of jsonb

On Sun, May 11, 2014 at 1:00 AM, Andrew Dunstan <andrew@dunslane.net> wrote:
>
> On 05/10/2014 04:42 PM, Heikki Linnakangas wrote:
>>
>>
>>
>> The main difference between the two opclasses from a user's standpoint is
>> not whether they hash or not. The big difference is that one indexes
>> complete paths from the root, and the other indexes just the "leaf" level.
>> For example, if you have an object like '{"foo": {"bar": 123 } }', one will
>> index "foo", "foo->bar", and "foo->bar->123" while the other will index
>> "foo", "bar" and "123".
>>
>> Whether the opclasses use hashing to shorten the key is an orthogonal
>> property, and IMHO not as important. To reflect that, I suggest that we name
>> the opclasses:
>>
>> json_path_ops
>> json_value_ops
>>
>> or something along those lines.
>>
>>
>
>
> That looks like the first suggestion I've actually liked and that users will
> be able to understand.
>
> cheers
>
> andrew
>
>
>
>
> --
> Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-hackers


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