Re: remaining sql/json patches - Mailing list pgsql-hackers

From Nikita Malakhov
Subject Re: remaining sql/json patches
Date
Msg-id CAN-LCVMgYejK3RgkZKNUwVY0smZsTCfS+v1QHPdwkAU86Kt4CQ@mail.gmail.com
Whole thread Raw
In response to Re: remaining sql/json patches  (Amit Langote <amitlangote09@gmail.com>)
List pgsql-hackers
Hi!

Amit, ok, I'll start a new thread with this patch after I deal with an issue on
plan execution, I've found it during testing.

On Mon, Nov 11, 2024 at 3:29 AM Amit Langote <amitlangote09@gmail.com> wrote:
Hi Nikita,

On Sat, Nov 9, 2024 at 5:22 PM Nikita Malakhov <hukutoc@gmail.com> wrote:
>
> Hi!
>
> We'd like to help to implement SQL/JSON in v18 and have adapted the JSON_TABLE PLAN clause code
> from patch v45-0001-JSON_TABLE.patch.

Nice, thanks.

I think it might be better to start a new thread for your patch and
please write a description of how it works.

> Could you please review it? There are some places with questionable behavior - please check the JSON_TABLE
> plan execution section in tests, and I'm not sure about the correctness of some tests.

I will try to make some time to review it in the January fest.

--
Thanks, Amit Langote


--
Regards,
Nikita Malakhov
Postgres Professional
The Russian Postgres Company

pgsql-hackers by date:

Previous
From: Ashutosh Bapat
Date:
Subject: Re: logical replication: restart_lsn can go backwards (and more), seems broken since 9.4
Next
From: Nisha Moond
Date:
Subject: Re: DOCS - pg_replication_slot . Fix the 'inactive_since' description