Showing 1-1000 of 9732 (Edit, Save, CSV, Feed) | Show Next 1000 Entries » |
ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
---|---|---|---|---|---|---|---|---|---|
48279 | 2009-10-24 11:48 | 2011-02-16 23:44 | MySQL Server | No Feedback (5496 days) | S3 | Mysql.5.1.39 | Linux | Any | Mysql.5.1.39 Automatic restart or Hangs (suspended animation) |
8026 | 2005-01-20 1:14 | 2005-01-20 8:23 | MySQL Server | Can't repeat (7266 days) | S3 | 5.0.2-alpha-debug | Windows (Windows XP SP1) | Any | Stored Procedure: Executing store procedure with out param crashes mysqld |
29083 | 2007-06-13 17:37 | 2007-11-28 18:24 | MySQL Server: Replication | Closed (6224 days) | S2 | 4.1.23 | MacOS (PPC 64 bit only) | Any | test suite times out on OS X 64bit - also in older releases |
12222 | 2005-07-27 18:17 | 2005-09-23 16:13 | MySQL Cluster: Cluster (NDB) storage engine | Closed (7020 days) | S2 | 5.1-wl2325 | Linux (Linux) | Any | One instance of TPC-B is getting Lock wait timeout exceeded (new cluster drop) |
43591 | 2009-03-12 12:00 | 2011-02-16 23:43 | MySQL Server: Locking | Duplicate (5534 days) | S5 | 5.0.67 | Linux (2.6.27-11 SMP x86_64 GNU/Linux) | Any | Deadlock on concurrent inserts results in "Lock wait timeout" for other tables |
74003 | 2014-09-22 3:08 | 2018-09-25 12:27 | MySQL Server | Can't repeat (2270 days) | S3 | 5.6.16 | Any | Any | The server was crashed because of long semaphore wait |
69127 | 2013-05-02 18:49 | 2013-05-29 23:51 | MySQL Server: InnoDB storage engine | Closed (4215 days) | S2 | 5.5.31 | Any | Any | InnoDB: possible regression in 5.5.31, Bug#16004999 |
55167 | 2010-07-11 17:23 | 2013-02-06 1:18 | MySQL Server: InnoDB storage engine | Can't repeat (4327 days) | S3 | 5.5.5 | Any | Any | InnoDB: performance regression in sysbench OLTP_RO test |
67615 | 2012-11-16 16:21 | 2018-01-26 16:20 | MySQL Server: InnoDB storage engine | Not a Bug (2512 days) | S2 | 5.5.28 | Linux (6.2) | Any | Massive conccurent inserts and lock wait timeout |
69969 | 2013-08-09 5:47 | 2014-03-27 13:43 | MySQL Server: Optimizer | Closed (3961 days) | S2 | 5.5.33 | Any | Any | Failing assertion: prebuilt->trx->conc_state == 1 from subselect |
7267 | 2004-12-14 13:48 | 2004-12-14 20:08 | MySQL Server: InnoDB storage engine | Can't repeat (7303 days) | S1 | 4.0.20 | Linux (RedHat 9.0 Linux) | Any | MySql crashed during use |
27967 | 2007-04-19 23:17 | 2007-05-22 14:45 | Connector / NET | Not a Bug (6414 days) | S1 | 5.0.6 | Windows | Any | Deadlock found when trying to get lock; try restarting transaction |
71041 | 2013-11-29 18:39 | 2017-09-05 1:11 | MySQL Server | Closed (2655 days) | S3 | 5.6 | Any | Any | Please, document every instrument in P_S.setup_instruments in details |
37775 | 2008-07-01 15:46 | 2012-10-15 14:50 | Tests: Server | Unsupported (4441 days) | S3 | 6.0-BK,5.4 | Any | Any | main.locktrans_innodb and rpl.rpl_locktrans_innodb fail randomly |
106412 | 2022-02-09 3:24 | 2022-02-09 13:35 | MySQL Server: Storage Engine API | Not a Bug (1037 days) | S3 | 5.7.20 | CentOS | x86 | The server was crashed because of long semaphore wait |
68573 | 2013-03-05 12:57 | 2017-07-07 9:08 | MySQL Server: Query Cache | Won't fix (2715 days) | S3 | 5.5.25a, 5.6.17 | Any | Any | 50ms query cache lock timeout not applied to SELECT statements correctly |
18808 | 2006-04-05 14:25 | 2013-10-06 20:45 | MySQL Cluster: Cluster (NDB) storage engine | Duplicate (6810 days) | S3 | 5.1.9 | Linux (Linux 32 Bit OS) | Any | "Rowid already allocated" Error duing update and not during node recovery |
79665 | 2015-12-16 10:50 | 2017-05-31 20:02 | MySQL Server: Documentation | Closed (2752 days) | S3 | any | Any | Any | Manual does NOT explain locks set by INSERT ... ON DUPLICATE KEY UPDATE properly |
27971 | 2007-04-20 3:43 | 2008-01-04 18:06 | MySQL Server: InnoDB storage engine | Closed (6187 days) | S1 | 5.0.37,5.0.45 | FreeBSD (FreeBSD 6.2-RELEASE) | Any | mysqld stop running after 'a long semaphore wait' appear |
38660 | 2008-08-08 8:50 | 2011-02-16 23:43 | MySQL Server: Replication | No Feedback (5845 days) | S2 | 5.0.51a, 5.1.26 | Linux | Any | Lock wait timeout exceeded while failing-over on master-master replication setup |
99171 | 2020-04-03 12:21 | 2021-03-02 13:20 | MySQL Server: InnoDB storage engine | Won't fix (1382 days) | S3 | 8.0.19 | Any | Any | Inconsistent and Incorrect rw-lock stats |
110584 | 2023-04-03 2:51 | 2023-04-03 4:10 | MySQL Server: InnoDB storage engine | Verified (619 days) | S3 | Ver 8.0 | Any | Any | add missing timestamp and headers information innodb_print_all_deadlocks |
74542 | 2014-10-24 10:05 | 2014-10-24 10:51 | MySQL Server: Optimizer | Verified (3702 days) | S3 | 5.6/5.7 | Any | Any | FLUSH TABLES WITH READ LOCK blocks EXPLAIN UPDATE/DELETE/INSERT |
68083 | 2013-01-14 14:41 | 2013-01-14 18:18 | MySQL Server | Not a Bug (4350 days) | S2 | 5.1.61 | Any | Any | Inserts that cannot progress that wait for a LOCK, innodb implicity kill them |
91743 | 2018-07-20 15:23 | 2018-11-13 15:46 | MySQL Server: Documentation | Closed (2221 days) | S2 | 8.0.11 | Red Hat (7.4) | Any | performance_schema.data_locks not working correctly |
114446 | 2024-03-21 14:30 | 2024-04-22 10:14 | MySQL Server: InnoDB storage engine | Not a Bug (266 days) | S3 | 8.0.* | Any | Any | A deadlock example cause by lock inherit |
54673 | 2010-06-21 16:22 | 2011-02-16 23:44 | MySQL Server: Locking | Closed (5111 days) | S3 | 5.1.48, 5.5.5pre | Any | Any | It takes too long to get readlock for 'FLUSH TABLES WITH READ LOCK' |
28478 | 2007-05-16 17:05 | 2007-06-20 0:51 | MySQL Server: MyISAM storage engine | Closed (6385 days) | S2 | 5.0.42, * | Any | Any | Improper key_cache_block_size corrupts MyISAM tables |
22106 | 2006-09-08 6:46 | 2018-09-09 20:45 | MySQL Server: DML | Verified (6217 days) | S3 | 5.0.26-BK | Linux (Linux) | Any | can't output to error log file when INNODB happened ERROR1205 |
57167 | 2010-10-01 13:08 | 2011-04-22 13:27 | MySQL Server: Locking | Won't fix (4983 days) | S3 | mysql-next-mr-wl3561 | Any | Any | Misleading error for LOCK TABLE t1 IN SHARE MODE NOWAIT |
47180 | 2009-09-07 18:17 | 2011-02-16 23:44 | MySQL Server: Locking | No Feedback (5531 days) | S1 | 5.0.27 | Linux | Any | ERROR 1205 (HY000): Lock wait timeout exceeded; try restarting transaction. |
87489 | 2017-08-21 8:15 | 2021-09-06 12:47 | MySQL Server: Replication | Can't repeat (2646 days) | S2 | 5.7.16 | Any | Any | MTS ordered commit may cause deadlock with "FLUSH TABLES WITH READ LOCK"of slave |
29154 | 2007-06-16 7:29 | 2007-07-04 1:52 | MySQL Server | Closed (6371 days) | S2 | 5.0.44-BK, 5.0.40 | Linux | Any | LOCK TABLES is not atomic when >1 InnoDB tables are locked |
40044 | 2008-10-15 12:27 | 2009-01-08 10:42 | MySQL Server: Maria storage engine | Closed (5817 days) | S3 | 5.1-maria | Windows | Any | Maria: maria.test fails under Windows (lock wait timeout) |
1728 | 2003-10-31 17:01 | 2003-12-13 4:44 | MySQL Server | Won't fix (7670 days) | S2 | 4.0.16 | Linux (Red Hat linux 8.0) | Any | lock timeout not consistently returned by mysql_query() |
20725 | 2006-06-27 14:05 | 2006-06-29 9:47 | MySQL Cluster: Cluster (NDB) storage engine | Closed (6741 days) | S3 | 5.1.12 | Linux (Linux 32 bit OS) | Any | MySQLD cluster use "fast count" is broken |
27380 | 2007-03-22 17:25 | 2007-03-26 15:22 | MySQL Server | Not a Bug (6471 days) | S2 | 5.0.22 and 5.0.37 | Linux (RedHat Enterprise 4) | Any | Problems Deleting Data from InnoDB |
51204 | 2010-02-16 6:13 | 2011-02-16 23:44 | MySQL Server: General | No Feedback (5385 days) | S5 | Linux (ubantu) | Any | Lock wait timeout exceeded; try restarting transaction | |
108891 | 2022-10-26 20:22 | 2022-10-27 6:07 | MySQL Server: InnoDB storage engine | Verified (777 days) | S3 | 8.0 | Any | Any | innodb_print_all_deadlocks missing information. |
71365 | 2014-01-13 16:24 | 2016-03-01 17:46 | MySQL Server: Documentation | Closed (3208 days) | S3 | 5.5, 5.6 | Any | Any | "Waiting for table level lock" thread state is not explained properly |
10472 | 2005-05-09 12:13 | 2007-02-13 16:54 | MySQL Server: InnoDB storage engine | Can't repeat (6512 days) | S1 | 4.1.9-max-log | Linux (Red Hat Linux release 9, Windows XP SP2) | Any | InnoDB deadlock in srv0srv.c causing server crash and restart |
48939 | 2009-11-20 11:30 | 2015-08-23 20:45 | MySQL Server: General | Duplicate (5491 days) | S2 | mysql-next | Any | Any | First character in error text replaced with Z on DBUG_EXTRA builds |
15005 | 2005-11-17 6:28 | 2005-11-30 7:55 | MySQL Cluster: Cluster (NDB) storage engine | Duplicate (6952 days) | S3 | 5.0.15 | Miracle Linux V3.0 | Any | MySQL Cluster respond "Lock wait timeout exceeded" after issuing SELECT stateme |
48956 | 2009-11-20 21:46 | 2011-02-16 23:44 | MySQL Server: Partitions | No Feedback (5466 days) | S3 | 5.5.0-beta | IBM i | Any | Partition tests are intolerably slow on i5os (factor more than 10) |
19527 | 2006-05-04 6:40 | 2006-06-12 11:47 | MySQL Server | No Feedback (6758 days) | S2 | 4.1.1 | Linux (Linux) | Any | Deadlock due to potential lock mode conflict |
113473 | 2023-12-20 11:29 | 2024-01-08 10:26 | MySQL Server: InnoDB storage engine | Unsupported (350 days) | S3 | 5.7.25 | CentOS (7.3) | Any | InnoDB: Assertion failure in thread 139747416012544 in file ut0ut.cc line 947 |
38085 | 2008-07-13 15:38 | 2021-05-02 20:45 | MySQL Cluster: Cluster (NDB) storage engine | No Feedback (5754 days) | S3 | Any | Any | rpl_ndb.rpl_ndb_basic: 'Lock wait timeout exceeded...' At line 8 | |
73168 | 2014-07-02 4:14 | 2015-02-25 10:51 | MySQL Server: InnoDB storage engine | Verified (3816 days) | S5 | 5.6/5.7 | Any | Any | locking/unlocking overhead for THD::LOCK_thd_data |
45901 | 2009-07-02 9:24 | 2009-07-02 14:03 | MySQL Server: InnoDB storage engine | Not a Bug (5642 days) | S3 | 5,1.30, 5.1.33, 5.1.35, 5.1.36 | Windows (XP) | Any | Cannot do SELECT FOR UPDATE with small amount of records. |
55203 | 2010-07-13 6:46 | 2017-05-09 12:20 | MySQL Cluster: Cluster (NDB) storage engine | No Feedback (5201 days) | S1 | mysql-5.1-telco-7.1 | Linux (Red Hat Enterprise Linux Server release 5.4) | Any | NDB node keep starting state for long time after changes on config.ini |
88964 | 2017-12-19 8:10 | 2017-12-26 10:21 | MySQL Server | Not a Bug (2543 days) | S3 | 5.7.20 | CentOS (6) | Any | binlog deadlock appears while backing up MTS slave |
36525 | 2008-05-06 10:34 | 2008-08-12 16:27 | MySQL Server | Closed (5966 days) | S2 | 5.0.45 | Linux (EDT 2007 x86_64 x86_64 x86_64 GNU/Linux ) | Any | Mysql Server becomes very slow. |
82774 | 2016-08-29 3:13 | 2017-04-13 22:01 | MySQL Server: Locking | Not a Bug (2800 days) | S3 | 5.7.13 | Any | Any | Reasonably easy to generate mysqld semi-hang. Input file is 1K lines. |
101695 | 2020-11-20 12:09 | 2022-02-01 13:33 | MySQL Server | Not a Bug (1483 days) | S3 | 5.6, 5.7, 8.0 | Any | Any | Deadlock behavior |
115194 | 2024-06-03 6:24 | 2024-06-03 13:43 | MySQL Server: Documentation | Verified (192 days) | S3 | 8.0 | Any | Any | Incorrect description of Online DDL Operations in reference manual |
45067 | 2009-05-25 13:35 | 2011-02-16 23:44 | MySQL Server: Locking | Closed (5395 days) | S3 | 6.0, 5.4 | Any | Any | Assertion `stmt_da->is_error()' in Delayed_insert::open_and_lock_table |
113950 | 2024-02-10 23:25 | 2024-02-19 12:32 | MySQL Server: InnoDB storage engine | Can't repeat (300 days) | S3 | 8.0.30 | Linux | x86 | MySQL 8.0.30 is stuck due to the processing of a large transaction |
48029 | 2009-10-13 19:30 | 2011-02-16 23:44 | MySQL Server: InnoDB storage engine | No Feedback (5508 days) | S3 | 5.1.34 | Linux | Any | Deadlock between INSERT...ON DUPLICATE KEY... and DELETE on InnoDB |
97452 | 2019-11-01 6:33 | 2019-11-11 6:21 | MySQL Server | Not a Bug (1858 days) | S3 | 5.7.27 | CentOS (CentOS release 6.10 (Final)) | x86 (Intel(R) Xeon(R) CPU E5-2687W v4) | InnoDB: Assertion failure in thread xxx in file ut0ut.cc line 910 |
72011 | 2014-03-11 16:06 | 2014-03-17 21:33 | MySQL Server: Documentation | Not a Bug (3923 days) | S3 | 5.6 | Any | Any | Deadlock with 3 transactions (inserts) |
90228 | 2018-03-27 11:19 | 2018-03-28 8:15 | MySQL Server: SYS Schema | Closed (2451 days) | S3 | 5.7.21 | Any | Any | sys.innodb_lock_waits showing the wrong blocking query |
90210 | 2018-03-26 2:22 | 2018-04-03 14:03 | MySQL Server: InnoDB storage engine | Not a Bug (2445 days) | S2 | 5.6.32+ | Any (CentOS,Ubuntu,MAC) | Any (intel64,MAC) | deadlock when concurrency update the same index |
114849 | 2024-05-02 9:53 | 2024-05-07 11:57 | MySQL Cluster: Cluster (NDB) storage engine | Not a Bug (219 days) | S2 | 8.0.35-cluster MySQL Cluster Community S | Any (20.04) | Any | Scan error in NDB cluster |
72407 | 2014-04-20 20:47 | 2014-04-24 17:30 | MySQL Server: Locking | Not a Bug (3885 days) | S1 | 5.6.10, 5.6.17 | Linux (Centos 6.5/6.3) | Any | Unclear Deadlock conditions with delete / update statement. |
30379 | 2007-08-13 1:55 | 2007-11-06 8:45 | MySQL Cluster: Cluster (NDB) storage engine | Closed (6246 days) | S3 | Any | Any | TC timeout check isn't very random | |
71638 | 2014-02-09 14:41 | 2016-05-13 19:29 | MySQL Server: Documentation | Closed (3135 days) | S3 | 5.6 | Any | Any | Manual does NOT explain "insert intention" lock mode properly |
86486 | 2017-05-28 1:01 | 2017-11-16 10:02 | MySQL Server: Replication | Duplicate (2583 days) | S3 | 5.7.x | Any | Any | XA Transactions in binlog cause replication broken |
56422 | 2010-08-31 19:28 | 2011-02-16 23:44 | MySQL Server | Closed (5136 days) | S3 | 5.5.6-m3, 5.6.0-m4, 5.6.99 | Any | Any | CHECK TABLE run when the table is locked reports corruption along with timeout |
5785 | 2004-09-28 12:36 | 2004-09-28 16:07 | MySQL Cluster: Cluster (NDB) storage engine | Closed (7380 days) | S2 | mysql 4.1.6 | Fermi Linux LTS 3.01 | Any | lock timeout during concurrent update |
113277 | 2023-11-29 6:09 | 2023-12-05 16:03 | MySQL Cluster: Cluster (NDB) storage engine | Not a Bug (373 days) | S3 | 8.0.35-cluster MySQL Cluster Community S | Ubuntu (20.04) | Any | Blocking prevents a transaction from acquiring a lock properly |
31275 | 2007-09-28 10:13 | 2007-09-28 10:49 | MySQL Server: InnoDB storage engine | Not a Bug (6285 days) | S3 | 5.0.21 | Windows (XP, SP2) | Any | slow querries |
106115 | 2022-01-08 15:01 | 2022-01-11 14:20 | MySQL Server: InnoDB storage engine | Unsupported (1066 days) | S3 | 8.0.19 | Red Hat (7.7) | Any | MySQL 8.0.19 is stuck due to the execution of big transaction |
106119 | 2022-01-09 2:31 | 2022-01-10 15:26 | MySQL Server: DML | Unsupported (1067 days) | S3 | 8.0.19 | Red Hat (7.7) | Any | MySQL 8.0.19 is stuck due to the execution of a big transaction |
107656 | 2022-06-25 13:55 | 2022-07-01 12:09 | MySQL Server | Not a Bug (895 days) | S3 | 5.7.29 | Linux | x86 | insert into on duplicate key update with PRIMARY cause a deadlock |
88110 | 2017-10-16 15:54 | 2017-10-16 16:05 | MySQL Server: Locking | Duplicate (2614 days) | S2 | 5.6.36-82 | CentOS (6.8 Final) | Any | Error: semaphore wait has lasted > 600 seconds, and forcing recovery |
43734 | 2009-03-18 20:53 | 2011-02-16 23:43 | MySQL Server: Locking | Can't repeat (5511 days) | S2 | 5.1.30 | Windows (XP Pro SP2) | Any | SELECT ... ORDER BY ... FOR UPDATE lock may be broken |
24922 | 2006-12-08 18:03 | 2006-12-08 18:13 | MySQL Server: Locking | Not a Bug (6579 days) | S3 | 5.0.18-pro | Linux (Linux 2.6.13-1.1532_FC4T) | Any | Question about locking with mysqldump |
69835 | 2013-07-25 2:41 | 2013-08-22 2:52 | MySQL Server: InnoDB storage engine | Not a Bug (4130 days) | S3 | 5.6.12 | Any | Any | deadlock detected on concurrent insert |
74743 | 2014-11-07 20:57 | 2014-11-07 21:53 | MySQL Server | Duplicate (3688 days) | S1 | 5.5.40 | Linux (Debian Wheezy) | Any | MySQL crashing after long semaphore wait |
65153 | 2012-04-30 6:26 | 2012-06-01 1:00 | MySQL Server: Locking | No Feedback (4579 days) | S2 | 5.1.45 | Linux (Fedora) | Any | InnoDB locking issues after mysql crash recovery |
72123 | 2014-03-25 14:12 | 2017-10-04 3:52 | MySQL Server: InnoDB storage engine | Verified (3913 days) | S3 | 5.6, 5.6.18 | Any | Any | Spurious lock_wait_timeout_thread wakeup in lock_wait_suspend_thread() |
45694 | 2009-06-24 7:04 | 2011-02-16 23:44 | MySQL Server: Replication | Closed (5566 days) | S2 | 5.0.77, 5.0 5.1, azalea bzr | Linux | Any | Deadlock in replicated statement is not retried |
51140 | 2010-02-12 12:06 | 2010-02-13 7:42 | MySQL Server: InnoDB storage engine | Not a Bug (5416 days) | S3 | 5.1.31 | Linux | Any | Deadlock instead of timeout when inserting the same row from two transactions |
62210 | 2011-08-19 11:47 | 2012-02-02 19:59 | MySQL Server: InnoDB Plugin storage engine | Can't repeat (4697 days) | S2 | 5.1.48 (1.0.9) | Linux (2.6.18-164.el5) | Any | memory corruption for THD after deadlock in foreign key reference constrain |
73816 | 2014-09-05 12:56 | 2016-04-18 3:18 | MySQL Server: Locking | Closed (3215 days) | S2 | 5.6.20 | Any | Any | MySQL instance stalling “doing SYNC index” |
65130 | 2012-04-27 12:12 | 2013-05-23 19:20 | MySQL Cluster: Cluster (NDB) storage engine | Closed (4221 days) | S3 | 7.1.x, 7.2.5 | Linux | Any | "Transaction already aborted" hides real error msg on INSERT ... ON DUP UPDATE |
43310 | 2009-03-02 16:42 | 2014-03-31 15:19 | Connector / J | Can't repeat (3909 days) | S2 | Linux | Any | Transaction rollback (because of a deadlock) doesn't throw an Exception | |
10641 | 2005-05-14 22:02 | 2005-06-13 6:53 | MySQL Server: InnoDB storage engine | Not a Bug (7122 days) | S3 | 4.1.11 | Linux (linux-2.6.11.9) | Any | 1205, 'Lock wait timeout exceeded; try restarting transaction' |
38087 | 2008-07-13 16:01 | 2021-05-02 20:45 | MySQL Cluster: Cluster (NDB) storage engine | No Feedback (5754 days) | S3 | Any | Any | rpl_truncate_7ndb failed at At line 15: replace into mysql.ndb_apply_status | |
59969 | 2011-02-05 21:41 | 2021-05-02 20:45 | Tests: Cluster | Verified | S3 | 7.1.10 | Any | Any | Test 'ndb_blob_big' times out in locking |
70424 | 2013-09-25 21:03 | 2016-04-05 14:08 | MySQL Cluster: Cluster (NDB) storage engine | Can't repeat (3173 days) | S2 | 7.3.2 | Linux (centos 6.4 64bit) | Any | Unable to add index to the table - tablespace and undo logs are used |
46044 | 2009-07-08 15:38 | 2011-02-16 23:44 | MySQL Server: Locking | Closed (5394 days) | S3 | 5.4 | Any | Any | MDL deadlock on LOCK TABLE + CREATE TABLE HIGH_PRIORITY FOR UPDATE |
65109 | 2012-04-26 7:56 | 2013-04-16 1:00 | MySQL Server: InnoDB Plugin storage engine | No Feedback (4259 days) | S5 | MySQL 5.1.61 | Linux (CentOS release 6.2 x86_64) | Any | Contention caused by buf_pool_zip_mutex |
41564 | 2008-12-17 18:35 | 2021-05-23 20:45 | MySQL Server: Falcon storage engine | Duplicate (5837 days) | S3 | 6.0.9 | Any | Any | Falcon; incorrect lock wait timeouts can occur |
19402 | 2006-04-27 15:51 | 2006-11-28 20:22 | MySQL Server: Replication | Closed (6589 days) | S2 | 4.1.all, 5.0.21 | Windows (Win2000) | Any | SQL close to the size of the max_allowed_packet fails on the slave |
73890 | 2014-09-11 13:01 | 2023-04-28 2:23 | MySQL Server: Locking | No Feedback (1322 days) | S1 | 5.5.39/5.7 | Windows (Server 2008) | Any | Error: semaphore wait has lasted > 600 seconds |
76361 | 2015-03-17 22:54 | 2015-03-23 12:39 | Tests | Verified (3552 days) | S3 | 5.6 | Any | Any | Some MTR tests fail if hostname is localhost |
55093 | 2010-07-08 17:32 | 2012-05-18 20:19 | MySQL Cluster: Replication | Verified | S3 | mysql-5.1-telco-7.0 | Solaris (Sparc) | Any | Timeout of tests 'rpl_ndb_typeconv_*' on Solaris Sparc |
96135 | 2019-07-09 7:36 | 2019-07-09 12:33 | MySQL Server | Can't repeat (1983 days) | S3 | mysql-8.0.16-linux-glibc2.12-x86_64 | CentOS (3.10.0-123.el7.x86_64) | x86 (x86_64) | mysql server bug |
48210 | 2009-10-21 17:32 | 2011-02-16 23:44 | MySQL Server: Locking | Closed (5394 days) | S3 | mysql-6.0-codebase-bugfixing | Any | Any | FLUSH TABLES WITH READ LOCK deadlocks against concurrent CREATE PROCEDURE |
92133 | 2018-08-22 17:43 | 2022-11-24 15:40 | MySQL Server: Data Dictionary | Verified (2238 days) | S5 | 8.0.12 | Any | Any | DICT_SYS mutex contention causes complete stall when running with 40 mill tables |
102791 | 2021-03-03 5:03 | 2021-03-05 13:13 | MySQL Server | Not a Bug (1379 days) | S3 | 5.7.30 GA | Any | Any | A deadlock occurs one innodb tables between unrelated rows |
58591 | 2010-11-30 15:32 | 2024-02-04 20:45 | MySQL Proxy: Scripts | Verified (5123 days) | S3 | 0.8.1 | Linux (Centos5) | Any | [network-mysqld.c:937]: error on a connection (fd: -1 event: 0). closing client |
46151 | 2009-07-13 15:12 | 2010-05-26 18:01 | MySQL Server: Falcon storage engine | Unsupported (5314 days) | S3 | 6.0.12-bzr | Solaris | Any | falcon_bug_34174 fails with lock wait timeout when pool-of-threads is enabled |
104138 | 2021-06-29 3:21 | 2021-08-02 12:21 | MySQL Server: InnoDB storage engine | Can't repeat (1228 days) | S3 | 8.0 | Any | Any | mtr index lock release fail |
29123 | 2007-06-14 22:44 | 2007-07-02 5:06 | Connector / NET | Closed (6373 days) | S1 | 5.0.7 | Windows | Any | Connection String grows with each use resulting in OutOfMemoryException |
45371 | 2009-06-08 12:28 | 2011-02-16 23:44 | MySQL Cluster: Cluster (NDB) storage engine | Closed (5603 days) | S3 | mysql-5.1-telco-7.0 | Any | Any | StartPartitionedTimeout and StartPartialTimeout def values not applied |
9949 | 2005-04-16 5:12 | 2005-06-08 14:38 | MySQL Server: Replication | Closed (7127 days) | S2 | 4.0.23 | Linux (Linux RH-E3) | Any | Corruption in master binlog caused by full disk |
15630 | 2005-12-09 11:20 | 2006-01-06 5:21 | MySQL Server: Stored Routines | Closed (6915 days) | S2 | clone-5.0.17-build | Various 64 bit ones | Any | Test case failure in sp-dynamic, sp-error, and sp |
64873 | 2012-04-05 10:51 | 2014-01-25 1:00 | MySQL Server: InnoDB storage engine | No Feedback (3975 days) | S3 | 5.5.20 | Linux (rhel 5: 2.6.18-274.7.1.el5) | Any | Error: semaphore wait has lasted > 600 seconds |
89896 | 2018-03-03 8:43 | 2018-03-05 4:14 | MySQL Server | Can't repeat (2474 days) | S1 | 5.0.41 | Linux | Any | Thread 139967096907520 has waited at trx0trx.c line 715 for 784.00 seconds the s |
68979 | 2013-04-17 3:47 | 2018-07-11 15:11 | MySQL Server: Optimizer | Verified (4222 days) | S5 | 5.6.10 | Linux | Any | performance regression of MySQL 5.6.10? |
56046 | 2010-08-17 9:12 | 2011-02-16 23:44 | MySQL Server: Locking | No Feedback (5199 days) | S1 | 5.1.46sp1-enterprise-gpl-pro-log | Linux (Red Hat Enterprise Linux Server release 5.3 (Tikanga) x86_64) | Any | 'SELECT ... FOR UPDATE' locked another table's index |
87476 | 2017-08-18 14:27 | 2017-08-23 10:32 | MySQL Server: InnoDB storage engine | Can't repeat (2668 days) | S2 | 5.7.12 | Debian (8.5) | Any | Semaphore wait crash due to long held lock during online index creation |
87477 | 2017-08-18 14:27 | 2018-12-03 20:50 | MySQL Server: InnoDB storage engine | Duplicate (2201 days) | S2 | 5.7.12 | Debian (8.5) | Any | Semaphore wait crash due to long held lock during online index creation |
52832 | 2010-04-14 18:46 | 2021-05-02 20:45 | MySQL Cluster: Cluster (NDB) storage engine | No Feedback (5242 days) | S1 | 5.1.35-ndb-7.0.7 | Linux (CentOS 5.3) | Any | Random lock up - Lock wait timeout exceeded - NDBCluster |
22667 | 2006-09-25 15:08 | 2006-09-27 7:54 | MySQL Server | Not a Bug (6651 days) | S2 | 5.0.22 | Linux (Linux 2.6.8.1-25mdkenterprise) | Any | Unable to lock /REP_MYSQL/mysql/innodb_file/ibdata1, error: 11 |
54318 | 2010-06-08 3:08 | 2012-05-18 20:19 | MySQL Server: Backup | Verified | S2 | 5.1.34 | Any | Any | global read lock via dump --master-data blocked with lots of commits |
46915 | 2009-08-25 11:16 | 2011-02-16 23:44 | MySQL Server: InnoDB storage engine | No Feedback (5557 days) | S2 | 5.0.77 | Linux (Red Hat Enterprise Linux Server release 5.3 (Tikanga)) | Any | long semaphore wait |
19201 | 2006-04-19 17:08 | 2006-05-13 14:46 | MySQL Cluster: Cluster (NDB) storage engine | Closed (6788 days) | S2 | 4.1 -> | Linux (Linux) | Any | TRUNCATE table with blobs fails with 1205 |
24144 | 2006-11-09 14:20 | 2022-08-21 20:45 | MySQL Server: Locking | Duplicate (6021 days) | S2 | 5.1-BK | Linux (Linux) | Any | strange transactional behaviour: DROP TABLE drops also locks |
28685 | 2007-05-25 19:11 | 2011-02-16 23:43 | MySQL Server: Tests | Can't repeat (5768 days) | S3 | 5.1.19 | Any | Any | Suite "rowlock" fails totally: "Lock wait timeout exceeded", common include file |
38070 | 2008-07-12 14:26 | 2011-02-16 23:43 | Tests: Replication | Closed (5698 days) | S3 | 6.0 | Any | Any | rpl_locktrans_innodb Lock wait timeout exceeded At line 632 |
51544 | 2010-02-26 9:39 | 2011-02-16 23:44 | MySQL Cluster: Cluster (NDB) storage engine | Can't repeat (5153 days) | S3 | 7.0.* | Any | Any | select (no locking) fails with "lock wait timeout exceeded" |
65912 | 2012-07-16 14:52 | 2012-07-16 15:42 | MySQL Server: Locking | Can't repeat (4532 days) | S1 | 5.1.49 | Linux | Any | Lock wait timeout exceeded while failing-over on master-master replication setup |
93115 | 2018-11-08 8:19 | 2019-05-21 12:45 | MySQL Server | Not a Bug (2225 days) | S3 | 8.0.13 | Any | Any | SKIP LOCKED mode is preventing to UPDATE the very next row. |
40147 | 2008-10-19 17:29 | 2008-11-21 7:12 | MySQL Server: InnoDB storage engine | No Feedback (5865 days) | S1 | 5.0.18 | Linux (SuSe 10.1) | Any | InnoDB: All tables / databases Lock / Global Lock ??? - Please help |
35047 | 2008-03-04 17:56 | 2021-05-23 20:45 | MySQL Server: Falcon storage engine | Duplicate (6058 days) | S3 | 6.0-falcon-team | Any | Any | Falcon crash in Table::hasUncommittedRecords line 3261 |
71916 | 2014-03-03 16:52 | 2016-10-26 13:43 | MySQL Server: Documentation | Closed (2969 days) | S3 | 5.6 | Any | Any | Manual does NOT explain locks set for UPDATE ... WHERE PK='const' properly |
81348 | 2016-05-08 16:52 | 2016-05-10 15:43 | MySQL Server: Locking | Verified (3138 days) | S3 | 5.7 | Any | Any | table_locks_waited not updated in MySQL 5.7 |
85749 | 2017-03-31 16:45 | 2018-05-15 18:45 | MySQL Server: Documentation | Closed (2403 days) | S3 | 5.7 | Any | Any | Manual does NOT explain gap locks set by SELECT ... FOR UPDATE |
91511 | 2018-06-30 21:08 | 2018-07-25 15:34 | MySQL Server: Documentation | Closed (2332 days) | S3 | 8.0 | Any | Any | List of mysqld command line options which are undocumented |
82592 | 2016-08-16 3:55 | 2016-09-02 13:11 | MySQL Server: InnoDB storage engine | Not a Bug (3033 days) | S3 | 5.7.14 | Any | Any | MySQL InnoDB update locking |
65938 | 2012-07-18 13:56 | 2017-03-12 20:45 | MySQL Cluster: Cluster (NDB) storage engine | No Feedback (4316 days) | S2 | 5.5.22-ndb-7.2.6-gpl-log | Linux (CentOS release 6.3 (Final) 2.6.32-279.1.1.el6.x86_64) | Any | ndbdmtd shutdown 1 min after started: Illegal signal ... (GSN 32 not added) |
40737 | 2008-11-14 12:14 | 2009-08-12 21:43 | MySQL Server: Locking | Not a Bug (5601 days) | S2 | 5.0.67 | Any | Any | Lock wait timeout exceeded during inserting row |
27766 | 2007-04-11 19:55 | 2021-05-02 20:45 | MySQL Cluster: Cluster (NDB) storage engine | Verified (6455 days) | S3 | mysql-5.1-telco-6.2 | Linux (32 Bit) | Any | DN restarts using ndb_mgm give inconsistent results |
39813 | 2008-10-02 14:29 | 2008-11-24 13:01 | MySQL Server: Backup | Can't repeat (5862 days) | S3 | 6.0-backup | Any | Any | Backup: possible deadlock when default and myisam drivers are used |
41857 | 2009-01-05 9:29 | 2015-04-13 7:37 | Connector / J | Can't repeat (3531 days) | S1 | 5.0.7 | Linux ( 2.4.20-8 #1 Thu Mar 13 17:54:28 EST 2003 i686 i686 i386 GNU/Linux) | Any | Simillar bug as 25514 |
54086 | 2010-05-29 18:46 | 2022-09-04 20:45 | MySQL Server: General | No Feedback (5194 days) | S1 | mysql-5.5.3-m3-winx64 | Windows (server 2003 x64) | Any | Server crashing when connector/J testsuite run against it |
3894 | 2004-05-26 5:52 | 2004-05-31 15:47 | MySQL Server: InnoDB storage engine | Closed (7500 days) | S2 | 4.0.20 | Linux (RedHat Linux) | Any | lock tables ... write works wrong |
13335 | 2005-09-20 5:26 | 2006-03-10 12:34 | MySQL Server | No Feedback (6852 days) | S2 | 4.1.14 | Linux (RedHat Enterprise Linux AS 3) | Any | running out of threads at just over 1000 connections |
40515 | 2008-11-05 0:18 | 2011-02-16 23:43 | MySQL Server: Partitions | Closed (5805 days) | S3 | 5.1.26,5.1.29 | Any | Any | Query on a partitioned table does not return 'lock wait timeout exceeded' |
76686 | 2015-04-14 9:14 | 2016-09-02 16:24 | MySQL Server: Replication | Verified (3306 days) | S3 | 5.7 | Any | Any | reduce mutex contention of LOCK_done during Group Commit |
76728 | 2015-04-17 4:48 | 2016-06-07 8:56 | MySQL Server: InnoDB storage engine | Closed (3114 days) | S3 | 5.7.7 | Any | Any | reduce lock_sys->mutex contention for transaction that only contains SELECT |
32395 | 2007-11-14 20:04 | 2010-10-11 7:54 | MySQL Server: Locking | Closed (6204 days) | S2 | 5.1 | Any | Any | Alter table under a impending global read lock causes a server crash |
51086 | 2010-02-11 11:11 | 2010-02-11 16:49 | MySQL Server: Locking | Not a Bug (5418 days) | S2 | 5.0.51a | Linux | Any | last deadlock detected not showing a valid reason for the deadlock |
77740 | 2015-07-15 20:41 | 2015-12-08 11:14 | MySQL Server: Replication | Closed (3292 days) | S1 | 5.7.9 | Windows | Any | silent failure to start if mysql.gtids_executed gets HA_ERR_LOCK_WAIT_TIMEOUT |
74154 | 2014-09-30 13:58 | 2014-11-04 18:05 | MySQL Cluster: Cluster (NDB) storage engine | Closed (3691 days) | S2 | 7.3.7 | Any | Any | Node restart blocked by DICT LOCK held by schema transaction |
70581 | 2013-10-10 4:16 | 2013-11-11 1:00 | MySQL Server: InnoDB storage engine | No Feedback (4050 days) | S3 | 5.5.21 | Linux (centos 5.4 ) | Any | mysql server hang |
59354 | 2011-01-07 15:07 | 2013-01-29 19:33 | MySQL Server: InnoDB storage engine | Closed (4335 days) | S3 | 5.5,mysql-trunk | Linux | Any | Assert !other_lock at lock_rec_add_to_queue during a delete operation |
38188 | 2008-07-16 23:04 | 2008-10-14 16:06 | MySQL Server: Replication | No Feedback (5903 days) | S1 | 5.1.26 | Linux (CentOS release 5 (Final) x86_64) | Any | Replication deadlock |
84492 | 2017-01-12 16:39 | 2018-05-15 14:04 | MySQL Server: Optimizer | Duplicate (2890 days) | S3 | 5.7.14, 5.7.17 | Oracle Linux (7.2) | Any | X lock on PRIMARY key for all records if a subquery is used in UPDATE statement |
68961 | 2013-04-15 9:04 | 2013-12-24 15:55 | MySQL Server: InnoDB storage engine | Duplicate (4006 days) | S2 | 5.5.28 | Linux (64 bit) | Any | mysql replication hangs |
47135 | 2009-09-04 12:56 | 2011-02-16 23:44 | MySQL Server: Partitions | Closed (5393 days) | S3 | 5.4.2-beta | Other (Solaris + OS X, see text) | Any | Server crashes on "partition_alter2_1_innodb" + "partition_alter2_2_innodb" |
48192 | 2009-10-20 18:05 | 2013-04-14 20:45 | MySQL Server: InnoDB storage engine | No Feedback (5262 days) | S1 | 5.0.86-enterprise-nt-log | Windows (XP Pro and 2003 Server) | Any | MySQL Crash (InnoDB: We intentionally generate a memory trap.) |
75615 | 2015-01-24 5:51 | 2018-05-15 23:44 | Connector / J | Analyzing (2403 days) | S2 | Any | Any | Incorrect implementation of Connection.setNetworkTimeout() | |
76488 | 2015-03-25 22:09 | 2016-09-02 16:25 | MySQL Cluster: Cluster (NDB) storage engine | Verified (3273 days) | S2 | 7.4.5 | Linux (suse enterprise 11) | Any | stall when dropping table |
26134 | 2007-02-07 5:51 | 2016-01-03 20:45 | MySQL Server: InnoDB storage engine | No Feedback (6482 days) | S1 | 5.X | MacOS (MAC 10.X) | Any | DEADLOCK while inserting data on (AUTO_INCREMENT) |
115496 | 2024-07-03 8:18 | 2024-07-03 9:00 | MySQL Server: Locking | Unsupported (162 days) | S3 | 5.6.16, 5.6.51, 5.7.1 | Any | Any | UPDATE and INSERT...ON DUPLICATE KEY UPDATE... cause dead lock |
81071 | 2016-04-13 15:36 | 2021-11-05 16:20 | Connector / ODBC | Not a Bug (2669 days) | S2 | 5.7.11-log | Windows (2012) | Any | Query execution was interrupted, max_statement_time exceeded |
84816 | 2017-02-04 7:48 | 2017-03-08 1:00 | MySQL Server | No Feedback (2837 days) | S1 | 5.6.12-debug | CentOS (7) | Any | lock table write timeout cause server crash |
49976 | 2009-12-29 14:10 | 2021-05-02 20:45 | MySQL Cluster: Cluster (NDB) storage engine | Duplicate (5421 days) | S3 | mysql-5.1-telco-7.0 | Any | Any | ndb_mgm help was cleaned up too good. |
41124 | 2008-11-29 14:28 | 2011-02-16 23:43 | MySQL Server: Locking | Closed (5739 days) | S3 | 5.0, 5.1, 6.0 | Windows | Any | Server hangs on Windows with --external-locking after INSERT...SELECT |
89110 | 2018-01-04 17:15 | 2018-04-03 1:00 | MySQL Server: Documentation | No Feedback (2446 days) | S3 | MySQL 5.7 | CentOS | Any | Test result doesn't match the document |
50846 | 2010-02-02 18:44 | 2012-05-18 20:19 | MySQL Server: Backup | Patch queued (5419 days) | S3 | 5.4.4 | Any | Any | BACKPORT: Locking tests failing in pushbuild tree |
73988 | 2014-09-20 20:26 | 2014-10-30 18:11 | MySQL Server: DML | Closed (3696 days) | S3 | 5.7.6 | Any | Any | find_all_keys spams server error log with deadlock/lock wait errors |
68824 | 2013-04-01 14:20 | 2016-04-18 13:41 | MySQL Cluster: Cluster (NDB) storage engine | Closed (3160 days) | S2 | 5.5.29-7.2.10 | Linux (Centos 5.6) | Any | alter online table ... reorganize partition crashes NDB data node |
41667 | 2008-12-22 1:54 | 2008-12-22 5:09 | MySQL Server: Locking | Not a Bug (5834 days) | S3 | 5.0.67 | Windows (XP SP3) | Any | Lock wait timeout exceeded when updating a row in a reference table |
37992 | 2008-07-09 14:17 | 2011-02-16 23:43 | MySQL Server: InnoDB storage engine | Won't fix (5567 days) | S3 | 5.1.26-rc | HP/UX (11.31, 32 + 64 bit) | Any | Timeout for test "stress.ddl_innodb" on one platform, repeatable |
45299 | 2009-06-03 11:21 | 2012-05-18 20:19 | Tests: Server | Duplicate (5194 days) | S3 | 5.1.33, mysql-5.1-telco-7.0 | Solaris (Sparc) | Any | Test "partition_alter4_innodb" is taking too long, timeout |
110564 | 2023-03-30 9:09 | 2023-03-30 10:24 | Tests | Verified (623 days) | S3 | 8.0.32 | Any | Any | Router tests failing on macOS |
56832 | 2010-09-17 0:24 | 2011-02-16 23:44 | MySQL Server: Performance Schema | Closed (5184 days) | S3 | 5.5.6-m3-release | Any | Any | perfschema.server_init test output not consistent |
8324 | 2005-02-04 18:38 | 2005-02-14 13:57 | MySQL Cluster: Cluster (NDB) storage engine | Can't repeat (7241 days) | S3 | 4.1.9-max-log | HP/UX (HP-UX B.11.23 U ia64) | Any | AUTOCOMMIT=ON causes Lock wait timeout with small Cluster table |
29490 | 2007-07-02 15:42 | 2021-05-02 20:45 | MySQL Cluster: Cluster (NDB) storage engine | No Feedback (5807 days) | S1 | 5.0.44 | Linux | Any | Lock wait timeout error in NDB during concurrent SELECTs |
36859 | 2008-05-21 20:08 | 2012-06-10 20:31 | MySQL Server: Errors | Closed (4568 days) | S3 | 5.1.24-rc | Any | Any | The optimize api does not handle the HA_ERR_LOCK_WAIT_TIMEOUT error. |
39498 | 2008-09-17 13:49 | 2021-05-02 20:45 | MySQL Cluster: Cluster (NDB) storage engine | Verified | S2 | mysql-5.1-telco-6.3 | Any | Any | Doing INSERT INTO .. SELECT brings down all data nodes. |
41521 | 2008-12-16 21:05 | 2009-05-07 16:56 | MySQL Server: Falcon storage engine | Closed (5698 days) | S3 | mysql-6.0-falcon | Any | Any | falcon_bug_34174 fails with lock wait timeout, sometimes |
67947 | 2012-12-19 9:22 | 2015-04-24 10:46 | MySQL Server: InnoDB storage engine | Closed (4046 days) | S3 | 5.0,5.1,5.5, 5.7 | Linux | Any | continue handler not invoked in a stored function after a lock wait timeout |
68465 | 2013-02-22 18:57 | 2014-09-25 10:26 | MySQL Server: Documentation | Closed (4203 days) | S2 | 5.6.10 | Any | Any | Make slave_transaction_retries work with MTS |
114862 | 2024-05-03 4:42 | 2024-05-07 12:04 | MySQL Cluster: Cluster (NDB) storage engine | Not a Bug (219 days) | S2 | 8.0.35-cluster MySQL Cluster Community S | Any | Any | Scan error in NDB cluster |
32210 | 2007-11-09 3:30 | 2007-11-09 5:35 | MySQL Server: Locking | Not a Bug (6243 days) | S2 | 5.0.22 | Linux (CentOS 5.0 x86_64) | Any | Deadlock when inserting into an InnoDB table and select from it at the same time |
58892 | 2010-12-13 6:45 | 2010-12-13 7:52 | MySQL Server: Locking | Not a Bug (5113 days) | S2 | 5,1,47-x86-64 | Linux | Any | deadlock |
60332 | 2011-03-04 9:59 | 2011-03-04 22:52 | MySQL Server | Not a Bug (5032 days) | S2 | 5.1.53 | Linux | Any | Deadlock of innodb |
61502 | 2011-06-13 14:02 | 2011-08-04 21:32 | MySQL Server: Locking | Not a Bug (4879 days) | S2 | 5.5.10 | Any | Any | deadlock on insertion - insert holds and waits on same lock |
65531 | 2012-06-06 9:27 | 2013-01-29 18:37 | MySQL Server: InnoDB storage engine | Not a Bug (4335 days) | S2 | 5.5.16 | Any | Any | InnoDB DeadLock with all X mode waiting by various non-trans DML |
79617 | 2015-12-12 15:16 | 2019-12-12 20:36 | MySQL Server: Locking | Closed (1827 days) | S3 | 8.0.18 | Windows (10) | Any | Foreign key causing deadlock for UPDATE together with simple transaction |
94087 | 2019-01-28 5:33 | 2019-01-28 14:15 | MySQL Server | Not a Bug (2145 days) | S3 | 5.7.22 | Linux (CentOS release 6.10 (Final)) | x86 | Two updates with PRIMARY cause a deadlock |
103493 | 2021-04-27 5:49 | 2021-05-01 9:00 | MySQL Server: Locking | Not a Bug (1321 days) | S3 | 5.7.21 | Any | Any | Transactions deadlock detected, dumping detailed information |
104734 | 2021-08-26 8:51 | 2021-08-27 15:18 | MySQL Server | Unsupported (1203 days) | S2 | 5.7.33 | Other (LINUX AWS RDS x86_64) | x86 (AWS RDS Master-Slave set up) | Parallel one record update by unique key cause deadlock |
12049 | 2005-07-20 8:38 | 2008-05-11 6:35 | MySQL Server | No Feedback (6059 days) | S1 | 4.1.12, 5.0.9 | IBM AIX (AIX 5.2) | Any | MySQL hangs |
66402 | 2012-08-15 16:14 | 2014-04-01 1:00 | MySQL Server: InnoDB storage engine | No Feedback (3912 days) | S2 | 5.5.21-55-log Percona | Linux | Any | Thread locks itself out with semaphore (crash) |
33395 | 2007-12-20 9:24 | 2008-04-17 9:31 | MySQL Server: MyISAM storage engine | No Feedback (6083 days) | S1 | Ver 14.12 Distrib 5.0.51 | Linux (pc-linux-gnu (x86_64) ) | Any | [ERROR] /usr/sbin/mysqld: Incorrect key file for table '/tmp/#sql_77d3_0.MYI'; |
34567 | 2008-02-14 20:59 | 2008-10-09 11:39 | MySQL Server: Falcon storage engine | Closed (5908 days) | S3 | 6.0-falcon-team | Any | Any | Falcon deadlock between ALTERs of temporary and non-temporary tables |
49620 | 2009-12-11 12:21 | 2011-02-16 23:44 | MySQL Server: Replication | Can't repeat (5470 days) | S3 | 5.1.43, 5.1, next-mr bzr | Any | Any | Repl diff with concurrent transactions with trigger+savepoint+lock wait timeout |
13079 | 2005-09-09 1:18 | 2005-09-28 12:10 | MySQL Server | Can't repeat (7015 days) | S2 | 4.1.13 | Linux (Linux 2.6.12) | Any | NDB/cluster reports excessive wait lock timeouts on table operations |
39392 | 2008-09-11 12:58 | 2008-10-13 19:59 | MySQL Server: Maria storage engine | Closed (5904 days) | S3 | 5.1-maria | Linux | Any | Maria: if INSERT in UNIQUE finds uncommitted same key, error instead of wait |
42209 | 2009-01-20 8:30 | 2012-08-31 15:44 | MySQL Server: Optimizer | Closed (4486 days) | S3 | 5.1.30 | Any | Any | Rollback affects the index usage for DELETE statement with FORCE INDEX. |
9459 | 2005-03-29 16:55 | 2005-08-08 16:06 | MySQL Server | Closed (7066 days) | S3 | 4.1.10a | Any (*) | Any | deadlock with flush with lock, and lock table write |
30273 | 2007-08-07 12:48 | 2008-01-14 18:05 | MySQL Server: Merge storage engine | Closed (6177 days) | S2 | 5.0.48BK,5.1.22BK | Windows (XP) | Any | merge tables: Can't lock file (errno: 155) |
116254 | 2024-09-27 11:33 | 2024-09-27 12:19 | MySQL Server: Documentation | Not a Bug (76 days) | S3 | 8.4 | Any | Any | InnoDB Table lock descrition error |
49348 | 2009-12-02 13:10 | 2009-12-11 13:15 | MySQL Server: Backup | Won't fix (5480 days) | S2 | 6.0-backup | Any | Any | backup_wait_timeout behaves differently from the other timeouts |
50696 | 2010-01-28 18:41 | 2021-05-02 20:45 | MySQL Cluster: Cluster (NDB) storage engine | Verified (5100 days) | S1 | mysql-5.1-telco-7.0 | Linux (RHEL5.4) | Any | Switching from ndbd to ndbmtd causes file system error |
45279 | 2009-06-02 21:59 | 2011-02-16 23:44 | MySQL Server: InnoDB storage engine | No Feedback (5641 days) | S2 | MySQL-server-enterprise-5.0.54a-0.sles10 | Linux (SUSE Linux Enterprise Server 10 (x86_64) VERSION = 10) | Any | deadlock when inserting into auto increment table, not lock on auto-inc |
101907 | 2020-12-08 11:39 | 2021-02-12 1:00 | MySQL Server: Replication | No Feedback (1400 days) | S2 | 5.7 | Any | Any | Replication sql_thread hung while executing DML in init state |
34990 | 2008-03-03 1:41 | 2008-10-05 14:27 | MySQL Server: Falcon storage engine | Closed (5912 days) | S2 | 6.0.4 | Any | Any | Falcon: falcon_bug_34351_A & falcon_bug_34251_C fail periodically |
89101 | 2018-01-04 1:52 | 2020-03-30 12:12 | MySQL Server: DML | Verified (2520 days) | S2 | 5.7.20 | Any | Any | MySQL server hang when gtid_mode=on and innodb_thread_concurrency>0 |
95070 | 2019-04-20 14:07 | 2019-05-02 13:09 | MySQL Server | Not a Bug (2051 days) | S3 | 8.0.15 | Any | x86 | INSERT .. VALUES ( .., (SELECT ..), ..) takes shared lock with READ-COMMITTED |
68141 | 2013-01-22 13:16 | 2022-03-02 11:15 | Connector / J | Can't repeat (1016 days) | S2 | 5.1.22 | Any | Any | querytimeout does not work for loadbalanced and failover connections |
3003 | 2004-02-28 10:28 | 2020-03-09 14:06 | MySQL Server | Not a Bug (7591 days) | S1 | 4.1.1 | Linux (Linux 2.6.2) | Any | mysqld got signal 11 |
45082 | 2009-05-26 3:52 | 2009-06-16 8:10 | MySQL Server | Not a Bug (5658 days) | S2 | 5.0.41-log | Linux (Linux 2.6.18-8.1.15.el5 #1 SMP Mon Oct 22 08:32:28 EDT 2007 x86_64) | Any | mysql crash because of a long semaphore wait |
7975 | 2005-01-17 22:56 | 2005-04-18 10:22 | MySQL Server: InnoDB storage engine | Closed (7178 days) | S3 | 4.1.9, official 686 binary | Linux (debian amd64 pure64) | Any | deadlock without any locking, simple select and update |
40670 | 2008-11-12 15:11 | 2011-02-16 23:43 | MySQL Server: InnoDB storage engine | No Feedback (5842 days) | S1 | 5.1.29 | MacOS (10.5.3) | Any | Getting database deadlocks on simultaneous inserts |
51391 | 2010-02-22 15:06 | 2011-02-16 23:44 | MySQL Server: Locking | Closed (5332 days) | S2 | 5.5.3-m3 | Any | Any | Deadlock involving events during rqg_info_schema test |
96819 | 2019-09-10 10:37 | 2019-09-10 11:38 | MySQL Server: InnoDB storage engine | Not a Bug (1920 days) | S2 | 5.7 | Any | Any | Latching order violation during B-tree operations |
87302 | 2017-08-03 12:23 | 2017-08-04 10:29 | MySQL Server: InnoDB storage engine | Not a Bug (2687 days) | S2 | 5.6.32 | CentOS (2.6.32-279.el6.x86_64) | Any | Data load and index creation taking time |
28215 | 2007-05-03 8:24 | 2007-05-03 12:57 | MySQL Cluster: Cluster (NDB) storage engine | Can't repeat (6433 days) | S1 | 5.0.37 | Linux | Any | MySQL Cluster version 5.0.37 is unable to start due to file system incosistency |
56601 | 2010-09-06 19:06 | 2011-02-16 23:44 | Tests: Engine | Closed (5140 days) | S3 | 5.5.6-m3 | Windows | Any | Test uses Unix path for temporary file, fails, and writes misleading message |
114883 | 2024-05-05 8:54 | 2024-05-07 12:51 | MySQL Cluster: Cluster (NDB) storage engine | Not a Bug (219 days) | S2 | 8.0.35-cluster MySQL Cluster Community S | Any | Any | Scan error in NDB cluster |
47182 | 2009-09-07 20:01 | 2011-02-16 23:44 | MySQL Server: Embedded Library ( libmysqld ) | Verified | S3 | 5.4.2-beta | Linux (SuSE 9, x86, ) | Any | Timeouts in "embedded" test run happen specific to the SuSE 9 x86 RPM build |
43630 | 2009-03-13 11:31 | 2009-10-22 10:35 | MySQL Server: Falcon storage engine | Closed (5530 days) | S2 | falcon-team | Any | Any | A SELECT using ORDER BY and LIMIT sometimes returns no rows |
44783 | 2009-05-11 12:00 | 2012-05-18 20:19 | MySQL Server: Falcon storage engine | Duplicate (5628 days) | S3 | falcon-team | Any | Any | A SELECT using ORDER BY and LIMIT sometimes returns too many rows |
45086 | 2009-05-26 7:10 | 2021-05-23 20:45 | MySQL Server: Falcon storage engine | Duplicate (5628 days) | S3 | 6.0.11 | Any | Any | A SELECT using ORDER BY and LIMIT sometimes misses one row |
55309 | 2010-07-16 7:04 | 2015-01-09 14:45 | Tools: Random Query Generator | Won't fix (3625 days) | S2 | bzr-revno481 | Windows | Any | RQG: Out Of Memory issues on Windows with runall-new.pl |
59850 | 2011-01-31 15:22 | 2011-07-13 10:40 | MySQL Server: Locking | Can't repeat (4901 days) | S2 | mysql-trunk | Linux | Any | rqg_mdl_stability failing on mysql-trunk with a query delay |
52044 | 2010-03-14 8:59 | 2016-03-02 15:46 | MySQL Server: Locking | Closed (5096 days) | S3 | 5.5.3-m3 | Any | Any | FLUSH TABLES WITH READ LOCK and FLUSH TABLES <list> WITH READ LOCK are incompati |
54436 | 2010-06-11 16:55 | 2011-03-17 19:04 | MySQL Server: Locking | Won't fix (5019 days) | S3 | 5.1.38-bzr, mysql-trunk-runtime | Any | Any | Deadlock on concurrent FLUSH WITH READ LOCK, ALTER TABLE, ANALYZE TABLE |
76563 | 2015-04-01 15:26 | 2017-06-01 14:20 | MySQL Server: Documentation | Closed (2751 days) | S3 | 5.5, 5.6, 5.7 | Any | Any | Manual does NOT explain when exactly AUTO-INC lock is set for "bulk inserts" |
95572 | 2019-05-30 3:01 | 2020-01-20 9:47 | MySQL Server: Group Replication | Closed (1926 days) | S3 | 8.0.17 | Any | Any | Rollback of big transaction due to conflict remains in hung state |
45066 | 2009-05-25 12:21 | 2011-02-16 23:44 | MySQL Server: Locking | Closed (5394 days) | S3 | 5.1 | Any | Any | FLUSH TABLES WITH READ LOCK deadlocks against LOCK TABLE |
99206 | 2020-04-08 8:08 | 2020-04-09 13:06 | MySQL Server: Locking | Verified (1709 days) | S3 | 5.7.29 | Any | Any | lock_wait_timeout is taking twice time while adding new partition in table |
27897 | 2007-04-17 18:56 | 2014-03-31 12:38 | Connector / J | Can't repeat (3909 days) | S1 | 5.0.37-community | Windows (xp) | Any | dead lock , affter delete data ,execute insert data |
40621 | 2008-11-10 20:07 | 2010-07-20 12:55 | MySQL Server: InnoDB storage engine | Not a Bug (5259 days) | S1 | 5.0.67_1 | FreeBSD (6.2-RELEASE kernel) | Any | Innodb file locking error on startup |
32149 | 2007-11-06 18:29 | 2011-02-16 23:43 | MySQL Server: Locking | Closed (5648 days) | S2 | 5.0 | Any | Any | Long semaphore wait for adaptive hash latch |
90863 | 2018-05-14 14:36 | 2018-05-14 15:12 | MySQL Server | Can't repeat (2404 days) | S2 | 5.6.36 | CentOS | Any | SEMAPHORE wait between trx0rseg.ic line 46 and reader buf0flu.cc line 1078 |
43002 | 2009-02-19 7:39 | 2013-07-04 13:10 | MySQL Server: Maria storage engine | Won't fix (4179 days) | S3 | 6.0-TRUNK | Any | Any | maria.maria_notembedded fails sporadically |
95223 | 2019-05-02 12:57 | 2019-07-17 12:23 | MySQL Server: Locking | Closed (1976 days) | S3 | 8.0.15 | Any | Any | Locking loop between LOCK_event_queue and event MDL lock |
109834 | 2023-01-30 6:54 | 2023-02-28 17:13 | Shell AdminAPI InnoDB Cluster / ReplicaSet | Can't repeat (653 days) | S3 | Linux | Any | Metadata is wrong after failure to invoke set_primary_instance | |
28004 | 2007-04-21 19:42 | 2007-04-23 1:24 | MySQL Server: InnoDB storage engine | Closed (6443 days) | S3 | 5.0.27 | Windows | Any | Using transaction in C# lock time out problem |
86790 | 2017-06-22 9:18 | 2017-06-22 10:34 | MySQL Server: Locking | Verified (2730 days) | S2 | 5.7.18 | Any | Any | FTWRL continues to freeze the server even if it times out ... |
104054 | 2021-06-18 7:47 | 2022-11-30 13:32 | MySQL Server: Partitions | Not a Bug (1267 days) | S3 | 8.0 | CentOS (centos 7.0) | x86 | Unnecessary next-key lock for partition table |
29441 | 2007-06-29 10:31 | 2007-07-10 13:31 | MySQL Cluster: Cluster (NDB) storage engine | Not a Bug (6365 days) | S3 | 5.1.16 | Linux (Locking Error on contineous insertions) | Any | Locking error |
51966 | 2010-03-11 19:08 | 2011-02-16 23:44 | MySQL Server: Locking | No Feedback (5356 days) | S3 | 5.1.40-community | Any | Any | INSERT ... SELECT should allow concurrent inserts when binary log is disabled. |
88658 | 2017-11-26 7:56 | 2017-12-27 1:00 | MySQL Server: InnoDB storage engine | No Feedback (2543 days) | S3 | 5.7.14 | Red Hat (7.2) | Any | The mysql hang when session insert,the disk util is 100% |
54538 | 2010-06-16 1:23 | 2011-02-16 23:44 | MySQL Server: InnoDB Plugin storage engine | Closed (5112 days) | S3 | 5.1.47 | Any | Any | use of exclusive innodb dictionary lock limits performance |
42474 | 2009-01-30 12:40 | 2012-05-18 20:19 | MySQL Cluster: Cluster (NDB) storage engine | Duplicate (5777 days) | S1 | 6.4.2 | Solaris | Any | Requests blocked in MySQL Cluster |
31907 | 2007-10-29 10:38 | 2016-01-03 20:45 | MySQL Server: InnoDB storage engine | Duplicate (6254 days) | S2 | 5.0.42 | Solaris (Solaris 10 U4 patch 120012-14) | Any | excessive innodb lock waiting, server crashes |
81229 | 2016-04-29 7:50 | 2016-05-23 23:38 | MySQL Cluster: NDB API | Closed (3138 days) | S3 | 7.3 | Any | Any | Client performance trashed due to threads woken up too early |
12529 | 2005-08-11 16:00 | 2005-10-03 8:11 | MySQL Server | Closed (7010 days) | S2 | 5.0.11 | several Unix | Any | yassl changes connect behaviour / error message |
24243 | 2006-11-13 8:51 | 2006-11-15 18:57 | MySQL Server: Documentation | Closed (6602 days) | S1 | MySQL 5.0.27, 4.0.27 | FreeBSD (FreeBSD 6.2 , Linux 2.6 kernel) | Any | max_questions resourse limit does not have effect on "select * from tbl_name" |
37607 | 2008-06-24 13:21 | 2021-05-02 20:45 | MySQL Cluster: Cluster (NDB) storage engine | No Feedback (5863 days) | S1 | mysql-5.1.23 ndb-6.2.15 | Other (CentOS release 5 (Final)) | Any | MySQL CLuster (mysql-5.1.23 ndb-6.2.15) not Starting on CentOS 5 |
113665 | 2024-01-17 14:06 | 2024-10-17 12:59 | MySQL Server: Tests | Verified (56 days) | S3 | 8.0.40, 8.4.3, 9.1.0 | MacOS (12.4.1) | ARM | perfschema.relaylog fails with a result difference |
32057 | 2007-11-02 16:48 | 2008-07-07 15:25 | Connector / ODBC | Closed (6002 days) | S1 | 3.51.21 and 5.1 | MacOS (Mac OS X 10.4 Intel and 10.5 Intel) | Any | MySQL ODBC 3.51 Driver crashes ODBC Administrator |
22475 | 2006-09-19 13:21 | 2013-10-06 20:45 | MySQL Cluster: Cluster (NDB) storage engine | No Feedback (6621 days) | S1 | 5.1.11 | Linux (Linux) | Any | ndbd hangs in phase 4 |
94881 | 2019-04-03 4:37 | 2019-04-23 12:34 | MySQL Server: InnoDB storage engine | Closed (2072 days) | S3 | 5.7.20 | Any | Any | slave replication lock wait timeout because of supremum record |
87747 | 2017-09-13 9:27 | 2017-09-28 4:24 | MySQL Server | Can't repeat (2632 days) | S2 | mysql5.7.19 | Any | Any | Open parallel copy, press a lot of transactions, the slave's SQL thread stuck |
116598 | 2024-11-08 9:44 | 2024-11-11 10:08 | MySQL Server: InnoDB storage engine | Can't repeat (33 days) | S3 | Any | Any | MDL deadlock occurs due to the order of the view filed | |
32157 | 2007-11-07 5:32 | 2016-01-03 20:45 | MySQL Server: InnoDB storage engine | Duplicate (6242 days) | S3 | 5.0.37 | Linux | Any | Crash from a long semaphore wait on Innodb checkpoint lock |
33819 | 2008-01-11 13:00 | 2021-05-02 20:45 | MySQL Cluster: Cluster (NDB) storage engine | Verified (3983 days) | S3 | mysql-5.0 | Linux | Any | single PK-only query transactiosn fail with deadlock timeout on BLOB tables |
50723 | 2010-01-29 10:01 | 2012-05-15 21:43 | MySQL Server: InnoDB storage engine | Closed (4594 days) | S1 | 5.0, 5.1 | Any | Any | InnoDB CHECK TABLE fatal semaphore wait timeout possibly too short for big table |
16898 | 2006-01-30 12:20 | 2006-04-12 10:48 | MySQL Server | Can't repeat (6819 days) | S3 | 4.1.18 | MacOS (OS X 10.4, 32 bit) | Any | Problems with character set and table file names |
63203 | 2011-11-11 10:20 | 2013-12-30 4:41 | MySQL Server: Locking | Closed (4000 days) | S2 | 5.1.61, 5.5 | Any | Any | Possible deadlock due to lock order violation |
80481 | 2016-02-23 14:02 | 2016-06-18 21:36 | MySQL Server: DDL | Closed (3213 days) | S3 | 8.0.0-git | Any | Any | Accesses to new data-dictionary add confusing stages to P_S.EVENTS_STAGES_*. |
9045 | 2005-03-08 10:09 | 2014-03-13 13:33 | MySQL Cluster: Cluster (NDB) storage engine | Won't fix (7219 days) | S3 | Any | Any | Lock wait timeout when using table with TEXT column | |
44581 | 2009-04-30 16:44 | 2011-02-16 23:43 | MySQL Server: Replication | Closed (5635 days) | S2 | 5.1.34 and 5.4.0 | Any | Any | Slave stops when transaction with non-transactional table gets lock wait timeout |
37346 | 2008-06-11 14:35 | 2011-02-16 23:43 | MySQL Server: Locking | Closed (5394 days) | S3 | 5.0,5.1 | Any | Any | innodb does not detect deadlock between update and alter table |
87796 | 2017-09-19 5:11 | 2021-09-01 13:10 | MySQL Server: Replication | Closed (1473 days) | S1 | 5.7.19 | Linux (Linux localhost 3.10.0-327.28.2.el7.x86_64 #1 SMP Wed Aug 3 11:11:39 UTC 2016 x) | Any | Commit_order_manager can't terminate MTS worker properly when deadlock happens |
84792 | 2017-02-02 12:49 | 2017-05-03 13:18 | MySQL Server: Group Replication | Can't repeat (2780 days) | S3 | 5.7.17 | Any | Any | Idle GR Cluster: Member CPU hog |
104982 | 2021-09-18 8:02 | 2021-09-18 8:04 | MySQL Server | Closed (1181 days) | S2 | 8.0.19 | Any | Any | long wait for log_wait_for_flush |
56529 | 2010-09-03 9:22 | 2011-02-16 23:44 | MySQL Server: Optimizer | Closed (5115 days) | S1 | bzr_mysql-next-mr-opt-backporting | Any | Any | Crash due to long semaphore wait in InnoDB with ICP and subqueries |
4852 | 2004-08-02 7:04 | 2008-09-29 22:33 | MySQL Server: InnoDB storage engine | Can't repeat (5918 days) | S3 | 4.0.21-nightly-20040729-Max-log | Linux (Linux RHEL AS 3.0) | Any | lock tables ... write still works wrong |
9265 | 2005-03-18 6:37 | 2005-07-02 14:54 | MySQL Server | Not a Bug (7103 days) | S1 | 14.1.14 | Linux (linux) | Any | mysql cluster "Lock" |
11966 | 2005-07-15 12:01 | 2005-09-11 11:00 | MySQL Server | Not a Bug (7032 days) | S3 | HP/UX (HP-UX 11.i) | Any | MySQL throws native error code : 1205 , | |
37994 | 2008-07-09 14:46 | 2011-02-16 23:43 | MySQL Server: InnoDB storage engine | No Feedback (5801 days) | S2 | 5.0.51a-community | Any (seen on windows server 2003 and linux) | Any | InnoDb waits for lock when DELETE from a table previously in a interrupted trans |
65983 | 2012-07-23 10:41 | 2012-08-24 1:00 | MySQL Server: DML | No Feedback (4494 days) | S2 | 5.1.40 | Linux | Any | a executing subquery , never stop |
68537 | 2013-03-01 10:37 | 2016-07-18 15:57 | MySQL Cluster: Cluster (NDB) storage engine | Closed (3069 days) | S2 | mysql-5.5.25 ndb-7.2.7 | Linux (Red Hat 6.3) | Any | error 2341: 'Internal program error' on production environment. Nodes shutdown. |
75104 | 2014-12-04 12:20 | 2015-01-05 1:00 | MySQL Server: Federated storage engine | No Feedback (3630 days) | S2 | 5.5.14 | Any | Any | Lock timout error on federated table update |
40206 | 2008-10-21 12:12 | 2012-05-18 20:19 | MySQL Server: Embedded Library ( libmysqld ) | In progress (5862 days) | S2 | 5.1.30, 6.0.8-alpha | Linux (PPC) | Any | Timeout in "embedded" tests |
56806 | 2010-09-15 19:32 | 2012-09-13 14:08 | Connector / NET | Closed (5174 days) | S2 | 6.3.4 | Windows | Any | Default Command Timeout has no effect in connection string |
85978 | 2017-04-18 2:55 | 2022-08-10 17:32 | Connector / NET | Can't repeat (855 days) | S2 | 6.9.9 | Windows | Any | UPDATE Timeout then ExecuteReader returns null |
89076 | 2017-12-29 7:39 | 2021-01-11 9:56 | Connector / NET | Verified (2516 days) | S1 | 5.7.19 | Linux (AWS RDS) | Any | Application has timeout exception,Still find queries getting executed on backend |
37391 | 2008-06-13 9:59 | 2008-06-13 10:51 | MySQL Server: InnoDB storage engine | Not a Bug (6026 days) | S3 | 5.0.51a | Linux (2.4 kernel) | Any | mysqld should not log scary warning messages when adjusting innodb logfile sizes |
37080 | 2008-05-29 21:59 | 2009-01-08 10:32 | MySQL Server: Falcon storage engine | Closed (5817 days) | S3 | mysql-6.0-falcon-team | Any | Any | Falcon deadlock on concurrent insert and truncate |
83079 | 2016-09-21 13:16 | 2019-01-10 14:59 | MySQL Server: InnoDB storage engine | Closed (2789 days) | S2 | 5.7 | Any | Any | long semaphore wait often resulting in crash, DICT_SYS mutex held by statistics |
72520 | 2014-05-03 4:53 | 2016-04-08 9:05 | MySQL Server: InnoDB storage engine | Verified (3874 days) | S3 | 5.5, 5.6, 5.7 | Any | Any | os_event_wait_time_low(): wait time calculation is messed up |
71053 | 2013-12-02 22:41 | 2014-01-04 1:00 | MySQL Server | No Feedback (3996 days) | S3 | 5.5.32 | Linux | Any | Lock wait timeout where there should be none |
51920 | 2010-03-10 16:14 | 2011-02-16 23:44 | MySQL Server: InnoDB storage engine | Closed (5279 days) | S3 | 5.0.84, 5.1.45, 5.5 | Any | Any | Innodb connections in row lock wait ignore KILL until lock wait timeout |
39694 | 2008-09-27 14:53 | 2008-12-13 9:03 | MySQL Server: Falcon storage engine | Closed (5843 days) | S1 | 6.0-falcon-team (6.0.8a) | Any | Any | Crash in StorageTable::setRecord during falcon_chill_thaw test |
39695 | 2008-09-27 15:14 | 2008-12-13 9:03 | MySQL Server: Falcon storage engine | Closed (5843 days) | S1 | 6.0-falcon-team (6.0.8a) | Linux | Any | Crash in SRLUpdateRecords::thaw during falcon_chill_thaw test |
39696 | 2008-09-27 15:53 | 2008-12-13 9:05 | MySQL Server: Falcon storage engine | Closed (5843 days) | S1 | 6.0-falcon-team (6.0.8a) | Windows (Version 6.0.6001, Visual Studio 2008) | Any | Assertion in Table.cpp (dup->state == recDeleted) fails during falcon_chill_thaw |
89247 | 2018-01-15 14:39 | 2021-09-01 13:10 | MySQL Server: Replication | Duplicate (1198 days) | S2 | 8.0.3, 5.7.20 | Any | Any | Deadlock with MTS when slave_preserve_commit_order = ON. |
60425 | 2011-03-11 2:58 | 2012-01-19 18:46 | MySQL Server: Replication | Not a Bug (4711 days) | S3 | mysql5.5 | Any | Any | The rpl_semi_sync_master_wait_no_slave variable is invalid |
72164 | 2014-03-30 17:13 | 2014-04-02 20:34 | MySQL Cluster: Cluster (NDB) storage engine | Duplicate (3907 days) | S2 | ndb-7.2.12 | Linux | Any | Job buffer full - data nodes crash |
59047 | 2010-12-19 22:02 | 2011-08-12 21:26 | MySQL Server: InnoDB storage engine | Not a Bug (4871 days) | S1 | 5.0.91-community-log | Linux (2.6.18-194.3.1.el5 x86_64) | Any | Crash due to long semaphore wait |
84004 | 2016-11-29 13:19 | 2018-06-07 14:09 | MySQL Server: Documentation | Closed (2380 days) | S3 | 5.6+ | Any | Any | Manual misses details on MDL locks set and released for online ALTER TABLE |
91515 | 2018-07-02 7:59 | 2018-08-04 1:00 | MySQL Server | No Feedback (2323 days) | S3 | 5.7.22 | CentOS | Any | semaphore wait has lasted > 600 seconds,can't logging, |
45978 | 2009-07-06 18:42 | 2011-02-16 23:44 | Connector / NET | Closed (5362 days) | S2 | 5.1.36 | Windows | Any | Silent problem when net_write_timeout is exceeded |
90631 | 2018-04-25 12:57 | 2018-04-25 15:14 | MySQL Server: Performance Schema | Verified (2423 days) | S3 | 8.0.11 | Ubuntu (14.04) | x86 | perfschema.statement_digest_query_sample test fails sporadically |
46114 | 2009-07-10 15:33 | 2011-02-16 23:44 | MySQL Cluster: Cluster (NDB) storage engine | Closed (5396 days) | S3 | mysql-5.1-telco-7.0 | Any | Any | ndb_mgm "help" does not show help for all commands |
46145 | 2009-07-13 12:56 | 2021-05-02 20:45 | MySQL Cluster: Cluster (NDB) storage engine | Duplicate (5596 days) | S3 | 7.0.6 | Solaris (10/x86_64) | Any | Broken HELP text in ndb_mgm |
101200 | 2020-10-16 3:25 | 2020-10-17 1:19 | MySQL Server: InnoDB storage engine | Verified (1518 days) | S5 | 8.0 | Any | Any | All commits are unnecessarily blocked for more than 1ms at binlog rotate |
66295 | 2012-08-10 2:41 | 2019-08-14 19:23 | MySQL Cluster: NDB API | Closed (1947 days) | S1 | mysql-5.1.56 ndb-7.1.15 | Linux (2.6.16.60-0.21-smp - x86_64 x86_64 x86_64 GNU/Linux) | Any | mysql cluster environment (mysql-5.1.56 ndb-7.1.15) date node often shutdown and |
97668 | 2019-11-17 6:13 | 2019-11-19 13:42 | MySQL Cluster: Cluster (NDB) storage engine | Can't repeat (1850 days) | S1 | mysql-5.7.23 ndb-7.6.12 | CentOS | Any | (urgent) Cluster crashed after alter table |
37141 | 2008-06-02 17:01 | 2008-10-16 15:56 | MySQL Server: Documentation | Closed (5901 days) | S3 | 5.1.24-rc-community-log | Any | Any | Doc page does not account for consequences of FLUSH TABLES WITH READ LOCK |
40892 | 2008-11-20 16:10 | 2009-01-08 10:38 | MySQL Server: Maria storage engine | Closed (5817 days) | S1 | 6.0.8-release | Any | Any | maria: Livelock in sysbench OLTP_RW test |
54603 | 2010-06-18 3:57 | 2021-05-02 20:45 | MySQL Cluster: Cluster (NDB) storage engine | No Feedback (5258 days) | S2 | mysql-5.1-telco-7.0 | Other (centos 5.2 x86_64) | Any | no storage nodes connected (timed out) |
39749 | 2008-09-30 6:37 | 2011-02-16 23:43 | Tests: Server | Closed (5792 days) | S3 | 6.0-TRUNK | MacOS (powermacg5) | Any | main.backup_timeout fails sporadically on OS X |
55621 | 2010-07-29 7:59 | 2010-07-29 11:18 | MySQL Server | Not a Bug (5250 days) | S3 | 5.1.45 | Linux (ubuntu 9.04) | Any | MySQL Server STARTS AND sTOPs Immediately |
3153 | 2004-03-12 4:58 | 2004-03-21 23:09 | MySQL Server: InnoDB storage engine | Can't repeat (7571 days) | S2 | 4.0.16 | HP/UX (HPUX11.11) | Any | bad result set data with "SELECT...FOR UPDATE" |
11015 | 2005-06-01 12:03 | 2005-07-03 11:31 | MySQL Cluster: Cluster (NDB) storage engine | No Feedback (7102 days) | S1 | 4.1.11 | Linux (Linux) | Any | massive concurrent inserts cause error or server crash |
11360 | 2005-06-15 19:57 | 2014-03-31 9:23 | Connector / J | Can't repeat (3909 days) | S3 | 3.1.8 | Windows (Windows XP) | Any | Connector/J dumping query into SQLException twice |
18856 | 2006-04-06 17:05 | 2007-08-21 19:50 | MySQL Cluster: Cluster (NDB) storage engine | Closed (6323 days) | S2 | 5.1 | Linux (Linux) | Any | Table remains locked after SELECT * INTO OUTFILE statment. |
21396 | 2006-08-01 17:04 | 2006-08-15 3:15 | MySQL Server: General | Closed (6694 days) | S1 | 5.0.24 | Windows (Windows 2003 AMD64) | Any | Wrong error number generated for a missing table: 1017 vs 1146 |
23456 | 2006-10-19 8:39 | 2006-10-19 10:28 | MySQL Server | Not a Bug (6629 days) | S2 | cluster 5.0.22 | Solaris (solaris 9) | Any | ODBC Error (S1T00,4B5) |
29386 | 2007-06-27 12:42 | 2012-05-18 20:19 | MySQL Cluster: Cluster (NDB) storage engine | No Feedback (6131 days) | S3 | 5.1.16 | Linux (Cluster failure on contineous insertion) | Any | Cluster failure on contineous insertion |
29452 | 2007-06-29 21:13 | 2007-12-03 13:14 | MySQL Server: Falcon storage engine | Closed (6219 days) | S3 | 6.0.1-alpha-debug | Linux (SUSE 10 64-bit) | Any | Falcon: two-way deadlock with unique index and trigger |
29828 | 2007-07-16 15:28 | 2015-03-15 20:45 | MySQL Server: Replication | Duplicate (5997 days) | S3 | 5.2.4-alpha | HP/UX (11.11 32 bit) | Any | Test 'rpl_locktrans_innodb' failed on HP-UX 11.11 32 bit |
38088 | 2008-07-13 16:03 | 2021-05-02 20:45 | MySQL Cluster: Cluster (NDB) storage engine | No Feedback (5754 days) | S3 | 6.0 | Any | Any | rpl_row_basic_7ndb failed At line 55 INSERT INTO t2 ... |
39705 | 2008-09-28 4:24 | 2011-05-12 10:52 | Tests | Duplicate (4963 days) | S3 | 6.0, 6.0-falcon, 5.1 | Any | Any | read_many_rows_innodb fails |
47245 | 2009-09-10 10:41 | 2021-05-02 20:45 | Tests: Cluster | Verified | S3 | 5.1 | Any | Any | rpl_ndb.rpl_ndb_2other fails on PB2. |
55911 | 2010-08-11 13:01 | 2021-05-02 20:45 | MySQL Cluster: Cluster (NDB) storage engine | Verified (5236 days) | S2 | mysql-5.1-telco-7.0 | Linux (Red Hat 3.4.6-8) | Any | Error updating primary key on more than one entry |
74614 | 2014-10-29 9:15 | 2015-07-14 14:07 | MySQL Server: Performance Schema | Closed (3439 days) | S3 | 5.6.16, 5.6.22, 5.7.7 | Any | Any | events_statements_history has errors=0 when there are errors |
78302 | 2015-09-02 8:40 | 2016-06-18 21:27 | MySQL Server: InnoDB storage engine | Not a Bug (3221 days) | S3 | 8.0 | Linux | Any | main.status fails on Linux environment for valgrind runs |
83900 | 2016-11-21 8:04 | 2019-10-20 10:08 | MySQL Server: Replication | Verified (2694 days) | S1 | 5.7.12-log | CentOS (6.5) | Any | mysql server is crashed by binlog dump thread |
93365 | 2018-11-27 14:39 | 2023-01-09 12:36 | MySQL Server: Performance Schema | Duplicate (706 days) | S2 | 8.0.12 | Any | Any | Query on performance_schema.data_locks causes replication issues |
95064 | 2019-04-19 11:05 | 2021-04-27 20:23 | MySQL Server: Replication | Verified (2064 days) | S2 | 5.7.22 | Any | x86 | slave server may has gaps in Executed_Gtid_Set when a special case happen |
100242 | 2020-07-17 5:48 | 2020-08-12 16:52 | MySQL Server | Can't repeat (1583 days) | S3 | 8.0.18 | Linux | Any | Upgrade from MySQL 8.0.16 to MySQL 8.0.18 failed |
111703 | 2023-07-10 6:40 | 2023-07-15 1:58 | MySQL Server: Documentation | Not a Bug (516 days) | S3 | 8.0.33, 5.7.42 | Any | Any | INSERT ON DUPLICATE KEY locks INSERT if table have many PRIMARY and UNIQUE key |
30661 | 2007-08-28 2:05 | 2007-08-28 16:06 | MySQL Enterprise Monitor: Server | Not a Bug (6316 days) | S2 | 1.2.0.7296 | Any | Any | Purging data can cause deadlocks |
65890 | 2012-07-13 9:17 | 2015-12-12 23:23 | MySQL Server: Documentation | Closed (3288 days) | S2 | 5.5.X | Linux (CentOS 6.X) | Any | Deadlock that is not a deadlock with transaction and lock tables |
46664 | 2009-08-12 3:10 | 2011-02-16 23:44 | MySQL Server: Locking | Closed (5539 days) | S3 | 5.4.4-alpha | Any | Any | NOWAIT in SHARE mode causes immediate timeout although the table is not locked |
50821 | 2010-02-02 9:59 | 2011-02-16 23:44 | MySQL Server: Locking | Closed (5394 days) | S1 | mysql-next-4284 | Any | Any | Deadlock between LOCK TABLES and ALTER TABLE |
89205 | 2018-01-12 10:13 | 2018-05-03 5:21 | MySQL Server: InnoDB storage engine | Closed (2415 days) | S3 | 5.7.20 | Any | Any | gap locks on READ COMMITTED cause by page split |
25913 | 2007-01-29 12:40 | 2012-05-18 20:19 | MySQL Cluster: Cluster (NDB) storage engine | Duplicate (6426 days) | S2 | 5.1.16-beta | Linux (SuSE 11, x64) | Any | rpl_ndb_dd_advance fails randomly |
8653 | 2005-02-21 16:33 | 2005-04-06 15:09 | MySQL Server | Closed (7190 days) | S1 | Any | 5.0.3 leaves an InnoDB trx open after connection ends; InnoDB shutdown hangs | ||
86116 | 2017-04-27 16:19 | 2017-04-27 18:51 | MySQL Server | Duplicate (2786 days) | S1 | 5.7.16 | Windows (Windows 2012) | Any | [ERROR] [FATAL] InnoDB: Semaphore wait has lasted > 600 seconds. |
99230 | 2020-04-10 14:04 | 2020-04-13 12:28 | MySQL Server: InnoDB storage engine | Not a Bug (1704 days) | S2 | 5.7 | Any | Any | The thread srv_error_monitor_thread hangs. |
103153 | 2021-03-30 16:08 | 2021-04-02 12:01 | MySQL Server: Locking | Not a Bug (1352 days) | S3 | 5.7, 8.0 | Any | Any | ALTER with LOCK=NONE blocks SELECTs |
35632 | 2008-03-28 8:16 | 2016-10-16 20:45 | MySQL Server: Replication | Verified (6097 days) | S1 | 5.1 | Any | Any | server can deadlock with three parallel xa transactions |
77872 | 2015-07-29 14:17 | 2018-08-27 12:02 | MySQL Server | Can't repeat (2299 days) | S3 | 5.7.7 | Linux | Any | possible three way lock deadlock |
97230 | 2019-10-15 10:44 | 2019-10-15 14:06 | MySQL Server: InnoDB storage engine | Verified (1885 days) | S5 | 8.0 | Any | ARM | rwlock: refine lock->waiters with C++11 atomics |
57652 | 2010-10-22 7:58 | 2011-02-16 23:44 | MySQL Server: InnoDB storage engine | No Feedback (5125 days) | S2 | 5.1.37 | Linux | Any | InnoDB memory crash when restarting... sometimes... |
61186 | 2011-05-16 11:09 | 2012-05-27 1:00 | MySQL Server: Locking | No Feedback (4583 days) | S2 | 5.5.11, 5.5.15 | Linux | Any | MYSQL_BIN_LOG::new_file_impl cant create new bin-log file |
92975 | 2018-10-27 1:04 | 2020-12-10 11:47 | MySQL Server: Replication | No Feedback (1788 days) | S2 | 5.7.19, 5.7.21 | Any | Any | SQL thread stuck in init state waiting for asynchronous rollback to complete |
40113 | 2008-10-17 15:51 | 2011-02-16 23:43 | MySQL Server: Locking | Closed (5606 days) | S2 | 5.0, 5.1, 6.0 bzr | Any (Linux, Win XP SP2 32bit) | Any | Embedded SELECT inside UPDATE or DELETE can timeout without error |
12125 | 2005-07-22 22:59 | 2005-07-26 21:40 | MySQL Server: InnoDB storage engine | Closed (7079 days) | S1 | 4.1.13 | MacOS (OS X 10.4.2) | Any | Massive Disk I/O Degradation under 4.1.13 in OS X |
48240 | 2009-10-22 18:51 | 2011-02-16 23:44 | Tools: MTR / mysql-test-run | Closed (5292 days) | S3 | Any | Any | Any | "Test suite timeout" and "Too many tests failed" is masked from status page |
48272 | 2009-10-23 18:12 | 2011-02-16 23:44 | Tests: Server | Won't fix (5124 days) | S3 | IBM i (32 bit only) | Any | Timeout for test "stress.ddl_myisam" on one platform, repeatable | |
106751 | 2022-03-16 17:25 | 2024-02-21 16:37 | MySQL Cluster: Cluster (NDB) storage engine | Closed (295 days) | S3 | 8.0.28 | Any | Any | Connect timeout too long towards MGMD nodes |
51193 | 2010-02-15 16:45 | 2015-02-04 22:35 | MySQL Server: Documentation | Closed (3599 days) | S3 | 5.1 | Any | Any | Update 1.8.5.2 Transactions and Atomic Operations in the reference manual |
57170 | 2010-10-01 13:32 | 2011-04-04 19:11 | MySQL Server: Locking | Won't fix (5001 days) | S3 | mysql-next-mr-wl3561 | Any | Any | NOWAIT clause can be ignored (expected an error) |
57474 | 2010-10-15 7:46 | 2014-09-26 13:08 | MySQL Server: Locking | Closed (3733 days) | S3 | 5.5.7-bzr,5.6.2m5 | Any | Any | Deadlock when DDL under LOCK TABLES WRITE, READ + PREPARE. |
75736 | 2015-02-03 2:07 | 2015-04-24 12:40 | MySQL Server: DML | Closed (3520 days) | S1 | 5.7.5-m15, 5.7.6 | Any | Any | DEADLOCK of threads detected! 5.7.5, 1 thread SQL testcase, sporadic, in ib_logf |
35291 | 2008-03-14 12:55 | 2016-01-03 20:45 | MySQL Server: InnoDB storage engine | No Feedback (6000 days) | S1 | mysql Ver 14.12 Distrib 5.0.41, for pc- | Linux (Linux mysql1 2.6.21-ARCH #1 SMP PREEMPT) | Any | InnoDB crashes with Mutex at 0xb79c20b4 created file log0log.c line 744, lock va |
79424 | 2015-11-26 14:22 | 2019-05-15 13:28 | MySQL Server | Not a Bug (2038 days) | S2 | 5.7.9 | Windows | Any | lock wait taken as io wait when using performance schema |
89715 | 2018-02-19 10:58 | 2018-02-19 14:31 | MySQL Server | Can't repeat (2488 days) | S2 | 5.5.41 | Red Hat ( Red Hat Enterprise Linux Server release 6.6 (Santiago)) | x86 (Intel(R) Xeon(R) CPU E7- 4830 @ 2.13GHz) | Thread is waiting for itself at btr0sea.c |
94930 | 2019-04-08 2:38 | 2019-04-08 8:09 | MySQL Server | Duplicate (2075 days) | S3 | 5.7.20-log | CentOS (6.7) | x86 (x86-64bit) | InnoDB: Semaphore wait has lasted > 600 seconds.Instance Hung |
100768 | 2020-09-08 11:40 | 2020-09-08 18:57 | MySQL Server: InnoDB storage engine | Can't repeat (1556 days) | S2 | CentOS (version 8) | Any | MySQL Server 8 is crashed and rebooted automatically with a long semaphore wait | |
50517 | 2010-01-21 17:39 | 2010-03-02 1:44 | MySQL Server: Backup | Closed (5399 days) | S2 | 6.0.14-alpha | Any | Any | mysqldump.test sometimes times out |
47298 | 2009-09-14 3:29 | 2011-02-16 23:44 | MySQL Server: Replication | Closed (5509 days) | S3 | 5.4 | Any | Any | Semisync: always wait until timeout if no semi-sync slave available |
40808 | 2008-11-18 1:48 | 2009-02-02 17:23 | MySQL Server: Backup | Closed (5792 days) | S3 | 6.0, 6.0-falcon tree | MacOS (powermacg5) | Any | The backup_wait_timeout variable is not working on powermac platform |
70183 | 2013-08-29 12:43 | 2014-08-22 1:00 | MySQL Server: InnoDB storage engine | No Feedback (3766 days) | S1 | 5.5.30 | Linux (rhel 5.3 (2.6.18-348.6.1.el5)) | Any | Error: semaphore wait has lasted > 600 seconds ( InnoDB: Assertion failure) |
54767 | 2010-06-24 10:35 | 2011-02-16 23:44 | MySQL Server: Documentation | Closed (5284 days) | S3 | 5.5.4-m3 | Any | Any | Please document the effect of metadata locks taken by failing statements |
34627 | 2008-02-17 16:21 | 2008-05-21 14:10 | MySQL Server: Falcon storage engine | Closed (6049 days) | S3 | 6.0.4 | Any | Any | Falcon potential deadlock in Bdb::addRef |
13957 | 2005-10-12 9:41 | 2005-11-22 9:39 | MySQL Server: Compiling | Closed (6960 days) | S1 | Any | yassl: opensrv6c compile failure | ||
15791 | 2005-12-15 21:26 | 2006-03-08 7:56 | MySQL Server | No Feedback (6854 days) | S2 | 4.1.12 | Linux (Linux) | Any | can't get requested lock after starting alter table disable keys |
17578 | 2006-02-20 12:03 | 2006-03-28 12:09 | MySQL Server: Stored Routines | Closed (6834 days) | S3 | 5.1.7-beta | some Unix | Any | Test "events" fails due to scheduling difference |
35935 | 2008-04-09 12:37 | 2011-02-16 23:43 | MySQL Server | Closed (5287 days) | S3 | 5.0.52-bk, 5.1 | Any | Any | CREATE TABLE under LOCK TABLES ignores FLUSH TABLES WITH READ LOCK |
36634 | 2008-05-09 18:35 | 2011-02-16 23:43 | MySQL Server: InnoDB storage engine | Can't repeat (5733 days) | S3 | 6.0.6 | Any | Any | LOCK TABLE: cannot acquire transactional lock |
38822 | 2008-08-15 14:09 | 2011-02-16 23:43 | MySQL Server: Locking | Can't repeat (5774 days) | S3 | 6.0 | Any | Any | Assertion failed in mdl_upgrade_shared_lock_to_exclusive() at mdl.cc:989 |
41513 | 2008-12-16 15:16 | 2013-12-20 8:18 | MySQL Server: Falcon storage engine | Won't fix (4010 days) | S3 | 6.0.8 | Any | Any | Falcon deadlock Bdb::addRef and Cache::fetchPage |
47648 | 2009-09-25 13:23 | 2011-02-16 23:44 | MySQL Server: Merge storage engine | Closed (5393 days) | S3 | 6.0, mysql-next-4284 | Any | Any | main.merge fails sporadically |
47682 | 2009-09-28 16:12 | 2011-02-16 23:44 | MySQL Server: Locking | Closed (5389 days) | S3 | 5.1,6.0.14 | Any | Any | strange behaviour of INSERT DELAYED |
47826 | 2009-10-05 8:24 | 2015-08-23 20:45 | Tests: Server | Verified | S3 | 5.1-bk | Any | Any | main.partition_innodb fails sometimes with the innodb plugin |
50786 | 2010-02-01 9:56 | 2011-02-16 23:44 | MySQL Server: Locking | Closed (5394 days) | S1 | mysql-next-4284-stage | Any | Any | Assertion `thd->mdl_context.trans_sentinel() == __null' failed in open_ltable() |
58689 | 2010-12-03 6:02 | 2012-07-31 1:44 | MySQL Server: Locking | Closed (4517 days) | S3 | 5.0, 5.1, 5.6.1 | Any | Any | MyISAM Selects locks inserts inside procedure only |
71634 | 2014-02-08 12:03 | 2015-04-27 14:29 | MySQL Server: Performance Schema | Closed (3863 days) | S3 | 5.6.16 | Any | Any | P_S digest looks wrong for system variables, shown as @ @ variable... |
76049 | 2015-02-25 15:13 | 2015-02-25 21:50 | MySQL Server: Replication | Verified | S3 | 5.6.22 | Any | Any | Filtered replication events do not reset the System lock thread state |
95115 | 2019-04-24 17:16 | 2019-07-18 13:18 | MySQL Server: Replication | Closed (1974 days) | S1 | 5.7.24 | CentOS (CentOS Linux release 7.6.1810 (Core)) | x86 (x86_64, ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked (uses shared libs) | mysqld deadlock of all client threads originating from 3-way deadlock |
100035 | 2020-06-29 14:24 | 2020-07-01 15:26 | MySQL Server | Not a Bug (1625 days) | S3 | 5.7.28, 8.0.20 | CentOS | Any | Socket lock file checking error |
106480 | 2022-02-17 0:11 | 2022-05-13 15:49 | MySQL Server: Documentation | Closed (944 days) | S3 | 8.0 | Any | Any | ALGORITHM=INSTANT takes exclusive metadata lock on table |
110561 | 2023-03-30 7:55 | 2023-06-27 6:15 | MySQL Server: Locking | Verified (534 days) | S2 | 8.0 | Any | Any | select * from performance_schema.data_locks returns wrong result |
113276 | 2023-11-29 5:55 | 2023-11-29 13:00 | MySQL Server | Can't repeat (379 days) | S3 | 8.0.24 | CentOS (7.9) | x86 | MYSQL does not respond after applications are inserted in batches |
114361 | 2024-03-15 1:53 | 2024-08-14 9:34 | MySQL Server: Replication | Verified (269 days) | S5 | 8.0 | Any | Any | Unaligned Delegate's lock reduces performance |
99638 | 2020-05-20 0:53 | 2020-12-04 12:54 | MySQL Server: InnoDB storage engine | Closed (1470 days) | S5 | 8.0.18 | Any | Any | xa transaction with low performance |
49456 | 2009-12-04 12:04 | 2018-04-08 20:45 | MySQL Server | Analyzing (5487 days) | S3 | mysql-5.1-rep+3 | Any | Any | replication out of sync |
108921 | 2022-10-28 17:15 | 2022-11-08 15:20 | Shell AdminAPI InnoDB Cluster / ReplicaSet | Can't repeat (765 days) | S2 | 8.0.31 | Any | Any | lock wait timeout trying to removeCluster from clusterset |
52515 | 2010-04-01 2:51 | 2011-05-09 19:26 | MySQL Server: Command-line Clients | Closed (4966 days) | S2 | 5.1.45, 5.1.40sp1 | Any | Any | mysql sessions are not terminated properly |
68047 | 2013-01-07 10:01 | 2013-01-22 19:48 | MySQL Server: InnoDB storage engine | Duplicate (4342 days) | S1 | 5.1.47 | Linux (X86_64) | Any | DB hung with InnoDB: Warning: a long semaphore wait when optimize table is going |
93500 | 2018-12-06 7:48 | 2019-01-31 13:47 | MySQL Server: InnoDB storage engine | Closed (2197 days) | S5 | 8.0.13 | Linux | Any | Question about Mysql8.0 Innodb's log_writer |
9341 | 2005-03-22 16:29 | 2013-10-06 20:45 | MySQL Cluster: Cluster (NDB) storage engine | No Feedback (7154 days) | S2 | 4.1.9 | Linux (Redhat) | Any | do not lock tables for reading |
98949 | 2020-03-13 21:20 | 2020-03-16 9:00 | MySQL Server: InnoDB storage engine | Not a Bug (1732 days) | S3 | 8.0.* | Any | Any | The count_os_wait in rw_lock_s_lock_spin could be wrong |
8215 | 2005-01-31 15:34 | 2014-01-21 17:45 | MySQL Server: Replication | Duplicate (3978 days) | S2 | 4.1.7 | Any (White Box EL release 3.0) | Any | Replication fails with "log event entry exceeded max_allowed_packet" |
42384 | 2009-01-27 17:48 | 2011-02-16 23:43 | MySQL Server | Closed (5732 days) | S2 | 6.0 | Any | Any | thread_handling = pool-of-threads, wrong handling of max_questions user limit |
76915 | 2015-05-03 9:06 | 2015-05-07 16:29 | MySQL Server: Errors | Closed (3507 days) | S3 | 5.7.7-rc | Any | Any | Misleading warning when per-query statement time is exceeded |
58003 | 2010-11-04 23:32 | 2011-02-16 23:44 | MySQL Server: Performance Schema | Closed (5089 days) | S2 | 5.6.99-m5-debug | Any | Any | Segfault on CHECKSUM TABLE performance_schema.EVENTS_WAITS_HISTORY_LONG EXTENDED |
59658 | 2011-01-21 14:46 | 2011-04-16 17:09 | MySQL Server: Performance Schema | Closed (4989 days) | S3 | 5.5.8 | Any | Any | performance_schema tracks both binary and relay logs in the same events |
79703 | 2015-12-18 12:54 | 2016-06-29 12:36 | MySQL Server: InnoDB storage engine | Closed (3088 days) | S3 | 5.6,5.7 | Any | Any | Spin rounds per wait will be negative in InnoDB status if spin waits > max32int |
74821 | 2014-11-12 14:48 | 2020-01-14 16:07 | MySQL Server: InnoDB storage engine | Not a Bug (3655 days) | S3 | 5.6.18-enterprise-commercial-advanced-lo | Linux (Red Hat Enterprise Linux Server release 6.3) | Any | DETECTED DEADLOCK are not shown in error log |
4159 | 2004-06-16 4:17 | 2004-09-09 16:44 | MySQL Server: InnoDB storage engine | Can't repeat (7399 days) | S1 | 4.0.20-max binary | Linux (Linux version 2.4.20-31.9smp) | Any | Ciritical Innodb shutdown ( about ha_innodb.cc ) |
116815 | 2024-11-28 3:51 | 2024-12-04 17:38 | MySQL Server: InnoDB storage engine | Analyzing (8 days) | S2 | 8.0.30 | Any | Any | INSERT locks primary key supremum after secondary index duplicate key collision |
100148 | 2020-07-08 3:07 | 2020-08-10 12:22 | MySQL Server | Can't repeat (1585 days) | S2 | 8.0.18 | Red Hat | x86 | During a parallel read operation, the rollback of a table load operation causes |
110872 | 2023-04-30 2:06 | 2023-05-04 11:32 | MySQL Server: DDL | Verified (589 days) | S3 | 8.0 | Any | Any | Unable to create indexes concurrently on the same table |
32737 | 2007-11-26 19:59 | 2011-02-16 23:43 | MySQL Cluster: Cluster (NDB) storage engine | Won't fix (5224 days) | S3 | mysql-5.0 | MacOS (10.5) | Any | Ndb is unreliable, fails with varying symptoms (platform-specific): optim. serv. |
68634 | 2013-03-11 10:59 | 2018-02-09 19:24 | MySQL Cluster: Cluster (NDB) storage engine | Verified (4291 days) | S3 | 5.5.22-ndb-7.2.6-log | Linux | Any | DROP/CREATE TABLE running into timeouts on certain api nodes, but not all |
79311 | 2015-11-17 11:25 | 2016-02-08 12:43 | MySQL Cluster: Cluster (NDB) storage engine | Closed (3306 days) | S3 | 7.2.22 | Any | Any | NDB binlog injector use incorrect mutex in condition signaling |
88967 | 2017-12-19 11:24 | 2018-01-21 1:00 | MySQL Server | No Feedback (2518 days) | S3 | 5.7.16 | CentOS | Any | Semaphore wait has lasted > 600 seconds mysqld restart |
101860 | 2020-12-03 18:15 | 2021-02-08 13:51 | MySQL Server: InnoDB storage engine | Unsupported (1403 days) | S3 | 5.6/5.7 | Any | Any | Deadlock happend under heavily write and delete workload |
40684 | 2008-11-13 5:08 | 2011-02-16 23:43 | Connector / NET | Closed (5602 days) | S1 | Any | Any (Tested on 5.0.9) | Any | Connector/NET does not obey Connect Timeout |
9670 | 2005-04-06 8:30 | 2009-12-07 10:32 | MySQL Server: InnoDB storage engine | Closed (7071 days) | S2 | 4.0.24, 4.1.10, 4.1.11 | MacOS (OS X, Linux) | Any | ut_a(cursor->old_stored == BTR_PCUR_OLD_STORED) fails, OPTIMIZE TABLE crashes |
13865 | 2005-10-08 15:34 | 2005-10-13 21:20 | Connector / NET | Closed (7000 days) | S2 | 1.0.6 | Server 2003 | Any | MySQl Conn. raises a wrong exception on connect |
25341 | 2006-12-30 23:08 | 2007-02-15 5:10 | MySQL Server: Command-line Clients | Closed (6510 days) | S2 | 5.0.34-BK, 5.0.30 | Linux (Linux) | Any | /etc/init.d/mysql stop may timeout too quickly |
36269 | 2008-04-22 23:32 | 2009-01-08 9:48 | MySQL Server: Falcon storage engine | Closed (5817 days) | S3 | 6.0 | Any | Any | Thread stalls during DBT2 run |
42874 | 2009-02-16 10:33 | 2021-05-23 20:45 | MySQL Server: Falcon storage engine | Duplicate (5761 days) | S1 | 6.0-falcon-team | Any | Any | Falcon 100% CPU loop during recovery in IndexPage::findInsertionPoint |
42903 | 2009-02-16 20:11 | 2010-05-26 18:00 | MySQL Server: Falcon storage engine | Unsupported (5314 days) | S1 | 6.0-falcon-team | Any | Any | Falcon: Inconsistent tablespace after recovery |
43554 | 2009-03-11 9:16 | 2010-05-26 17:59 | MySQL Server: Falcon storage engine | Unsupported (5314 days) | S3 | 6.0-falcon-team | Any | Any | Intermittent lock-wait-timeout in falcon_deadlock test |
59306 | 2011-01-05 10:09 | 2013-01-10 12:05 | MySQL Server: Optimizer | Can't repeat (4354 days) | S2 | 5.6.1-m5 | Linux | Any | Server crashes at Item_in_optimizer::fix_left during a Join Operation |
63730 | 2011-12-13 9:53 | 2011-12-19 6:57 | MySQL Server: Locking | Duplicate (4742 days) | S3 | mysql-5.1.56 ndb-7.1.15 | Solaris (sol10) | Any | Update different rows of table in Function will cause 'Lock Wait Timeout' |
67409 | 2012-10-29 11:47 | 2012-12-29 0:25 | MySQL Server: Documentation | Closed (4366 days) | S2 | 5.5 | Linux | Any | Inconsistent Documentation & use of nouns |
84889 | 2017-02-08 14:55 | 2017-03-28 14:33 | MySQL Server: Errors | Closed (2817 days) | S3 | 8.0.1 | Any | Any | MYSQL 8.0.1 - MYSQLD ERRORLOG UPGRADE ERRORS AT SERVER START LIVE UPGRADE |
74684 | 2014-11-04 14:48 | 2014-11-05 8:01 | MySQL Server: InnoDB storage engine | Duplicate (3690 days) | S3 | 5.5.38 | Linux (RHEL 6.5 x86_64) | Any | semaphore wait has lasted > 600 seconds causes server to crash |
102538 | 2021-02-09 4:03 | 2021-02-10 17:49 | MySQL Server | Can't repeat (1401 days) | S3 | 5.7.22 | Any | Any | Master dump thread stuck in 'Waiting to finalize termination' state |
28622 | 2007-05-23 15:03 | 2011-02-16 23:43 | MySQL Cluster: Cluster (NDB) storage engine | Can't repeat (5340 days) | S3 | mysql-5.0 | Linux | Any | REPLACE INTO cause DELETE to time out on lock |
57481 | 2010-10-15 12:22 | 2011-02-16 23:44 | MySQL Cluster: Cluster (NDB) storage engine | Closed (5131 days) | S3 | 5.1.47-ndb-7.1.9 | Any | Any | 'multi range read' may fail to close completed NdbScanOperations |
30331 | 2007-08-09 14:17 | 2011-02-16 23:43 | MySQL Server | Closed (5389 days) | S3 | any | Any | Any | Table_locks_waited shows inaccurate values |
30990 | 2007-09-13 4:30 | 2012-09-13 8:35 | Connector / J | Closed (6236 days) | S3 | connectorJ 5.0.4 & 5.0.7 | Any | Any | JDBC connections do not properly free up resources when returned a pool |
47300 | 2009-09-14 8:19 | 2011-02-16 23:44 | MySQL Server: Locking | No Feedback (5470 days) | S2 | 5.1.30 | Linux | Any | innodb insert dead lock |
79274 | 2015-11-13 15:03 | 2019-07-25 12:42 | MySQL Server: Locking | Can't repeat (1967 days) | S2 | 5.6, 5.7, 8.0 | Any | Any | CREATE TRIGGER etc is not able to get a SHARED_NO_WRITE metadata lock |
91959 | 2018-08-10 9:10 | 2019-05-14 17:33 | MySQL Server: InnoDB storage engine | Closed (2039 days) | S3 | 8.0.14 | Any | Any | UBSAN: signed integer overflow in lock_update_trx_age |
24745 | 2006-12-01 7:00 | 2007-01-04 16:17 | MySQL Server: InnoDB storage engine | Can't repeat (6552 days) | S3 | 4.0.26, 5.0.38 | Linux (Linux) | Any | InnoDB semaphore wait timeout/crash - deadlock waiting for itself |
12914 | 2005-08-31 15:59 | 2005-08-31 16:08 | MySQL Query Browser | Not a Bug (7043 days) | S2 | php5 | Windows (xp) | Any | php5 with phpMyAdmin won't browse tables, Apache crash |
18475 | 2006-03-23 23:50 | 2006-09-06 10:09 | MySQL Cluster: Cluster (NDB) storage engine | Closed (6672 days) | S2 | 5.0.19-max-log with openssl | Linux (Fedora Core 4) | Any | Out of memory in COPY_FRAG |
19645 | 2006-05-09 17:26 | 2007-01-25 4:07 | MySQL Cluster: Cluster (NDB) storage engine | Closed (6531 days) | S2 | 5.1.11 | Linux (Linux 32 Bit OS) | Any | Data Node hangs in phase 100 |
27092 | 2007-03-13 15:39 | 2015-03-15 20:45 | MySQL Cluster: Cluster (NDB) storage engine | No Feedback (6357 days) | S2 | 5.1.16 | Linux (Linux x86_64) | Any | NDBD not freeing up memory after stopping |
67126 | 2012-10-07 23:58 | 2013-05-03 6:36 | MySQL Cluster: Cluster (NDB) storage engine | Duplicate (4241 days) | S2 | 7.2.8 | Linux (Linux Generic x68 binaries) | Any | LCP fragment scan watchdog crash in DBLQH in 7.2.8 after 60 seconds |
37963 | 2008-07-08 11:06 | 2011-02-16 23:43 | MySQL Server: Locking | Duplicate (5508 days) | S2 | 5.x | Any | Any | all threads wait in 'opening tables' or 'closing tables' status on mutex/lock |
41506 | 2008-12-16 14:00 | 2011-02-16 23:43 | MySQL Server: InnoDB storage engine | No Feedback (5435 days) | S1 | 5.0.22 | Linux (Ubuntu 6.06/x86_64) | Any | InnoDB hang on purge_sys->latch in row0vers.c:107 and trx0purge.c:1059 |
100692 | 2020-08-31 6:27 | 2020-11-24 15:16 | Connector / NET | Closed (1479 days) | S1 | 8.021 | Windows | Any | class Ssl 无限期等候的情况 |
40342 | 2008-10-27 9:26 | 2009-05-15 12:56 | MySQL Server: Falcon storage engine | Closed (5690 days) | S5 | 6.0-falcon | Linux (RHEL 5.2 x64) | Any | Falcon; big idle spike when running sysbench with 50 million table size |
47171 | 2009-09-07 11:40 | 2011-02-16 23:44 | MySQL Cluster: Cluster (NDB) storage engine | Closed (5566 days) | S3 | Any | Any | MaxNoOfOpenFiles exceeded during REDO invalidation | |
5009 | 2004-08-12 1:50 | 2004-09-02 16:50 | MySQL Query Browser | Closed (7406 days) | S3 | 1.0.5-alpha | Linux (RH9) | Any | crash due to gconf lock failure |
10174 | 2005-04-26 13:02 | 2005-04-26 14:16 | MySQL Server | Duplicate (7170 days) | S3 | 5.0-bk | Linux (linux) | Any | blackhole test hangs on 64 bit in 5.0 |
10175 | 2005-04-26 13:04 | 2005-05-19 14:16 | MySQL Server | Closed (7147 days) | S3 | 5.0-bk | Linux (linux) | Any | blackhole test hangs on 64 bit in 5.0 |
17120 | 2006-02-04 15:23 | 2006-04-06 12:57 | MySQL Server | Can't repeat (6825 days) | S2 | 5.0 | Windows (XP) | Any | LOCK tables with subqueries and alias table |
19629 | 2006-05-09 8:33 | 2006-05-09 9:07 | MySQL Server | Not a Bug (6792 days) | S2 | 5.0.20 | Linux (Linux 2.6.12) | Any | FLUSH TABLES WITH READ LOCK doesn't work in some cases |
31080 | 2007-09-18 14:12 | 2007-09-18 15:24 | MySQL Server: Locking | Not a Bug (6295 days) | S3 | 5.0.45 | Windows (2000 Server) | Any | LOCK TABLES + subqueries: Table 'test' was not locked with LOCK TABLES |
38231 | 2008-07-18 19:15 | 2011-02-16 23:43 | MySQL Server: InnoDB storage engine | Closed (5291 days) | S1 | 5.0.22, 5.0.42, 5.0.66a, 5.1.23, 5.1.28, 6.0.5 | Any | Any | Innodb crash in lock_reset_all_on_table() on TRUNCATE + LOCK / UNLOCK |
41364 | 2008-12-10 17:26 | 2022-12-04 20:45 | MySQL Server: Locking | Verified | S3 | 6.0 and probably earlier | Windows | Any | CHECK TABLE does not work with --external-locking on Windows |
43685 | 2009-03-17 2:41 | 2011-02-16 23:43 | MySQL Server: Locking | Closed (5394 days) | S3 | 5.0.78,5.1.32 | Any | Any | Lock table affects other non-related tables |
46650 | 2009-08-11 12:51 | 2011-02-16 23:44 | MySQL Server: InnoDB Plugin storage engine | Closed (5289 days) | S1 | 5.1,5.4 | Any | Any | Innodb assertion autoinc_lock == lock in lock_table_remove_low on INSERT SELECT |
48609 | 2009-11-06 21:41 | 2011-04-04 18:56 | MySQL Server: Locking | Won't fix (5001 days) | S3 | mysql-6.0-codebase-bugfixing | Any | Any | deadlock when running concurrent LOCK TABLE, ALTER TABLE,DELETE LOW_PRIORITY |
51838 | 2010-03-08 17:29 | 2011-02-16 23:44 | MySQL Server: InnoDB storage engine | Won't fix (5382 days) | S2 | 5.0.84 | Any | Any | Innodb gets X lock for INSERT ON DUPLICATE KEY UPDATE but not INSERT SELECT |
52590 | 2010-04-05 5:10 | 2011-02-16 23:44 | MySQL Server: InnoDB storage engine | Closed (5326 days) | S1 | 5.5.4-m3 | Any | Any | Assertion heap_no == ULINT_UNDEFINED in lock/lock0lock.c line 3695 |
54117 | 2010-05-31 20:00 | 2011-02-16 23:44 | MySQL Server: Locking | Closed (5173 days) | S3 | 5.6.99-m4-debug,5.5.5-m3-debug-log,5.1.48-debug | Any | Any | crash in thr_multi_unlock, temporary table |
55065 | 2010-07-08 2:33 | 2010-07-08 8:11 | MySQL Server: Locking | Not a Bug (5271 days) | S3 | 5.1 | Any | Any | LOCK TABLES ... READ does not lock tables used in triggers |
68244 | 2013-02-01 13:24 | 2013-06-06 15:13 | MySQL Server: InnoDB storage engine | Closed (4207 days) | S3 | 5.5 | Any | Any | lock_rec_validate_page() may dereference a pointer to a freed lock |
68647 | 2013-03-12 3:05 | 2014-08-28 19:20 | MySQL Server: InnoDB storage engine | Closed (3759 days) | S3 | 5.5.31,5.6.11,5.7.1 | Any | Any | function lock_number_of_rows_locked may be Inefficient |
72131 | 2014-03-26 5:52 | 2020-04-24 19:41 | MySQL Server: Replication | Can't repeat (1693 days) | S3 | 5.6.16-log | Linux (CentOS 5.9) | Any | Slave running state: System lock |
76803 | 2015-04-23 8:42 | 2019-01-25 1:21 | MySQL Server: InnoDB storage engine | Closed (2148 days) | S3 | 5.1, 5.5, 5.6, 5.7, 8.0 | Any | Any | InnoDB: Unlock row could not find a 2 mode lock on the record |
77477 | 2015-06-25 2:06 | 2015-07-12 20:43 | MySQL Server: Documentation | Closed (3441 days) | S3 | 5.6 | Any | Any | LOCK TABLES doc erroneously states truncate table generates error in transaction |
83574 | 2016-10-27 11:29 | 2018-02-23 0:44 | MySQL Server: InnoDB storage engine | Verified (2936 days) | S5 | 8.0 | Any | ARM | InnoDB atomics bs: loads and stores |
83640 | 2016-11-01 14:46 | 2017-01-10 17:02 | MySQL Server: InnoDB storage engine | Verified (2893 days) | S3 | any, 5.6.34 | Any | Any | Locks set by DELETE statement on already deleted record |
93043 | 2018-11-01 14:45 | 2018-11-16 14:26 | MySQL Server: Documentation | Closed (2218 days) | S3 | 8.0 | Any | Any | MySQL Manual describes get_lock() behavior in a wrong/unclear way |
93089 | 2018-11-06 3:37 | 2018-11-07 7:45 | MySQL Server: Replication | Can't repeat (2227 days) | S2 | 5.7 | Any | Any | parallel workers+slave_preserve_commit_order+flushtables with read lock deadlock |
93572 | 2018-12-12 11:37 | 2022-11-04 13:54 | MySQL Server: Locking | Won't fix (769 days) | S3 | 5.7.18 | Any | Any | parallel workers+slave_preserve_commit_order+flushtables with read lock deadlock |
93806 | 2019-01-03 17:41 | 2020-09-21 14:21 | MySQL Server: Documentation | Closed (2122 days) | S3 | all | Any | Any | Document error about "ON DUPLICATE KEY UPDATE " |
99369 | 2020-04-27 13:12 | 2020-04-29 12:13 | MySQL Server | Closed (1688 days) | S2 | 8.0.17, 8.0.19 | Red Hat (7.5) | Any | Bugs in "LOCK INSTANCE FOR BACKUP" |
109784 | 2023-01-26 3:19 | 2023-02-03 9:36 | MySQL Server: InnoDB storage engine | Verified (682 days) | S3 | 8.0 | Any | Any | Remove innodb table lock and use MDL lock to protect table |
109938 | 2023-02-04 21:51 | 2023-02-13 13:27 | MySQL Server: Locking | Not a Bug (671 days) | S3 | 8.0.31 | Any | Any | next key lock with ROLLBACK TO SAVEPOINT |
110795 | 2023-04-25 5:45 | 2023-04-25 8:41 | MySQL Server: Locking | Verified (597 days) | S3 | 8.0.27, 8.0.33, 5.7.42 | Any | Any | mysql insert is deadlocked |
41597 | 2008-12-18 17:16 | 2011-02-16 23:43 | MySQL Server: Security: Privileges | Closed (5473 days) | S3 | mysql-6.0-backup, 5.1, 5.0, azalea | Linux | Any | After rename of user, there are additional grants when grants are reapplied. |
90573 | 2018-04-23 13:14 | 2018-10-09 16:07 | MySQL Server | Can't repeat (2256 days) | S1 | 5.6.40 | FreeBSD (11.1) | Other (amd64) | MySQL crash |
8572 | 2005-02-17 15:59 | 2005-06-03 23:46 | MySQL Server | Closed (7132 days) | S1 | 4.1.9 | Windows (XP) | Any | LibMySQL closes SSL connection using 5sec timeout |
9220 | 2005-03-16 13:02 | 2005-04-24 22:12 | Connector / NET | Can't repeat (7172 days) | S2 | 1.0.4 | Windows (W2K3) | Any | Connection Timout problem... |
47244 | 2009-09-10 10:28 | 2011-02-16 23:44 | Tests: Cluster | Verified | S3 | 5.1 | Any | Any | rpl_ndb_innodb2ndb fails on PB2 with timeout |
62266 | 2011-08-26 13:43 | 2012-07-27 23:24 | Connector / NET | Closed (4521 days) | S3 | 6.5.4 | Any | Any | Timed out sessions are removed without notification |
87551 | 2017-08-26 7:20 | 2017-09-06 10:35 | Connector / NET | Not a Bug (2654 days) | S3 | 6.9.9 | Windows | Any | in ReplicationGroup, open connection timeout doesn't mark server as UnAvailable |
110789 | 2023-04-24 18:17 | 2024-10-07 12:57 | Connector / NET | Verified (554 days) | S2 | 8.0.33, 8.3.0 | Windows (10) | Any | OpenAsync throws unhandled exception from thread pool |
115135 | 2024-05-27 8:54 | 2024-05-27 10:02 | Connector / NET | Analyzing (199 days) | S3 | mysql 8.0.35 & MySql.EFCore 8.0.2 | Ubuntu (22.04) | x86 (x86_64 ) | EntityFrameworkCore+MySQL hangs when `Min Pool Size=10` only on ubuntu/linux |
28680 | 2007-05-25 14:22 | 2008-05-08 8:28 | MySQL Server: Installing | Closed (6062 days) | S3 | 6.0.0-alpha-community-nt-debug | Windows (XP SP2) | Any | Can't open and lock privilege tables: Table 'mysql.servers' doesn't exist |
77717 | 2015-07-14 11:23 | 2016-06-18 21:26 | Tests: Server | Closed (3307 days) | S3 | 8.0 | Any | Any | perfschema.no_threads : fails sporadically on daily-trunk |
6817 | 2004-11-24 23:58 | 2004-11-25 22:45 | MySQL Server | Closed (7322 days) | S1 | 4.1.7 | Linux (Linux) | Any | mysqld crashes after innodb buffer pool fills up |
15211 | 2005-11-24 3:08 | 2007-03-07 8:00 | Connector / ODBC | Duplicate (6490 days) | S2 | 3.51.12 | Windows (Window XP) | Any | ODBC timeouts can't be change with MyODBC! |
83537 | 2016-10-25 22:33 | 2017-03-31 19:18 | MySQL Server: Replication | Closed (2813 days) | S3 | 5.6, 5.6.34 | Any | Any | WAIT_UNTIL_SQL_THREAD_AFTER_GTIDS timeout value handles some inputs badly |
86009 | 2017-04-19 16:28 | 2017-04-21 13:53 | Connector / NET | Verified (2792 days) | S3 | 6.9.9 | Windows | Any | Connector connection times-out after command completes |
70654 | 2013-10-18 10:11 | 2016-05-25 13:38 | MySQL Server: InnoDB storage engine | Duplicate (4029 days) | S1 | 5.5.34 | Any | Any | [ERROR] Table x contains y indexes inside InnoDB, which is different from MySQL |
4979 | 2004-08-10 16:10 | 2016-01-03 20:45 | MySQL Server: InnoDB storage engine | No Feedback (7348 days) | S1 | 4.0.20-Max | Linux (Linux Redhat 9.0) | Any | INNODB SHOW TABLES hangs causes a long semaphore wait |
26834 | 2007-03-05 7:07 | 2007-08-24 0:13 | MySQL Server: InnoDB storage engine | Duplicate (6320 days) | S2 | 5.0.32 | Linux (Linux (Debian Sarge)) | Any | MySQL crashes with "long semaphore wait" |
102097 | 2020-12-31 8:51 | 2021-01-25 20:04 | MySQL Server: Clone Plugin | Closed (1417 days) | S3 | 8.0.21, 8.0.22 | Any | Any | Cloning fails with low wait_timeout |
40746 | 2008-11-14 15:03 | 2008-11-14 15:37 | MySQL Server: InnoDB storage engine | Not a Bug (5872 days) | S2 | 5.0.67 | Windows (XP SP2) | Any | SQL locks more rows that we asked to lock |
69946 | 2013-08-07 7:13 | 2017-02-17 12:22 | MySQL Cluster: Documentation | Duplicate (2861 days) | S2 | 5.6.11-ndb-7.3.2-cluster | Linux (RHEL 6.2) | Any | Shared read lock on SELECT in transaction on VARCHAR column with UK constraint |
81563 | 2016-05-24 8:18 | 2016-05-26 13:13 | MySQL Server | Not a Bug (3122 days) | S3 | 5.6.21,5.6.16 | Any | Any | Insert operation will add S-lock on one record after deleted one. |
32092 | 2007-11-04 21:58 | 2007-11-13 20:05 | Connector / NET | Closed (6239 days) | S3 | 5.1.3 | Windows (used with VS 2005 Team Edition (SP1)) | Any | It seemes that MySqlConnection.open() ignores "Connect timeout" setting |
93047 | 2018-11-01 17:30 | 2018-11-04 16:16 | Connector / NET | Unsupported (2230 days) | S1 | 8.0.13 | Windows (10) | Any | Timeout after a read error returns HA_ERR_INTERNAL_ERROR (122) |
41799 | 2008-12-30 19:53 | 2008-12-30 20:20 | MySQL Server: InnoDB storage engine | Not a Bug (5826 days) | S3 | 5.1.30 | Linux (Debian) | Any | Invisible transaction lock my table |
53676 | 2010-05-15 20:42 | 2011-02-16 23:44 | MySQL Server: Partitions | Closed (5215 days) | S2 | 5.5.3-m3, 5.5.5-m3, 5.6.99 | Any | Any | Unexpected errors and possible table corruption on ADD PARTITION and LOCK TABLE |
54905 | 2010-06-30 0:07 | 2011-02-16 23:44 | MySQL Server: Locking | Closed (5236 days) | S3 | 5.5.5-m3 | Any | Any | Connection with WRITE lock cannot ALTER table due to concurrent SHOW CREATE |
102098 | 2020-12-31 9:40 | 2021-03-03 1:00 | MySQL Server: XA transactions | No Feedback (1381 days) | S2 | 8.0.22,5.7.32 | CentOS (7.4) | x86 | XA Transactions Next-key Lock lost lead to slave replication lock wait timeout |
73730 | 2014-08-26 19:50 | 2014-08-27 18:02 | MySQL Server: Documentation | Closed (3760 days) | S3 | 5.6, 5.5, 5.1,5.0 | Any | Any | mysql-service documentation bug |
93347 | 2018-11-26 14:56 | 2019-07-25 8:30 | MySQL Server: Group Replication | Closed (2116 days) | S3 | 5.7 | Any | Any | VIEW_CHANGE_LOG_EVENT may not be logged on a overloaded primary |
48106 | 2009-10-16 7:50 | 2011-02-16 23:44 | MySQL Server: InnoDB storage engine | No Feedback (5505 days) | S3 | 5.0.67 | Any | Any | Concurrent DELETE / INSERT throw lock wait timeout |
72007 | 2014-03-11 11:14 | 2014-04-25 4:02 | MySQL Server: Documentation | Closed (3884 days) | S3 | 5.6 | Any | Any | Broken links in the manual |
79963 | 2016-01-13 21:00 | 2018-07-19 14:38 | MySQL Server: Storage Engines | Not a Bug (2338 days) | S3 | 5.6.27 | Any | Any | myql 5.6.27 table locking / timing issue bug |
98809 | 2020-03-03 3:54 | 2020-03-04 12:32 | MySQL Server | Not a Bug (1744 days) | S3 | 8.0.18 | CentOS | x86 | Semaphore wait has lasted > 600 seconds. We intentionally crash the server becau |
98995 | 2020-03-19 3:09 | 2020-03-19 14:12 | MySQL Server: InnoDB storage engine | Duplicate (1729 days) | S3 | 5.7.26 | Linux | x86 | thread that holding lock disappear |
4068 | 2004-06-09 3:32 | 2004-06-23 4:38 | MySQL Server: Installing | Not a Bug (7477 days) | S1 | 4.1.1-alpha-win | Windows (Windows XP) | Any | I can't start the mysql service on my Windows XP local host |
38584 | 2008-08-05 21:28 | 2016-10-16 20:45 | MySQL Server: Replication | Duplicate (5802 days) | S3 | 5.0.44, 5.0, 5.1, 6.0 bzr | Any | Any | Wrong Exec_Master_Log_Pos from 'SHOW SLAVE STATUS' |
73366 | 2014-07-23 13:23 | 2014-09-05 5:18 | MySQL Utilities | Closed (3751 days) | S1 | 1.4.3 | Linux (CentOS 6.5) | Any | mysqlserverclone does not detect full disk error in Linux |
28899 | 2007-06-05 14:55 | 2007-06-11 21:08 | MySQL Cluster: Cluster (NDB) storage engine | Closed (6394 days) | S3 | Any | Any | not possible to set separate watchdog timeout at startup | |
44099 | 2009-04-05 20:55 | 2011-02-16 23:43 | MySQL Cluster: Cluster (NDB) storage engine | Closed (5720 days) | S3 | * | Any | Any | Scan can timeout incorrectly if low selectivity |
86957 | 2017-07-05 12:49 | 2019-01-22 14:20 | MySQL Server: Group Replication | Closed (2353 days) | S3 | 5.7.20 | Any | Any | SETTING gr_force_members HITS ERROR1231 SOMETIMES WHILE UNBLOCKING THE GROUP |
8673 | 2005-02-22 9:34 | 2005-02-23 8:20 | MySQL Server | Duplicate (7232 days) | S1 | 5.0.3-bk | Linux (Linux 2.4.21-99-smp) | Any | MySQL crash when creating a new database |
44533 | 2009-04-29 2:50 | 2009-08-17 20:06 | MySQL Server: Backup | Won't fix (5596 days) | S3 | 5.1, mysql-6.0 | Any | Any | No way to use debug_sync code to wait for event to fire. |
61188 | 2011-05-16 16:43 | 2011-11-02 16:32 | MySQL Server: InnoDB storage engine | Closed (4789 days) | S3 | 5.5.12-log | Linux (CentOS release 5.3 (Final)) | Any | DROP TABLE extremely slow |
74884 | 2014-11-16 20:59 | 2015-05-26 23:44 | MySQL Workbench: Modeling | Closed (3488 days) | S1 | 6.2.3 | Windows (Microsoft Windows 7 Professional Service Pack 1) | Any | Can't open .mwb file |
86482 | 2017-05-27 7:54 | 2017-10-19 17:49 | MySQL Server: Performance Schema | Closed (2611 days) | S1 | 5.7 | Any | Any | innodb leaks memory, performance_schema file_instances #sql-ib3129987-252773.ibd |
97934 | 2019-12-09 22:55 | 2021-06-02 17:15 | MySQL Visual Studio Integration | Closed (1289 days) | S5 | Windows | Any | UI delay in mysql.visualstudio.dll MySqlQuickInfoController.OnTextViewMouseHover | |
111860 | 2023-07-24 8:59 | 2023-09-18 10:17 | MySQL Server: Performance Schema | Closed (464 days) | S3 | Any | Any | shutdown plugin core when init_events_waits_history_long failed | |
110485 | 2023-03-24 5:00 | 2024-09-25 10:54 | MySQL Server: InnoDB storage engine | Verified (78 days) | S2 | 8.0.32, 8.0.39 | Any | Any | FLUSH TABLE FOR EXPORT will lead deadlock |
38796 | 2008-08-14 12:31 | 2011-02-16 23:43 | Connector / NET | Duplicate (5664 days) | S1 | 5.2.2.0 | Windows (XP) | Any | MySqlConnection.open() hangs if disconnect connection |
91062 | 2018-05-29 13:52 | 2018-06-11 16:27 | MySQL Cluster: Cluster (NDB) storage engine | Can't repeat (2376 days) | S1 | 7.4.13 | Any | Any | MySQL Cluster NDB node crashes with SIGFPE, floating point exception |
45035 | 2009-05-22 12:27 | 2011-02-16 23:44 | MySQL Server: Locking | Closed (5394 days) | S3 | 6.0.12-bzr, 5.4 | Any | Any | Altering table under LOCK TABLES results in "Error 1213 Deadlock found..." |
33988 | 2008-01-22 18:43 | 2019-08-08 13:04 | MySQL Server: Locking | Won't fix (5700 days) | S3 | 5.0, 5.1 | Any | Any | "Locked" state of the thread can be misleading |
27700 | 2007-04-07 18:38 | 2016-01-03 20:45 | MySQL Server: InnoDB storage engine | No Feedback (6417 days) | S1 | 5.0.37 | Other (CentOS 3) | Any | MySQL Server Fails To Start After RPM Install (InnoDB Error) |
8825 | 2005-02-26 22:39 | 2005-02-27 6:59 | MySQL Server: InnoDB storage engine | Won't fix (7228 days) | S2 | 4.0.22 | Linux (Linux) | Any | Fail to remove foreign key constraint |
47020 | 2009-08-31 14:35 | 2021-05-02 20:45 | MySQL Cluster: Cluster (NDB) storage engine | Duplicate (5580 days) | S1 | 7.0.5 | Linux | Any | MySQL Cluster 7.0.5 datas nodes crash |
29929 | 2007-07-20 11:20 | 2007-08-02 3:50 | MySQL Server: Locking | Closed (6342 days) | S1 | 5.0, 5.1, 5.2 | Any | Any | LOCK TABLES does not pre-lock tables used in triggers of the locked tables |
68985 | 2013-04-17 16:07 | 2013-04-20 5:50 | MySQL Server: General | Can't repeat (4254 days) | S2 | 5.0.45 | Linux (Debian 6.0.6) | Any | MySQL database drop insanely slow |
70611 | 2013-10-12 9:05 | 2013-12-30 1:00 | MySQL Server: InnoDB storage engine | No Feedback (4001 days) | S3 | 5.5.33 | Linux (Red Hat Enterprise Linux Server release 5.5) | Any | Mutex cause Thread waited at srv0srv.c line 1703 for xx seconds the semaphore |
73666 | 2014-08-21 9:09 | 2014-08-21 19:12 | MySQL Server: Locking | Verified (3766 days) | S3 | 5.5.37-bzr, 5.6.21-bzr, 5.7.5-bzr | Any | Any | DEADLOCK WHEN DDL UNDER LOCK TABLES WRITE, READ LOCAL + PREPARE. |
90675 | 2018-04-28 7:30 | 2018-05-02 13:34 | MySQL Server: InnoDB storage engine | Not a Bug (2416 days) | S3 | mysql-5.7 | Any | Any | Improper Record lock With Primary Key. where key >= or <= N |
93882 | 2019-01-10 20:39 | 2019-01-13 18:26 | MySQL Server: DML | Can't repeat (2160 days) | S2 | 5.6.42 | CentOS | x86 | Many queries executing delete returns "starting index read" |
104273 | 2021-07-11 16:33 | 2021-07-16 22:45 | MySQL Server | Can't repeat (1245 days) | S2 | 5.7.30 | Red Hat (7.5) | x86 | Replication sql_thread hung while executing XA START in System lock state |
27487 | 2007-03-28 7:26 | 2016-01-03 20:45 | MySQL Server: InnoDB storage engine | Duplicate (6469 days) | S3 | 5.1.18, 5.0 | Linux (linux) | Any | pthread_create failure leads to innodb tablespaces unusable |
82253 | 2016-07-16 14:21 | 2016-07-27 2:41 | MySQL Server: XA transactions | Not a Bug (3060 days) | S3 | 5.7 | Any | Any | deadlock xa transaction restarting break the ACID of transaction |
49780 | 2009-12-17 19:30 | 2011-02-16 23:44 | MySQL Server: InnoDB storage engine | Can't repeat (5049 days) | S2 | 5.1.38 | Linux (x86 RedHat AS 4) | Any | innodb engine hang with long semaphore wait warning in mysqld.log |
90993 | 2018-05-23 14:21 | 2018-08-20 12:24 | MySQL Server: InnoDB storage engine | Closed (2306 days) | S2 | 8.0.11 | Any | Any | InnoDB crashes from long lock wait - log writer waiting for checkpointer |
4137 | 2004-06-15 5:43 | 2004-06-16 11:35 | MySQL Server | Not a Bug (7484 days) | S1 | 4.0 | Any (ALL) | Any | get_lock does not work |
64475 | 2012-02-27 20:15 | 2013-02-15 16:46 | Connectors: DBD::mysql ( Perl ) | Unsupported (4318 days) | S3 | 4.020 | Any | Any | select* methods output misleading error messages on InnoDB lock timeout |
15019 | 2005-11-17 14:56 | 2007-10-24 14:09 | MySQL Cluster: Replication | Can't repeat (6259 days) | S2 | 5.1.2 | Linux (Linux) | Any | binlog purge fails if more binlogs open then O/S limits allow |
43213 | 2009-02-26 8:45 | 2010-05-26 18:00 | MySQL Server: Falcon storage engine | Unsupported (5314 days) | S2 | 6.0.10-alpha | Any | Any | falcon_limit test reports deadlock when locking indexes |
47343 | 2009-09-16 1:23 | 2011-02-16 23:44 | MySQL Server: Partitions | Closed (5289 days) | S1 | 5.1.38 | Any | Any | InnoDB fails to clean-up after lock wait timeout on REORGANIZE PARTITION |
84499 | 2017-01-13 7:40 | 2018-07-19 20:17 | MySQL Server: XA transactions | Closed (2877 days) | S3 | 5.7.16 | Any | Any | Transaction branch in inconsistent state after xa commit lock wait timeout |
111083 | 2023-05-19 7:07 | 2024-04-10 9:57 | MySQL Server: InnoDB storage engine | Verified (573 days) | S3 | 5.7* | Any | Any | why Bug #32617942 not fixed in 5.7*,it may cause lock wiat timeout |
104677 | 2021-08-20 12:04 | 2021-09-24 1:00 | MySQL Server: Group Replication | No Feedback (1176 days) | S3 | 8.0.23 | Debian | Any | Old joiner blocked for a long time in the failure recovery(Local recovery phase) |
110273 | 2023-03-06 3:12 | 2023-03-17 14:41 | MySQL Cluster NDB Operator | Not a Bug (636 days) | S1 | 1.0.1 | CentOS (7.9) | x86 (64) | NDB Cluster hangs on restarting management node 2 and shows InitialSystemRestart |
1866 | 2003-11-17 20:22 | 2003-11-18 5:14 | MySQL Server: InnoDB storage engine | Not a Bug (7695 days) | S2 | 4.0.16 | Linux (Linux) | Any | Attempting to insert into a gap you hold a row lock on can deadlock |
2385 | 2004-01-14 7:16 | 2004-04-02 11:01 | MySQL Server | Closed (7559 days) | S2 | 4.1 | Any (all) | Any | CREATE TABLE LIKE lacks locking on source and destination table |
2494 | 2004-01-23 11:31 | 2004-02-03 2:22 | MySQL Server | Won't fix (7618 days) | S2 | 4.0.17 | Windows (windows 2000) | Any | LOW_PRIORITY WRITE LOCK AFFECTING SUBSEQUENT WRITE LOCKS |
7389 | 2004-12-17 17:27 | 2005-01-03 12:57 | MySQL Server: Compiling | Closed (7283 days) | S1 | 5.0.3-pre | FreeBSD (FreeBSD, Linux/sparc and others) | Any | Linking mysqld fails because of undefined references in InnoDB |
12856 | 2005-08-29 18:29 | 2005-09-24 10:44 | MySQL Server: Replication | Closed (7019 days) | S1 | 5.0-wl1012 | Linux (Linux) | Any | RBR (ps-protocol) slave core in call to get_lock_data |
14737 | 2005-11-08 8:35 | 2005-11-08 9:53 | MySQL Server | Not a Bug (6974 days) | S3 | 5.0.15 | Linux (Linux) | Any | After "FLUSH TABLES WITH READ LOCK", Copying InnoDB files is really no problem? |
17017 | 2006-02-01 17:27 | 2006-02-01 20:51 | MySQL Server | Not a Bug (6889 days) | S3 | 4.1 | Linux (Linux debian) | Any | can lock the database in order to build a tar archive |
17812 | 2006-03-01 1:59 | 2006-03-09 2:48 | MySQL Cluster: Cluster (NDB) storage engine | Closed (6853 days) | S2 | 5.1.8 | Linux (Linux 32 Bit OS) | Any | Previous lock table for write causes "stray" lock although table is recreated |
27177 | 2007-03-15 15:14 | 2007-07-03 15:05 | MySQL Server: Documentation | Closed (6372 days) | S3 | All Versions | Any | Any | SHOW PROCESSLIST Syntax - add descriptions for state |
27281 | 2007-03-20 8:19 | 2008-04-11 17:33 | MySQL Server: Locking | No Feedback (6089 days) | S3 | 5.0 | Windows (windows) | Any | Warning at 'failed wait_for_lock' |
31477 | 2007-10-09 13:02 | 2008-03-02 9:19 | MySQL Cluster: Cluster (NDB) storage engine | Closed (6129 days) | S2 | 5.1.11 | Linux | Any | Transaction atomicity not as expected between insert and scan |
37848 | 2008-07-03 18:49 | 2012-05-18 20:19 | MySQL Server: Tests | Duplicate (5814 days) | S3 | 5.1.26-rc | Linux (RPM builds) | Any | Test relies on invalid timing/speed assumptions |
38740 | 2008-08-12 8:16 | 2010-05-26 18:00 | MySQL Server: Falcon storage engine | Unsupported (5314 days) | S5 | 6.0-falcon, rev. 2757 | Linux (SLES10SP1 (2.6.16.46-0.12-smp)) | Any | DBT3 Q13 query slow down so much in a concurrency environment when using Falcon |
40959 | 2008-11-23 20:24 | 2011-02-16 23:43 | MySQL Server: Documentation | Closed (5726 days) | S3 | any | Any | Any | Doc request - docs on LOCK TABLE is 'insiderish' |
48538 | 2009-11-04 17:40 | 2011-02-16 23:44 | MySQL Server: Locking | Closed (5394 days) | S3 | 6.0-codebase-bugfixing | Any | Any | Assertion in thr_lock() on LOAD DATA CONCURRENT INFILE |
55273 | 2010-07-15 6:07 | 2011-02-16 23:44 | MySQL Server: Locking | Closed (5136 days) | S3 | 5.5.6-bzr | Any | Any | FLUSH TABLE tm WITH READ LOCK for Merge table causes assert failure. |
56594 | 2010-09-06 12:54 | 2012-05-18 20:19 | MySQL Server: Locking | Duplicate (5197 days) | S2 | 5.5.6-m3 | Linux (icc x86) | Any | "Lock tables" is claimed not to work in the embedded server |
57335 | 2010-10-08 6:35 | 2011-02-16 23:44 | MySQL Enterprise Backup | Closed (5067 days) | S3 | 3.5.2 | Any | Any | abnormal termination of the backup process could leave the global lock active |
58220 | 2010-11-16 7:48 | 2016-07-28 17:50 | MySQL Cluster: NDB API | Not a Bug (3059 days) | S2 | mysql-5.1-telco-6.2 | Linux (2.6.18-194.11.4.el5) | Any | Unable to restart a node |
58618 | 2010-12-01 4:52 | 2022-12-04 20:45 | MySQL Server: Locking | Verified (5121 days) | S3 | 5.1.55-debug,5.5.9-debug | Any | Any | Warning: found too many locks at read: read lock with no write locks |
61965 | 2011-07-24 20:25 | 2011-08-03 22:41 | MySQL Server: Locking | Duplicate (4880 days) | S3 | 5.5 | Windows (XP) | Any | deadlock simultaneously insert on tbl1 and update on tbl2 from diff tx, innodb |
63665 | 2011-12-08 11:12 | 2011-12-08 13:27 | MySQL Server: InnoDB storage engine | Not a Bug (4753 days) | S2 | 14.14 Distrib 5.1.58, for deb | Linux (Debian sid) | Any | X row locks do not prevent an IX table lock, contrary to documentation |
65581 | 2012-06-11 10:07 | 2012-06-18 6:37 | MySQL Server: InnoDB storage engine | Verified (4567 days) | S3 | 5.5 | Any | Any | INSERT statement can be delayed by SELECT ... LOCK. |
70417 | 2013-09-25 11:04 | 2014-02-03 10:48 | MySQL Server: InnoDB storage engine | Closed (3965 days) | S5 | 5.6 | Any | Any | rw_lock_x_lock_func_nowait() calls os_thread_get_curr_id() mostly needlessly |
72887 | 2014-06-05 12:07 | 2014-12-10 14:13 | MySQL Server: Locking | Closed (3699 days) | S3 | 5.6.17-bzr | Any | Any | LOCK TABLES uses incorrect lock for implicitly used tables |
73733 | 2014-08-27 0:42 | 2014-10-01 15:06 | MySQL Server: Documentation | Closed (3725 days) | S3 | all | Any | Any | mysqldump manual page wrong about --all-databases and --single-transaction |
78867 | 2015-10-17 20:58 | 2015-10-20 14:49 | MySQL Server: Logging | Not a Bug (3341 days) | S3 | Any | Any | Having to lock tables by specifying every single alias is completely ridiculous | |
81106 | 2016-04-16 20:30 | 2016-05-18 1:00 | MySQL Server: InnoDB storage engine | No Feedback (3131 days) | S3 | 5.6.29 | CentOS (7.2) | Any | InnoDB: error in sec index entry update in |
85431 | 2017-03-14 7:05 | 2017-03-24 16:47 | MySQL Server: InnoDB storage engine | Not a Bug (2820 days) | S3 | mysql5.6.26 | Red Hat | Any | Execute “ if(not exists (select ..))” locked next record |
91671 | 2018-07-17 2:08 | 2018-11-27 12:05 | MySQL Server: Group Replication | Closed (2207 days) | S3 | 5.7.22 | Any | Any | stop slave sql_thread for channel 'group_replication_applier' could not return |
91977 | 2018-08-11 3:57 | 2023-12-09 19:04 | MySQL Server: InnoDB storage engine | Verified | S2 | 5.7.17 | Any | Any | Dropping Large Table Causes Semaphore Waits; No Other Work Possible |
93424 | 2018-11-30 10:58 | 2021-02-23 1:00 | MySQL Enterprise Monitor | No Feedback (1389 days) | S2 | 4.0.7 | Red Hat | Any | MEM upgrade - recreating existing keys and FKs |
95551 | 2019-05-28 12:50 | 2019-05-29 12:36 | MySQL Server: Locking | Not a Bug (2024 days) | S3 | 5.6, and 5.7 | Any | Any | MySQL GET_LOCK function is assigning lock to more than one thread |
97053 | 2019-09-27 13:57 | 2019-10-07 13:21 | MySQL Server | Not a Bug (1893 days) | S3 | 5.7.23 | CentOS (6.8) | Other (VMWare 64-bit) | Mysql instance crash after many "buffer pool occupied by lock heaps" messages |
110266 | 2023-03-03 6:40 | 2024-03-14 6:59 | MySQL Server: Group Replication | Can't repeat (646 days) | S3 | 8.0.27 | Any | Any | The secondary node of the mgr cluster has a deadlock |
113468 | 2023-12-20 4:07 | 2024-01-08 9:56 | MySQL Server: InnoDB storage engine | Verified (358 days) | S3 | 8.0 | Any | Any | The lock for unmatched record should be released but not in READ-COMMITTED |
113862 | 2024-02-02 6:22 | 2024-02-02 12:11 | MySQL Server: InnoDB storage engine | Can't repeat (314 days) | S3 | Any | Any | problem with btree latch acquisition when updating histogram | |
114085 | 2024-02-21 18:28 | 2024-02-22 22:47 | MySQL Server: Documentation | Closed (294 days) | S3 | 8.0 | Any | Any | Incorrect SQL example given for ALGORITHM=INSTANT |
116503 | 2024-10-30 6:55 | 2024-10-31 14:25 | MySQL Server | Not a Bug (42 days) | S3 | 8.0 | Any | Any | duplicate-key error will hold gap lock when there are multi unique keys |
33474 | 2007-12-21 23:02 | 2008-05-02 23:23 | MySQL Server: Falcon storage engine | Closed (6068 days) | S3 | 6.0 | Any | Any | falcon_lock_timeout is different from innodb_wait_lock_timeout |
17594 | 2006-02-20 19:41 | 2012-05-18 20:19 | MySQL Cluster: Cluster (NDB) storage engine | No Feedback (6817 days) | S1 | 5.1.7-beta | Various Unix | Any | Various NDB startup / restart problems |
97851 | 2019-12-02 16:15 | 2019-12-03 11:31 | Connector / ODBC | Not a Bug (1836 days) | S2 | 8.0.15 | Windows | Any | MS Access timeout using ODBC |
66533 | 2012-08-24 17:17 | 2012-11-09 18:12 | MySQL Server: Documentation | Closed (4416 days) | S3 | 5.5, 5.6 | Any | Any | lock_wait_timeout ignored with system tables and FLUSH TABLES WITH READ LOCK |
90959 | 2018-05-22 6:40 | 2018-06-11 11:23 | MySQL Server: Replication | Won't fix (2376 days) | S2 | 5.7.22 | Any | Any | XA transactions can lock forever if a gap lock is also taken on the slave |
29068 | 2007-06-13 10:38 | 2016-01-03 20:45 | MySQL Server: InnoDB storage engine | No Feedback (6348 days) | S2 | 5.0.32 | Linux | Any | InnoDB long semaphore wait brings down server |
42429 | 2009-01-28 16:35 | 2009-05-07 16:58 | MySQL Server: Falcon storage engine | Closed (5698 days) | S3 | 6.0.9 | Any | Any | Falcon crash in Table::checkUniqueRecordVersion |
45160 | 2009-05-28 14:28 | 2011-02-16 23:44 | MySQL Server: InnoDB storage engine | Closed (5644 days) | S2 | 5.0.22 | Linux ( 2.6.18-53.el5) | Any | Mysql crashes after getting hanged with following error in error log |
80955 | 2016-04-05 3:07 | 2018-04-16 12:52 | MySQL Server: InnoDB Plugin storage engine | Not a Bug (2432 days) | S3 | 5.7.11 | CentOS | Any | innodb master thread "making checkpoint" but is hang |
93366 | 2018-11-27 15:11 | 2018-11-27 15:38 | MySQL Server | Unsupported (2207 days) | S2 | 5.1.46-log | Linux | Any | a too long 4906.00 seconds wait at buf0buf.c |
97955 | 2019-12-11 4:26 | 2019-12-11 11:28 | MySQL Server: Replication | Verified (1828 days) | S2 | 5.6/5.7/8.0, 8.0.18 | Any | Any | Multi 'show binary logs' statement may block transaction commit |
54584 | 2010-06-17 14:06 | 2017-11-08 14:12 | MySQL Server: Query Cache | Won't fix (2715 days) | S1 | Any | Any | Any | query cache can lock DML threads if a reader is slow |
50178 | 2010-01-08 10:29 | 2023-02-12 20:45 | MySQL Server: Backup | Duplicate (5449 days) | S3 | Any | Any | rpl_backup_multi fails on PB2 with various symptoms | |
57973 | 2010-11-04 11:37 | 2021-03-04 14:30 | MySQL Server: InnoDB Plugin storage engine | Won't fix (4136 days) | S2 | 1.0.7, 1.0.13 | Any | Any | UPDATE tries to lock rows not visible to read view |
53439 | 2010-05-05 15:32 | 2011-02-16 23:44 | Connector / NET | Closed (5266 days) | S3 | 6.3.2 (actually revision 760+) | Any | Any | EndOfStreamException is not thrown when net_write_timeout exceeded |
41613 | 2008-12-19 5:13 | 2011-02-16 23:43 | MySQL Server: Replication | Closed (5509 days) | S3 | 5.1,6.0 | Any | Any | Slave I/O status inconsistent between SHOW SLAVE STATUS and START SLAVE |
42359 | 2009-01-26 22:31 | 2009-06-03 23:29 | MySQL Server: Backup | Closed (5671 days) | S3 | mysql-6.0-backup | Linux | Any | Restore fails if uncommitted data from falcon table is included in backup image. |
28704 | 2007-05-27 15:00 | 2012-09-13 10:49 | Connector / NET | Not a Bug (6403 days) | S3 | 1.08 | Windows | Any | Where to restart transaction ? |
42475 | 2009-01-30 12:51 | 2009-05-15 13:02 | MySQL Server: Falcon storage engine | Closed (5690 days) | S3 | 6.0.9 | Any | Any | Falcon can crash in Sync::findLocks after a timeout. |
65777 | 2012-06-30 20:01 | 2018-10-12 6:52 | MySQL Server: MyISAM storage engine | Verified (3303 days) | S2 | 5.5.21 | Other (mac-10.7.1 & debian) | Any | killing 'Flush tables' in 'waiting for table flush' makes other queries block |
77390 | 2015-06-17 12:54 | 2017-04-12 16:27 | MySQL Server: Documentation | Closed (2801 days) | S3 | 5.6 | Any | Any | Manual does not explain a "deadlock" case of online ALTER |
106818 | 2022-03-24 11:23 | 2022-06-07 2:29 | MySQL Server: Replication | Verified (919 days) | S2 | 5.7,8.0, 5.7.37 | Any | Any | Replication may fail when XA transactions use replace into statements |
31575 | 2007-10-13 1:25 | 2011-02-16 23:43 | MySQL Server: Installing | Can't repeat (5846 days) | S3 | 5.0.45, 5.0, 5.1, 6.0 bzr | Linux | Any | MySQL startup script hangs if mysqld was killed |
46832 | 2009-08-20 13:04 | 2011-02-16 23:44 | MySQL Server: InnoDB storage engine | Unsupported (5593 days) | S1 | 5.0.84 | FreeBSD (FreeBSD www-int2 7.1-RELEASE FreeBSD 7.1-RELEASE #0: Thu Jan 1 14:37:25 UTC 2009 root@logan.cse) | Any | Crach during creating InnoDB table |
64683 | 2012-03-18 10:22 | 2016-12-09 8:56 | MySQL Server: Installing | Can't repeat (2925 days) | S1 | 5.6.5 | MacOS (10.7.3) | Any | installing with mysql_install_db fails with huge key-buffer |
44841 | 2009-05-13 9:39 | 2013-01-14 18:23 | MySQL Server: InnoDB storage engine | Can't repeat (4350 days) | S1 | 5.1.34-0, 5.1.43sp1 | Linux (SUSE Linux Enterprise Server 10 SP2 (x86_64)) | Any | purge thread + rollback hang forever waiting on dict_operation_lock semaphore |
93761 | 2018-12-29 2:45 | 2019-03-20 7:38 | MySQL Server: Replication | Verified (2105 days) | S2 | 5.7.22 | Red Hat (6.5) | Any | optimize table cause the slave MTS deadlock! |
96317 | 2019-07-24 13:52 | 2019-08-02 17:55 | MySQL Server: Locking | Not a Bug (1960 days) | S3 | 5.7.18 | Any | Any | Lock wait time out is not occuring for INSERT query |
98295 | 2020-01-20 11:00 | 2023-02-01 7:55 | MySQL Server: InnoDB storage engine | Closed (1772 days) | S3 | 5.7.23 | Any | Any | Innodb internal deadlock cause a long wait semaphore, and a mysqld crash |
112532 | 2023-09-27 3:14 | 2024-07-02 19:34 | MySQL Server: InnoDB storage engine | Closed (364 days) | S3 | 8.0 | Any | Any | Innodb_row_lock_current_waits values show non-zero when there is no lock |
459 | 2003-05-20 8:01 | 2003-06-30 4:42 | MySQL Server: Compiling | No Feedback (7836 days) | S3 | 4.0.12 | HP/UX (HPUX 11.00) | Any | Data linkage table overflow in source build of innobase |
4770 | 2004-07-27 16:57 | 2004-07-27 17:39 | Connector / J | Not a Bug (7443 days) | S1 | mysql-connector-java-3.0.14 | Windows (MS windows) | Any | Java JDBC driver has dead lock |
29560 | 2007-07-05 2:06 | 2011-02-16 23:43 | MySQL Server: InnoDB storage engine | Closed (5923 days) | S2 | 5.0.41 | Any (Multi CPU) | Any | InnoDB >= 5.0.30 hangs on adaptive hash rw-lock 'waiting for an X-lock' |
65468 | 2012-05-30 20:48 | 2013-03-01 1:00 | MySQL Server: InnoDB storage engine | No Feedback (4305 days) | S2 | 5.5.14-enterprise-commercial-advanced-lo | Solaris (innodb) | Any | A couple of rows in tbl had write locks that couldn't be cleared |
70863 | 2013-11-08 14:50 | 2013-11-08 23:27 | MySQL Server: Errors | Verified (4052 days) | S3 | 5.6.14 | Any | Any | Wrong error message on a failed ALTER .. LOCK=NONE attempt |
95232 | 2019-05-02 22:45 | 2019-05-03 8:05 | MySQL Server: Errors | Verified (2050 days) | S3 | 5.7.23, 5.7.26 | Any | Any | The text of error message 1846 and the online DDL doc table should be updated |
9187 | 2005-03-15 10:27 | 2005-06-30 16:59 | MySQL Server | No Feedback (7105 days) | S3 | 4.1.10 | Windows (xp pro sp2) | Any | Adnormal network disconnect |
9906 | 2005-04-14 14:25 | 2011-02-16 23:43 | Connector / J | Won't fix (5510 days) | S3 | 3.1.7 | Linux (linux) | Any | Connector/J: QueryTimeout is ignored in Statement |
11290 | 2005-06-13 14:49 | 2005-06-14 12:47 | MySQL Cluster: Cluster (NDB) storage engine | Closed (7121 days) | S3 | 4.1-> | Any (any) | Any | TransactionInactiveTimeout = 0 does not result in infinite timeout |
15440 | 2005-12-02 15:24 | 2006-08-30 19:56 | MySQL Server: Embedded Library ( libmysqld ) | Closed (6679 days) | S3 | 4.1.16 | Any (all) | Any | Timeout in "embedded" test run of "handler" |
16848 | 2006-01-27 18:09 | 2006-02-02 16:31 | Connector / J | Not a Bug (6888 days) | S3 | 3.1.10 | Linux (Linux JDK1.4.2) | Any | Hang in SocketRead |
32784 | 2007-11-27 18:22 | 2011-02-16 23:43 | MySQL Server: Tests | Closed (5699 days) | S5 | 5.0.51-54 | Other (see bug text) | Any | Timeout in test "innodb_charset": InnoDB much slower than other handlers |
33771 | 2008-01-09 14:43 | 2008-04-26 3:28 | MySQL Server: General | Closed (6074 days) | S2 | 6.0 BK | Linux (Fedora 8) | Any | -mysqld=--thread-handling=pool-of-threads causes the tests to fail |
34703 | 2008-02-20 19:46 | 2012-09-13 8:47 | Connector / J | Closed (6130 days) | S3 | 5.1.5 | Windows (WinXP) | Any | isValild() aborts Connection on timeout |
37803 | 2008-07-02 11:09 | 2008-10-17 17:40 | MySQL Server: Tests | Closed (5900 days) | S3 | 5.1.26,6.0.6 | Any | Any | Test "partition_alter2_innodb" exhausts resources (time and/or memory) |
37811 | 2008-07-02 17:25 | 2023-03-15 15:14 | MySQL Server: mysqldump Command-line Client | Verified (5425 days) | S3 | 5.0,5.1,6.0.6 | HP/UX (11.31, 32 + 64 bit) | Any | "mysqldump" command hangs on HP-UX 11.31 (specifically) |
44221 | 2009-04-12 12:59 | 2009-05-14 11:06 | MySQL Query Browser | Unsupported (5691 days) | S3 | 5.0r12-9.fc10 | Linux (Fedora 10) | Any | GConf Error when using mysql-query-browser |
45842 | 2009-06-30 7:21 | 2021-05-02 20:45 | Tests: Cluster | Verified | S3 | 5.4 | Any | Any | funcs_1.is_cml_ndb crashes sporadically (disabled) |
46029 | 2009-07-08 7:18 | 2018-04-23 17:23 | Tests: Replication | Can't repeat (3929 days) | S3 | 5.1-bugteam, 5.1 | Any | Any | rpl_innodb_bug28430 times out on certain pb2 hosts |
47478 | 2009-09-21 10:24 | 2014-03-01 6:18 | Tests: Replication | Can't repeat (3939 days) | S3 | 5.1 | Any | Any | PB2: rpl_extraColmaster_innodb sporadic failures (timeout) |
48318 | 2009-10-26 15:36 | 2011-02-16 23:44 | MySQL Server: Logging | Unsupported (5420 days) | S3 | 5.1.40 | MacOS (10.4, PPC-64) | Any | The "debug_sync" mechanism doesn't work correctly (on one platform) |
57350 | 2010-10-09 20:16 | 2014-06-29 20:45 | Connector / ODBC | Verified (4201 days) | S2 | 3.51, 5.1 and 5.2 | Windows (any) | Any | Connection timeout cannot be set, please add to connection string options |
57503 | 2010-10-17 12:53 | 2013-08-19 19:16 | MySQL Cluster: Cluster/J | Can't repeat (4133 days) | S3 | mysql-5.1-telco-7.1 | Linux | Any | JpaCluster on Glassfish using persistence.xml: Can not connect to 192.168.56.101 |
61091 | 2011-05-08 1:57 | 2011-05-08 18:38 | MySQL Server: Replication | Can't repeat (4967 days) | S2 | 5.1 bzr | Windows | Any | rpl_stop_slave hangs on Windows |
61595 | 2011-06-22 7:36 | 2013-12-22 23:58 | MySQL Server: Tests | Verified (4008 days) | S3 | 5.1, 5.5 | Any | Any | [PATCH] mysql-test/include/wait_for_slave_param.inc timeout logic is incorrect |
63601 | 2011-12-05 12:06 | 2012-01-19 11:00 | Connector / ODBC | Duplicate (4711 days) | S1 | all | Any | Any | Connection Timeout Parameter in MyODBC Connector ignored |
69416 | 2013-06-06 14:17 | 2017-12-22 4:40 | Connector / ODBC | Closed (2547 days) | S2 | 5.2.5 | Windows (Windows 2008 Server Standard Edition) | Any | MySQL Connector/ODBC 5.2.5 - Command Timeout does not work |
73882 | 2014-09-11 6:06 | 2014-09-14 19:11 | MySQL Server | Can't repeat (3742 days) | S3 | 5.6 | Any | Any | MySql.Data.MySqlClient.MySqlException (0x80004005): Timeout expired. |
76243 | 2015-03-10 13:17 | 2019-08-09 12:28 | MySQL Server | Can't repeat (1952 days) | S3 | 5.5.41 | Linux (RH) | Any | rc script does not respect both delimiters for service timeout startup |
82365 | 2016-07-27 21:59 | 2021-11-23 20:58 | Connector / NET | Not a Bug (1115 days) | S2 | 6.9.9 | Windows | Any | Command Timeout 1 second takes 3 seconds to timeout |
84475 | 2017-01-11 22:48 | 2017-01-23 12:19 | MySQL Server: Replication | Not a Bug (2880 days) | S3 | 5.7.11 | Ubuntu | Any | Frequent slave reconnects and zombies thread warnings when master is idle |
89740 | 2018-02-21 3:59 | 2018-02-26 22:59 | MySQL Router | Closed (2481 days) | S2 | 2.1.5 | CentOS (7.2) | x86 | "Timeout reached trying to connect to MySQL Server" occurs too frequently |
94142 | 2019-01-30 14:19 | 2019-02-01 11:19 | MySQL Workbench: Migration | Verified (2141 days) | S3 | 8 | Windows | Any | INSERT INTO `migration`.`nombres` (`nombre`) VALUES ('\�\�\���\�\�\����\��\�\�\� |
103229 | 2021-04-06 21:39 | 2021-05-23 1:00 | Connector / ODBC | No Feedback (1300 days) | S1 | 8.0.23 | Any | Any | Timeout during statement fetch causes silent loss of trailing rows |
110517 | 2023-03-27 20:34 | 2023-05-03 9:37 | MySQL Workbench: Migration | Can't repeat (589 days) | S3 | 8.0.28 | Windows | Any | Misuse of wbcopytables.exe in migration wizard |
112884 | 2023-10-30 15:02 | 2023-12-15 23:04 | Connector / J | Closed (363 days) | S3 | 8.1.0 | Any | Any | Setting a large timeout leads to errors when executing SQL. |
115788 | 2024-08-06 19:27 | 2024-08-19 21:29 | Connector / Python | Verified | S2 | 8.4.0 | Any | Any | Option `connection_timeout` is overwritten and works as "query" timeout instead |
60804 | 2011-04-08 10:06 | 2011-05-08 23:00 | MySQL Server | No Feedback (4967 days) | S1 | 5.0.27 | Linux (sles9) | Any | Mysql got signal 11 |
21491 | 2006-08-07 20:31 | 2006-08-16 12:50 | MySQL Server: Documentation | Closed (6693 days) | S3 | 5.1 | Any | --master-connect-retry should talk about --slave-net-timeout | |
32172 | 2007-11-07 21:06 | 2007-12-06 13:21 | Tests: Server | Closed (6216 days) | S3 | 5.1, 6.0 | Windows | Any | information_schema test fails with wait_condition timeout |
45632 | 2009-06-20 7:49 | 2018-09-07 11:55 | MySQL Server: Query Cache | Won't fix (2288 days) | S3 | 5.1 bzr | Linux (x86) | Any | query_cache_debug.test fails |
56836 | 2010-09-17 9:22 | 2014-07-29 15:15 | MySQL Server: Locking | Closed (3789 days) | S3 | 5.1.50, 5.5.37, 5.6.17 | Any (See description) | Any | GET_LOCK() timeout behaves differently on differing platforms |
76900 | 2015-04-30 9:39 | 2015-05-08 8:23 | MySQL Server: Packaging | Closed (3506 days) | S3 | 5.7.7 | Linux (CentOS 6) | Any | increase stop timeout of community rpm shutdown script /etc/init.d/mysqld |
84728 | 2017-01-31 8:22 | 2017-07-11 11:08 | MySQL Server: Group Replication | Closed (2711 days) | S2 | 5.7.17 | Any | Any | Not Possible To Avoid MySQL From Starting When GR Cannot Start |
86956 | 2017-07-05 12:04 | 2017-08-25 10:48 | MySQL Server: Group Replication | Verified (2716 days) | S3 | 5.7.18 | Any | Any | Joining group timeout on permissions error |
99628 | 2020-05-19 9:16 | 2020-05-28 14:59 | MySQL Server: Replication | Verified (1666 days) | S2 | 8.0.* | Any | Any | semi sync master not handle ack packet correctly when recv packet timeout |
16481 | 2006-01-13 14:07 | 2006-02-14 9:15 | MySQL Cluster: Cluster (NDB) storage engine | Closed (6876 days) | S1 | 5.1.6-alpha | Linux (Linux) | Any | DD: Cluster fails during load of TPC-B tables |
20647 | 2006-06-23 5:39 | 2006-06-23 7:37 | MySQL Server | Not a Bug (6747 days) | S1 | 4.1.15 | Solaris (Solaris 8) | Any | Mysql which is originally bound to IP, shift to IP1 without restarting |
41897 | 2009-01-06 16:49 | 2021-05-02 20:45 | MySQL Cluster: Replication | No Feedback (5682 days) | S2 | mysql-5.1-telco-6.3 | Linux (debian etch) | Any | Table events are no more collected for one table until we restart the mysqld |
45119 | 2009-05-27 8:44 | 2021-05-02 20:45 | MySQL Cluster: Disk Data | No Feedback (5531 days) | S3 | mysql-5.1-telco-7.06 | Linux | Any | Segmentation Fault on update of indexed column in mixed disk-memory column table |
48431 | 2009-10-30 9:31 | 2011-02-16 23:44 | MySQL Cluster: Cluster (NDB) storage engine | Closed (5463 days) | S3 | mysql-5.1-telco-6.3 | Linux (RHEL 5.2) | Any | Loop in linked list when printing crash dump |
58129 | 2010-11-11 1:31 | 2011-02-16 23:44 | MySQL Server: Row Based Replication ( RBR ) | Closed (5089 days) | S3 | next-mr, mysql-trunk | Any | Any | Valgrind error when sanity check fails in read_log_event |
79081 | 2015-11-02 20:47 | 2017-07-02 1:00 | MySQL Workbench | No Feedback (2721 days) | S2 | 6.3.6 | Windows (When connecting to mySQL server running raspbian) | Any | Connection successful, cannot to database. |
63122 | 2011-11-06 22:51 | 2020-06-18 9:14 | MySQL Server: InnoDB storage engine | Verified (4783 days) | S3 | 5.0+ | Any | Any | "Searched SQL update" seems to release lock got by "select for update" |
21105 | 2006-07-18 7:16 | 2006-10-11 11:41 | MySQL Server | No Feedback (6637 days) | S3 | 5.0.21 | Linux (SLES 9 PPC) | Any | Connections are not kill by server after timeout |
13524 | 2005-09-27 12:48 | 2005-11-24 0:05 | MySQL Server | Closed (6958 days) | S1 | 5.0.14-rc-nightly-20050926 | Linux (Linux Suse SLES 9 FP 1) | Any | lock timeout gives incorrect warning on open cursor |
57232 | 2010-10-04 22:44 | 2011-02-16 23:44 | MySQL Server: InnoDB storage engine | Closed (5126 days) | S1 | All | Any | Any | Possible corruption during UNDO phase at startup after crash recovery |
83986 | 2016-11-28 13:36 | 2016-12-08 17:43 | MySQL Server: InnoDB Plugin storage engine | Duplicate (2926 days) | S3 | 5.7.16 | Windows | Any | MySql crashes if lock is put, but never released if some specific scenario is on |
2896 | 2004-02-19 14:25 | 2004-02-20 3:57 | MySQL Administrator | Closed (7601 days) | S3 | 1.0.1a ALPHA | Any (All) | Any | Value name for Wait Timeout is 'wait_amount' instead of 'wait_timeout' |
8786 | 2005-02-24 17:46 | 2005-02-25 9:18 | MySQL Cluster: Cluster (NDB) storage engine | Closed (7230 days) | S3 | Any | ndb_autodiscover, drop index can fail, wait 2 minutes timeout | ||
50167 | 2010-01-08 0:18 | 2013-01-11 12:23 | Tests: Backup | Unsupported (4353 days) | S3 | 5.6.0 (mysql-backup-backport) | Any | Any | backup_triggers_and_events fails with: "backup wait timeout has expired for..." |
68250 | 2013-02-02 0:35 | 2013-04-23 13:10 | MySQL Server: Replication | Not a Bug (4251 days) | S3 | 5.6.9 | Any | Any | Current semi-synchronous replication may cause deadlock |
68420 | 2013-02-18 19:18 | 2013-02-18 19:33 | MySQL Server: Command-line Clients | Verified (4315 days) | S3 | 5.5+ | Any | Any | MySQL programs produce out of order --help entries |
89042 | 2017-12-23 6:47 | 2018-05-31 14:53 | MySQL Server: Group Replication | Closed (2485 days) | S2 | 8.0.5 | Any | Any | START GR HANGS AND WITH THAT NO NEW CONNECTION IS ALLOWED ON THAT SERVER |
96244 | 2019-07-18 7:25 | 2019-12-02 14:28 | MySQL Server: Group Replication | No Feedback (1900 days) | S3 | 8.0.16 | Ubuntu (Ubuntu 18.04 in Digital Ocean) | Any | [GCS] The member was unable to join the group. Local port: 33061 |
104491 | 2021-07-30 22:12 | 2023-04-18 15:07 | MySQL Server: Replication | Closed (878 days) | S3 | 8.0.20 | Any | Any | Contribution by Facebook: Fix race between binlog sender heartbeat timeout ... |
106430 | 2022-02-10 8:41 | 2022-02-17 14:31 | MySQL Server: Group Replication | Can't repeat (1029 days) | S3 | Any (OKD) | x86 | Timeout on wait for view after joining group | |
109580 | 2023-01-11 8:02 | 2023-01-11 15:23 | MySQL Server: Group Replication | Not a Bug (701 days) | S3 | 5.7.40 | Any | Any | Timeout on wait for view after joining group |
109615 | 2023-01-13 7:14 | 2023-01-17 19:05 | MySQL Server: Group Replication | Not a Bug (695 days) | S3 | 5.7.40 | Any | Any | Timeout on wait for view after joining group |
50230 | 2010-01-11 13:07 | 2010-01-19 11:35 | Connector / NET | Not a Bug (5441 days) | S2 | 6.2.0.0 | Windows (XP Service Pack 3) | Any | MySqlBulkLoader.load() |
39994 | 2008-10-13 6:56 | 2011-02-16 23:43 | MySQL Server: Documentation | Closed (5798 days) | S3 | 6.0.6-alpha-community | Windows | Any | innodb_locks_unsafe_for_binlog |
41579 | 2008-12-18 5:25 | 2008-12-18 8:53 | MySQL Cluster: Replication | Not a Bug (5838 days) | S2 | 5.1.23-ndb-6.2.15-log | Linux | Any | Replication from NDBCLUSTER to other storage engines problem |
49084 | 2009-11-25 2:46 | 2011-02-16 23:44 | MySQL Server: InnoDB storage engine | Duplicate (5467 days) | S1 | 5.0.51 | Linux (RHEL 4.7) | Any | Dead Lock caused by Waiting Auto-INC LOCK |
55722 | 2010-08-03 21:45 | 2011-02-16 23:44 | MySQL Server: InnoDB storage engine | Duplicate (5239 days) | S2 | 5.1.42, 5.1.45 | Solaris (also Linux Debian) | Any | Drop a large innodb table hung the server and lead to server crash |
64325 | 2012-02-14 18:07 | 2012-02-15 12:05 | MySQL Server: Replication | Duplicate (4684 days) | S2 | 5.1.49 | Linux (CentOS 5.5) | Any | MySQL Replication not applying changes |
87827 | 2017-09-21 14:09 | 2023-11-02 6:39 | MySQL Server: InnoDB storage engine | Closed (2519 days) | S5 | 8.0.3 | Any | Any | Performance regression in "create table" speed and scalability in 8.0.3 |
89643 | 2018-02-13 7:53 | 2019-03-12 0:58 | MySQL Cluster: Cluster (NDB) storage engine | Closed (2102 days) | S3 | 7.6.4 | Any | Any | MAX_EXECUTION_TIME hint doesn't work if waiting on ndbcluster global schema lock |
101407 | 2020-10-31 12:44 | 2020-11-04 12:49 | MySQL Server: C API (client library) | Not a Bug (1499 days) | S3 | 5.7 | Linux | Any | cant get a exist data. even no error throw by api(php) |
116760 | 2024-11-23 13:44 | 2024-11-25 7:24 | MySQL Server: InnoDB storage engine | Verified (17 days) | S3 | 8.0.40,8.4.3,9.1.0 | Any | Any | Page deadlock occured when searching BTREE after nullable cols dropped by INSTAN |
68992 | 2013-04-18 6:09 | 2013-09-12 1:00 | MySQL Server: Replication | No Feedback (4110 days) | S1 | 5.6.10 | Windows (Server 2012) | Any | MySQL |
82328 | 2016-07-24 22:35 | 2016-07-26 14:17 | MySQL Server: Locking | Not a Bug (3061 days) | S5 | 5.6.27 | Linux | Any | Waiting in end_thr_alarm can be avoided for performance improvement |
181 | 2003-03-22 8:28 | 2003-03-22 13:43 | MySQL Server: Replication | Closed (7936 days) | S1 | 4.0.12 | FreeBSD (Freebsd 4.5/4.7) | Any | Error replicating LOAD DATA INFILE in 4.0.12 |
1666 | 2003-10-26 6:47 | 2024-10-27 20:45 | MySQLCC | Duplicate (7694 days) | S3 | 0.9.2beta | Windows (Win2K) | Any | Control Center crash on max _connect_errors exceeded |
1818 | 2003-11-12 10:05 | 2004-06-21 11:11 | MySQL Server: Replication | Not a Bug (7479 days) | S2 | 4.0.19 | Linux (RedHat 7.2 or 7.3) | Any | Replication failed between 4.0.16-4.0.16 on Linux. Reproductible. |
2556 | 2004-01-29 8:21 | 2004-03-06 12:31 | MySQL Server: Replication | No Feedback (7586 days) | S2 | 4.0.17 | Linux (Mandrake linux 9.2) | Any | Error in Log_event::read_log_event(): 'Event too big', data_len: 808333356, eve |
9022 | 2005-03-07 14:21 | 2005-03-09 23:06 | MySQL Server | Closed (7218 days) | S1 | 5.0.3-bk | Linux (GNU/Linux) | Any | Server crashes when max_connection is exceeded |
9089 | 2005-03-10 6:43 | 2005-03-10 7:19 | MySQL Cluster: Cluster (NDB) storage engine | Closed (7217 days) | S3 | 4.10 | Any | MaxOpen files exceeded | |
21702 | 2006-08-17 18:05 | 2006-09-26 9:15 | MySQL Server | No Feedback (6652 days) | S1 | 4.1.18 | HP/UX (HP-UX) | Any | Innodb crash on HP-UX Itanium |
26201 | 2007-02-08 22:25 | 2016-10-16 20:45 | MySQL Server: Replication | Duplicate (6405 days) | S3 | 5.0, 4.1 BK, 5.1 BK | Any (any) | Any | Replication broke on packet size, but show slave status does not indicate this |
27956 | 2007-04-19 14:38 | 2015-03-15 20:45 | MySQL Server: Replication | No Feedback (6382 days) | S3 | 5.1.16 | MacOS | Any | corrupt binlog gives incorrect error message |
29272 | 2007-06-21 14:58 | 2007-06-22 0:23 | MySQL Server: Replication | Not a Bug (6383 days) | S2 | 5.0.41 | Linux | Any | Replicate errors with 1236 after harddrive upgrade in 5.0.41 |
30555 | 2007-08-22 6:11 | 2011-02-16 23:43 | MySQL Cluster: Cluster (NDB) storage engine | Won't fix (5775 days) | S2 | 5.0.45 | Linux (WhiteBox 4 2.6.9-5.ELsmp) | Any | MaxNoOfOpenFiles Exceeded Then Node Shutsdown |
55231 | 2010-07-13 20:40 | 2023-12-18 16:27 | MySQL Server: Replication | In progress (5132 days) | S2 | 5.1.48, 5.7.22 | Any | Any | COM_BINLOG_DUMP needs to accept 64-bit positions else slaves can break |
55807 | 2010-08-06 18:14 | 2010-08-17 18:23 | MySQL Server: Replication | Not a Bug (5231 days) | S1 | 4.1.22, 5.1.40 | Windows | Any | Last_IO_Errno: 1236 and mysqlbinlog unable to read log with --start-position=N |
57563 | 2010-10-19 11:17 | 2011-02-16 23:44 | MySQL Cluster: Cluster (NDB) storage engine | Closed (5167 days) | S2 | Linux | Any | m_gcp_rep_counter ring buffer capacity exceeded | |
74167 | 2014-10-01 1:06 | 2014-10-22 13:52 | MySQL Server: InnoDB storage engine | Closed (3704 days) | S3 | 5.7.5 | Linux | Any | call to posix_fallocate from fil_extend_space_to_desired_size fails |
97398 | 2019-10-28 13:57 | 2019-11-05 15:49 | MySQL Server: Documentation | Closed (1864 days) | S3 | 5.7 | Any | Any | Wrong documentation for innodb_max_purge_lag. |
102477 | 2021-02-04 10:54 | 2021-02-07 3:37 | MySQL Server | Unsupported (1407 days) | S3 | Linux | Any | When one row of result exceeded 4GB, the server does not response appropriately | |
105878 | 2021-12-13 13:32 | 2022-10-25 16:18 | MySQL Server: Federated storage engine | Unsupported (1095 days) | S3 | 8.0.27 | Any | Any | FEDERATED engine not reconnecting on wait_timeout exceeded |
111471 | 2023-06-17 14:28 | 2023-06-18 13:26 | MySQL Server: Optimizer | Verified (543 days) | S2 | 8.0.33 | Ubuntu | x86 | Unexpected Error: Memory capacity exceeded |
108426 | 2022-09-08 12:36 | 2022-12-06 11:06 | Shell AdminAPI InnoDB Cluster / ReplicaSet | Closed (737 days) | S3 | 8.0.30 | Any | Any | Adding instance to a new replica cluster under load results in errors |
37364 | 2008-06-12 12:52 | 2015-11-07 7:30 | MySQL Server: InnoDB storage engine | Can't repeat (3323 days) | S2 | 5.0.51a, 5.5.21 | Linux (Linux ES release 4) | Any | InnoDB: error in sec index entry update |
28497 | 2007-05-17 12:04 | 2007-06-18 16:30 | MySQL Server: Tests | Closed (6387 days) | S3 | 5.1 | Linux | Any | wait_for_slave_to_stop can cause random replication mysql-test failures |
44146 | 2009-04-08 9:34 | 2013-10-10 15:50 | MySQL Cluster: Cluster (NDB) storage engine | Closed (4081 days) | S2 | mysql-5.1-telco-7.0 | Solaris | Any | ndb_mgm -e " START BACKUP WAIT STARTED" not works as documented |
48402 | 2009-10-29 11:00 | 2011-02-16 23:44 | MySQL Cluster: Cluster (NDB) storage engine | Closed (5229 days) | S3 | mysql-5.1-telco-7.0 | Linux | Any | --ndb-wait-* options do not set mysqld variables |
58512 | 2010-11-26 8:47 | 2011-02-16 23:44 | MySQL Server: Performance Schema | Closed (5089 days) | S3 | 5.5 | Any | Any | Performance_schema.myisam_file_io fails sporadically in PB2 |
68009 | 2013-01-02 9:22 | 2022-11-05 12:45 | MySQL Server: Performance Schema | Duplicate (4354 days) | S2 | 5.5.28, 5.5.29 | Any | Any | Floating point exception in "insert_events_waits_history_long" |
68854 | 2013-04-03 9:54 | 2013-06-27 21:41 | MySQL Cluster: Cluster (NDB) storage engine | Closed (4186 days) | S3 | mysql-cluster-7.2.10, 7.2.12 | Linux | Any | START BACKUP WAIT STARTED waits forever on backup errors |
71047 | 2013-12-02 4:50 | 2014-09-30 12:21 | MySQL Server: Replication | Closed (3758 days) | S3 | 5.7.2, 5.7.3-m13 | Any | Any | shutdown hang if semisync is enabled and slave abort |
77577 | 2015-07-01 10:51 | 2015-07-15 12:18 | MySQL Server: Performance Schema | Closed (3439 days) | S3 | 5.5, 5.6, 5.7 | Any | Any | setup_timers initialization assumes CYCLE timer is always available |
80979 | 2016-04-06 14:25 | 2022-01-17 9:31 | MySQL Server: InnoDB storage engine | Verified (3171 days) | S3 | 5.7 | Any | Any | Doublewrite buffer event waits should be annotated for Performance Schema |
90604 | 2018-04-24 13:50 | 2018-04-25 4:41 | MySQL Server: InnoDB storage engine | Verified (2423 days) | S5 | 5.7 | CentOS | Any | ut_rnd_ulint_counter () : Default delay for spin wait gives better performance |
98549 | 2020-02-11 8:49 | 2020-04-25 1:00 | MySQL Cluster: Cluster (NDB) storage engine | No Feedback (1693 days) | S2 | 5.7.21 | CentOS (CentOS 7) | x86 | Node1 Crash on cluster mysql NDB |
99417 | 2020-05-02 11:13 | 2020-11-19 18:07 | MySQL Workbench: SQL Editor | Verified (1683 days) | S2 | 8.0.19-1ubuntu18.04, 8.0.20 | Debian (10 Buster) | x86 (64bit) | MySQL Workbench: Unresponsive several minutes after each "use DB" statement |
103636 | 2021-05-10 7:23 | 2023-04-28 5:55 | MySQL Server: Replication | Closed (1126 days) | S3 | 8.0.24 | Any | Any | Slave hangs with slave_preserve_commit_order On |
104186 | 2021-07-01 15:04 | 2022-01-25 17:07 | MySQL Server: Optimizer | Closed (1178 days) | S5 | 8.0 | Any | Any | Too few chunk files are created for hybrid hash join |
19171 | 2006-04-18 18:12 | 2006-04-20 11:08 | MySQL Server | Can't repeat (6811 days) | S2 | 5.1.9-beta | Solaris (Solaris 8 Sparc (32)) | Any | Test "information_schema": Incorrect key file for table './mysql/event' |
83557 | 2016-10-27 3:08 | 2016-10-27 9:03 | MySQL Server: InnoDB storage engine | Verified (2968 days) | S1 | 5.7.16 | CentOS | Any | Can't use LOCK=NONE to drop columns in table with virtual columns |
88628 | 2017-11-23 16:03 | 2018-01-10 16:09 | MySQL Server: Documentation | Closed (2528 days) | S2 | 5.7.17 | Solaris | Any | increased memory allocation querying IS.TABLES and FLUSH TABLES ... FOR EXPORT |
99095 | 2020-03-27 5:39 | 2020-03-31 13:32 | MySQL Server | Not a Bug (1718 days) | S3 | 5.7.24-log | CentOS (7.4.1708) | x86 | The n bits which transaction waiting for X lock is already locked by itself |
107029 | 2022-04-14 22:42 | 2022-04-15 13:19 | MySQL Server: Locking | Not a Bug (972 days) | S3 | 8.0.28 | Any | Any | deadlock when using trigger logic implementation |
68568 | 2013-03-05 3:17 | 2021-09-15 20:49 | MySQL Server: Replication | Verified (4046 days) | S3 | 5.6.10 | Linux (CentOS 5.8 X64) | Any | Stop Slave statement will timeout not waiting the event group complete |
37101 | 2008-05-30 13:08 | 2008-07-19 14:42 | MySQL Server: Errors | Not a Bug (5990 days) | S2 | 5.0.51b | Windows (server 2003 standart X64) | Any | Can't create a new thread (errno 12) |
12081 | 2005-07-21 13:17 | 2005-09-27 9:21 | MySQL Cluster: Cluster (NDB) storage engine | Can't repeat (7016 days) | S3 | 4.1.12 | Linux (Linux/x86) | Any | Cluster: BEGIN after lock-wait timeout results in error 1296 |
13182 | 2005-09-14 14:26 | 2005-09-16 16:22 | MySQL Server: Documentation | Closed (7027 days) | S3 | All | Any (All) | Any | Deadlock or a lock wait timeout in InnoDB does not cancel the effect of 'BEGIN' |
1985 | 2003-11-29 15:59 | 2004-01-01 14:20 | MySQL Server | No Feedback (7651 days) | S1 | 3.23.58 | Linux (RH 9) | Any | server |
24450 | 2006-11-21 3:03 | 2006-11-22 8:34 | MySQL Server | Not a Bug (6595 days) | S1 | 5.0.26-r1 | Linux (Gentoo, Ubuntu (EM64T)) | Any | Crashes on create table |
40423 | 2008-10-30 10:43 | 2008-11-11 22:15 | MySQL Server: General | Duplicate (5875 days) | S1 | 6.0 | Linux | Any | mysqld_safe loops forever if server is started with wrong --innodb-log-file-size |
52179 | 2010-03-18 13:14 | 2011-02-16 23:44 | MySQL Server | No Feedback (5352 days) | S3 | 5.1.30-community | Windows (32 Bit) | Any | read_buffer_size and read_rnd_buffer_size make problem |
62970 | 2011-10-27 14:55 | 2011-12-15 7:00 | MySQL Server: Installing | No Feedback (4747 days) | S3 | 5.5 .16 | Windows (7) | Any | MySQL Installer, Samples and Examples 5.5.15 configuration fail |
4056 | 2004-06-08 13:40 | 2023-02-12 20:45 | MySQL Server: Replication | Duplicate (4354 days) | S5 | 5.0.66a | Any (Any) | Any | Replicating lock type in LOAD DATA INFILE statements |
5998 | 2004-10-09 3:29 | 2004-10-15 12:14 | MySQL Server: InnoDB storage engine | Closed (7363 days) | S2 | 4.0.22 4.1.6 | Any | Any | LOCK TABLE write locks for same table conflict |
8820 | 2005-02-26 8:41 | 2015-08-10 14:33 | MySQL Server: mysqldump Command-line Client | Can't repeat (7229 days) | S2 | 4.1.10 | Linux (Linux) | Any | mysqldump --quick --lock-tables cancels out the --lock-tables |
9355 | 2005-03-23 12:12 | 2005-03-28 17:50 | MySQL Server: MyISAM storage engine | Not a Bug (7199 days) | S2 | 4.0.20-log | Linux (Debian/kernel 2.4.29) | Any | Locked aliases not recognized during queries |
10919 | 2005-05-27 15:54 | 2005-05-28 10:27 | MySQL Server: Compiling | Not a Bug (7138 days) | S1 | 4.0.24 | GNU/Linux (Gentoo) | Any | Unable to use the AS keyword inside LOCK TABLES; ...; UNLOCK TABLES |
12098 | 2005-07-21 22:08 | 2005-08-21 22:21 | MySQL Server: Documentation | Closed (7053 days) | S3 | Your Web Site | Your Web Site | Any | MySQL Reference Manual: "lock type compatibility matrix" Unclear |
13035 | 2005-09-07 12:05 | 2005-09-13 17:26 | MySQL Server | Duplicate (7030 days) | S3 | ysql-4.1.11-Debian_4 (Source distributio | Linux (Linux 2.4.24) | Any | Locks acquired with get_lock() persisting, even after MySQL thread has exited |
16979 | 2006-01-31 15:43 | 2011-02-16 23:43 | MySQL Server: InnoDB storage engine | Closed (5289 days) | S5 | 5.0.18 | Any (All) | Any | AUTO_INC lock in InnoDB works a table level lock |
18884 | 2006-04-07 12:02 | 2006-07-07 19:02 | MySQL Server: Locking | Can't repeat (6733 days) | S3 | 5.1 | Any | lock table + global read lock = crash | |
20252 | 2006-06-03 22:04 | 2006-07-04 13:07 | MySQL Cluster: Cluster (NDB) storage engine | Closed (6736 days) | S3 | 5.0.21-max | Any (all) | Any | NDB API: NdbIndexScanOperation::readTuples ignores the batch parameter |
23904 | 2006-11-02 19:32 | 2007-02-17 15:30 | MySQL Server: General | Can't repeat (6508 days) | S3 | 5.0.24a-max | Linux (suse9.3 x86) | Any | deadlocked when 2 threads waiting for INSERT and 1 was deleting on same table |
24918 | 2006-12-08 17:20 | 2007-08-03 1:40 | MySQL Server: Locking | Closed (6341 days) | S1 | 4.1.22, 4.1.23-BK, 5.0.27 | Linux (Linux, freebsd) | Any | drop table and lock / inconsistent between perm and temp tables |
25042 | 2006-12-13 15:15 | 2007-03-30 19:37 | MySQL Server | Closed (6467 days) | S2 | 5.0.15/5.0BK/5.1BK | Windows (Windows (XP)) | Any | OPTIMIZE TABLE cause race condition in IO CACHE SHARE |
27370 | 2007-03-22 12:15 | 2007-04-30 9:40 | MySQL Cluster: NDB API | Closed (6436 days) | S2 | 5.0-bk, 5.1-bk | Any (Any) | Any | Potential inconsistent blob reads for ReadCommitted reads |
28073 | 2007-04-24 13:32 | 2007-04-30 9:11 | MySQL Cluster: Cluster (NDB) storage engine | Closed (6436 days) | S1 | 5.1-bk | Any | Any | Infinite loop in lock queue |
32947 | 2007-12-03 23:47 | 2007-12-05 8:33 | MySQL Server: Documentation | Closed (6217 days) | S3 | 6.0 | Any | Any | Misleading LOCK TABLES description in 6.0 Nutshell section |
35382 | 2008-03-18 8:23 | 2008-11-04 13:57 | MySQL Query Browser | Closed (5882 days) | S1 | 1.2.12 | Windows (lock tables does not work) | Any | Lock tables does not work - not even while using FLUSH TABLES WITH... |
36988 | 2008-05-26 18:34 | 2011-02-16 23:43 | MySQL Server: Documentation | Closed (5855 days) | S3 | 5.1.24-rc-community-log | Any | Any | Documentation on Next-Key Locking is confusing and misleading |
46673 | 2009-08-12 12:39 | 2011-02-16 23:44 | MySQL Server: Locking | Closed (5394 days) | S2 | 5.4, azalea | Any | Any | Deadlock between FLUSH TABLES WITH READ LOCK and DML |
47635 | 2009-09-24 21:06 | 2011-02-16 23:44 | MySQL Server: Locking | Closed (5394 days) | S3 | 6.0.14 | Any | Any | assert in start_waiting_global_read_lock during CREATE VIEW |
48911 | 2009-11-19 15:46 | 2016-12-04 20:45 | MySQL Server: InnoDB storage engine | Duplicate (5370 days) | S2 | 5.1.41, 5.1.42-bzr | Any | Any | SELECT ... FOR UPDATE doesn't do exclusive lock when table is empty |
49206 | 2009-11-30 12:00 | 2009-12-09 10:37 | MySQL Server: Backup | Can't repeat (5482 days) | S2 | 6.0-codebase-bugfixing | Any | Any | Deadlock between BACKUP, the locking thread and DDL DML |
57006 | 2010-09-24 14:31 | 2011-02-16 23:44 | MySQL Server: Locking | Closed (5111 days) | S2 | 5.1.52-bzr, 5.5.7 | Any | Any | Deadlock between HANDLER and FLUSH TABLES WITH READ LOCK |
58489 | 2010-11-25 12:42 | 2013-03-05 14:18 | MySQL Server: Locking | Won't fix (4300 days) | S3 | 5.5 | Any | Any | FLUSH TABLES WITH READ LOCK - issue with concurrent load |
58562 | 2010-11-29 15:05 | 2011-03-07 11:32 | MySQL Workbench: Administration | Closed (5029 days) | S1 | 5.2.30 | Any | Any | --lock-tables enabled even when --single-transaction option selected |
61414 | 2011-06-05 22:22 | 2011-06-06 5:23 | MySQL Server: Backup | Not a Bug (4938 days) | S2 | 5.5.12 | Linux (x86_64, opensuse 11.4, pkg) | Any | upgraded from 5.1->5.5. now getting a mysqldump ERROR "1142:SELECT,LOCK TABL com |
63997 | 2012-01-11 16:57 | 2013-01-03 2:31 | Connector / NET | Closed (4361 days) | S3 | 6.4.4 | Windows (7 or 2008) | Any | Session locking issue with MySqlSessionStateStore |
66416 | 2012-08-16 8:57 | 2012-09-06 18:55 | MySQL Server: Locking | Not a Bug (4480 days) | S2 | 5.5.16 | Linux | Any | DDL hangs on "Waiting for table metadata lock" even after database restart. |
67760 | 2012-11-29 20:02 | 2017-11-09 17:00 | Connector / J | Closed (3599 days) | S2 | 5.1.22 | Any (Observed on Debian 64bits and Windows 64 bits) | Any | Deadlock when concurrently executing prepared statements with Timestamp objects |
73066 | 2014-06-20 15:45 | 2023-01-12 18:36 | MySQL Server: Replication | Closed (2225 days) | S2 | 5.6.17 | Any | Any | Replication stall with multi-threaded replication |
75513 | 2015-01-15 10:20 | 2019-01-08 12:48 | MySQL Server: InnoDB storage engine | Can't repeat (2165 days) | S5 | 5.5.31 | Linux | Any | DROP TABLE creating a stall when foreign keys in use on other tables |
80200 | 2016-01-29 15:33 | 2016-02-02 19:03 | MySQL Utilities | Closed (3236 days) | S2 | 1.6.2 | Any | Any | msyqldbcopy does not work with MySQL 5.7 |
81002 | 2016-04-08 3:00 | 2016-04-19 19:02 | MySQL Server: Documentation | Closed (3159 days) | S3 | 5.6.29 | Any | Any | Concurrent DML via LOCK=NONE does not error on tables with foreign keys. |
84609 | 2017-01-23 12:21 | 2017-06-27 7:43 | MySQL Server: Performance Schema | Verified (2880 days) | S3 | 5.7, 8.0, 5.7.17 | Any | Any | Lock information in TABLE_HANDLES misplaced |
85765 | 2017-04-03 7:43 | 2017-10-16 12:47 | MySQL Server: InnoDB storage engine | Closed (2617 days) | S3 | 8.0.2 (trunk) | Any | Any | Assert !rw_lock_own(lock, RW_LOCK_S) rw_lock_s_lock_func in include/sync0rw.ic |
86422 | 2017-05-23 9:00 | 2017-10-13 17:00 | MySQL Server: InnoDB storage engine | Closed (2617 days) | S2 | 8.0.2 | Any | Any | lock0lock.cc: ((m_mode - (0xFUL & m_mode)) - (0xF0UL & m_mode) - (256 & m_mode)) |
89331 | 2018-01-20 0:36 | 2018-02-14 17:02 | MySQL Server: Replication | Closed (2493 days) | S2 | 8.0.3 | Red Hat | Any | Changing lock/release order in group commit causes a deadlock |
97228 | 2019-10-15 10:40 | 2019-10-25 12:07 | MySQL Server: InnoDB storage engine | Verified (1875 days) | S5 | 8.0 | Any | ARM | rwlock: refine lock->lock_word with C11 atomics |
99101 | 2020-03-27 19:19 | 2020-09-01 18:07 | MySQL Server: DML | Closed (1563 days) | S3 | 8.0, 8.0.11, 8.0.19 | Any | Any | SELECT .. LOCK IN SHARE MODE requires LOCK TABLES grant |
101305 | 2020-10-24 8:55 | 2021-02-17 10:52 | MySQL Server: InnoDB storage engine | Closed (1394 days) | S3 | 8.0 | Any | Any | trx->lock.n_rec_locks inconsistent with real num of trx rec locks |
102967 | 2021-03-15 2:39 | 2021-03-16 11:46 | MySQL Server: InnoDB storage engine | Verified (1367 days) | S3 | 5.7.18 | Any | Any | deadlock transaction hang up when connection is broken |
106608 | 2022-03-01 7:36 | 2022-03-16 13:45 | MySQL Server | Not a Bug (1003 days) | S3 | 8.0.17 MySQL Community Server | Linux (openSUSE Leap 15.1) | x86 (Intel(R) Xeon(R) Gold 6126 CPU @ 2.60GHz) | Queey hangs with "Waiting for table metadata lock" |
108069 | 2022-08-04 8:50 | 2022-08-04 11:42 | MySQL Enterprise Monitor | Duplicate (861 days) | S3 | 8.0.30 | Any | Any | PFS didn't display metadata lock correctly |
108210 | 2022-08-22 2:24 | 2022-08-22 7:56 | MySQL Server: Documentation | Verified (843 days) | S2 | Any | Any | Description about LOCK_MODE is not accurate | |
113760 | 2024-01-25 13:00 | 2024-01-25 14:00 | MySQL Server: InnoDB storage engine | Unsupported (322 days) | S3 | 5.7.44 | Linux | ARM | Insufficient memory barriers in rw-lock implementation caused crash on ARM arch |
116323 | 2024-10-09 13:32 | 2024-11-30 16:06 | MySQL Server: Connection Handling | Verified (12 days) | S2 | 8.0.39, 8.0.40 | Any | Any | Waiting for MDL lock during COM_CHANGE_USER may cause connection leaks |
43733 | 2009-03-18 16:11 | 2011-02-16 23:43 | MySQL Server: Embedded Library ( libmysqld ) | Closed (5473 days) | S1 | 5.1.33-debug, 5.1-bugteam | Linux (suse-linux-gnu on i686) | Any | Select on processlist let the embedded server crash (concurrent_innodb_safelog) |
47768 | 2009-10-01 17:15 | 2011-02-16 23:44 | MySQL Server: General | Closed (5473 days) | S2 | 5.0+ | Windows | Any | pthread_cond_timedwait() is broken on windows |
49251 | 2009-12-01 8:23 | 2024-08-28 9:05 | MySQL Server: InnoDB storage engine | Duplicate (5222 days) | S1 | 5.0.91,5.1.50, 5.5, 5.6.1 | Any | Any | deadlock/crash with concurrent truncate table and index statistics calculation |
55576 | 2010-07-27 2:59 | 2011-02-16 23:44 | MySQL Server: Performance Schema | Closed (5116 days) | S3 | 5.6, 5,5 | Any | Any | Two perfschema tests failed on mysql-next-mr-innodb PB2 tests |
68768 | 2013-03-25 21:28 | 2013-04-09 14:25 | MySQL Server: Performance Schema | Closed (4265 days) | S3 | Any | Any | MIN_TIMER_WAIT in events_waits_summary_global_by_event_name overflows | |
77319 | 2015-06-11 15:03 | 2019-10-15 1:00 | MySQL Server | No Feedback (1886 days) | S3 | 5.6.25 | Linux | Any | InnoDB: Warning: a long semaphore wait:Thread xxx has waited at trx0 |
86902 | 2017-07-03 7:10 | 2017-07-12 5:40 | MySQL Server | Not a Bug (2710 days) | S2 | 5.6 | Linux | Any | Dead lock cause mysqld hand |
114374 | 2024-03-15 18:38 | 2024-03-25 17:51 | MySQL Server | Not a Bug (262 days) | S2 | 8.0.32 | Any | Any | InnoDB semaphore wait bug - a thread is waiting for itself? |
19815 | 2006-05-15 13:17 | 2006-06-10 15:44 | MySQL Server: Locking | Closed (6760 days) | S1 | 5.0.21 | Linux (Linux) | Any | CREATE/RENAME/DROP DATABASE can deadlock on a global read lock |
2460 | 2004-01-20 7:17 | 2004-05-28 19:52 | MySQL Server | Closed (7503 days) | S2 | Any | Crash wih Stored Procedure and UNOIN | ||
26483 | 2007-02-19 22:26 | 2021-05-02 20:45 | MySQL Cluster: Cluster (NDB) storage engine | Verified (6504 days) | S3 | mysql-5.1-telco-6.2 | Linux (Linux 32 Bit) | Any | Slave MySQLD does not reconnect w/ slave cluster after network outage restored |
30687 | 2007-08-29 10:22 | 2007-09-30 10:41 | MySQL Server: Replication | No Feedback (6283 days) | S2 | 5.0.17 | Linux (FC4) | Any | Next record offset is nonsensical |
20143 | 2006-05-30 10:18 | 2006-06-01 11:02 | MySQL Server: InnoDB storage engine | Not a Bug (6769 days) | S1 | 5.0.21 community nt | Windows (Windows XP SP2) | Any | Timeout while aquiring lock on table with foreign key |
28602 | 2007-05-22 17:39 | 2011-02-16 23:43 | MySQL Server | Can't repeat (5706 days) | S3 | 5.1.18 | Any | Any | Can't open and lock privilege tables: Incorrect key file for table 'db'; try to |
45522 | 2009-06-16 10:57 | 2013-04-14 20:45 | MySQL Server: InnoDB storage engine | Duplicate (5273 days) | S1 | 5.0.67 | Linux (RHEL4u4) | Any | InnoDB continuously restarts after hard power off |
52952 | 2010-04-19 18:45 | 2011-02-16 23:44 | MySQL Enterprise Monitor: Agent | Closed (5231 days) | S2 | 2.2.0.1695 | Any | Any | If Agent gets a timeout on initial checkin, it will not retry |
67291 | 2012-10-18 18:19 | 2012-10-18 21:43 | MySQL Server | Duplicate (4438 days) | S1 | 5.5.11 | Linux (CentOS release 4.7 (Final)) | Any | Production MySQL master server crashed and could not get recovered |
70728 | 2013-10-25 20:34 | 2014-03-04 11:14 | MySQL Enterprise Monitor: Documentation | Closed (3936 days) | S3 | 3.0 | Any | Any | InnoDB Buffer Pool Usage Graph doc does not reflect actual behavior |
35498 | 2008-03-22 5:51 | 2011-02-16 23:43 | MySQL Server: InnoDB storage engine | Closed (5289 days) | S3 | 5.1.22, 5.1.30, 5.0.45 | Any | Any | Cannot get table test/table1 auto-inccounter value in ::info |
46163 | 2009-07-14 9:10 | 2009-12-22 23:32 | MySQL Server | Not a Bug (5620 days) | S2 | 5.0, 5.1,5.4 | Any | Any | KILL QUERY causes implicit COMMIT |
56134 | 2010-08-20 6:16 | 2011-05-11 8:41 | MySQL Server: DDL | Can't repeat (4964 days) | S3 | 5.1.49 | Any | Any | mysql_admin_table should check the return value of open_and_lock_tables |
74177 | 2014-10-01 13:51 | 2015-06-26 16:01 | MySQL Server: Replication | Closed (3457 days) | S2 | 5.7.5, 5.7.6 | Any | Any | --slave-preserve-commit-order causes slave to deadlock and break for some querie |
94814 | 2019-03-28 11:12 | 2022-12-01 12:01 | MySQL Server: XA transactions | Closed (742 days) | S2 | 5.7, 8.0, 5.7.25 | Any | Any | slave replication lock wait timeout because of wrong trx order in binlog file |
99736 | 2020-05-29 7:34 | 2020-05-29 14:23 | MySQL Server: InnoDB storage engine | Not a Bug (1658 days) | S3 | 8.0.20 | Windows (Windows 10 (1909)) | x86 | Unique index lock after INSERT, DELETE, INSERT with same values |
110162 | 2023-02-22 7:06 | 2023-02-23 14:17 | MySQL Server | Not a Bug (658 days) | S5 | 8.0 | Linux | ARM | Improve vio read performance by introducing short busy poll before sleep |
69993 | 2013-08-12 10:36 | 2013-11-19 13:48 | MySQL Server: Memcached | Closed (4041 days) | S2 | 5.6.13 | Linux (CentOS 5) | Any | innodb tries to access tablespace that does not exist or is just being dropped |
31660 | 2007-10-17 9:08 | 2007-10-29 21:58 | MySQL Server: Replication | Duplicate (6254 days) | S2 | 5.1.22 | Windows (2003 SP 2) | Any | mysql stops when starting with replication options+missing mysql table |
37633 | 2008-06-25 14:58 | 2015-11-07 7:37 | MySQL Server: InnoDB storage engine | Can't repeat (3323 days) | S5 | 5.0.45 | Any | Any | certain queries become very slow - locking related? |
44499 | 2009-04-27 19:55 | 2011-02-16 23:43 | MySQL Cluster: Cluster (NDB) storage engine | Closed (5403 days) | S3 | mysql-5.1-telco-7.0 | Solaris | Any | GCP Stop / failed handling of GCP_SAVEREQ / Dbdih::execBLOCK_COMMIT_ORD |
17016 | 2006-02-01 16:51 | 2008-01-09 23:08 | Connector / ODBC | Can't repeat (6182 days) | S2 | 3.51 | Windows (Windows) | Any | I find some problem in MySQL (bugs) - 'update' command in C++ |
38037 | 2008-07-11 8:48 | 2008-07-11 11:08 | MySQL Server: Installing | Not a Bug (5998 days) | S5 | mysql-5.0.51a-linux-i686 | Linux (Mandriva Summer 2008) | Any | Installation of system tables failed! |
44047 | 2009-04-02 16:01 | 2011-02-16 23:43 | MySQL Server: Locking | No Feedback (5464 days) | S1 | mysql-5.1.30 ndb-6.3.20 | Linux (ubuntu 8.04 (ec2)) | Any | Cluster API node, All threads stuck in lock wait |
47814 | 2009-10-04 18:33 | 2011-02-16 23:44 | MySQL Server: InnoDB storage engine | Closed (5290 days) | S2 | 5.0.44 | Linux | Any | Diagnostics are frequently not printed after a long lock wait in InnoDB |
51543 | 2010-02-26 9:26 | 2013-04-14 20:45 | MySQL Server: InnoDB storage engine | No Feedback (5225 days) | S5 | 5.0.81, 5.1.34 sp1, 5.1.44 | Linux (rh5.3) | Any | innodb sorting result very slow(using index,no filesort) |
55834 | 2010-08-09 8:42 | 2011-02-16 23:44 | MySQL Server: Documentation | Closed (5238 days) | S3 | 5.5 | Any | Any | INNODB_TRX docs list BLOCKED instead of LOCK WAIT state |
60293 | 2011-03-01 12:35 | 2018-09-23 20:45 | MySQL Server: InnoDB storage engine | Duplicate (4371 days) | S3 | 5.5.11 | Any | Any | SHOW ENGINE INNODB STATUS: full path names instead of filenames |
62180 | 2011-08-16 16:18 | 2011-08-20 15:31 | MySQL Server: Locking | Duplicate (4863 days) | S2 | 5.5.12 | Any | Any | Metadata lock during index creation eliminates concurrent selects |
82400 | 2016-08-01 17:32 | 2016-12-15 13:06 | MySQL Server: Row Based Replication ( RBR ) | Closed (2919 days) | S2 | 5.7.14 | Any | Any | MTS: LOGICAL_CLOCK slave hangs and breaks for innodb_lock_wait_timeout |
97319 | 2019-10-21 22:19 | 2019-10-22 5:56 | MySQL Server: SYS Schema | Verified (1878 days) | S3 | 5.7.26, 8.0.18, 5.7.28 | Any | Any | sys schema lock wait view not timezone-aware |
99219 | 2020-04-09 12:16 | 2020-04-10 12:19 | MySQL Server: InnoDB storage engine | Not a Bug (1707 days) | S2 | 5.7.27 | Any | Any | Innodb freeze running REPLACE statements |
4515 | 2004-07-12 13:18 | 2004-07-29 15:21 | MySQL Websites: lists.mysql.com | Not a Bug (7441 days) | S2 | Any | DNS cannot find my mail server | ||
9998 | 2005-04-19 13:04 | 2005-06-24 2:58 | MySQL Server | Closed (7111 days) | S3 | 5.0 | N/A | Any | MySQL client hangs on USE "database" |
13769 | 2005-10-05 11:28 | 2005-10-13 15:00 | MySQL Server | Not a Bug (7000 days) | S3 | 4.1.14 (-bk) | Linux (Gentoo 1.6.13 [ AMD64]) | Any | Innodb 'Table was not locked with LOCK TABLES', LOCK TABLES not used |
35647 | 2008-03-28 14:21 | 2008-03-28 17:07 | MySQL Server: InnoDB storage engine | Won't fix (6103 days) | S3 | 5.0, 5.1, 6.0 | Any | Any | endless innodb loop when starting server twice |
47277 | 2009-09-11 17:13 | 2011-02-16 23:44 | MySQL Server: Locking | No Feedback (5344 days) | S2 | 5.1.38 | FreeBSD (7.2-RELEASE) | Any | Query stuck "Sending data" locks table; query cache off; MyISAM |
49560 | 2009-12-09 14:18 | 2011-02-16 23:44 | MySQL Cluster: Cluster (NDB) storage engine | Closed (5480 days) | S3 | mysql-5.1-telco-7.0 | Any | Any | Hanging restart with mysqld + take-over during system restart |
56494 | 2010-09-02 12:07 | 2011-02-16 23:44 | MySQL Server: Locking | Closed (5136 days) | S3 | 5.5 | Any | Any | Segfault in upgrade_shared_lock_to_exclusive() for REPAIR of merge table |
93901 | 2019-01-12 9:17 | 2019-03-26 14:03 | MySQL Server: InnoDB storage engine | Closed (2150 days) | S2 | 8.0.13 | Any | Any | InnoDB purge thread don't release GLOBAL and BACKUP MDL lock after undo truncate |
57757 | 2010-10-27 0:58 | 2011-02-16 23:44 | Connector / J | Closed (5144 days) | S3 | 5.1.13 | Any | Any | Race condition in simple.StatementsTest.testCancelStatement causes failure |
9277 | 2005-03-18 12:56 | 2005-04-06 14:08 | MySQL Server: InnoDB storage engine | Closed (7190 days) | S2 | 4.1.11-bk | Linux (Linux) | Any | 4.1.11bk crashes assertion failure; log_open() false? |
13791 | 2005-10-06 1:59 | 2005-10-06 18:47 | MySQL Server | Closed (7007 days) | S1 | 5.0.15-rc from BK | Linux (Linux/Windows) | Any | mysqld crashes at startup in 5.0.15bk |
15869 | 2005-12-19 21:04 | 2006-05-22 18:37 | MySQL Server | Closed (6779 days) | S2 | 4.1.16 | Other (IRIX 6.5.28) | Any | Cannot shutdown the server - it restarts |
20223 | 2006-06-02 10:27 | 2006-06-07 20:25 | MySQL Server: Embedded Library ( libmysqld ) | Duplicate (6763 days) | S1 | 5.1.11-beta | Unix (almost all) | Any | Embedded server crashes (almost all platforms, all tests) |
28477 | 2007-05-16 17:05 | 2011-02-16 23:43 | MySQL Server: Partitions | Closed (5634 days) | S1 | 5.1.19, 5.1.17, 5.1.36 | Any | Any | innodb assertion and crash during alter table to add/drop partitions |
29344 | 2007-06-25 19:53 | 2007-06-25 22:40 | MySQL Server: Installing | Can't repeat (6380 days) | S3 | MySql 5 | Windows (Vista) | Any | MySQL Vista |
31111 | 2007-09-20 14:16 | 2007-11-09 17:26 | MySQL Server: Stored Routines | Closed (6243 days) | S1 | 5.1-bk | Any | Any | --read-only crashes MySQL (events fail to load) |
38316 | 2008-07-23 16:54 | 2011-02-16 23:43 | MySQL Server: Replication | Can't repeat (5837 days) | S1 | 5.1-bugteam | Linux (ubuntu 8.04) | Any | Assertion `m_curr_row_end <= m_rows_end' failed in unpack_current_row |
39490 | 2008-09-16 23:04 | 2015-03-15 20:45 | MySQL Server: Falcon storage engine | Duplicate (5929 days) | S1 | 6.0.6 | Linux (RHEL5) | Any | Falcon Crash: Assertion Failed at line 779 in file Transaction.cpp |
42640 | 2009-02-06 7:17 | 2011-02-16 23:43 | MySQL Server | Closed (5690 days) | S2 | 5.1-bugteam, 5.1 | Any | Any | mysqld crashes when unsafe statements are executed (STRICT_TRANS_TABLES mode) |
50474 | 2010-01-20 13:12 | 2011-02-16 23:44 | Tests: Replication | Closed (5244 days) | S3 | Betony (M2) | Windows | Any | rpl_slave_load_remove_tmpfile failed on windows debug enabled binary |
55981 | 2010-08-14 7:07 | 2018-09-23 20:45 | MySQL Server: InnoDB storage engine | Duplicate (5224 days) | S2 | 5.6.99-m5 | Any | Any | Assertion failure in file fsp0fsp.c line 3276 |
71775 | 2014-02-20 5:03 | 2018-08-08 11:34 | MySQL Server: InnoDB storage engine | Can't repeat (2318 days) | S2 | 5.6.10 | Linux (CentOS 6.2 (2.6.32-220.2.1.el6.x86_64)) | Any | crashe : semaphore wait has lasted |
2886 | 2004-02-19 2:29 | 2004-11-08 10:34 | MySQL Server: Replication | Closed (7339 days) | S2 | 4.0.17 | Linux (GNU/Linux) | Any | IO-Thread stops working at illegal master log position |
8348 | 2005-02-07 1:19 | 2005-02-07 11:43 | MySQL Server | Duplicate (7248 days) | S2 | 4.0.23 binary rpm | Linux (RHEL 3.0) | Any | Query/hour count issues |
34436 | 2008-02-08 23:31 | 2008-03-16 6:12 | MySQL Server: Replication | No Feedback (6115 days) | S2 | 5.0.45 | Linux (Ubuntu Edgy) | Any | Binlog corruption on inserts with utf8 |
60788 | 2011-04-07 7:10 | 2013-08-25 20:45 | MySQL Server: InnoDB storage engine | Duplicate (4378 days) | S3 | Any | Any | InnoDB crashes with an assertion failure when receiving a signal on pwrite() | |
88523 | 2017-11-16 14:13 | 2020-08-28 13:13 | MySQL Server: InnoDB storage engine | Can't repeat (2269 days) | S3 | 5.7.16/5.7.22 | Windows | Any | InnoDB: Semaphore wait has lasted > 600 seconds. We intentionally crash the serv |
91078 | 2018-05-30 13:37 | 2023-11-20 11:34 | MySQL Server | Can't repeat (388 days) | S3 | 5.7.21 | Red Hat (RHEL 6.7) | x86 | Queries stuck in 'query end' forever |
97523 | 2019-11-06 21:02 | 2021-01-27 10:18 | MySQL Server | No Feedback (1832 days) | S3 | 5.7.26 | Any | Any | Infinite loop on query end re TrxInInnoDB::wait() |
71127 | 2013-12-11 11:51 | 2013-12-19 11:32 | MySQL Fabric | Closed (4011 days) | S3 | 1.4.0 | Any | Any | Checkpoint routine can lead to deadlock |
12082 | 2005-07-21 13:52 | 2005-08-12 19:29 | MySQL Server | Closed (7062 days) | S1 | 5.0.10-beta | Linux (Linux) | Any | Prepared statement "FOR UPDATE" "LOCK IN SHARE MODE": timeout gives server crash |
9381 | 2005-03-24 13:47 | 2005-04-08 12:42 | MySQL Server: InnoDB storage engine | Closed (7188 days) | S3 | 4.1 | Linux (linux) | Any | InnoDB unlocks data file too late (after PID file is removed) |
10942 | 2005-05-29 12:42 | 2005-12-09 18:52 | MySQL Server: Replication | Closed (6943 days) | S3 | 4.1 | Linux (linux) | Any | deadlock with FLUSH TABLES WITH READ LOCK + STOP SLAVE |
20139 | 2006-05-30 7:44 | 2006-08-10 16:32 | MySQL Server: Locking | Closed (6699 days) | S1 | 5.1.12-BK, 5.1.11 | Linux (FC5) | Any | Infinite loop after "FLUSH" and "LOCK tabX, general_log" |
23769 | 2006-10-30 12:05 | 2006-11-27 19:10 | MySQL Server: InnoDB storage engine | Closed (6590 days) | S3 | 5.0 | Any (All) | Any | Debug assertion failure with innodb_locks_unsafe_for_binlog |
39222 | 2008-09-03 19:00 | 2008-09-03 19:32 | MySQL Server | Not a Bug (5944 days) | S3 | 5.0.51-log | Any | Any | no difference between LOCK IN SHARE MODE and LOCK FOR UPDATE |
43867 | 2009-03-25 22:10 | 2011-02-16 23:43 | MySQL Server: Partitions | Closed (5394 days) | S2 | 6.0-runtime, azalea | Any | Any | ALTER TABLE on a partitioned table causes unnecessary deadlocks |
46224 | 2009-07-16 14:08 | 2011-02-16 23:44 | MySQL Server: Locking | Closed (5394 days) | S2 | 5.4+ | Any | Any | HANDLER statements within a transaction might lead to deadlocks |
53510 | 2010-05-08 0:02 | 2011-02-16 23:44 | MySQL Server: Locking | No Feedback (5262 days) | S2 | 5.0+ | Linux | Any | Potential deadlock |
56114 | 2010-08-19 10:10 | 2011-02-16 23:44 | MySQL Server: InnoDB storage engine | Closed (5116 days) | S3 | 5.1 plugin, 5.5+ | Any | Any | Disallow trx->dict_operation_lock_mode==RW_X_LATCH in srv_suspend_mysql_thread() |
64478 | 2012-02-28 2:20 | 2012-04-17 8:24 | MySQL Server: Locking | Duplicate (4622 days) | S2 | 5.5.19, 5.5.21 | Any | Any | CREATE TABLE IF NOT EXISTS waits for table metadata lock |
73369 | 2014-07-24 6:52 | 2015-04-07 17:32 | MySQL Server: InnoDB storage engine | Verified (3756 days) | S3 | 5.6.19 | Linux | Any | Tail of secondary index may cause gap lock in read-committed |
93649 | 2018-12-18 3:23 | 2022-09-16 7:22 | MySQL Server: Replication | Closed (2071 days) | S3 | 8.0.13 | Any | Any | STOP SLAVE SQL_THREAD deadlocks if done while holding LOCK INSTANCE FOR BACKUP |
98139 | 2020-01-07 9:04 | 2020-01-20 12:47 | MySQL Server: Documentation | Verified (1791 days) | S3 | 8.0.16 | Any | Any | Committing a XA transaction causes a wrong sequence of events in binlog |
112670 | 2023-10-09 15:47 | 2023-10-10 5:04 | MySQL Server: Documentation | Verified (429 days) | S3 | 8.0.34 | Any | Any | Documentation outdated related ANALYZE TABLE locking |
113312 | 2023-12-01 22:48 | 2024-10-23 11:29 | MySQL Server: InnoDB storage engine | Verified (308 days) | S2 | 8.0.35, 8.1.0 | Any | Any | Server stall during Alter/Drop table while clearing AHIs from the buffer pool |
116055 | 2024-09-11 5:54 | 2024-09-11 6:32 | MySQL Server: Errors | Verified (92 days) | S3 | 8.0.39, 8.4.2, 9.0.1 | CentOS (7.9) | x86 | MY-004085 and MY-014054 message is bit wrong |
42165 | 2009-01-16 16:45 | 2011-02-16 23:43 | MySQL Server: Replication | No Feedback (5775 days) | S3 | 5.0 | Any | Any | Slave retries incompletely rolled back transaction |
87225 | 2017-07-27 15:38 | 2017-10-23 18:07 | MySQL Server: InnoDB storage engine | Closed (2607 days) | S3 | 8.0.3 | Any | Any | assert failure: !sdi_insert_failed || trx_is_interrupted(trx) |
66497 | 2012-08-22 13:01 | 2013-01-10 14:00 | MySQL Server: Replication | Duplicate (4354 days) | S1 | 5.6.6 | Any (Linux, MacOS X) | Any | crash after restarting a parallel slave |
67033 | 2012-10-01 11:07 | 2017-12-14 5:05 | MySQL Cluster: Cluster (NDB) storage engine | Can't repeat (3111 days) | S1 | 7.2.7 | Solaris (5.10) | Any | Mysqld got signal 11 during NDB binlog setup after cluster failure |
73924 | 2014-09-16 5:56 | 2014-09-16 7:42 | MySQL Server: FULLTEXT search | Duplicate (3740 days) | S2 | 5.6.15, 5.6.17 | Windows | Any | MySql innodb_ft_max_token_size is not changing |
88170 | 2017-10-20 21:29 | 2019-04-08 14:00 | MySQL Server: Query Cache | Duplicate (2597 days) | S3 | 5.6.27, 5.6.35 | Other (Amazon RDS) | Any | MYSQL Server keep restarting every day |
103894 | 2021-06-02 15:05 | 2022-09-06 10:07 | MySQL Visual Studio Integration | Can't repeat (1259 days) | S3 | 1.2.9 | Windows (10.0.19042 Build 19042) | x86 (Intel(R) Core(TM) i5-10210U CPU @ 1.60GHz, 2112 Mhz, 4 Core(s), 8 Logical Processor(s)) | MySQL for Visual Studio fails to load on Microsoft Visual Studio |
3559 | 2004-04-25 21:53 | 2004-05-15 12:44 | MySQL Server: Replication | Closed (7516 days) | S2 | 4.0.18-log | Linux (Redhat linux 9) | Any | Replication crash when slave under high load |
5214 | 2004-08-25 20:03 | 2004-08-26 17:10 | Connector / NET | Closed (7413 days) | S2 | 0.76 | Windows (XP SP2) | Any | Connection Timeout seems to be ignored |
10397 | 2005-05-05 19:27 | 2005-05-07 19:55 | MySQL Server | Can't repeat (7159 days) | S3 | 4.1.10 | Windows (Windows XP) | Any | Connection timeout is ignored on Windows |
11774 | 2005-07-06 12:30 | 2012-05-18 20:19 | MySQL Server | Duplicate (6688 days) | S3 | 4.1.12 | Linux (Linux) | Any | Libmysqlclient read/write timeout options |
11985 | 2005-07-16 20:52 | 2012-05-18 20:19 | MySQL Server | Duplicate (6940 days) | S3 | 4.0.24 | Linux (Gentoo) | Any | timeout doesn't work as expected |
15718 | 2005-12-13 21:22 | 2006-01-20 22:40 | MySQL Server: Documentation | Closed (6901 days) | S3 | 5.0.16-nt-max | Windows (XP, with SP2) | Any | mysql_real_connect() using named pipe doesn't honor wait_timeout |
15855 | 2005-12-19 10:43 | 2006-06-08 17:50 | MySQL Server | Can't repeat (6762 days) | S3 | 5.0.16 | IBM AIX 5.3 ML2 | Any | Upgrade + old privilege tables yields information_schema timeout |
18414 | 2006-03-22 9:47 | 2006-03-27 13:58 | MySQL Cluster: Cluster (NDB) storage engine | Closed (6835 days) | S3 | 4.1,5.0,5.1 | Any | Timeout in ABORT handling with more that 32 ops can yield NF | |
24146 | 2006-11-09 16:01 | 2007-04-05 14:27 | MySQL Cluster: Cluster (NDB) storage engine | Closed (6461 days) | S1 | 5.1.12-beta | MacOS (OS-X 10.4 PPC 64bit) | Any | Connect to server fails in run with NDB, timeout 400 s for "apply_status.ndb" |
24685 | 2006-11-29 11:27 | 2012-05-18 20:19 | MySQL Server: MyISAM storage engine | Duplicate (6495 days) | S1 | 5.0-bk, 5.1-bk | Windows (Windows 2003) | Any | Test case 'myisam' timeout on Windows 32-bit |
24786 | 2006-12-04 4:28 | 2011-02-16 23:43 | Connector / NET | Closed (5053 days) | S2 | 5.0.2 | Windows (Windows XP SP2) | Any | Command timeout does not raise exception, documentation incorrect |
25487 | 2007-01-09 5:30 | 2007-01-25 8:08 | MySQL Cluster: NDB API | Closed (6531 days) | S3 | 5.0.34,5.1.14 | Any | deleting ndb_cluster_connection object takes long time | |
29063 | 2007-06-13 2:59 | 2007-06-19 12:08 | MySQL Cluster: Cluster (NDB) storage engine | Closed (6386 days) | S3 | 5.1.4-a_drop6p8, 5.1.19 | Any | Any | mgmapi: connect timeout set incorrectly |
29113 | 2007-06-14 16:52 | 2007-10-29 9:10 | MySQL Server: Embedded Library ( libmysqld ) | Can't repeat (6254 days) | S2 | 4.1.23 | Any (several Unix) | Any | Test "lock_multi" fails in "embedded" runs: Timeout. |
30714 | 2007-08-30 1:45 | 2007-10-17 9:50 | Connector / NET | Not a Bug (6266 days) | S2 | 5.0.8.1 | Windows | Any | Getting connection timeout while using pooled connection |
31698 | 2007-10-18 19:16 | 2011-02-16 23:43 | Connector / J | Closed (5726 days) | S2 | 5.1.5 | Linux (2.6.22.9-61.fc6) | Any | Statement.setQueryTimeout(int) does not throw exception on timeout |
33268 | 2007-12-16 13:20 | 2014-01-31 13:04 | MySQL Server: Compiling | Won't fix (3968 days) | S3 | 5.1.23 | Linux (Debian x86_64) | Any | Gcov offsets one line in sql_yacc.yy rules |
34151 | 2008-01-29 22:29 | 2008-10-03 9:53 | MySQL Server: Tests | No Feedback (5914 days) | S3 | 5.0.51a | Linux (Debian i386) | Any | Timeout in ndb_alter_table test when built with gcc 4.3 |
37981 | 2008-07-09 5:59 | 2008-07-11 9:24 | Connector / J | Not a Bug (5998 days) | S3 | mysql-connector-java-5.1.6 | Any | Any | Cannot set socketTimeout (read timeout defaults to 0/infinite) |
39739 | 2008-09-29 23:21 | 2011-02-16 23:43 | MySQL Server: Command-line Clients | Verified | S3 | Any | Any | Any | The mysql client automatically adjusts timeout values for negative/ large values |
40135 | 2008-10-18 21:34 | 2008-12-18 16:55 | MySQL Server: Falcon storage engine | Closed (5838 days) | S2 | 6.0-rpl | Linux (debx86-b) | Any | falcon_bug_30124 is too slow, times out in pushbuild |
41004 | 2008-11-25 10:57 | 2011-02-16 23:43 | MySQL Server | Can't repeat (5574 days) | S2 | 5.1, 6.0 | Any | Any | events_scheduling times out sporadically on pushbuild |
41092 | 2008-11-28 12:56 | 2020-09-13 20:45 | MySQL Server: Maria storage engine | Duplicate (5733 days) | S3 | 6.0-maria | Linux (itanium) | Any | Maria: timeout in waiting_threads-t |
41861 | 2009-01-05 11:27 | 2011-02-16 23:43 | MySQL Server: Tests | Closed (5735 days) | S3 | 6.0-rpl, 5.1 | Any | Any | random tests fail sporadically in pushbuild with timeout at shutdown |
43065 | 2009-02-20 17:45 | 2011-02-16 23:43 | Tests: Server | Closed (5722 days) | S3 | 5.0, 5.1, 6.0 | Any | Any | main.lock_multi: This test is too big if the disk is slow |
44401 | 2009-04-22 4:07 | 2009-06-18 13:27 | MySQL Cluster: Cluster (NDB) storage engine | Not a Bug (5656 days) | S3 | mysql-5.1-telco-7.0 | Windows | Any | mtr daily-basic-tests.DbAsyncGeneratorime_60__1 failed once, but not again... |
46823 | 2009-08-20 9:53 | 2011-02-16 23:44 | Tests: Cluster | Verified (5585 days) | S3 | 5.1 | Any | Any | rpl_ndb.rpl_ndb_extraCol test fails on PB-2 with a timeout |
47792 | 2009-10-02 12:45 | 2011-02-16 23:44 | Tests: Server | Closed (5081 days) | S3 | 5.4.5 (mysql-trunk), 6.0-codebase-bugfixing | Solaris (solaris 10) | Any | main.lock_multi_bug38691 times out sporadically on Solaris 10 |
47815 | 2009-10-04 22:47 | 2011-02-16 23:44 | Connector / NET | Closed (5537 days) | S3 | 6.1.2 | Any | Any | Session expires is incorrect |
47924 | 2009-10-08 19:08 | 2011-02-16 23:44 | MySQL Server: Locking | Closed (5096 days) | S3 | 5.1 | Any | Any | main.log_tables times out sporadically |
48494 | 2009-11-03 9:40 | 2011-02-16 23:44 | Connector / NET | Closed (5511 days) | S1 | Connector/Net 6.1.2 | Windows (Windows Vista) | Any | "Fatal error encountered during command execution", "Timeout expired" |
48883 | 2009-11-18 21:13 | 2011-08-17 14:48 | MySQL Server: Tests | Closed (4866 days) | S3 | 5.1, 5.5, 5.6 | Linux | Any | Test "innodb_information_schema" takes fewer locks than expected |
48918 | 2009-11-19 18:26 | 2011-02-16 23:44 | Tools: MTR / mysql-test-run | Closed (5292 days) | S3 | 5.5.0-beta | Linux (SLES 9 RPM) | Any | MTR uses an un-initialized value in comparison |
52019 | 2010-03-12 21:07 | 2011-02-16 23:44 | Tools: MTR / mysql-test-run | Closed (5142 days) | S3 | 5.1.45 | IBM AIX | Any | main.mysqltest fails on new tests for lowercase_result |
55715 | 2010-08-03 14:53 | 2011-02-16 23:44 | MySQL Cluster: Cluster (NDB) storage engine | Closed (5236 days) | S2 | mysql-5.1-telco-6.3 | Any | Any | multiple node failures caused by DBTC/DIH timeout of COMMIT |
57720 | 2010-10-25 20:32 | 2011-02-16 23:44 | MySQL Server: InnoDB storage engine | Closed (5112 days) | S3 | mysql-5.5-innodb | Windows (Vista & 7) | Any | InnoDB crashes at startup in Windows Vista/7 in os0sync.c; os_cond_wait_timed() |
58424 | 2010-11-23 18:20 | 2011-02-16 23:44 | Tools: MTR / mysql-test-run | Closed (5106 days) | S3 | 5.5 | Any | Any | mtr ignores failing mysqltest in the presence of expect file for mysqld |
67171 | 2012-10-10 4:26 | 2013-03-11 17:46 | Connector / NET | Closed (4294 days) | S3 | 6.4.5 & 6.6.3 | Windows (Windows 7) | Any | Default Command Timeout not applying for EFMySqlCommand |
68692 | 2013-03-16 16:35 | 2021-07-02 19:00 | MySQL Workbench: Administration | No Feedback (4162 days) | S3 | 5.2.47 | Windows | Any | Workbench model synchronization timeout too short/non-configurable |
69400 | 2013-06-04 22:12 | 2022-01-23 20:45 | Connector / NET | No Feedback (4065 days) | S2 | 5.6.5 | Windows (.NET 4.0) | Any | MySqlConnection Dispose throws exception |
70042 | 2013-08-14 22:33 | 2013-09-16 8:59 | MySQL Server: Replication | Verified (4105 days) | S3 | MySQL 5.6.13 | Any | Any | semisync master waits for timeout if 'stop slave' is executed on semisync slave |
75604 | 2015-01-23 15:33 | 2019-06-19 16:24 | Connector / NET | Closed (2003 days) | S2 | 6.8.3.0 | Windows | Any | Unable to access MySQL Server via Connector/NET after 24.9 days of uptime |
84907 | 2017-02-09 12:28 | 2018-04-25 13:09 | MySQL Workbench | Duplicate (2856 days) | S2 | 6.3.9 | Windows (Microsoft Windows 8.1 Pro) | Any | Can't connect to MySQL database over SSH using private key |
86363 | 2017-05-17 19:34 | 2017-05-19 6:21 | Connector / J | Closed (2765 days) | S2 | 5.1.42 | Debian | Any | JDBC socket timeout set to 15ms regardless of uri settings |
87463 | 2017-08-18 2:02 | 2021-10-18 18:21 | MySQL Server: InnoDB storage engine | Can't repeat (2673 days) | S2 | 5.7.15 | Windows (Server 2012R2) | Any | MySQL Crashes with operating system error number 995 in a file operation |
89648 | 2018-02-13 11:52 | 2018-04-02 17:16 | MySQL Workbench: Migration | Unsupported (2446 days) | S3 | 6.3.10 | Ubuntu (17.10 64-bit) | Any | MySQL Workbench - Migration Wizard - invalid option |
91205 | 2018-06-11 7:22 | 2019-02-16 17:34 | MySQL Server: XA transactions | Closed (2126 days) | S3 | 8.0.12 | Any | Any | dd_upgrade tests failing on Debian |
93983 | 2019-01-18 15:01 | 2020-08-19 18:35 | MySQL Workbench: Migration | No Feedback (1679 days) | S1 | 8.0.13 | Ubuntu | x86 | source-timeout parameter requested but none |
94155 | 2019-01-31 16:04 | 2019-01-31 16:43 | MySQL Workbench: Migration | Duplicate (2142 days) | S1 | 8.0.13 | Ubuntu (18.04) | x86 | source-timeout parameter requested but none |
98203 | 2020-01-13 14:09 | 2020-01-15 3:04 | MySQL Server: mysqldump Command-line Client | Closed (1793 days) | S3 | 8.0 | Any | Any | mysql dump "sufficiently long" network timeout too short |
101275 | 2020-10-22 13:26 | 2020-10-23 10:23 | MySQL Server: Replication | Verified (1511 days) | S3 | 5.7, 5.7.31, 5.7.32, 8.0.22 | Any | Any | rpl_semi_sync_master_enabled=ON without any connected slaves will cause timeout |
112123 | 2023-08-21 9:15 | 2023-11-27 21:33 | Connector / NET | Closed (381 days) | S1 | 8.0.31, 8.1.0 | Any | Any | Pool exhaustion after timeouts in transactions |
113604 | 2024-01-10 5:42 | 2024-01-17 6:12 | Connector / ODBC | Not a Bug (335 days) | S3 | 5.3, 8.0, 8.1 | Windows | Any | SQLSetStmtAttr and SQL_ATTR_QUERY_TIMEOUT does not work in 8.x ODBC Connector |
5898 | 2004-10-05 8:42 | 2004-10-30 8:49 | MySQL Server: InnoDB storage engine | Closed (7348 days) | S1 | 4.0, 4.1, 5.0 | Any (All) | Any | Intentional server crash in InnoDB code |
9014 | 2005-03-07 10:21 | 2005-03-07 18:42 | MySQL Server: Documentation | Closed (7220 days) | S3 | 4.0, 4.1 | Any (*) | Any | mysqladmin timeout options |
16995 | 2006-02-01 5:44 | 2007-01-30 18:12 | MySQL Server | Closed (6526 days) | S2 | 4.0 | Linux (Linux 2.6.x) | Any | idle connections not being killed due to timeout when NPTL is used |
24554 | 2006-11-23 19:35 | 2007-10-05 15:33 | Instance Manager | Unsupported (6278 days) | S3 | 5.0 BK | Any | Any | IM: STOP INSTANCE does not work properly if an instance has been started outside |
32113 | 2007-11-05 14:45 | 2021-05-02 20:45 | MySQL Cluster: Cluster (NDB) storage engine | Verified | S3 | mysql-5.1 | Any | Any | ndb: setting api heartbeat timeout high may cause strange reconnect behavior |
50176 | 2010-01-08 10:08 | 2017-05-21 20:45 | MySQL Server: Backup | Patch queued (5447 days) | S3 | Any | Any | rpl_backup_block times out on mysql-backup-backport | |
85725 | 2017-03-31 6:17 | 2017-04-07 23:00 | Tests: Group Replication | Not a Bug (2806 days) | S3 | 5.7.17 | Windows | Any | mysql group replication |
86010 | 2017-04-19 18:25 | 2020-07-17 18:40 | Connector / NET | Not a Bug (1609 days) | S3 | 6.9.9 | Any | Any | SLEEP command does not happen on subsequent UPDATEs |
92981 | 2018-10-29 4:33 | 2019-10-14 11:15 | MySQL Server: Group Replication | Not a Bug (1886 days) | S2 | 5.7.22 | Oracle Linux | Any | Potential connection leak in group replication |
4386 | 2004-07-02 20:41 | 2004-07-07 18:02 | Connector / NET | Closed (7463 days) | S2 | Any | Inserted data doesn't update properly | ||
19807 | 2006-05-14 20:47 | 2006-06-18 21:45 | MySQL Server | No Feedback (6752 days) | S1 | 5.0.21 | Linux (Linux Suse ES9; 2.6.5; gcc 3.3.3) | Any | linux build from source 5.0.21 tests failed; SUSE ES9 |
31147 | 2007-09-22 14:42 | 2012-09-13 10:58 | Connector / NET | No Feedback (6181 days) | S2 | 1.0.9 | Windows | Any | Isolation level not working |
98082 | 2019-12-27 8:04 | 2024-09-15 20:45 | MySQL Server | Duplicate (1742 days) | S1 | 8.0.18 | CentOS (7.5) | Any | MySQL Community Server 8.0.18 got signal 6 |
113413 | 2023-12-14 6:01 | 2023-12-15 5:18 | Connector / J | Verified (363 days) | S3 | 8.0.33, 8.1.0 | Any | Any | Connection.changeUser cannot be done after DriverManager.loginTimeout elapses. |
1955 | 2003-11-25 16:12 | 2014-03-28 13:36 | Connector / J | Can't repeat (3912 days) | S1 | 3.0.9, 3.0.8, ...? | Any | Any | deadlock in LogicalConnection and MySqlPooledConnection |
2234 | 2003-12-29 12:07 | 2004-01-11 14:28 | MySQL Server | Closed (7641 days) | S1 | 4.0.16/4.0.17 | Linux (Redhat AS3) | Any | MySQL hang on adding index to 2 tables in the database |
2926 | 2004-02-23 10:41 | 2004-03-31 7:34 | MySQL Server | Not a Bug (7561 days) | S3 | 4.1.1 | Solaris (solaris 8 & 9) | Any | some potential race conditions |
5010 | 2004-08-12 2:32 | 2004-08-13 8:31 | MySQL Server | Not a Bug (7426 days) | S3 | 4.1.3-beta-standard | Linux (Redhat Linux 9) | Any | Problem with LOCK TABLES and subqueries |
6732 | 2004-11-20 23:15 | 2004-11-30 21:53 | MySQL Server | Closed (7317 days) | S1 | 4.0.22 | Any (all) | Any | FLUSH TABLES WITH READ LOCK + COMMIT makes next FLUSH...LOCK hang forever |
9207 | 2005-03-15 22:06 | 2005-03-24 19:33 | MySQL Server | Closed (7203 days) | S3 | 4.1.10 | Any (*) | Any | inconsistence with lock and desc |
9453 | 2005-03-29 13:48 | 2005-03-29 15:10 | MySQL Server | Not a Bug (7198 days) | S3 | 4.1.11 | Linux (linux) | Any | LOCK TABLE does not do proper checking of the existence of tables except 1st |
9565 | 2005-04-01 16:25 | 2005-07-18 20:08 | MySQL Server | Closed (7087 days) | S3 | 5.0.3 | Linux (Linux/x86) | Any | wrong locking in stored procedure if a sub-sequent procedure is called |
11238 | 2005-06-10 11:45 | 2005-10-06 0:15 | MySQL Server | Closed (7007 days) | S1 | 4.1, 5.0 | Any (All) | Any | SELECT ... FOR UPDATE executed as consistent read inside LOCK TABLES |
12410 | 2005-08-06 6:20 | 2005-09-01 14:46 | MySQL Server: InnoDB storage engine | Closed (7042 days) | S2 | 4.1 | Any (any) | Any | mysqldump/InnoDB too permissive with LOCK TABLE foo READ LOCAL |
12532 | 2005-08-11 18:13 | 2005-08-26 19:36 | MySQL Server: Replication | Closed (7048 days) | S1 | 5.0.9-5.0.12-bk | Linux (linux x86_64) | Any | sql_thread causing memory overrun |
14618 | 2005-11-03 21:18 | 2007-08-03 16:19 | MySQL Server | Closed (6341 days) | S3 | 4.1.15, 5.1 BK, 5.0 BK | Linux (Debian GNU/Linux) | Any | mysql_setpermission doest not work anymore |
14972 | 2005-11-16 9:25 | 2006-06-15 16:23 | Connector / J | Duplicate (6755 days) | S1 | 3.1-nightly-20051121 | Linux (Linux, Java build 1.5.0_05-b05) | Any | Found one Java-level deadlock |
16329 | 2006-01-10 9:54 | 2006-01-16 9:48 | MySQL Server | Won't fix (6905 days) | S2 | 5.0.18 | HP/UX (HP-UX 11.00) | Any | Compile failure : noinst_HEADERS |
16593 | 2006-01-18 3:14 | 2006-02-23 3:24 | MySQL Server | Closed (6867 days) | S1 | 5.0.17a-cert,5.0.18 | Any (ALL) | Any | Deadlock or crash in stress test for case where triggers starting trigger |
17709 | 2006-02-24 19:41 | 2022-09-04 20:45 | Connector / J | Duplicate (3909 days) | S1 | 5.0.0-night 2006/02/18 | Linux (Linux) | Any | Found one Java-level deadlock |
19285 | 2006-04-23 2:08 | 2006-06-19 17:28 | MySQL Cluster: Cluster (NDB) storage engine | Closed (6751 days) | S3 | 5.0, 5.1 | Linux (linux) | Any | NDBAPI blob access can corrupt tables if done wrong |
20256 | 2006-06-04 6:07 | 2006-09-25 19:57 | MySQL Server: Locking | Closed (6653 days) | S3 | 5.0.25-BK, 5.0.22 | Linux (Linux, W2K) | Any | LOCK WRITE - MyISAM |
20662 | 2006-06-23 14:23 | 2007-05-16 19:25 | MySQL Server: Locking | Closed (6420 days) | S1 | 4.0, 4.1, 5.0, 5.1 | Linux (Linux) | Any | Infinite loop in CREATE TABLE IF NOT EXISTS ... SELECT with locked tables |
21050 | 2006-07-13 23:03 | 2006-09-02 6:09 | MySQL Cluster: Cluster (NDB) storage engine | Closed (6676 days) | S2 | 5.1.12 | Linux (Linux 32 Bit OS) | Any | Drop db during DN recovery causes other DN to fail & causes recovery issues |
21281 | 2006-07-25 18:07 | 2007-08-25 16:07 | MySQL Server: Locking | Closed (6319 days) | S3 | 4.1.19, 5.0.40 | Linux (Linux) | Any | Pending write lock is incorrectly removed when its statement being KILLed |
22246 | 2006-09-11 21:37 | 2022-12-04 20:45 | MySQL Server: Locking | Verified (5479 days) | S3 | 4.1.22, 5.0.45, 5.1.43, 6.0.14 | Linux (Linux) | Any | Allow LOCK TABLE WRITE lock a non-existent table. |
23713 | 2006-10-27 12:25 | 2007-12-18 21:45 | MySQL Server: Stored Routines | Closed (6204 days) | S3 | 5.0.27-bk | Any | Any | LOCK TABLES + CREATE TRIGGER + FLUSH TABLES WITH READ LOCK = deadlock |
25324 | 2006-12-29 6:11 | 2009-05-15 16:05 | MySQL Server: Falcon storage engine | Closed (5690 days) | S2 | 5.1.14-falcon-alpha-pb349 | MacOS (MacOSX 10.4.8) | Any | Build fails on MacOSX for mysql-5.1.14-falcon-alpha-pb349 |
25966 | 2007-01-31 7:03 | 2007-03-16 17:52 | MySQL Server: Locking | Closed (6481 days) | S1 | <=5.0.36, 5.1 | Windows (windows, linux) | Any | 2MB per second endless memory consumption after LOCK TABLE ... WRITE |
26141 | 2007-02-07 10:01 | 2011-02-16 23:43 | MySQL Server: Stored Routines | Closed (5395 days) | S3 | 5.0.36, 5.1.16 | Linux (linux, windows) | Any | mixing table types in trigger causes full table lock on innodb table |
26241 | 2007-02-09 22:07 | 2007-05-27 19:17 | MySQL Server: Locking | Closed (6409 days) | S3 | 5.1.15 | Linux (Linux, Mac OS X) | Any | Blackhole tables don't honor table locks |
27655 | 2007-04-04 18:09 | 2007-04-13 8:31 | Connector / J | Closed (6453 days) | S3 | 5.0.5 | Any | Any | Excessive SHOW VARIABLES LIKE 'tx_isolation' |
28249 | 2007-05-04 16:01 | 2007-07-23 20:23 | MySQL Server | Closed (6352 days) | S2 | 5.0.42/5,1 | Any | Any | Query Cache returns wrong result with concurrent insert / certain lock |
31418 | 2007-10-05 11:10 | 2007-10-24 19:51 | MySQL Server | Closed (6259 days) | S1 | 5.1.21-beta-debug | Linux (Linux linux-eu6p 2.6.16.53-0.8-bigsmp #1 SMP Fri Aug 31 13:07:27 UTC 2007 i686 i686 i386 GNU/Linux) | Any | User locks misfunctioning after mysql_change_user() |
37773 | 2008-07-01 15:38 | 2012-05-18 20:19 | MySQL Server: General | Duplicate (5684 days) | S3 | 6.0-BK | Any | Any | main.events_2 fails randomly |
37844 | 2008-07-03 17:58 | 2017-07-07 9:44 | MySQL Server: Query Cache | Won't fix (2715 days) | S5 | 5.0.62,5.1.25 | Any | Any | Fix SMP performance for the query cache |
39460 | 2008-09-15 20:41 | 2008-10-16 7:33 | MySQL Server: InnoDB storage engine | Not a Bug (5901 days) | S3 | 5.1.28 | Any | Any | No deprecation when removing "Total number of lock structs in row lock hash" |
41499 | 2008-12-16 12:53 | 2015-03-15 20:45 | MySQL Server: Partitions | No Feedback (5772 days) | S3 | Any (Mac OS X 10.5.5.) | Any | DBUG_ASSERT when full disk on partitioned MyISAM tables. | |
41688 | 2008-12-23 0:13 | 2011-02-16 23:43 | MySQL Server | Closed (5770 days) | S3 | 6.1.0-alpha-debug | Linux (SUSE 10.0 / 32-bit) | Any | Foreign keys: lock warnings |
41885 | 2009-01-05 20:15 | 2010-05-26 18:00 | MySQL Server: Falcon storage engine | Unsupported (5314 days) | S3 | 6.0.9-release | Any | Any | Falcon: slowdown in 6.0.9 in update_of_key_big test from mysql-bench suite |
43529 | 2009-03-10 8:08 | 2011-02-16 23:43 | MySQL Server | Won't fix (5671 days) | S3 | 5.0 | Any | Any | Adding DBUG_SYNC_POINT cause DROP TABLE and KILL dead lock |
43672 | 2009-03-16 10:40 | 2012-05-18 20:19 | MySQL Server: Tests | Duplicate (5727 days) | S3 | 6.0 bzr, 5.1 | Any | Any | Test main.myisamlog fails when run with option --no-check-testcases |
43719 | 2009-03-18 4:46 | 2010-05-26 18:00 | MySQL Server: Falcon storage engine | Unsupported (5314 days) | S5 | 6.0.10-release | Any | Any | Falcon: performance regression in sysbench test OLTP_RW |
44230 | 2009-04-13 7:55 | 2010-05-26 18:00 | MySQL Server: Falcon storage engine | Unsupported (5314 days) | S3 | 6.0.11-bzr | Linux | Any | Altering Falcon table under LOCK TABLES fails with "Can't lock file" error. |
44955 | 2009-05-19 15:11 | 2011-02-16 23:43 | MySQL Server: Documentation | Closed (5685 days) | S3 | 5.x | Any | Any | FOR UPDATE does not lock reading, only writing |
45324 | 2009-06-04 8:53 | 2011-02-16 23:44 | MySQL Server: Performance Schema | Closed (5446 days) | S3 | mysql-6.0-perfschema | Any | Any | Performance schema: can write lock |
46780 | 2009-08-18 10:15 | 2011-02-16 23:44 | MySQL Server: Command-line Clients | Can't repeat (5595 days) | S3 | 5.0.38 | Linux | Any | lock table write, then create trigger, but failed |
47024 | 2009-08-31 15:31 | 2017-05-07 20:45 | MySQL Server: Locking | Duplicate (5572 days) | S3 | 5.4 | Any | Any | server hangs on FLUSH TABLES WITH READ LOCK or UNLOCK TABLES |
47583 | 2009-09-24 7:15 | 2011-03-09 16:34 | MySQL Server: Tests | Closed (5027 days) | S3 | 5.5.99, 6.0.14, 6.0-codebase | Any | Any | Test main.lock fails if server is compiled without support for partition |
47769 | 2009-10-01 17:41 | 2016-06-13 9:15 | MySQL Server: Errors | Closed (5550 days) | S1 | 5.0.51a | FreeBSD | Any | InnoDB: Unable to lock ./ibdata1, error: 45 |
48173 | 2009-10-20 0:25 | 2011-02-16 23:44 | MySQL Server: Documentation | Closed (5532 days) | S3 | Ver 14.12 Distrib 5.0.79, 5.0.85 | Linux | Any | Unable to drop index while innodb table is locked. |
48930 | 2009-11-20 8:10 | 2010-03-07 19:32 | MySQL Server: Backup | Closed (5394 days) | S2 | Any | Any | Backup: Lock thread race condition for default backup driver | |
49960 | 2009-12-28 14:41 | 2011-02-16 23:44 | MySQL Server: Locking | Can't repeat (5313 days) | S2 | next-mr-wl3561 | Any | Any | Deadlock on a concurrent workload involving transactional lock table |
Showing 1-1000 of 9732 (Edit, Save, CSV, Feed) | Show Next 1000 Entries » |