Bug #34554 Merge tables cannot exceed 4GB boundary

• Submitted: 14 Feb 2008 16:27
• Modified: 16 Feb 2008 15:57
• Reporter: Scott Noyes
• Status: Can't repeat
• Category: MySQL Server: Merge storage engine
• Severity: S2 (Serious)
• Version: 5.0.48
• OS: Windows (2003 R2)
• CPU Architecture: Any
• Tags: 1168, ER_WRONG_MRG_TABLE

[14 Feb 2008 16:27] Scott Noyes

Description:
When a MERGE table is created over several underlying MyISAM tables which individually do not exceed the 4G rows boundary but combined do, the MERGE table reports erroneous statistics or failes with error 1168.

How to repeat:
See description

Suggested fix:
Verify that 5.0.48-enterprise was built with --with-big-tables, and verify that Merge tables may exceed the 4G row boundary.

Seems to be similar to bug 26881, though this version should contain that fix.

[14 Feb 2008 21:30] Sveta Smirnova

Bug is not repeatable on 64-bit Windows

[14 Feb 2008 21:39] Sveta Smirnova

Sorry: misprint

s/Windows/Linux/

[14 Feb 2008 23:58] Sveta Smirnova

Bug is not repeatable with version 5.0.51a also on Windows Vista 32-bit

[16 Feb 2008 15:57] Sveta Smirnova

Thank you for the report.

I can not repeat described behavior with version 5.0.54.

[22 Feb 2008 13:38] MySQL Verification Team

i repeated on 5.0.48. will try now on 5.0.56 and show results later.

[22 Feb 2008 14:39] MySQL Verification Team

I suspect this is related to bug #30638 ?

[22 Feb 2008 17:59] MySQL Verification Team

i also can't repeat it anymore on 5.0.56: (end of testcase)

mysql> load data infile 'data.txt' into table t39;
Query OK, 107374183 rows affected (4 min 17.02 sec)
Records: 107374183  Deleted: 0  Skipped: 0  Warnings: 0

mysql> select count(*) from m1;
+------------+
| count(*)   |
+------------+
| 4294967320 |
+------------+
1 row in set (0.00 sec)

mysql> select version();
+--------------------------+
| version()                |
+--------------------------+
| 5.0.56-enterprise-gpl-nt |
+--------------------------+
1 row in set (0.03 sec)