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

help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: ldh@laurent-hasson.com <ldh@laurent-hasson.com>
Cc: Justin Pryzby <pryzby@telsasoft.com>
Cc: Ranier Vilela <ranier.vf@gmail.com>
Cc: pgsql-performance@postgresql.org <pgsql-performance@postgresql.org>
Subject: Re: Big Performance drop of Exceptions in UDFs between V11.2 and 13.4
Date: Fri, 27 Aug 2021 13:43:25 -0400
Message-ID: <846170.1630086205@sss.pgh.pa.us> (raw)
In-Reply-To: <MN2PR15MB2560F5ABDE7BE85C11625AFD85C39@MN2PR15MB2560.namprd15.prod.outlook.com>
References: <MN2PR15MB2560AE2A878FBBE88DCFF33385C29@MN2PR15MB2560.namprd15.prod.outlook.com>
	<2092859.1629558281@sss.pgh.pa.us>
	<MN2PR15MB25607BDC72A325CA9B9D3E3385C29@MN2PR15MB2560.namprd15.prod.outlook.com>
	<2136207.1629569846@sss.pgh.pa.us>
	<20210821191950.GW10479@telsasoft.com>
	<MN2PR15MB2560ED2A8F967B14E7D7881E85C29@MN2PR15MB2560.namprd15.prod.outlook.com>
	<20210821221729.GY10479@telsasoft.com>
	<MN2PR15MB2560FB03666CEABB651FB32185C29@MN2PR15MB2560.namprd15.prod.outlook.com>
	<MN2PR15MB256034533A31A7C11E3C347985C39@MN2PR15MB2560.namprd15.prod.outlook.com>
	<CAEudQAocYZieAMgCtXa8Oau8=dVJ1_R1r0coLeF1LfiYkBCTNA@mail.gmail.com>
	<20210822154758.GZ10479@telsasoft.com>
	<30496.1629654632@sss.pgh.pa.us>
	<MN2PR15MB2560C3FF951319B18A3CA83585C39@MN2PR15MB2560.namprd15.prod.outlook.com>
	<MN2PR15MB25601CCA9E337403E1754BDE85C39@MN2PR15MB2560.namprd15.prod.outlook.com>
	<35729.1629660223@sss.pgh.pa.us>
	<MN2PR15MB2560634E97465D56FFB4601D85C39@MN2PR15MB2560.namprd15.prod.outlook.com>
	<MN2PR1! ! 5MB256016A7233E15D049F1FDB885C39@MN2PR15MB2560.namprd15.prod.outlook.com>
	<38107.1629663085@sss.pgh.pa.us>
	<MN2PR15MB2560F5ABDE7BE85C11625AFD85C39@MN2PR15MB2560.namprd15.prod.outlook.com>

"ldh@laurent-hasson.com" <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





view thread (78+ messages)  latest in thread

Message-ID: <846170.1630086205@sss.pgh.pa.us>
Permalink:  ../846170.1630086205@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/846170.1630086205@sss.pgh.pa.us

 · 

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-performance@postgresql.org
  Cc: tgl@sss.pgh.pa.us, ldh@laurent-hasson.com, pryzby@telsasoft.com, ranier.vf@gmail.com
  Subject: Re: Big Performance drop of Exceptions in UDFs between V11.2 and 13.4
  In-Reply-To: <846170.1630086205@sss.pgh.pa.us>

* 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