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 1mJftB-0000QT-Ia for pgsql-performance@arkaria.postgresql.org; Fri, 27 Aug 2021 17:43:37 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1mJft8-0007J4-Ii for pgsql-performance@arkaria.postgresql.org; Fri, 27 Aug 2021 17:43:34 +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 1mJft8-0007Iv-AJ for pgsql-performance@lists.postgresql.org; Fri, 27 Aug 2021 17:43:34 +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 1mJft5-00038L-QI for pgsql-performance@postgresql.org; Fri, 27 Aug 2021 17:43:33 +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 17RHhPnI846171; Fri, 27 Aug 2021 13:43:26 -0400 From: Tom Lane To: "ldh@laurent-hasson.com" cc: Justin Pryzby , Ranier Vilela , "pgsql-performance@postgresql.org" Subject: Re: Big Performance drop of Exceptions in UDFs between V11.2 and 13.4 In-reply-to: References: <2092859.1629558281@sss.pgh.pa.us> <2136207.1629569846@sss.pgh.pa.us> <20210821191950.GW10479@telsasoft.com> <20210821221729.GY10479@telsasoft.com> <20210822154758.GZ10479@telsasoft.com> <30496.1629654632@sss.pgh.pa.us> <35729.1629660223@sss.pgh.pa.us> <38107.1629663085@sss.pgh.pa.us> Comments: In-reply-to "ldh@laurent-hasson.com" message dated "Sun, 22 Aug 2021 21:12:43 -0000" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <846169.1630086205.1@sss.pgh.pa.us> Date: Fri, 27 Aug 2021 13:43:25 -0400 Message-ID: <846170.1630086205@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk "ldh@laurent-hasson.com" writes: > That being said, do you have any suggestion how I could circumvent the > issue altogether? Based on Andrew's report, it seems like you might be able to work around it for the time being by disabling message translations, i.e. SET lc_messages = 'C'; Even if that's not acceptable in your work environment, it would be useful to verify that you see an improvement from it. regards, tom lane