Subject: Re: Optimization of some jsonb functions
To: Andrew Dunstan <andrew.dunstan@2ndquadrant.com>,
 Nikita Glukhov <n.gluhov@postgrespro.ru>,
 PostgreSQL mailing lists <pgsql-hackers@postgresql.org>
References: <7c417f90-f95f-247e-ba63-d95e39c0ad14@postgrespro.ru>
 <5e8027a6-e175-55f8-96c8-0e24dd30e97f@pgmasters.net>
 <6467863b-4220-ebd1-536c-a39e7193dbac@2ndQuadrant.com>
From: David Steele <david@pgmasters.net>
Message-ID: <700fcc48-7e30-aa80-83de-99d6015dfc81@pgmasters.net>
Date: Thu, 7 Mar 2019 14:23:53 +0200
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:60.0)
 Gecko/20100101 Thunderbird/60.5.0
MIME-Version: 1.0
In-Reply-To: <6467863b-4220-ebd1-536c-a39e7193dbac@2ndQuadrant.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Precedence: bulk

Hi Andrew,

On 3/6/19 9:50 PM, Andrew Dunstan wrote:
> 
> On 3/5/19 5:24 AM, David Steele wrote:
>> On 2/22/19 2:05 AM, Nikita Glukhov wrote:
>>> Attached set of patches with some jsonb optimizations that were made
>>> during
>>> comparison of performance of ordinal jsonb operators and jsonpath
>>> operators.
>>
>> This patch was submitted just before the last commitfest for PG12 and
>> seems to have potential for breakage.
>>
>> I have updated the target to PG13.
>>
>>
> 
> I think that's overly cautious. The first one I looked at, to optimize
> JsonbExtractScalar, is very small, self-contained, and I think low risk.
> I haven't looked at the others in detail, but I think at least some part
> of this is reasonably committable.
> 
> 
> I'll try to look at the others fairly shortly.

If you decide all or part of this can be committed then feel free to 
update the target version.

Regards,
-- 
-David
david@pgmasters.net