| Bug #11494 | Setting myisam_data_pointer_size to 8 causes warnings when checking the table | ||
|---|---|---|---|
| Submitted: | 22 Jun 2005 7:45 | Modified: | 9 Aug 2005 14:03 |
| Reporter: | Gleb Paharenko | Email Updates: | |
| Status: | Duplicate | Impact on me: | |
| Category: | MySQL Server | Severity: | S3 (Non-critical) |
| Version: | 4.1.12 | OS: | Linux (Linux) |
| Assigned to: | Assigned Account | CPU Architecture: | Any |
[22 Jun 2005 7:46]
Gleb Paharenko
First appeared at: http://lists.mysql.com/mysql/185726
[22 Jun 2005 21:08]
David Sparks
When the tables grow bigger than a certain size, data returned from queries that do joins comes back corrupt (ie alpha characters in numeric fields, control/high bit characters in text fields, etc). This problem is actually quite serious.
[9 Aug 2005 14:03]
Ingo Strüwing
This has already been fixed in 4.1.13 with Bug #11226.
Description: Setting myisam_data_pointer_size to 8 causes warnings when checking the table. How to repeat: Put into configuration file myisam_data_pointer_size=8 Restart the server. mysql> use test; Database changed mysql> create table testp(a int); Query OK, 0 rows affected (0.01 sec) mysql> insert into testp values('1'); Query OK, 1 row affected (0.00 sec) mysql> check table testp; +------------+-------+----------+--------------------------------------+ | Table | Op | Msg_type | Msg_text | +------------+-------+----------+--------------------------------------+ | test.testp | check | warning | Datafile is almost full, 9 of 7 used | | test.testp | check | status | OK | +------------+-------+----------+--------------------------------------+ 2 rows in set (0.03 sec) Suggested fix: Remove the warning or document it