MySQL's MyISAM storage engine fixes and modifies maximum file size

Two days ago there was a minor glitch in the production library about MySQL's storage engine problem.

This failure is related to the MySQL 4.1.20 version of the MyISAM storage engine, a more than 10 million table.

Failure phenomenon:

When you do a simple select query, there is no problem, but when you do a connection query or other complex queries, you will be wrong: The specific error code is forgotten due to the time problem. The errors recorded in the system log are as follows:

You can guess from the error message that there is a problem with the storage engine.

It's not surprising to go into the appropriate database directory and look at the size of the data file, which is 4G in size.

MySQL 4 version of the database created table default maximum file size is 4G which means that the table is full and cannot insert data. In fact, version 4 is to support more than 4G data file size, you need to create the table when the phrase added: max_rows=1000000000 avg_row_length=15000.

Perform MYISAMCHK-DVV table name display attribute information:

Then change the maximum file size of the table

ALTER TABLE table_name max_rows=1000000000 avg_row_length=15000;

The time to perform this modification is longer, about a few hours.