Re: SQL/JSON: functions

From: Nikita Glukhov <n(dot)gluhov(at)postgrespro(dot)ru>
To: Dmitry Dolgov <9erthalion6(at)gmail(dot)com>
Cc: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, Oleg Bartunov <obartunov(at)postgrespro(dot)ru>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Alexander Korotkov <a(dot)korotkov(at)postgrespro(dot)ru>, Andres Freund <andres(at)anarazel(dot)de>, Michael Paquier <michael(at)paquier(dot)xyz>, Simon Riggs <simon(at)2ndquadrant(dot)com>, Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com>
Subject: Re: SQL/JSON: functions
Date: 2018-12-04 23:01:19
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

On 01.12.2018 15:36, Dmitry Dolgov wrote:
>> On Mon, Nov 26, 2018 at 5:11 PM Nikita Glukhov <n(dot)gluhov(at)postgrespro(dot)ru> wrote:
>> On 26.11.2018 15:57, Dmitry Dolgov wrote:
>>>> On Tue, Jul 3, 2018 at 2:57 PM Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> wrote:
>>>> 2018-07-03 14:30 GMT+02:00 Nikita Glukhov <n(dot)gluhov(at)postgrespro(dot)ru>:
>>>>> Attached 16th version of the patches:
>>>>> * changed type of new SQL keyword STRING
>>>>> (STRING is used as a function parameter name in Pl/Tcl tests)
>>>>> * removed implicit coercion via I/O from JSON_VALUE (see below)
>>> Unfortunately, the current version of patch 0010-add-invisible-coercion-form
>>> doesn't not apply anymore without conflicts, could you please rebase it?
>> Attached 20th version of the patches rebased onto the current master.
> Thank you,
> Unfortunately, looks like we're in the loop "Rebase. Wait. Repeat", since the
> patch again has some conflicts (this time I hope just minor conflicts). Which
> is probably understandable taking into account the size of it. Maybe we need to
> think about how to proceed with this, do you have any ideas?

Attached 21st version of the patches.

I decided to include here patch 0000 with complete jsonpath implementation (it
is a squash of all 6 jsonpath-v21 patches). I hope this will simplify reviewing
and testing in

If it will conflict again, then you can see all SQL/JSON v21 patches
successfully applied in our GitHub repository on the following branches: (one commit per patch) (original commit history)

Nikita Glukhov
Postgres Professional:
The Russian Postgres Company

Attachment Content-Type Size
0000-Jsonpath-v21.patch text/x-patch 485.6 KB
0007-Add-invisible-coercion-form-v21.patch text/x-patch 7.2 KB
0008-Add-function-formats-v21.patch text/x-patch 10.8 KB
0009-SQL-JSON-functions-v21.patch text/x-patch 300.9 KB
0010-SQL-JSON-functions-for-json-type-v21.patch text/x-patch 56.9 KB
0011-Optimize-SQL-JSON-subtransactions-v21.patch text/x-patch 8.4 KB

In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message Nikita Glukhov 2018-12-04 23:10:04 Re: SQL/JSON: JSON_TABLE
Previous Message Alvaro Herrera 2018-12-04 21:55:47 Re: Query with high planning time at version 11.1 compared versions 10.5 and 11.0