Re: The performance issues caused by upgrading PostgreSQL to version 16.3.

From: Greg Sabino Mullane <htamfids(at)gmail(dot)com>
To: 馬 騰飛 <ma-tengfei(at)nec(dot)cn>
Cc: "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: Re: The performance issues caused by upgrading PostgreSQL to version 16.3.
Date: 2025-02-17 14:22:50
Message-ID: CAKAnmm+eSi+M6UevXJh6WH=yToNYD+fqVvBb7YsZ7u_=tKRtDA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Mon, Feb 17, 2025 at 2:55 AM 馬 騰飛 <ma-tengfei(at)nec(dot)cn> wrote:

> 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.
>

Another reason could be a poor type casting by your driver/middleware. Can
you share the query that is problematic? (also, since you mentioned a
version upgrade, also make sure you run ANALYZE; post-upgrade.)

Cheers,
Greg

--
Crunchy Data - https://www.crunchydata.com
Enterprise Postgres Software Products & Tech Support

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Rucha Kulkarni 2025-02-17 15:12:15 Doubts regarding pg_freespacemap extension
Previous Message Ron Johnson 2025-02-17 14:17:32 Re: The performance issues caused by upgrading PostgreSQL to version 16.3.