MySQL Bugs: #15407: Partitions: crash if subpartition

Bug #15407	Partitions: crash if subpartition
Submitted:	2 Dec 2005 2:09	Modified:	16 Mar 2006 8:03
Reporter:	Peter Gulutzan	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Server: Partitions	Severity:	S3 (Non-critical)
Version:	5.1.4-alpha-debug	OS:	Linux (linux)
Assigned to:	Mikael Ronström	CPU Architecture:	Any

Description:
If I define a partitioned table, with two partitions and one subpartition, crash.

How to repeat:
mysql> create table tpp (s1 int, s2 int) partition by range (s1) subpartition by hash (s1) (partition p1 values less than (0) (subpartition p1b), partition p2 values less than (1));
ERROR 2013 (HY000): Lost connection to MySQL server during query

mysql> create table tpp (s1 int, s2 int) partition by range (s1) subpartition by hash (s1) (partition p1 values less than (0) (subpartition p1b), partition p2 values less than (1));
Query OK, 0 rows affected (0.00 sec)

mysql> select version();
+-------------+
| version()   |
+-------------+
| 5.1.4-alpha |
+-------------+
1 row in set (0.00 sec)

Oops sorry. Last time I compiled mysql without -max and that is way was not able to reproduce. After rebuilding with -max-debug, I reproduced it.

mysql> create table tpp (s1 int, s2 int) partition by range (s1) subpartition by
    -> hash (s1) (partition p1 values less than (0) (subpartition p1b), partition p2
    -> values less than (1));
ERROR 2013 (HY000): Lost connection to MySQL server during query

ysqld got signal 11;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
We will try our best to scrape up some info that will hopefully help diagnose
the problem, but since we have already crashed, something is definitely wrong
and this may fail.

key_buffer_size=8388572
read_buffer_size=131072
max_used_connections=1
max_connections=100
threads_connected=1
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 225788
 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd=0x91cb4d0
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
Cannot determine thread, fp=0xbe5fe998, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x81f12d1
0x40184715
0x8157a1f
0x82e55c9
0x820b92e
0x8213a73
0x8208adf
0x82082cc
0x8207331
0x4017f4eb
0x402e8b0a
New value of fp=(nil) failed sanity check, terminating stack trace!
Please read http://dev.mysql.com/doc/mysql/en/Using_stack_trace.html and follow
instructions on how to resolve the stack trace. Resolved
stack trace is much more helpful in diagnosing the problem, so please do
resolve it
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at 0x91eb7e0 = create table tpp (s1 int, s2 int) partition by range (
s1) subpartition by
hash (s1) (partition p1 values less than (0) (subpartition p1b), partition p2
values less than (1))
thd->thread_id=1
The manual page at http://www.mysql.com/doc/en/Crashing.html contains
information that should help you find out what is causing the crash.

0x81f12d1 sort_get_next_record + 670
0x40184715 _end + 936132053
0x8157a1f _Z19handle_grant_structjbP11st_lex_userS0_ + 435
0x82e55c9 yytable + 18761
0x820b92e flush_key_blocks_int + 57
0x8213a73 list_walk + 9
0x8208adf vio_in_addr + 24
0x82082cc hp_rb_key_length + 2
0x8207331 hp_hashnr + 128
0x4017f4eb _end + 936111019
0x402e8b0a _end + 937591242

A crash occurred if subpartitions were not set on all partitions but on at least one
partition

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.8 changelog. Closed.