Showing 1-30 of 75 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
---|---|---|---|---|---|---|---|---|---|
63751 | 2011-12-14 20:06 | 2011-12-21 20:55 | MySQL Server: Locking | Not a Bug (4482 days) | S3 | 5.5.15 | Any | Any | "SELECT ... WHERE w_id%4=1 FOR UPDATE" locks whole table |
72072 | 2014-03-19 7:31 | 2014-04-14 13:18 | MySQL Server: Locking | Not a Bug (3637 days) | S3 | 5.5 | Any | Any | 5.5 Lock |
62641 | 2011-10-06 14:05 | 2011-12-26 19:00 | MySQL Server: Locking | Not a Bug (4477 days) | S2 | 5.5.16 | Windows (7 64bit) | Any | A simple SELECT relock the table what was locked with LOCK TABLES WRITE. |
44277 | 2009-04-15 2:56 | 2009-04-15 10:27 | MySQL Server: Locking | Not a Bug (5462 days) | S2 | 5.1.32 | Linux | Any | Abort (Ctrl+C) via mysql client can't free some locks in transaction |
67172 | 2012-10-10 7:03 | 2012-10-12 15:10 | MySQL Server: Locking | Not a Bug (4186 days) | S1 | 5.x | Any | Any | Alter query getting locked |
103153 | 2021-03-30 16:08 | 2021-04-02 12:01 | MySQL Server: Locking | Not a Bug (1094 days) | S3 | 5.7, 8.0 | Any | Any | ALTER with LOCK=NONE blocks SELECTs |
104858 | 2021-09-07 15:07 | 2021-09-08 11:17 | MySQL Server: Locking | Not a Bug (933 days) | S3 | 8.0.26 | Any | Any | An improper locking bug due to unrelased lock |
109015 | 2022-11-07 10:55 | 2022-12-01 9:38 | MySQL Server: Locking | Not a Bug (507 days) | S3 | Linux | Any | BETWEEN takes more locks then needed | |
39358 | 2008-09-10 5:38 | 2008-10-04 6:53 | MySQL Server: Locking | Not a Bug (5655 days) | S3 | 5.0.51-log | Any | Any | Concurrency locks causes deadlocks |
69373 | 2013-06-01 2:57 | 2014-07-21 19:42 | MySQL Server: Locking | Not a Bug (3539 days) | S3 | 5.1,5.5 | Any | Any | Confused about behavior for InnoDB next-key locks |
93935 | 2019-01-15 13:33 | 2019-05-17 4:50 | MySQL Server: Locking | Not a Bug (1880 days) | S3 | Any | Any | Contribution: my_fclose - retry on close fail like my_close | |
57249 | 2010-10-05 13:53 | 2010-11-22 15:21 | MySQL Server: Locking | Not a Bug (4876 days) | S2 | 5.1,5.5 | Any | Any | crash in mysql_unlock_tables, sysbench with high number of threads |
66416 | 2012-08-16 8:57 | 2012-09-06 18:55 | MySQL Server: Locking | Not a Bug (4222 days) | S2 | 5.5.16 | Linux | Any | DDL hangs on "Waiting for table metadata lock" even after database restart. |
43700 | 2009-03-17 13:27 | 2009-03-18 8:56 | MySQL Server: Locking | Not a Bug (5490 days) | S3 | Ver 14.12 Distrib 5.0.54 | Any (ubuntu) | Any | dead lock after insert inside transaction |
58892 | 2010-12-13 6:45 | 2010-12-13 7:52 | MySQL Server: Locking | Not a Bug (4855 days) | S2 | 5,1,47-x86-64 | Linux | Any | deadlock |
50396 | 2010-01-17 13:30 | 2010-01-21 15:42 | MySQL Server: Locking | Not a Bug (5181 days) | S2 | mysql-next-4284, 6.0-backup, backup-backport | Any | Any | Deadlock between DROP DATABASE (mysql_rm_table_part2) and SELECT |
43211 | 2009-02-26 7:14 | 2009-02-26 9:16 | MySQL Server: Locking | Not a Bug (5510 days) | S2 | 5.0.51a-community-log | Linux | Any | Deadlock detected on concurrent delete/insert into same table |
61502 | 2011-06-13 14:02 | 2011-08-04 21:32 | MySQL Server: Locking | Not a Bug (4621 days) | S2 | 5.5.10 | Any | Any | deadlock on insertion - insert holds and waits on same lock |
72439 | 2014-04-24 13:42 | 2016-08-29 9:21 | MySQL Server: Locking | Not a Bug (3424 days) | S3 | 5.5.35 | Any | Any | Deadlock using SELECT … FOR UPDATE in MySQL |
96748 | 2019-09-04 11:59 | 2023-03-22 13:45 | MySQL Server: Locking | Not a Bug (1668 days) | S3 | 8.0.17 | Any | Any | deadlock when doing SELECT FOR UPDATE and INSERT |
32210 | 2007-11-09 3:30 | 2007-11-09 5:35 | MySQL Server: Locking | Not a Bug (5985 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 |
107029 | 2022-04-14 22:42 | 2022-04-15 13:19 | MySQL Server: Locking | Not a Bug (714 days) | S3 | 8.0.28 | Any | Any | deadlock when using trigger logic implementation |
38870 | 2008-08-18 18:16 | 2008-11-12 6:59 | MySQL Server: Locking | Not a Bug (5616 days) | S3 | 5.1.26, 5.1.28, 5.1.29 | Any | Any | deadlocked threads with myisam table |
56571 | 2010-09-05 17:22 | 2012-10-16 5:25 | MySQL Server: Locking | Not a Bug (4182 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 |
113175 | 2023-11-22 5:55 | 2023-11-22 11:35 | MySQL Server: Locking | Not a Bug (128 days) | S3 | 8.0.34 | Any | Any | Getting wrong result for locked rows |
61935 | 2011-07-21 5:24 | 2011-08-10 19:51 | MySQL Server: Locking | Not a Bug (4615 days) | S2 | 5.5.11 | Linux (openSUSE 11.2 "Emerald") | Any | Hang Waiting for table metadata lock |
44618 | 2009-05-01 22:12 | 2009-05-23 15:11 | MySQL Server: Locking | Not a Bug (5424 days) | S3 | 5.0.75, 5.1 bzr | Linux | Any | HIGH_PRIORITY/LOW_PRIORITY don't work |
102676 | 2021-02-21 18:29 | 2021-02-22 21:03 | MySQL Server: Locking | Not a Bug (1131 days) | S2 | 5.7.12, 8.0.11 | Linux (RDS of AWS) | Any | In REPEATABLE READ, the behavior after executing select for update is strange. |
104431 | 2021-07-27 22:13 | 2021-07-29 13:49 | MySQL Server: Locking | Not a Bug (974 days) | S3 | 8.0.26 | Any | Any | Incorrect data locks listed for INSERT |
67941 | 2012-12-18 19:29 | 2012-12-26 11:02 | MySQL Server: Locking | Not a Bug (4111 days) | S3 | 5.5 | Any | Any | InnoDB table status "waiting for table level lock" |
Showing 1-30 of 75 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |