Re: SQL/JSON features for v15

From: Andres Freund <andres(at)anarazel(dot)de>
To: "Jonathan S(dot) Katz" <jkatz(at)postgresql(dot)org>
Cc: Andrew Dunstan <andrew(at)dunslane(dot)net>, Amit Langote <amitlangote09(at)gmail(dot)com>, Nikita Glukhov <n(dot)gluhov(at)postgrespro(dot)ru>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Robert Haas <robertmhaas(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Michael Paquier <michael(at)paquier(dot)xyz>, John Naylor <john(dot)naylor(at)enterprisedb(dot)com>
Subject: Re: SQL/JSON features for v15
Date: 2022-08-31 15:49:16
Message-ID: 20220831154916.pgspuz3bp4427int@awork3.anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

On 2022-08-31 10:20:24 -0400, Jonathan S. Katz wrote:
> Andres, Robert, Tom: With this recent work, have any of your opinions
> changed on including SQL/JSON in v15?

I don't really know what to do here. It feels blatantly obvious that this code
isn't even remotely close to being releasable. I'm worried about the impact of
the big revert at this stage of the release cycle, and that's not getting
better by delaying further. And I'm getting weary of being asked to make the
obvious call that the authors of this feature as well as the RMT should have
made a while ago.

From my POV the only real discussion is whether we'd want to revert this in 15
and HEAD or just 15. There's imo a decent point to be made to just revert in
15 and aggressively press forward with the changes posted in this thread.

Greetings,

Andres Freund

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Pavel Stehule 2022-08-31 15:50:42 Re: [PATCH] Query Jumbling for CALL and SET utility statements
Previous Message Drouvot, Bertrand 2022-08-31 15:33:44 [PATCH] Query Jumbling for CALL and SET utility statements