Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1WjEON-0003cC-P7 for pgsql-hackers@arkaria.postgresql.org; Sat, 10 May 2014 21:01:12 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1WjEON-0002R9-2t for pgsql-hackers@arkaria.postgresql.org; Sat, 10 May 2014 21:01:11 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1WjEOK-0002Qy-Ms for pgsql-hackers@postgresql.org; Sat, 10 May 2014 21:01:08 +0000 Received: from relay3-d.mail.gandi.net ([2001:4b98:c:538::195]) by magus.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1WjEOG-0006b8-Le for pgsql-hackers@postgresql.org; Sat, 10 May 2014 21:01:07 +0000 Received: from mfilter29-d.gandi.net (mfilter29-d.gandi.net [217.70.178.160]) by relay3-d.mail.gandi.net (Postfix) with ESMTP id 0A222A80B1; Sat, 10 May 2014 23:01:01 +0200 (CEST) X-Virus-Scanned: Debian amavisd-new at mfilter29-d.gandi.net Received: from relay3-d.mail.gandi.net ([217.70.183.195]) by mfilter29-d.gandi.net (mfilter29-d.gandi.net [10.0.15.180]) (amavisd-new, port 10024) with ESMTP id uR2qAbLkm3wJ; Sat, 10 May 2014 23:00:59 +0200 (CEST) X-Originating-IP: 98.27.58.255 Received: from [192.168.10.146] (cpe-098-027-058-255.nc.res.rr.com [98.27.58.255]) (Authenticated sender: adsend@dunslane.net) by relay3-d.mail.gandi.net (Postfix) with ESMTPSA id E0C5AA80B8; Sat, 10 May 2014 23:00:55 +0200 (CEST) Message-ID: <536E9386.6050701@dunslane.net> Date: Sat, 10 May 2014 17:00:54 -0400 From: Andrew Dunstan User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130110 Thunderbird/17.0.2 MIME-Version: 1.0 To: Heikki Linnakangas CC: Tom Lane , Greg Stark , Bruce Momjian , Gavin Flower , "David E. Wheeler" , Robert Haas , Peter Geoghegan , "pgsql-hackers@postgresql.org" Subject: Re: default opclass for jsonb (was Re: Call for GIST/GIN/SP-GIST opclass documentation) 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> <28961.1399668272@sss.pgh.pa.us> <536E8F3A.40706@vmware.com> In-Reply-To: <536E8F3A.40706@vmware.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Pg-Spam-Score: -1.9 (-) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-hackers Precedence: bulk Sender: pgsql-hackers-owner@postgresql.org 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