Message-ID: <548B79E3.5070301@dunslane.net>
Date: Fri, 12 Dec 2014 18:27:31 -0500
From: Andrew Dunstan <andrew@dunslane.net>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
 rv:31.0) Gecko/20100101 Thunderbird/31.2.0
MIME-Version: 1.0
To: Tom Lane <tgl@sss.pgh.pa.us>, Josh Berkus <josh@agliodbs.com>
CC: Tim Dudgeon <tdudgeon.ml@gmail.com>, pgsql-sql@postgresql.org,
 pgsql-performance@postgresql.org
Subject: Re: Re: [SQL] querying with index on jsonb slower than
 standard column. Why?
References: <5484DBDA.6090405@gmail.com> <5484EEA7.1030403@aklaver.com>
 <5484F437.2080402@gmail.com> <16147.1418002090@sss.pgh.pa.us>
 <5485C449.4020204@aklaver.com> <26002.1418053572@sss.pgh.pa.us>
 <5485C8BA.7040704@aklaver.com> <5485D584.8080105@aklaver.com>
 <27877.1418057764@sss.pgh.pa.us> <3936.1418071989@sss.pgh.pa.us>
 <548614C8.90203@aklaver.com> <54861A81.8030509@gmail.com>
 <WM!10a58876093961b15d913f3acfd3ae6e8f5f3f7b48bfbafc745c1350051f176f2eb1f0d024840ed24712614adf91b2b6!@asav-3.01.com>
 <548B5CF4.4030009@agliodbs.com> <8867.1418420650@sss.pgh.pa.us>
In-Reply-To: <8867.1418420650@sss.pgh.pa.us>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Precedence: bulk
Sender: pgsql-performance-owner@postgresql.org


On 12/12/2014 04:44 PM, Tom Lane wrote:
> Josh Berkus <josh@agliodbs.com> writes:
>> Yeah, I believe the core problem is that Postgres currently doesn't have
>> any way to have variadic return times from a function which don't match
>> variadic input types.  Returning a value as an actual numeric from JSONB
>> would require returning a numeric from a function whose input type is
>> text or json.  So a known issue but one which would require a lot of
>> replumbing to fix.
> Well, it'd be easy to fix if we were willing to invent distinct operators
> depending on which type you wanted out (perhaps ->> for text output as
> today, add ->># for numeric output, etc).

That was my immediate reaction. Not sure about the operator name. I'd 
tentatively suggest -># (taking an int or text argument) and #># taking 
a text[] argument, both returning numeric, and erroring out if the value 
is a string, boolean, object or array.


>    Doesn't seem terribly nice
> from a usability standpoint though.
>
> The usability issue could be fixed by teaching the planner to fold a
> construct like (jsonb ->> 'foo')::numeric into (jsonb ->># 'foo').
> But I'm not sure how we do that except in a really ugly and ad-hoc
> fashion.
>
> 			


I would be inclined to add the operator and see how cumbersome people 
find it. I suspect in many cases it might be sufficient.

cheers

andrew


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