From: Tom Lane <tgl@sss.pgh.pa.us>
To: "Jonathan S. Katz" <jkatz@postgresql.org>
cc: Andrew Dunstan <andrew@dunslane.net>, Andres Freund <andres@anarazel.de>,
        Amit Langote <amitlangote09@gmail.com>,
        David Rowley <dgrowleyml@gmail.com>,
        Alvaro Herrera <alvherre@alvh.no-ip.org>,
        Michael Paquier <michael@paquier.xyz>,
        John Naylor <john.naylor@enterprisedb.com>,
        Peter Geoghegan <pg@bowt.ie>,
        PostgreSQL-development <pgsql-hackers@postgresql.org>,
        Nikita Glukhov <n.gluhov@postgrespro.ru>
Subject: Re: PG 15 (and to a smaller degree 14) regression due to ExprEvalStep
 size
In-reply-to: <4b02e8a0-2541-a739-d1e7-6cdd29239b24@postgresql.org>
References: 
 <CA+HiwqHS3LSmWpjdCfq2cdB2W--=0ETHmQPF8bXCY2Mn=bXBog@mail.gmail.com>
 <20220721171235.7okm3q5i7jyuwtqw@alvherre.pgsql>
 <CA+HiwqENocTzGwbzdLrc7CwTW4qivkFRhSvWKi7Ph77s=85aTg@mail.gmail.com>
 <CAApHDvr_DPoAfe2jAyP5rd=h+Z0-WZxeEB025=Fvw7JRbeWDOA@mail.gmail.com>
 <CA+HiwqFyNvVYSegZw5pWTSAi1EtZLBtAexP2APqgOOcGLn_31g@mail.gmail.com>
 <CA+HiwqEp=vF=0=tUPYz2N3OOp+19CgCrNBgLUUK7SWec_YZ5UQ@mail.gmail.com>
 <20220802003947.x2ezq7u7pkmxt6ie@awork3.anarazel.de>
 <CA+HiwqHU+wWGNjzk=5eV15Nth3jySbQeeUFnVfbZ1F3M6QUjDA@mail.gmail.com>
 <20220802150022.jqomxwum5eazybfv@awork3.anarazel.de>
 <CA+HiwqEe3n-v86zy4gL2g+BWZDxwEtVeGX8YuOqRh8y7R8QPPw@mail.gmail.com>
 <20220805203656.mdgmajvsahi5srcy@awork3.anarazel.de>
 <787cef45-15de-8f1d-ed58-a1c1435bfc0e@postgresql.org>
 <32d4a1e4-d218-b129-205e-e123ebaef6b8@dunslane.net>
 <4b02e8a0-2541-a739-d1e7-6cdd29239b24@postgresql.org>
Comments: In-reply-to "Jonathan S. Katz" <jkatz@postgresql.org>
	message dated "Tue, 09 Aug 2022 14:04:48 -0400"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <35777.1660072664.1@sss.pgh.pa.us>
Date: Tue, 09 Aug 2022 15:17:44 -0400
Message-ID: <35778.1660072664@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/35778.1660072664%40sss.pgh.pa.us>
Precedence: bulk

"Jonathan S. Katz" <jkatz@postgresql.org> writes:
> Speaking personally, I would like to see what we could do to include 
> support for this batch of the SQL/JSON features in v15. What is included 
> looks like it closes most of the gap on what we've been missing 
> syntactically since the standard was adopted, and the JSON_TABLE work is 
> very convenient for converting JSON data into a relational format. I 
> believe having this feature set is important for maintaining standards 
> compliance, interoperability, tooling support, and general usability. 
> Plus, JSON still seems to be pretty popular :)
> ...
> I hope that these can be addressed satisfactorily in a reasonable (read: 
> now a much shorter) timeframe so we can include the SQL/JSON work in v15.

We have delayed releases for $COOL_FEATURE in the past, and I think
our batting average on that is still .000: not once has it worked out
well.  I think we're better off getting the pain over with quickly,
so I regretfully vote for revert.  And for a full redesign/rewrite
before we try again; based on Andres' comments, it needs that.

			regards, tom lane