MySQL Bugs: #44686: some hints for mysqlcheck documentation

Bug #44686	some hints for mysqlcheck documentation
Submitted:	6 May 2009 10:16	Modified:	22 May 2009 20:11
Reporter:	Susanne Ebrecht	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Server: Documentation	Severity:	S3 (Non-critical)
Version:		OS:	Any
Assigned to:	Paul DuBois	CPU Architecture:	Any

Description:
When you will read:

http://dev.mysql.com/doc/refman/5.1/en/mysqlcheck.html

There is none hint about locking and also there is none hint that this will need a looong while for big tables.

That mysqlcheck really is checking every piece of your database (every table and so on doesn't matter which storage engine) is not really pointed out.

When you have a huge database and run mysqlcheck i.e. because mysql_upgrade is running it, it could need ages.

It would be nice to make it clearer here that every piece is checked or to give the user an idea that using this means that it will need a while.

Also a statement what is about locking during mysqlcheck would be nice.

How to repeat:
Just read http://dev.mysql.com/doc/refman/5.1/en/mysqlcheck.html

You also could take a tera byte database and run mysqlcheck and look how long it needs :)

Suggested fix:
Overwork the mysqlcheck documentation and make more clear statements here that will let the user assume that it needs a while.
Add locking situation.

Thank you for your bug report. This issue has been addressed in the documentation. The updated documentation will appear on our website shortly, and will be included in the next release of the relevant products.