These Are Not the Rows You’re Looking For

In April, I wondered why a simple COUNT(1) query took 30 seconds.  Now I know it could be a lot worse:

[bobbojones@test (none)] > SELECT COUNT(1) FROM r2;
+----------+
| COUNT(1) |
+----------+
|        0 |
+----------+
1 row in set (59.76 sec)

It just took nearly a minute to determine that the table is empty.

That’ll do, MySQL.  That’ll do.

One thought on “These Are Not the Rows You’re Looking For

  1. just pixels says:

    WRONG!

    It took nearly a minute for MySQL to tell you the table was empty.

    Perhaps the table is not supposed to empty. Perhaps MySQL was just standing there, not doing anything, not touching the table at all when suddenly all the rows disappeared. And MySQL doesn’t have any idea how that could have happened. Unless maybe it accidentally bumped into the page map, not on purpose.

    And MySQL just needs a minute to figure it out if you’d just stop asking.

Leave a Reply

Your email address will not be published. Required fields are marked *