From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
---|---|
To: | "Abraham, Danny" <danny_abraham(at)bmc(dot)com>, psql-performance <pgsql-performance(at)postgresql(dot)org> |
Subject: | Re: Performance down with JDBC 42 |
Date: | 2023-11-04 21:07:19 |
Message-ID: | fbfaf1a0a5a83d35971b7d77c5cbf64d72375dc4.camel@cybertec.at |
Views: | Whole Thread | Raw Message | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
On Sat, 2023-11-04 at 19:08 +0000, Abraham, Danny wrote:
> Asking for help with a JDBC related issue.
> Environment: Linux 7.9 PG 14.9 , very busy PG Server.
>
> A big query - 3 unions and about 10 joins runs :
> - 70ms on psql , DBeaver with JDBC 42 and in our Server using old JDBC 9.2
> - 2500 ms in our Server using new JDBC 42 driver. ( and this is running many times)
>
> Question: Is there a structured way to identify optimization setup ( Planner Method s ) changes?
> Are there any known changes specific to JDBC 42.
What I would do is enable auto_explain and look at the execution plan
when the statement is run by the JDBC driver. Then you can compare the
execution plans and spot the difference.
Yours,
Laurenz Albe
From | Date | Subject | |
---|---|---|---|
Next Message | Abraham, Danny | 2023-11-05 16:20:07 | RE: [EXTERNAL] Re: Performance down with JDBC 42 |
Previous Message | Abraham, Danny | 2023-11-04 19:08:22 | Performance down with JDBC 42 |