The performance issues caused by upgrading PostgreSQL to version 16.3.

From: 馬 騰飛 <ma-tengfei(at)nec(dot)cn>
To: "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: The performance issues caused by upgrading PostgreSQL to version 16.3.
Date: 2025-02-17 07:55:01
Message-ID: BJSPR01MB04988FBD8D4EBA094B62FD91E2FBA@BJSPR01MB0498.CHNPR01.prod.partner.outlook.cn
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Dear PostgreSQL Community,

I hope this message finds you well. I am reaching out to seek your technical assistance regarding a performance issue we encountered after upgrading our PostgreSQL version from 12.19 to 16.3.
We have noticed a significant performance problem with a specific SQL query on one of our application screens.
Interestingly, when we isolate the problematic SQL statement and replace its parameters with actual values, it executes in just a few seconds in pgAdmin.
However, when we run the same SQL query through our application using Npgsql, it takes over ten minutes to complete.
We are using NpgsqlCommand.ExecuteReader to execute the SQL query, and the parameters are set using NpgsqlCommand.Parameters.Add.
The main table involved in this query contains approximately 800,000 records.
We believe that the SQL statement itself does not have performance issues, but there may be problems related to how the SQL is executed in the application or how the parameters are set.
However, we are unable to pinpoint the exact cause of the performance degradation.
Could you please provide us with some possible reasons or suggestions for improvement? Your insights would be greatly appreciated.
Thank you for your assistance, and I look forward to your response.

Best regards,
Ma

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Laurenz Albe 2025-02-17 09:15:10 Re: The performance issues caused by upgrading PostgreSQL to version 16.3.
Previous Message Tom Lane 2025-02-17 07:01:41 Re: Wasteful nested loop join when there is `limit` in the query