Horton

Re: SQL/JSON features for v15

Jonathan S. Katz <jkatz@postgresql.org>

View thread View on postgr.es
From: "Jonathan S. Katz" <jkatz@postgresql.org>
To: Andrew Dunstan <andrew@dunslane.net>, Tom Lane <tgl@sss.pgh.pa.us>, Bruce Momjian <bruce@momjian.us>
Cc: Robert Haas <robertmhaas@gmail.com>, Amit Langote <amitlangote09@gmail.com>, Nikita Glukhov <n.gluhov@postgrespro.ru>, Alvaro Herrera <alvherre@alvh.no-ip.org>, Andres Freund <andres@anarazel.de>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>, Michael Paquier <michael@paquier.xyz>, John Naylor <john.naylor@enterprisedb.com>
Date: 2022-08-31T20:18:00Z
Lists: pgsql-hackers 
On 8/31/22 3:08 PM, Andrew Dunstan wrote:
> 
> On 2022-08-31 We 14:45, Tom Lane wrote:
>> To the extent that there was a management failure here, it was that
>> we didn't press for a resolution sooner.  Given the scale of the
>> concerns raised in June, I kind of agree with Andres' opinion that
>> fixing them post-freeze was doomed to failure.  It was definitely
>> doomed once we reached August with no real work done towards it.
> 
> 
> I'm not going to comment publicly in general about this, you might
> imagine what my reaction is. The decision is the RMT's to make and I
> have no quarrel with that.
> 
> But I do want it understood that there was work being done right from
> the time in June when Andres' complaints were published. These were
> difficult issues, and we didn't let the grass grow looking for a fix. I
> concede that might not have been visible until later.

June was a bit of a rough month too -- we had the issues that spawned 
the out-of-cycle release at the top of the month, which started almost 
right after Beta 1, and then almost immediately into Beta 2 after 14.4. 
I know that consumed a lot of my cycles. At that point in time for the 
v15 release process I was primarily focused on monitoring open items at 
that point, so I missed the June comments.

Jonathan

Commits

  1. JSON_TABLE: Add support for NESTED paths and columns

  2. Add basic JSON_TABLE() functionality

  3. Add SQL/JSON query functions

  4. Add soft error handling to some expression nodes

  5. Adjust populate_record_field() to handle errors softly

  6. Refactor code used by jsonpath executor to fetch variables

  7. Add more SQL/JSON constructor functions

  8. SQL/JSON: support the IS JSON predicate

  9. SQL/JSON: add standard JSON constructor functions

  10. Revert SQL/JSON features

  11. Numeric error suppression in jsonpath