Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1Whns1-0005fC-71 for pgsql-hackers@arkaria.postgresql.org; Tue, 06 May 2014 22:29:53 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1Whns0-0006jc-MQ for pgsql-hackers@arkaria.postgresql.org; Tue, 06 May 2014 22:29:52 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1Whnrz-0006iE-79 for pgsql-hackers@postgresql.org; Tue, 06 May 2014 22:29:51 +0000 Received: from mail-oa0-f43.google.com ([209.85.219.43]) by magus.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1Whnrq-0004Fm-SI for pgsql-hackers@postgresql.org; Tue, 06 May 2014 22:29:50 +0000 Received: by mail-oa0-f43.google.com with SMTP id l6so193516oag.2 for ; Tue, 06 May 2014 15:29:40 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=e2tGbxsHlelUD3IXzcIbmxknI9+hAfBWbmXo0NgmvUk=; b=jf4faDmWePCyC1HJSSxisZBqVFgZxuIxh5/v/ux6lK/LjannXraw9qGXDFDeSViq0o QC4xuzZAHt9t4s2t44P1oqJGDhdtVu91qUZtMY+glSKd/lAOS5MipHlkGFoUa5HZQL9b 9uK122+OkGsA0Qsd5Hq0nQRUP9+IbnoU1omxrTI28zaue7ji7kFE6gbNCniMQwyY8RBq fvOqryj6koTZ2aoz2mz0ZGIx+GJwtvWTmq9V4EsU0rXs5IwyAoVqQOD5d2JQPk98Ym+s fb7LLBHP9Jx/O+TQBlQijEQSLgN1JT2/JcXYGhKS0T7RohhetVnC49kOtUz5hYAn5tSS 8WJg== X-Gm-Message-State: ALoCoQm43tRDy/cHwB378XkVfD2UbNabxQ79a9Y2Gi3/NpAWx12F+Js60wGECd4iKL1ztnUTIVss MIME-Version: 1.0 X-Received: by 10.182.229.34 with SMTP id sn2mr41251131obc.6.1399415380816; Tue, 06 May 2014 15:29:40 -0700 (PDT) Received: by 10.182.176.67 with HTTP; Tue, 6 May 2014 15:29:40 -0700 (PDT) In-Reply-To: <28554.1399414853@sss.pgh.pa.us> References: <534475B7.6020908@dunslane.net> <5344EAA4.1050605@vmware.com> <30137.1397057056@sss.pgh.pa.us> <20140422223230.GL10046@momjian.us> <16527.1398214220@sss.pgh.pa.us> <20140506201048.GI30817@momjian.us> <16769.1399407530@sss.pgh.pa.us> <20140506212020.GK30817@momjian.us> <57E8AA44-F816-45F2-BB61-5A854FFB0A97@justatheory.com> <28554.1399414853@sss.pgh.pa.us> Date: Tue, 6 May 2014 15:29:40 -0700 Message-ID: Subject: Re: default opclass for jsonb (was Re: Call for GIST/GIN/SP-GIST opclass documentation) From: Peter Geoghegan To: Tom Lane Cc: "David E. Wheeler" , Bruce Momjian , Greg Stark , Robert Haas , Heikki Linnakangas , Andrew Dunstan , "pgsql-hackers@postgresql.org" Content-Type: text/plain; charset=UTF-8 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 On Tue, May 6, 2014 at 3:20 PM, Tom Lane wrote: > I wonder whether the most effective use of time at this point > wouldn't be to fix jsonb_ops to do that, rather than arguing about > what to rename it to. If it didn't have the failure-for-long-strings > problem I doubt anybody would be unhappy about making it the default. I would expect the selectivity of keys on their own to be very low with idiomatic usage of jsonb. Typically, every row in a table will have almost the same keys. The current default opclass makes more sense for when that isn't the case. -- Peter Geoghegan -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers