When EXPLAIN estimates can go wrong!

This is the title of my first blog post on MySQL Performance Blog. It deals with a customer case where the customer was facing a peculiar problem where the rows column in the EXPLAIN output of the query was totally off. The actual number of rows was 18 times more than the number of rows reported by MySQL in the output of EXPLAIN. Now this can be a real pain as MySQL uses “the number of rows” estimation to pick and choose indexes and it could really be picking up a wrong index simply because of the wrong estimate.

You can read the complete post here.

  • http://www.umbeehosting.co.uk/vps-hosting Virtual Server Hosting

    It could be hard to
    distinguish the worn one with such a poor explanation, the customer should
    bring back more explanatory problem about the case.