Re: Query causing CPU Spike to 100% after MYSQL upgrade
I don't see anything in the 5.7.19-5.7.20 change list that would make such a difference.
The query cross joins cct with cfit, ie it will return every logically possible combination of cct and cfit rows. Is that intentional?
Explicit join syntax (a join b on a.x=b.y) is much easier to read, debug, maintain.
Subject
Views
Written By
Posted
1574
December 11, 2017 02:16PM
Re: Query causing CPU Spike to 100% after MYSQL upgrade
614
December 11, 2017 09:21PM
576
December 12, 2017 09:13AM
508
December 12, 2017 02:52PM
536
December 13, 2017 12:29PM
Sorry, you can't reply to this topic. It has been closed.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion
of Oracle or any other party.