Bug #56516 | Optimizing MERGE table asserts in MDL_context::upgrade_shared_lock_to_exclusive | ||
---|---|---|---|
Submitted: | 2 Sep 2010 19:03 | Modified: | 22 Sep 2010 8:22 |
Reporter: | Matthias Leich | Email Updates: | |
Status: | Duplicate | Impact on me: | |
Category: | MySQL Server: Locking | Severity: | S3 (Non-critical) |
Version: | 5.5.6, 5.5.7-bzr | OS: | Any |
Assigned to: | Assigned Account | CPU Architecture: | Any |
Tags: | locking, mdl, regression |
[2 Sep 2010 19:03]
Matthias Leich
[2 Sep 2010 19:36]
Valeriy Kravchuk
Verified with current mysql-5.5 from bzr: macbook-pro:5.5 openxs$ bin/mysql -uroot test Reading table information for completion of table and column names You can turn off this feature to get a quicker startup with -A Welcome to the MySQL monitor. Commands end with ; or \g. Your MySQL connection id is 1 Server version: 5.5.7-m3-debug Source distribution Copyright (c) 2000, 2010, Oracle and/or its affiliates. All rights reserved. This software comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to modify and redistribute it under the GPL v2 license Type 'help;' or '\h' for help. Type '\c' to clear the current input statement. mysql> CREATE TABLE t1 ( pk int, primary key (pk)); ERROR 1050 (42S01): Table 't1' already exists mysql> ALTER TABLE t1 ENGINE = MERGE UNION ( t_not_exists ); Query OK, 0 rows affected (0.08 sec) Records: 0 Duplicates: 0 Warnings: 0 mysql> OPTIMIZE TABLE t1; ERROR 2013 (HY000): Lost connection to MySQL server during query mysql> mysql> 100902 22:33:26 mysqld_safe mysqld restarted mysql> exit Bye macbook-pro:5.5 openxs$ tail -100 var/macbook-pro.err ... 100902 22:33:22 [Note] /Users/openxs/dbs/5.5/libexec/mysqld: ready for connections. Version: '5.5.7-m3-debug' socket: '/tmp/mysql.sock' port: 3306 Source distribution 100902 22:33:26 - mysqld got signal 10 ; 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=8388608 read_buffer_size=131072 max_used_connections=1 max_threads=151 thread_count=1 connection_count=1 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 337860 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. thd: 0x1020000 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... stack_bottom = 0xb0576f34 thread_stack 0x30000 0 mysqld 0x005c2b79 my_print_stacktrace + 44 1 mysqld 0x00105c28 handle_segfault + 876 2 libSystem.B.dylib 0x940472bb _sigtramp + 43 3 ??? 0xffffffff 0x0 + 4294967295 4 mysqld 0x0016c822 _Z24wait_while_table_is_usedP3THDP5TABLE17ha_extra_function + 182 5 mysqld 0x001d9cfb _Z18mysql_print_statusv + 4397 6 mysqld 0x001db4ad _ZN24Optimize_table_statement7executeEP3THD + 321 7 mysqld 0x00120da9 _Z21mysql_execute_commandP3THD + 33113 8 mysqld 0x00121414 _Z11mysql_parseP3THDPcjP12Parser_state + 624 9 mysqld 0x00121fa6 _Z16dispatch_command19enum_server_commandP3THDPcj + 2632 10 mysqld 0x001233af _Z10do_commandP3THD + 621 11 mysqld 0x00110c21 _Z24do_handle_one_connectionP3THD + 425 12 mysqld 0x00110ce5 handle_one_connection + 37 13 libSystem.B.dylib 0x9400c095 _pthread_start + 321 14 libSystem.B.dylib 0x9400bf52 thread_start + 34 Trying to get some variables. Some pointers may be invalid and cause the dump to abort... thd->query at 0x109ca10 = OPTIMIZE TABLE t1 thd->thread_id=1 thd->killed=NOT_KILLED mysql-.5.1 does not crash, so this can be called a regression.
[6 Sep 2010 7:19]
Jon Olav Hauglid
A different manifestation of Bug#56494 and fixed by the proposed patch for Bug#56494.
[22 Sep 2010 8:22]
Jon Olav Hauglid
Closed as a duplicate of Bug#56494