public inbox for [email protected]  

help / color / mirror / Atom feed

From: Doron Tsur <[email protected]>
To: Greg Sabino Mullane <[email protected]>
Cc: 馬 騰飛 <[email protected]>
Cc: [email protected] <[email protected]>
Subject: Re: The performance issues caused by upgrading PostgreSQL to version 16.3.
Date: Mon, 17 Feb 2025 18:04:57 +0200
Message-ID: <CAPZZA0rj2zU=K6yS=F9apn62P_Wj4ov1gh4KLvBL-E6of5b0bg@mail.gmail.com> (raw)
In-Reply-To: <CAKAnmm+eSi+M6UevXJh6WH=yToNYD+fqVvBb7YsZ7u_=tKRtDA@mail.gmail.com>
References: <BJSPR01MB04988FBD8D4EBA094B62FD91E2FBA@BJSPR01MB0498.CHNPR01.prod.partner.outlook.cn>
	<CAKAnmm+eSi+M6UevXJh6WH=yToNYD+fqVvBb7YsZ7u_=tKRtDA@mail.gmail.com>

post installing, did you run analyze verbose?

-Doron


On Mon, Feb 17, 2025 at 4:23 PM Greg Sabino Mullane <[email protected]>
wrote:

> On Mon, Feb 17, 2025 at 2:55 AM 馬 騰飛 <[email protected]> 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
>
>

-- 
---
Sent with Gmail for Sidekick Browser <https://join.meetsidekick.com/_qi4a5;

view thread (5+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected], [email protected]
  Subject: Re: The performance issues caused by upgrading PostgreSQL to version 16.3.
  In-Reply-To: <CAPZZA0rj2zU=K6yS=F9apn62P_Wj4ov1gh4KLvBL-E6of5b0bg@mail.gmail.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox