Hello A user of the Debian packages that I maintain reported a problem with the "mysqlcheck --all-databases --fast --quiet" command that is run in the "/etc/init.d/mysql" script just after the server is up and running as reported by "mysqladmin ping".
According to all documentation that I found and the source code, mysqlcheck in opposide to myisamchk does not deal with the tables files itself which could be suspicious (e.g. with skip-locking) but just issue a "CHECK TABLE xyz FAST" command to the server which should be safe regardless who else does whatever to the table. Can somebody acknowledge that? Or give me a pointer what could get wrong with this approach? (BTW: I am right that as long as there are no not properly closed tables, this command should only take a few seconds even with some thousand tables?) thanks, -christian-
pgpB02TTw3dZ1.pgp
Description: PGP signature
