pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Jonathan S. Katz <jkatz@postgresql.org>
To: Andrew Dunstan <andrew@dunslane.net>
To: Tom Lane <tgl@sss.pgh.pa.us>
To: Bruce Momjian <bruce@momjian.us>
Cc: Robert Haas <robertmhaas@gmail.com>
Cc: Amit Langote <amitlangote09@gmail.com>
Cc: Nikita Glukhov <n.gluhov@postgrespro.ru>
Cc: Alvaro Herrera <alvherre@alvh.no-ip.org>
Cc: Andres Freund <andres@anarazel.de>
Cc: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Cc: Michael Paquier <michael@paquier.xyz>
Cc: John Naylor <john.naylor@enterprisedb.com>
Subject: Re: SQL/JSON features for v15
Date: Wed, 31 Aug 2022 16:18:00 -0400
Message-ID: <72ac60fe-f3d8-d155-ff7a-a1b8796b548d@postgresql.org> (raw)
In-Reply-To: <0b193cae-776d-790f-5708-21d9cfe40ff5@dunslane.net>
References: <CA+HiwqH8gTp2uNN3QtgeOSgHhZUZz1=0U+JObJJUmEoch_269Q@mail.gmail.com>
	<20220830092008.6dbublx6la226zis@alvherre.pgsql>
	<CA+HiwqFvP23i3kTHt6TW4FqO6he1YSJXeyGOdFV_YbP=xeS99A@mail.gmail.com>
	<f54ebd2b-0e67-d1c6-4ff7-5d732492d1a0@postgrespro.ru>
	<CA+HiwqHLVPdA7e3Y-S5giKPsqQPf8M0nuvgz8+3D8GjQexXLYA@mail.gmail.com>
	<CA+HiwqECHA0aUi0Bo3tdYTJ27i2MRWUZ5BewQoO0WgRvRXQO-Q@mail.gmail.com>
	<abd31e0b-56aa-044f-6700-8a1c1bba87f1@dunslane.net>
	<2276d20d-43ff-f9f6-5c9c-c2875739e66c@postgresql.org>
	<CA+TgmoaM1LeGZw58cxSHXFJuejp-Sw6W7jzwHjZjq2+J5bQQaA@mail.gmail.com>
	<Yw+nJbDhHRle4Q2e@momjian.us>
	<35146.1661971558@sss.pgh.pa.us>
	<0b193cae-776d-790f-5708-21d9cfe40ff5@dunslane.net>

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


Attachments:

  OpenPGP_signature (application/pgp-signature, 839B) download

view thread (95+ messages)  latest in thread

Message-ID: <72ac60fe-f3d8-d155-ff7a-a1b8796b548d@postgresql.org>
Permalink:  ../72ac60fe-f3d8-d155-ff7a-a1b8796b548d@postgresql.org/
Also on:    postgresql.org/message-id/72ac60fe-f3d8-d155-ff7a-a1b8796b548d@postgresql.org

 · 

reply
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, andrew@dunslane.net, tgl@sss.pgh.pa.us, bruce@momjian.us, robertmhaas@gmail.com, amitlangote09@gmail.com, n.gluhov@postgrespro.ru, alvherre@alvh.no-ip.org, andres@anarazel.de, pgsql-hackers@lists.postgresql.org, michael@paquier.xyz, john.naylor@enterprisedb.com
  Subject: Re: SQL/JSON features for v15
  In-Reply-To: <72ac60fe-f3d8-d155-ff7a-a1b8796b548d@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