MIME-Version: 1.0
References: <CAEzWdqfeaLov=e3Dk_wMpzh0yWhGcVJhundmL=QL1X_KqG_Jfw@mail.gmail.com>
 <20241016213610.wbfqj3r7gg5ba6eh@hjp.at>
In-Reply-To: <20241016213610.wbfqj3r7gg5ba6eh@hjp.at>
From: yudhi s <learnerdatabase99@gmail.com>
Date: Tue, 22 Oct 2024 11:01:27 +0530
Message-ID: <CAEzWdqdDTPxxzQYJfr_RdJTtLx-kNnc__z8f9nB25wVQuKzapg@mail.gmail.com>
Subject: Re: Query performance issue
To: pgsql-general@lists.postgresql.org, hjp-pgsql@hjp.at
Content-Type: multipart/alternative; boundary="000000000000734d9606250a15f5"
Archived-At: <https://www.postgresql.org/message-id/CAEzWdqdDTPxxzQYJfr_RdJTtLx-kNnc__z8f9nB25wVQuKzapg%40mail.gmail.com>
Precedence: bulk

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

On Thu, Oct 17, 2024 at 3:06=E2=80=AFAM Peter J. Holzer <hjp-pgsql@hjp.at> =
wrote:

>
> The execution plan looks like a postgresql execution plan, not a mysql
> execution plan. Did you run this query on postgresql? That may be
> interesting for comparison purposese, but ultimately it is useless: You
> won't get mysql to work like postgresql, and any tips to speed up this
> query on postgresql (which is all you can expect on a postgresql mailing
> list) probably won't work on mysql.
>
>
>

Tried running the same in postgres and below is the plan from bothe
postgres and mysql. Can you please guide me to understand ,  if anything
else can be done to make it better?

https://gist.github.com/databasetech0073/746353a9e76d5e29b2fc6abdc80cdef8

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

<div dir=3D"ltr"><div dir=3D"ltr"><br></div><div class=3D"gmail_quote"><div=
 dir=3D"ltr" class=3D"gmail_attr">On Thu, Oct 17, 2024 at 3:06=E2=80=AFAM P=
eter J. Holzer &lt;<a href=3D"mailto:hjp-pgsql@hjp.at">hjp-pgsql@hjp.at</a>=
&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px =
0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><br>
The execution plan looks like a postgresql execution plan, not a mysql<br>
execution plan. Did you run this query on postgresql? That may be<br>
interesting for comparison purposese, but ultimately it is useless: You<br>
won&#39;t get mysql to work like postgresql, and any tips to speed up this<=
br>
query on postgresql (which is all you can expect on a postgresql mailing<br=
>
list) probably won&#39;t work on mysql.<br>
<br>=C2=A0 =C2=A0 =C2=A0<br></blockquote><div><br></div><div>Tried running =
the same in postgres and below is the plan from bothe postgres and mysql. C=
an you please guide me to understand ,=C2=A0 if anything else can be done t=
o make it better?</div><div><br></div><div><a href=3D"https://gist.github.c=
om/databasetech0073/746353a9e76d5e29b2fc6abdc80cdef8">https://gist.github.c=
om/databasetech0073/746353a9e76d5e29b2fc6abdc80cdef8</a><br></div><div><br>=
</div></div></div>

--000000000000734d9606250a15f5--