Bug #43871 SHOW TABLE STATUS constantly wildly fluctuating
Submitted: 26 Mar 2009 0:31 Modified: 27 Mar 2009 7:14
Reporter: Dan Jacobson Email Updates:
Status: Not a Bug Impact on me:
None 
Category:MySQL Server Severity:S3 (Non-critical)
Version:mysql-5.1.32-1 ((Debian)) OS:Any
Assigned to: CPU Architecture:Any

[26 Mar 2009 0:31] Dan Jacobson
Description:
$ watch -d mysqlshow --status myDB
Shows the count of rows is
constantly fluctuating for some tables, even though the database is
offline. There ought to be a note about it here and on HELP SHOW TABLE STATUS;
Must use
       o  --count
          Show the number of rows per table.
(Which also should mention that it also shows number of columns.)

How to repeat:
$ watch -d mysqlshow --status myDB
[26 Mar 2009 6:01] Sveta Smirnova
Thank you for the report.

> Shows the count of rows is constantly fluctuating for some tables

Does it happen for InnoDB tables?
[26 Mar 2009 21:34] Dan Jacobson
A cpio archive of "watch -d ...|tee file" for three different databases

Attachment: playback.gz (application/gzip, text), 1.59 KiB.

[26 Mar 2009 21:37] Dan Jacobson
Yes.
For some databases that is.

I've attached a gziped cpio archive of three different databases where I
did watch -d mysqlshow --status DB|tee FILE

You can probably just "cat" each file in xterm, or even a VT100 ansi terminal...
they are about three seconds long.
Anyway, the white part is what is changing.

However on the smaller DB, everything stays still.

The DBs are totally offline.
[27 Mar 2009 7:14] Sveta Smirnova
Thank you for the feedback.

In case of InnoDB this is not a bug. See http://dev.mysql.com/doc/refman/5.1/en/innodb-restrictions.html for details:

SHOW TABLE STATUS does not give accurate statistics on InnoDB tables, except for the physical size reserved by the table. The row count is only a rough estimate used in SQL optimization.