Re: SQL/JSON: JSON_TABLE - Mailing list pgsql-hackers

From Andrew Dunstan
Subject Re: SQL/JSON: JSON_TABLE
Date
Msg-id acbbc4af-fb1c-1842-0938-ecd4bfcb50ae@dunslane.net
Whole thread Raw
In response to Re: SQL/JSON: JSON_TABLE  (Erik Rijkers <er@xs4all.nl>)
Responses Re: SQL/JSON: JSON_TABLE
List pgsql-hackers
On 4/12/21 11:34 AM, Erik Rijkers wrote:
>> On 2021.03.27. 02:12 Nikita Glukhov <n.gluhov@postgrespro.ru> wrote:
>> Attached 47th version of the patches.
> We're past feature freeze for 14 and alas, JSON_TABLE has not made it.
>
> I have tested quite a bit with it and because I didn't find any trouble with functionality or speed, I wanted to at
leastmention that here once.
 
>
> I looked at v47, these files
>> [0001-SQL-JSON-functions-v47.patch]
>> [0002-JSON_TABLE-v47.patch]
>> [0003-JSON_TABLE-PLAN-DEFAULT-clause-v47.patch]
>> [0004-JSON_TABLE-PLAN-clause-v47.patch]
>> [manual_addition_fixed.patch]  # for this see [1], [2]
>    (v47 doesn't apply anymore, as cfbot shows, but instances can still be built on top of 6131ffc43ff from 30 march
2021)
>
> I hope it will fare better next round, version 15.
>


Me too. Here's a set that should remove the bitrot.


cheers


andrew


--
Andrew Dunstan
EDB: https://www.enterprisedb.com


Attachment

pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: SQL/JSON: functions
Next
From: Ahsan Hadi
Date:
Subject: Re: [BUG] Logical replication failure "ERROR: could not map filenode "base/13237/442428" to relation OID" with catalog modifying txns