| Showing 1-30 of 75 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
| ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
|---|---|---|---|---|---|---|---|---|---|
| 82774 | 2016-08-29 3:13 | 2017-04-13 22:01 | MySQL Server: Locking | Not a Bug (2564 days) | S3 | 5.7.13 | Any | Any | Reasonably easy to generate mysqld semi-hang. Input file is 1K lines. |
| 95595 | 2019-06-02 4:34 | 2019-06-04 12:20 | MySQL Server: Locking | Not a Bug (1782 days) | S3 | 5.6.26 | Any | Any | MySQL 5.6.26 high concurrency dead lock |
| 55065 | 2010-07-08 2:33 | 2010-07-08 8:11 | MySQL Server: Locking | Not a Bug (5035 days) | S3 | 5.1 | Any | Any | LOCK TABLES ... READ does not lock tables used in triggers |
| 56571 | 2010-09-05 17:22 | 2012-10-16 5:25 | MySQL Server: Locking | Not a Bug (4204 days) | S3 | 5.5.3-m3, 5.5.6-rc, 5.6.0-m4 | Any | Any | DROP VIEW is not permitted if the view is locked by LOCK TABLE ... WRITE |
| 57249 | 2010-10-05 13:53 | 2010-11-22 15:21 | MySQL Server: Locking | Not a Bug (4898 days) | S2 | 5.1,5.5 | Any | Any | crash in mysql_unlock_tables, sysbench with high number of threads |
| 95551 | 2019-05-28 12:50 | 2019-05-29 12:36 | MySQL Server: Locking | Not a Bug (1788 days) | S3 | 5.6, and 5.7 | Any | Any | MySQL GET_LOCK function is assigning lock to more than one thread |
| 94775 | 2019-03-26 4:37 | 2021-07-26 10:26 | MySQL Server: Locking | Not a Bug (1815 days) | S3 | 5.7.24, 8.0.15 | Any | Any | Innodb_row_lock_current_waits status variable incorrect values on idle server |
| 61502 | 2011-06-13 14:02 | 2011-08-04 21:32 | MySQL Server: Locking | Not a Bug (4643 days) | S2 | 5.5.10 | Any | Any | deadlock on insertion - insert holds and waits on same lock |
| 94148 | 2019-01-31 5:47 | 2019-03-01 13:37 | MySQL Server: Locking | Not a Bug (1877 days) | S2 | 5.7.24 | Any | Any | Unnecessary Shared lock on parent table During UPDATE on a child table |
| 93935 | 2019-01-15 13:33 | 2019-05-17 4:50 | MySQL Server: Locking | Not a Bug (1902 days) | S3 | Any | Any | Contribution: my_fclose - retry on close fail like my_close | |
| 93464 | 2018-12-04 8:28 | 2018-12-06 17:15 | MySQL Server: Locking | Not a Bug (1964 days) | S3 | 8.0.13 | Any | Any | select xxx for update statement conflict insert statement |
| 63751 | 2011-12-14 20:06 | 2011-12-21 20:55 | MySQL Server: Locking | Not a Bug (4504 days) | S3 | 5.5.15 | Any | Any | "SELECT ... WHERE w_id%4=1 FOR UPDATE" locks whole table |
| 96317 | 2019-07-24 13:52 | 2019-08-02 17:55 | MySQL Server: Locking | Not a Bug (1724 days) | S3 | 5.7.18 | Any | Any | Lock wait time out is not occuring for INSERT query |
| 67172 | 2012-10-10 7:03 | 2012-10-12 15:10 | MySQL Server: Locking | Not a Bug (4208 days) | S1 | 5.x | Any | Any | Alter query getting locked |
| 67941 | 2012-12-18 19:29 | 2012-12-26 11:02 | MySQL Server: Locking | Not a Bug (4133 days) | S3 | 5.5 | Any | Any | InnoDB table status "waiting for table level lock" |
| 69373 | 2013-06-01 2:57 | 2014-07-21 19:42 | MySQL Server: Locking | Not a Bug (3561 days) | S3 | 5.1,5.5 | Any | Any | Confused about behavior for InnoDB next-key locks |
| 71571 | 2014-02-03 21:27 | 2014-02-04 16:11 | MySQL Server: Locking | Not a Bug (3728 days) | S3 | 5.6.16 | Any | Any | MyISAM waiting for table lock within transaction combined with innodb table |
| 71714 | 2014-02-14 5:36 | 2014-02-14 5:57 | MySQL Server: Locking | Not a Bug (3718 days) | S1 | mysql 5.5.17 | Any | Any | Select query locking the table |
| 72005 | 2014-03-11 10:17 | 2014-03-13 13:46 | MySQL Server: Locking | Not a Bug (3692 days) | S3 | 5.2.3-falcon-alpha-community-nt | Any | Any | Update table using join clause |
| 72072 | 2014-03-19 7:31 | 2014-04-14 13:18 | MySQL Server: Locking | Not a Bug (3659 days) | S3 | 5.5 | Any | Any | 5.5 Lock |
| 80721 | 2016-03-14 8:13 | 2016-03-14 14:08 | MySQL Server: Locking | Not a Bug (2959 days) | S3 | 5.7.11 | Any | Any | the new GET_LOCK implementation has a limit on the identifier name |
| 72439 | 2014-04-24 13:42 | 2016-08-29 9:21 | MySQL Server: Locking | Not a Bug (3446 days) | S3 | 5.5.35 | Any | Any | Deadlock using SELECT … FOR UPDATE in MySQL |
| 75028 | 2014-11-27 19:42 | 2014-11-28 13:02 | MySQL Server: Locking | Not a Bug (3431 days) | S2 | 5.6.21, 5.6.22 | Any | Any | Unable to shutdown mysqld when HandlerSocket is installed |
| 42243 | 2009-01-21 15:30 | 2009-02-13 12:25 | MySQL Server: Locking | Not a Bug (5545 days) | S2 | 5.1.30 | Any | Any | LOAD DATA CONCURRENT INFILE locks table even when concurrent_insert = 2 |
| 113472 | 2023-12-20 10:58 | 2024-01-08 10:07 | MySQL Server: Locking | Not a Bug (120 days) | S3 | 8.0.24 | Any | Any | when use skip locked syntax, different query plan return different result |
| 113175 | 2023-11-22 5:55 | 2023-11-22 11:35 | MySQL Server: Locking | Not a Bug (150 days) | S3 | 8.0.34 | Any | Any | Getting wrong result for locked rows |
| 111598 | 2023-06-28 10:38 | 2023-06-30 15:10 | MySQL Server: Locking | Not a Bug (295 days) | S3 | 8.0.33 | Any | Any | SELECT FOR SHARE does not acquire lock correctly |
| 109938 | 2023-02-04 21:51 | 2023-02-13 13:27 | MySQL Server: Locking | Not a Bug (435 days) | S3 | 8.0.31 | Any | Any | next key lock with ROLLBACK TO SAVEPOINT |
| 107029 | 2022-04-14 22:42 | 2022-04-15 13:19 | MySQL Server: Locking | Not a Bug (736 days) | S3 | 8.0.28 | Any | Any | deadlock when using trigger logic implementation |
| 106546 | 2022-02-23 9:15 | 2022-02-24 13:50 | MySQL Server: Locking | Not a Bug (786 days) | S3 | 8.0.28 | Any | Any | The gap lock range is too large |
| Showing 1-30 of 75 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
