Message-ID: <5b5ba309ccb2a32953f01adc2dcf96260bc9b6c8.camel@cybertec.at>
Subject: Re: Query optimization
From: Laurenz Albe <laurenz.albe@cybertec.at>
To: Durgamahesh Manne <maheshpostgres9@gmail.com>, pgsql-general
	 <pgsql-general@lists.postgresql.org>
Date: Thu, 13 Mar 2025 20:34:01 +0100
In-Reply-To: <CAJCZkoL+DHs0H9enQEg8JXZw=7032zrmFKG8Vx0fup6_wqNpnQ@mail.gmail.com>
References: 
	<CAJCZkoL+DHs0H9enQEg8JXZw=7032zrmFKG8Vx0fup6_wqNpnQ@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
User-Agent: Evolution 3.54.3 (3.54.3-1.fc41) 
MIME-Version: 1.0
Archived-At: <https://www.postgresql.org/message-id/5b5ba309ccb2a32953f01adc2dcf96260bc9b6c8.camel%40cybertec.at>
Precedence: bulk

On Fri, 2025-03-14 at 00:42 +0530, Durgamahesh Manne wrote:
> This query takes more=C2=A0time than usual for execution=C2=A0
>=20
> How to optimize it in best possible way
>=20
> Columns used in this query >> composite index eventhough not running opti=
mally=C2=A0
> SELECT EXISTS (SELECT Key FROM CACHEKEYS WHERE CacheType =3D $1 AND TrsId=
 =3D $2 AND
>                BrandId =3D $3 AND SportId =3D $4 AND CompetitionId =3D $5=
 AND
>                EventId =3D $6 AND MarketId =3D $7 LIMIT ?)

"The best possible way" is hard to say, because an index will have negative
effects on data modification statements.

But for the fastest execution of the query, simply create an index on all t=
he
columns that occur in the WHERE clause.  The order doesn't matter.

And remove that useless LIMIT clause.

Yours,
Laurenz Albe