| From: | Doron Tsur <qballer(at)gmail(dot)com> |
|---|---|
| To: | Greg Sabino Mullane <htamfids(at)gmail(dot)com> |
| Cc: | 馬 騰飛 <ma-tengfei(at)nec(dot)cn>, "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 16:04:57 |
| Message-ID: | CAPZZA0rj2zU=K6yS=F9apn62P_Wj4ov1gh4KLvBL-E6of5b0bg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
post installing, did you run analyze verbose?
-Doron
On Mon, Feb 17, 2025 at 4:23 PM Greg Sabino Mullane <htamfids(at)gmail(dot)com>
wrote:
> 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
>
>
--
---
Sent with Gmail for Sidekick Browser <https://join.meetsidekick.com/_qi4a5>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adrian Klaver | 2025-02-17 16:10:17 | Re: The performance issues caused by upgrading PostgreSQL to version 16.3. |
| Previous Message | Rucha Kulkarni | 2025-02-17 15:12:15 | Doubts regarding pg_freespacemap extension |