Re: [Cloud] Question about NOT EXISTS

Hi, I have not checked the actual queries, but EXPLAIN in old versions of MySQL did not give sometimes accurate results (specially related to subqueries). This is an old but illustrative example of it: https://www.percona.com/blog/2011/10/13/when-explain-estimates-can-go-wrong/ Sometimes running ANALYZE on the tables involved can recalculate statistics and provide better results (I can do that if I get pinged about it, like here: https://phabricator.wikimedia.org/T224656 ). Sometimes there is an optimizer bug and we need to upgrade to overcome it. Sometimes we are personally dissatisfied with the lack of response on our optimizer bug reports on MariaDB tracker. In this aspect I personally think MariaDB used to be ahead, but since 5.6 and beyond, MySQL has generally done a better job in some cases. Rewriting queries is sometimes the only solution. To test performance of query plans post-execution, Handler statistics can be used on a fresh session: https://www.slideshare.net/jynus/query-optimization-with-mysql-80-and-maria… Regarding your last question- *links tables and other similar data (certain counters) are non-canonical data, which are generally calculated at some point after edits. There can be some delay on it to be updated, and in some exceptional cases (e.g. temporary sw or hw error), they can be out of sync from the actual edit due to postprocessing errors. They cannot be in sync because if one does an edit and then it has to count millions of members of a category/wikilnks, an edit would take minutes to be processed. A null edit or sometimes some production maintenance can lead to getting the revision data and the other metadata in sync. On Wed, Jun 26, 2019 at 3:42 AM Huji Lee &lt;huji.huji(a)gmail.com&gt; wrote: -- Jaime Crespo <http://wikimedia.org>