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 1pVGmB-0003Bb-CJ for pgsql-hackers@arkaria.postgresql.org; Thu, 23 Feb 2023 18:57:07 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1pVGmA-0005wb-8T for pgsql-hackers@arkaria.postgresql.org; Thu, 23 Feb 2023 18:57:06 +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 1pVGm9-0005wS-V4 for pgsql-hackers@lists.postgresql.org; Thu, 23 Feb 2023 18:57:05 +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 1pVGm7-0004pL-UP for pgsql-hackers@postgresql.org; Thu, 23 Feb 2023 18:57:05 +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 31NIuumu587322; Thu, 23 Feb 2023 13:56:56 -0500 From: Tom Lane To: Corey Huinker cc: Andres Freund , pgsql-hackers@postgresql.org, Nikita Glukhov , Andrew Dunstan , David Rowley Subject: Re: PG 15 (and to a smaller degree 14) regression due to ExprEvalStep size In-reply-to: References: <20220616233130.rparivafipt6doj3@alap3.anarazel.de> <1014296.1655422634@sss.pgh.pa.us> <295606.1677101684@sss.pgh.pa.us> <20230222224713.m65d55udzlq5mpbz@awork3.anarazel.de> Comments: In-reply-to Corey Huinker message dated "Thu, 23 Feb 2023 13:39:14 -0500" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <587320.1677178616.1@sss.pgh.pa.us> Date: Thu, 23 Feb 2023 13:56:56 -0500 Message-ID: <587321.1677178616@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Corey Huinker writes: > My not-ready-for-16 work on CAST( ... ON DEFAULT ... ) involved making > FuncExpr/IoCoerceExpr/ArrayCoerceExpr have a safe_mode flag, and that > necessitates adding a reserror boolean to ExprEvalStep for subsequent steps > to test if the error happened. Why do you want it in ExprEvalStep ... couldn't it be in ExprState? I can't see why you'd need more than one at a time during evaluation. regards, tom lane