From: Jonathan S. Katz <jkatz@postgresql.org>
To: Michael Paquier <michael@paquier.xyz>
To: Andres Freund <andres@anarazel.de>
Cc: Nikita Glukhov <n.gluhov@postgrespro.ru>
Cc: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Cc: Andrew Dunstan <andrew@dunslane.net>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: John Naylor <john.naylor@enterprisedb.com>
Cc: Amit Langote <amitlangote09@gmail.com>
Cc: Robert Haas <robertmhaas@gmail.com>
Subject: Re: SQL/JSON features for v15
Date: Tue, 23 Aug 2022 10:47:28 -0400
Message-ID: <61ae42f1-817a-1e2d-cd31-f9d715a1dab7@postgresql.org> (raw)
In-Reply-To: <YwRT07h1UPT1Qtfs@paquier.xyz>
References: <abd9b83b-aa66-f230-3d6d-734817f0995d@postgresql.org>
<20220815223853.itrlpqgpqheg6r6a@awork3.anarazel.de>
<225d341b-f310-eed0-ceff-b8ec61669d9f@postgrespro.ru>
<20220816021425.5sa6gx67zmpou3bc@awork3.anarazel.de>
<8d0ffc54-469a-ffab-68a3-8b547e24a08d@postgresql.org>
<7d83684b-7932-9f29-400b-0beedfafcdd4@postgrespro.ru>
<69022273-e7e3-6d1a-10f8-d1b4740e4b97@postgresql.org>
<92cab50c-152b-84fc-fd49-12b936113a3d@postgresql.org>
<20220823025729.wyotbeazn6zysbt7@awork3.anarazel.de>
<YwRT07h1UPT1Qtfs@paquier.xyz>
On 8/23/22 12:13 AM, Michael Paquier wrote:
> On Mon, Aug 22, 2022 at 07:57:29PM -0700, Andres Freund wrote:
>> To me it feels like there's a probably too much work here to cram it at this
>> point. If several other committers shared the load of working on this it'd
>> perhaps be doable, but I've not seen many volunteers.
>
> While 0002 is dead simple, I am worried about the complexity created
> by 0001, 0003 (particularly tightening subtransactions with a
> CASE_EEOP) and 0004 at this late stage of the release process:
> https://www.postgresql.org/message-id/7d83684b-7932-9f29-400b-0beedfafcdd4@postgrespro.ru
>
> This is not a good sign after three betas for a feature as complex as
> this one.
I see Amit is taking a closer look at the patches.
The RMT had its regular meeting today and discussed the state of
progress on this and how it reflects release timing. Our feeling is that
regardless if the patchset is included/reverted, it would necessitate a
Beta 4 (to be discussed with release team). While no Beta 4 date is set,
given where we are this would probably push the release into early
October to allow for adequate testing time.
To say it another way, if we want to ensure we can have a 15.1 in the
November update releases, we need to make a decision soon on how we want
to proceed.
Thanks,
Jonathan
Attachments:
OpenPGP_signature (application/pgp-signature, 839B) download
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: jkatz@postgresql.org, michael@paquier.xyz, andres@anarazel.de, n.gluhov@postgrespro.ru, pgsql-hackers@lists.postgresql.org, andrew@dunslane.net, tgl@sss.pgh.pa.us, john.naylor@enterprisedb.com, amitlangote09@gmail.com, robertmhaas@gmail.com
Subject: Re: SQL/JSON features for v15
In-Reply-To: <61ae42f1-817a-1e2d-cd31-f9d715a1dab7@postgresql.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox