Bug #2948 | Unpacked table has decreased max data length | ||
---|---|---|---|
Submitted: | 24 Feb 2004 20:34 | Modified: | 25 Feb 2004 2:42 |
Reporter: | Jeffrey Jones | Email Updates: | |
Status: | Not a Bug | Impact on me: | |
Category: | MySQL Server | Severity: | S3 (Non-critical) |
Version: | Ver 12.22 Distrib 4.0.16 | OS: | Linux (redhat linux) |
Assigned to: | Sergei Golubchik | CPU Architecture: | Any |
[24 Feb 2004 20:34]
Jeffrey Jones
[25 Feb 2004 2:42]
Sergei Golubchik
most probably yes. As myisampack tries to make a table as small as possible, it also tries to make an offset to a row as small as possible (as it is used in the table file for various purposes). Thus if you have max_data_length=4294967295 (that is 4-byte offset) but actual datafile length is smaller, myisampack may conclude that, e.g. 3 bytes for an offset is enough, and reduce max_data_length to save a byte on each offset.