From: | yudhi s <learnerdatabase99(at)gmail(dot)com> |
---|---|
To: | pgsql-general(at)lists(dot)postgresql(dot)org, hjp-pgsql(at)hjp(dot)at |
Subject: | Re: Query performance issue |
Date: | 2024-10-22 05:31:27 |
Message-ID: | CAEzWdqdDTPxxzQYJfr_RdJTtLx-kNnc__z8f9nB25wVQuKzapg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Thu, Oct 17, 2024 at 3:06 AM Peter J. Holzer <hjp-pgsql(at)hjp(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Rossana Ocampos | 2024-10-22 11:31:12 | CURRENTE_DATE |
Previous Message | David G. Johnston | 2024-10-21 22:34:58 | Re: Basebackup fails without useful error message |