From: Tom Lane <tgl@sss.pgh.pa.us>
To: benleis1@gmail.com
cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #17467: Perf degradation after switching to latest jdbc
 drivers
In-reply-to: <17467-84ec51d124f40fa0@postgresql.org>
References: <17467-84ec51d124f40fa0@postgresql.org>
Comments: In-reply-to PG Bug reporting form <noreply@postgresql.org>
	message dated "Thu, 21 Apr 2022 18:15:33 -0000"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <37277.1650893772.1@sss.pgh.pa.us>
Date: Mon, 25 Apr 2022 09:36:12 -0400
Message-ID: <37278.1650893772@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/37278.1650893772%40sss.pgh.pa.us>
Precedence: bulk

PG Bug reporting form <noreply@postgresql.org> writes:
> Due to the CVE-2022-21724  we upgraded our driver from 42.2.22 to 43.3.3. 
> We've now started to a large perf degradation during initial opens to the
> database.

You'd be best off to inquire about that on the pgsql-jdbc mailing list.
This list deals with issues in the core server, which I doubt that is.

FWIW, you might want to double-check that you've not accidentally
changed any connection parameters.  It could be useful to enable
log_connections on the server, so you can see if the connection
attempts look any different in the server log.

			regards, tom lane