Re: SQL/JSON features for v15

From: "Jonathan S(dot) Katz" <jkatz(at)postgresql(dot)org>
To: Andres Freund <andres(at)anarazel(dot)de>, Nikita Glukhov <n(dot)gluhov(at)postgrespro(dot)ru>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Andrew Dunstan <andrew(at)dunslane(dot)net>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Michael Paquier <michael(at)paquier(dot)xyz>, John Naylor <john(dot)naylor(at)enterprisedb(dot)com>, Amit Langote <amitlangote09(at)gmail(dot)com>
Subject: Re: SQL/JSON features for v15
Date: 2022-08-17 01:45:06
Message-ID: 8d0ffc54-469a-ffab-68a3-8b547e24a08d@postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

On 8/15/22 10:14 PM, Andres Freund wrote:

> I pushed a few cleanups to https://github.com/anarazel/postgres/commits/json
> while I was hacking on this (ignore that it's based on the meson tree, that's
> just faster for me). Some of them might not be applicable anymore, but it
> might still make sense for you to look at.

With RMT hat on, this appears to be making progress. A few questions /
comments for the group:

1. Nikita: Did you have a chance to review Andres's changes as well?

2. There seems to be some, though limited, progress on design docs.
Andres keeps making a point on adding additional comments to the code to
make it easier to follow. Please do not lose sight of this.

3. Robert raised a point about the use of subtransactions and the
increased risk of wraparound on busy systems using the SQL/JSON
features. Do these patches help reduce this risk? I read some clarity on
the use of subtransactions within the patchset, but want to better
understand if the risks pointed out are a concern.

Thanks everyone for your work on this so far!

Jonathan

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2022-08-17 01:47:00 Re: build remaining Flex files standalone
Previous Message Quan Zongliang 2022-08-17 01:43:54 Bug: When user-defined AM is used, the index path cannot be selected correctly