Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1owzLU-0003xj-Dc for pgsql-hackers@arkaria.postgresql.org; Mon, 21 Nov 2022 05:27:52 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1owzKU-000097-SZ for pgsql-hackers@arkaria.postgresql.org; Mon, 21 Nov 2022 05:26:50 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1owzKU-00008c-Je for pgsql-hackers@lists.postgresql.org; Mon, 21 Nov 2022 05:26:50 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1owzKS-00010p-G1 for pgsql-hackers@lists.postgresql.org; Mon, 21 Nov 2022 05:26:50 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 2AL5Qjkf3049338; Mon, 21 Nov 2022 00:26:45 -0500 From: Tom Lane To: Corey Huinker cc: Andrew Dunstan , Nikita Glukhov , PostgreSQL Hackers Subject: Re: Error-safe user functions In-reply-to: References: <3bbbb0df-7382-bf87-9737-340ba096e034@postgrespro.ru> <3190059.1665164276@sss.pgh.pa.us> <57b7cc2e-1215-3f43-84e4-6d9f8ad575df@dunslane.net> Comments: In-reply-to Corey Huinker message dated "Mon, 21 Nov 2022 00:17:12 -0500" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <3049336.1669008405.1@sss.pgh.pa.us> Date: Mon, 21 Nov 2022 00:26:45 -0500 Message-ID: <3049337.1669008405@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Corey Huinker writes: > On Tue, Nov 15, 2022 at 11:36 AM Andrew Dunstan wrote: >> Nikita, >> just checking in, are you making progress on this? I think we really >> need to get this reviewed and committed ASAP if we are to have a chance >> to get the SQL/JSON stuff reworked to use it in time for release 16. > I'm making an attempt at this or something very similar to it. I don't yet > have a patch ready. Cool. We can't delay too much longer on this if we want to have a credible feature in v16. Although I want a minimal initial patch, there will still be a ton of incremental work to do after the core capability is reviewed and committed, so there's no time to lose. regards, tom lane