MIME-Version: 1.0
References: <BJSPR01MB04988FBD8D4EBA094B62FD91E2FBA@BJSPR01MB0498.CHNPR01.prod.partner.outlook.cn>
In-Reply-To: <BJSPR01MB04988FBD8D4EBA094B62FD91E2FBA@BJSPR01MB0498.CHNPR01.prod.partner.outlook.cn>
From: Greg Sabino Mullane <htamfids@gmail.com>
Date: Mon, 17 Feb 2025 09:22:50 -0500
Message-ID: <CAKAnmm+eSi+M6UevXJh6WH=yToNYD+fqVvBb7YsZ7u_=tKRtDA@mail.gmail.com>
Subject: Re: The performance issues caused by upgrading PostgreSQL to version 16.3.
To: =?UTF-8?B?6aasIOmosOmjmw==?= <ma-tengfei@nec.cn>
Cc: "pgsql-general@lists.postgresql.org" <pgsql-general@lists.postgresql.org>
Content-Type: multipart/alternative; boundary="0000000000008c5827062e5744d5"
Archived-At: <https://www.postgresql.org/message-id/CAKAnmm%2BeSi%2BM6UevXJh6WH%3DyToNYD%2BfqVvBb7YsZ7u_%3DtKRtDA%40mail.gmail.com>
Precedence: bulk

--0000000000008c5827062e5744d5
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Mon, Feb 17, 2025 at 2:55=E2=80=AFAM =E9=A6=AC =E9=A8=B0=E9=A3=9B <ma-te=
ngfei@nec.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

--0000000000008c5827062e5744d5
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr">On Mon, Feb 17, 2025 at 2:55=E2=80=AFAM =
=E9=A6=AC=E3=80=80=E9=A8=B0=E9=A3=9B &lt;<a href=3D"mailto:ma-tengfei@nec.c=
n">ma-tengfei@nec.cn</a>&gt; wrote:</div><div class=3D"gmail_quote gmail_qu=
ote_container"><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0p=
x 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Interestin=
gly, when we isolate the problematic SQL statement and replace its paramete=
rs with actual values, it executes in just a few seconds in pgAdmin. <br>
However, when we run the same SQL query through our application using Npgsq=
l, it takes over ten minutes to complete.<br>
</blockquote><div><br></div><div>Another reason could be a poor type castin=
g by your driver/middleware. Can you share the query that is problematic? (=
also, since you mentioned=C2=A0a version upgrade, also make sure you run AN=
ALYZE; post-upgrade.)</div><div><br></div><div>Cheers,</div><div>Greg</div>=
<div><br></div></div><div dir=3D"ltr" class=3D"gmail_signature"><div dir=3D=
"ltr"><div>--</div><div>Crunchy Data - <a href=3D"https://www.crunchydata.c=
om" target=3D"_blank">https://www.crunchydata.com</a></div><div>Enterprise =
Postgres Software Products &amp; Tech Support</div><div><br></div></div></d=
iv></div>

--0000000000008c5827062e5744d5--