Hi, We have a database with a table whose data file (.MYD) has grown to 42 GB and an associated index (.MYI) file that's grown to 17 GB, at which point MySQL gave us an error 136 (No more room in index file).
The MySQL manual says (in paragraph 4.4.6.9 "How to Repair Tables") that this type of error can be fixed with a "repair table", but in our case that doesn't seem to have helped. The maximum size of the index file, as reported by myisamchk -d -v is still 17 GB with a keyfile pointer size of 3 bytes. Since then we've tried to drop the index and re-create it, but that hasn't helped either. The new index file is slightly smaller than it was before, but it's obviously only a matter of time until we'll run into the same limitation again. Does anyone know what we need to do to force MySQL to start using 4-byte keyfile pointers? Groeten, - Jacco -- +-------------------------+ | IRL: Jacco van Schaik | The time is 14:20 on Monday October 6 2003. | mail: [EMAIL PROTECTED] | Here at Frontier HQ it's 15 degrees with a | URL: www.frontier.nl | strong breeze from the west. +-------------------------+ -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
