From: Tom Lane <tgl@sss.pgh.pa.us>
To: Sajith Prabhakar Shetty <ssajith@blackduck.com>
cc: "pgsql-bugs@lists.postgresql.org" <pgsql-bugs@lists.postgresql.org>
Subject: Re: Postgres: Queries are too slow after upgrading to PG17 from PG15
In-reply-to: 
 <PH7PR19MB6481278D3A55C8BD04B9B9EDB590A@PH7PR19MB6481.namprd19.prod.outlook.com>
References: 
 <PH7PR19MB6481278D3A55C8BD04B9B9EDB590A@PH7PR19MB6481.namprd19.prod.outlook.com>
Comments: In-reply-to Sajith Prabhakar Shetty <ssajith@blackduck.com>
	message dated "Thu, 15 May 2025 05:33:28 -0000"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <11969.1747323991.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Thu, 15 May 2025 11:46:31 -0400
Message-ID: <11970.1747323991@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/11970.1747323991%40sss.pgh.pa.us>
Precedence: bulk

Sajith Prabhakar Shetty <ssajith@blackduck.com> writes:
> Now surprisingly one of the query i took from application which used to =
execute in 2s in PG15, is now taking 1min+ in PG17.

The data you've actually showed us does not back up that complaint.
But I do see a 2x slowdown.

> Explain plan of the two queries almost same, all the joins and paths use=
d are exactly same.

Yeah, that is odd.  The only simple explanation I can think of is that you
are using a debug build of v17.

			regards, tom lane