| Bug #2986 | Mis-spelled option on http://www.mysql.com/doc/en/myisamchk_check_options.html | ||
|---|---|---|---|
| Submitted: | 26 Feb 2004 21:34 | Modified: | 27 Feb 2004 13:05 |
| Reporter: | Mike Hillyer | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Server: Documentation | Severity: | S3 (Non-critical) |
| Version: | n/a | OS: | n/a |
| Assigned to: | CPU Architecture: | Any | |
[27 Feb 2004 13:05]
Paul DuBois
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 product(s).
Description: --extend-check, -e Check the table very thoroughly. This is quite slow if the table has many indexes. This option should only be used in extreme cases. Normally, myisamchk or myisamchk --medium-check should be able to determine whether there are any errors in the table. If you are using --extended-check and have plenty of memory, setting the key_buffer_size variable to a large value will help the repair operation run faster. "--extended-check" should read --extend-check How to repeat: See Page