Bug #5769 Error 136 when doing CREATE TABLE...SELECT
Submitted: 27 Sep 2004 17:30 Modified: 27 Oct 2004 22:57
Reporter: Thomas Johnson Email Updates:
Status: Verified Impact on me:
None 
Category:MySQL Server: DDL Severity:S4 (Feature request)
Version:4.0.20 OS:Linux (Gentoo Linux)
Assigned to: CPU Architecture:Any

[27 Sep 2004 17:30] Thomas Johnson 
Description:
I have a table with about 1.7 billion rows. It is approximatly 80G in size (for both data and indicies combined). I attempted to issue the command:
CREATE TABLE newTable AS SELECT DISTINCT * FROM bigTable;
After a few hours, this resulted in error 136

How to repeat:
Create a table with a huge number of rows. Try to do a CREATE TABLE newTable AS SELECT * FROM hugeTable

Suggested fix:
CREATE TABLE...SELECT should automatically figure out the value of MAX_ROWS for the newly created table.
[25 Oct 2004 21:42] MySQL Verification Team 
The error means:

miguel@hegel:~/dbs/4.0$ bin/perror 136
MySQL error:  136 = No more room in index file

Please read in the Manual about:

ALTER TABLE to increase the MAX_ROWS and AVG_ROW_LENGTH
[25 Oct 2004 22:37] Sergei Golubchik 
You are right.
It could do it. It's a quite sound feature request. (though not a bug, of course)