Bug #10161 | Error 136 (Index file is full) when index file does not actually appear as full | ||
---|---|---|---|
Submitted: | 25 Apr 2005 21:12 | Modified: | 9 Sep 2005 14:42 |
Reporter: | Scott Nebor | Email Updates: | |
Status: | Can't repeat | Impact on me: | |
Category: | MySQL Server | Severity: | S1 (Critical) |
Version: | 4.1.11 | OS: | Linux (Red Hat 9) |
Assigned to: | CPU Architecture: | Any |
[25 Apr 2005 21:12]
Scott Nebor
[25 Apr 2005 21:40]
Scott Nebor
Correction, my first workaround (Changing the big int columns to ints ) does not seem to fix the problem. It only delays the problem until we get reach a couple million rows
[18 Jun 2005 17:17]
David Sparks
I ran into the same bug with a very small table: -rw-rw---- 1 mysql mysql 19M Jun 18 10:16 employee_domains.MYD -rw-rw---- 1 mysql mysql 41M Jun 18 10:16 employee_domains.MYI -rw-rw---- 1 mysql mysql 8.5K Jun 18 10:14 employee_domains.frm
[9 Sep 2005 14:42]
MySQL Verification Team
I was not unable to repeat the behavior reported with current source server. I inserted 2 millions records with the query you reported: Record No. 1999998 Record No. 1999999 Record No. 2000000 miguel@hegel:~/dbs/4.1> mysql> select count(*) from TransactionDetail; +----------+ | count(*) | +----------+ | 2000000 | +----------+ 1 row in set (0.00 sec) mysql> select version(); +------------------+ | version() | +------------------+ | 4.1.15-debug-log | +------------------+ 1 row in set (0.03 sec) mysql>