Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1Wcy01-00026X-8A for pgsql-hackers@arkaria.postgresql.org; Wed, 23 Apr 2014 14:18:09 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1Wcy00-0001vH-L1 for pgsql-hackers@arkaria.postgresql.org; Wed, 23 Apr 2014 14:18:08 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1Wcxzy-0001v7-RB for pgsql-hackers@postgresql.org; Wed, 23 Apr 2014 14:18:06 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1Wcxzv-0002el-GD for pgsql-hackers@postgresql.org; Wed, 23 Apr 2014 14:18:05 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id s3NEHmi3022286; Wed, 23 Apr 2014 10:17:48 -0400 From: Tom Lane To: Alvaro Herrera cc: Bruce Momjian , Petr Jelinek , Peter Geoghegan , Greg Stark , Robert Haas , Heikki Linnakangas , Andrew Dunstan , "pgsql-hackers@postgresql.org" Subject: Re: Re: default opclass for jsonb (was Re: Call for GIST/GIN/SP-GIST opclass documentation) In-reply-to: <20140423140251.GL25695@eldon.alvh.no-ip.org> References: <534475B7.6020908@dunslane.net> <5344EAA4.1050605@vmware.com> <30137.1397057056@sss.pgh.pa.us> <20140422223230.GL10046@momjian.us> <535777DA.3000203@2ndquadrant.com> <20140423105630.GQ10046@momjian.us> <21608.1398261050@sss.pgh.pa.us> <20140423140251.GL25695@eldon.alvh.no-ip.org> Comments: In-reply-to Alvaro Herrera message dated "Wed, 23 Apr 2014 11:02:51 -0300" Date: Wed, 23 Apr 2014 10:17:48 -0400 Message-ID: <22285.1398262668@sss.pgh.pa.us> X-Pg-Spam-Score: -2.6 (--) 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 Alvaro Herrera writes: > Tom Lane wrote: >> That seems to be the consensus, but now we need a name for the >> soon-to-be-not-default opclass. What's a good short adjective for it? > "comprehensive"? Not particularly short ... > According to Merriam Webster: > Synonyms > all-embracing, all-in [chiefly British], all-inclusive, > broad-gauge (or broad-gauged), compendious, complete, > encyclopedic, cover-all, cyclopedic, embracive, exhaustive, > full, global, inclusive, in-depth, omnibus, panoramic, thorough, > universal > Related Words > broad, catholic, encyclical, general, inclusionary, overall; > cosmic (also cosmical), extensive, far, far-reaching, grand, > large, panoptic, sweeping, vast, wide, wide-ranging; blanket, > indiscriminate, unrestricted > jsonb_omnibus_ops ? hm ... jsonb_full_ops seems nicely short, but on the other hand it just begs the question "full what?". I'm a bit worried about future-proof-ness too; what if somebody later comes up with a new opclass that indexes more operators? We'd end up calling it jsonb_fuller_ops, ick. I was kind of hoping for a technical adjective, like "hash" is for the soon-to-be-default opclass. What is it about this opclass that distinguishes it from other indexing approaches that someone might try? regards, tom lane -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers