Re: remaining sql/json patches

From: Amit Langote <amitlangote09(at)gmail(dot)com>
To: Nikita Malakhov <hukutoc(at)gmail(dot)com>
Cc: Andrew Dunstan <andrew(at)dunslane(dot)net>, jian he <jian(dot)universality(at)gmail(dot)com>, Erik Rijkers <er(at)xs4all(dot)nl>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: remaining sql/json patches
Date: 2024-11-11 00:28:43
Message-ID: CA+HiwqExUo=EoP74JCm7Ge7y1A82SO+rE4A4amqgWXSL4Qdjig@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi Nikita,

On Sat, Nov 9, 2024 at 5:22 PM Nikita Malakhov <hukutoc(at)gmail(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Richard Guo 2024-11-11 00:51:51 Re: Eager aggregation, take 3
Previous Message Michael Paquier 2024-11-11 00:21:31 Re: pg_stat_statements: Avoid holding excessive lock