On 10/21/24 23:31, yudhi s wrote:
On Thu, Oct 17, 2024 at 3:06 AM Peter J. Holzer <hjp-pg...@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
Here's your postgres query as analyzed and made more readable by the
most excellent explain.depesz.com.
https://explain.depesz.com/s/VyeM#html
Under the hints tab are suggestions to bump your work_mem to avoid
writing sorts out to disk.
Jeff
