Bug #18730 Partitions: NDB, crash on SELECT MIN(<unique column>)
Submitted: 3 Apr 2006 8:54 Modified: 25 May 2006 23:57
Reporter: Matthias Leich Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server: Partitions Severity:S1 (Critical)
Version:5.1 OS:
Assigned to: Sergey Glukhov CPU Architecture:Any

[3 Apr 2006 8:54] Matthias Leich
Description:
CREATE TABLE t1 (f_int1 INTEGER,f_int2 INTEGER,
f_char1 CHAR(10),f_char2 CHAR(10),f_charbig VARCHAR(1000),
UNIQUE INDEX (f_int2)) ENGINE=NDB
PARTITION BY HASH(f_int1) PARTITIONS 2;
# Attention: Here is an important difference between storage engines.
#   NDB gets success, but MyISAM+InnoDB get
#  1482: A UNIQUE INDEX need to include all fields in the partition function
#   If I  remove the UNIQUE INDEX, the bug disappears.

# crash
SELECT MIN(f_int2) FROM t1;

My environment:
   - Intel PC with Linux(SuSE 9.3)
   - MySQL compiled from source
         Version 5.1 last ChangeSet@1.2277, 2006-04-01

How to repeat:
Please use my attached testscript ndb_ml003.test
  copy it to mysql-test/t
  echo "Dummy" > r/ndb_ml003.result   # Produce a dummy file with 
                                                   # expected results
  ./mysql-test-run ndb_ml003
[3 Apr 2006 8:55] Matthias Leich
stacktrace

Attachment: stacktrace (application/octet-stream, text), 5.02 KiB.

[3 Apr 2006 8:56] Matthias Leich
testscript

Attachment: ndb_ml003.test (application/test, text), 355 bytes.

[19 Apr 2006 13:09] Bugs System
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:

  http://lists.mysql.com/commits/5140
[17 May 2006 11:44] Bugs System
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:

  http://lists.mysql.com/commits/6504
[25 May 2006 6:39] Sergey Glukhov
I can't repeat a crash on latest 5.1 tree
[25 May 2006 23:57] 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
    http://www.mysql.com/doc/en/Installing_source_tree.html

Additional info:

Documented bugfix in 5.1.11 changelog; closed.