Bug #17390 Partitions: sporadic crash, SELECT on partitioned NDB table
Submitted: 14 Feb 2006 17:34 Modified: 28 Feb 2006 19:34
Reporter: Matthias Leich Email Updates:
Status: Closed Impact on me:
Category:MySQL Server: Partitions Severity:S1 (Critical)
Version:5.1 OS:
Assigned to: Mikael Ronström CPU Architecture:Any

[14 Feb 2006 17:34] Matthias Leich
--source include/have_ndb.inc
SET SESSION storage_engine='NDB'; 
 f_int1 INTEGER, f_int2 INTEGER,
 f_char1 CHAR(10), f_char2 CHAR(10), f_charbig VARCHAR(1000)  )
# It looks like this record is needed.
INSERT INTO t1 SET f_int1 = 4, f_int2 = 4, 
f_char1 = '4', f_char2 = '4', f_charbig = '===4===';
# It looks like INSERT + DELETE of this record is needed.
INSERT INTO t1 SET f_int1 = 3, f_int2 = 3, 
f_char1 = '3', f_char2 = '3', f_charbig = 'delete me';
DELETE FROM t1 WHERE f_charbig = 'delete me';

let $num2 = 300;
while ($num2)
   eval SELECT COUNT(*) FROM t1 WHERE f_int1 = 1;
   dec $num2;
The crash appears normally not on the first SELECT, but
I cannot remember a test run, where 300 was not sufficient.

My environment:
   - Intel PC with Linux(SuSE 9.3)
   - MySQL compiled from source
         Version 5.1 last ChangeSet@1.2096.1.1, 2006-02-14

How to repeat:
Please execute the statements above or use my attached 
testscript ndb_ml026.test
  copy it to mysql-test/t
  echo "Dummy" > r/ndb_ml026.result   # Produce a dummy file with 
                                                   # expected results
  ./mysql-test-run ndb_ml026ml
[14 Feb 2006 17:35] Matthias Leich

Attachment: ndb_ml026.test (application/test, text), 719 bytes.

[28 Feb 2006 12:40] Tomas Ulin
committed with wrong bug reference to 16385

A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

[28 Feb 2006 12:43] Tomas Ulin
pushed to 5.1.8
[28 Feb 2006 19:34] Jon Stephens
Thank you for your bug report. This issue has been committed to our
source repository of that product and will be incorporated into the
next release.

If necessary, you can access the source repository and build the latest
available version, including the bugfix, yourself. More information 
about accessing the source trees is available at

Additional info:

Documented fix in 5.1.8 changelog. Closed.