ALTER table Crash in highperf release
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Percona patches |
Fix Released
|
Critical
|
Unassigned |
Bug Description
ALTER TABLE art55.article55 ADD `domain_id` INT UNSIGNED NOT NULL AFTER `site_id`,
-> ADD `subdomain_id` INT UNSIGNED NOT NULL AFTER `domain_id`;
InnoDB: Assertion failure in thread 1283164512 in file btr0sea.c line 967
InnoDB: Failing assertion: 0 == ut_dulint_
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://
InnoDB: about forcing recovery.
InnoDB: Thread 1256540512 stopped in file row0sel.c line 2088
090210 10:59:12 - mysqld got signal 11 ;
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 1265858912 (LWP 30454)]
0x00000000006f30a0 in btr_search_
(gdb) bt
#0 0x00000000006f30a0 in btr_search_
#1 0x000000000071fa0e in buf_LRU_
#2 0x000000000071fd72 in buf_LRU_
#3 0x000000000071290f in buf_page_
#4 0x000000000072178f in buf_LRU_print ()
#5 0x000000000072250c in buf_read_
#6 0x0000000000717ff7 in buf_page_get_gen ()
#7 0x00000000006ed7c0 in btr_pcur_
#8 0x00000000006c21bc in row_search_
#9 0x000000000061aaeb in ha_innobase:
#10 0x000000000061ae2a in ha_innobase:
#11 0x000000000060a095 in rr_sequential ()
#12 0x00000000006299f3 in mysql_alter_table ()
#13 0x00000000005725e0 in mysql_execute_
#14 0x0000000000572c90 in mysql_parse ()
#15 0x00000000005733ec in dispatch_command ()
#16 0x0000000000574d41 in handle_
#17 0x00000030e4b06137 in start_thread () from /lib64/
#18 0x00000030e42c9883 in clone () from /lib64/
Related branches
Changed in percona-patches: | |
importance: | Undecided → Critical |
Changed in percona-patches: | |
status: | Fix Committed → Fix Released |
I see this problem only in -highperf release, not in regular one