Re: BUG #17467: Perf degradation after switching to latest jdbc drivers

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: benleis1(at)gmail(dot)com
Cc: pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #17467: Perf degradation after switching to latest jdbc drivers
Date: 2022-04-25 13:36:12
Message-ID: 37278.1650893772@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-jdbc

PG Bug reporting form <noreply(at)postgresql(dot)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

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2022-04-25 13:47:25 Re: domain type with create cast not working on pg15, but work on pg14
Previous Message 와따가따 2022-04-25 07:51:43 [issue] wal_buffers_full increases depending on the values of wal_buffers and wal-segsize

Browse pgsql-jdbc by date

  From Date Subject
Next Message Benjamin Leis 2022-04-25 16:58:15 Fwd: BUG #17467: Perf degradation after switching to latest jdbc drivers
Previous Message David G. Johnston 2022-04-22 18:05:48 Re: Why does the prepareThreshold=0 (to cover pgbouncer transaction mode) disables protocol binary transfers ? (w/ PoC patch and measurements)