Showing 1-30 of 75 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
---|---|---|---|---|---|---|---|---|---|
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 |
94775 | 2019-03-26 4:37 | 2021-07-26 10:26 | MySQL Server: Locking | Not a Bug (1793 days) | S3 | 5.7.24, 8.0.15 | Any | Any | Innodb_row_lock_current_waits status variable incorrect values on idle server |
94148 | 2019-01-31 5:47 | 2019-03-01 13:37 | MySQL Server: Locking | Not a Bug (1855 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 (1880 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 (1942 days) | S3 | 8.0.13 | Any | Any | select xxx for update statement conflict insert statement |
82774 | 2016-08-29 3:13 | 2017-04-13 22:01 | MySQL Server: Locking | Not a Bug (2542 days) | S3 | 5.7.13 | Any | Any | Reasonably easy to generate mysqld semi-hang. Input file is 1K lines. |
82328 | 2016-07-24 22:35 | 2016-07-26 14:17 | MySQL Server: Locking | Not a Bug (2803 days) | S5 | 5.6.27 | Linux | Any | Waiting in end_thr_alarm can be avoided for performance improvement |
80721 | 2016-03-14 8:13 | 2016-03-14 14:08 | MySQL Server: Locking | Not a Bug (2937 days) | S3 | 5.7.11 | Any | Any | the new GET_LOCK implementation has a limit on the identifier name |
78581 | 2015-09-27 7:32 | 2015-09-27 10:14 | MySQL Server: Locking | Not a Bug (3106 days) | S1 | 5.5.45 | CentOS (CentOS 6) | Any | Select with UNION: Error Code: 1100. Table was not locked with LOCK TABLES |
75028 | 2014-11-27 19:42 | 2014-11-28 13:02 | MySQL Server: Locking | Not a Bug (3409 days) | S2 | 5.6.21, 5.6.22 | Any | Any | Unable to shutdown mysqld when HandlerSocket is installed |
95551 | 2019-05-28 12:50 | 2019-05-29 12:36 | MySQL Server: Locking | Not a Bug (1766 days) | S3 | 5.6, and 5.7 | Any | Any | MySQL GET_LOCK function is assigning lock to more than one thread |
72407 | 2014-04-20 20:47 | 2014-04-24 17:30 | MySQL Server: Locking | Not a Bug (3627 days) | S1 | 5.6.10, 5.6.17 | Linux (Centos 6.5/6.3) | Any | Unclear Deadlock conditions with delete / update statement. |
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 |
72005 | 2014-03-11 10:17 | 2014-03-13 13:46 | MySQL Server: Locking | Not a Bug (3670 days) | S3 | 5.2.3-falcon-alpha-community-nt | Any | Any | Update table using join clause |
71714 | 2014-02-14 5:36 | 2014-02-14 5:57 | MySQL Server: Locking | Not a Bug (3696 days) | S1 | mysql 5.5.17 | Any | Any | Select query locking the table |
71571 | 2014-02-03 21:27 | 2014-02-04 16:11 | MySQL Server: Locking | Not a Bug (3706 days) | S3 | 5.6.16 | Any | Any | MyISAM waiting for table lock within transaction combined with innodb table |
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 |
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" |
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 |
104758 | 2021-08-29 12:26 | 2021-08-30 13:16 | MySQL Server: Locking | Not a Bug (942 days) | S5 | Ver 8.0.25 for Linux on x86_64 | Any | Any | UPDATE gets unnecessary locks in Repeatable-read isolation level |
113472 | 2023-12-20 10:58 | 2024-01-08 10:07 | MySQL Server: Locking | Not a Bug (98 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 (128 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 (273 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 (413 days) | S3 | 8.0.31 | Any | Any | next key lock with ROLLBACK TO SAVEPOINT |
109388 | 2022-12-15 6:59 | 2022-12-15 12:48 | MySQL Server: Locking | Not a Bug (470 days) | S3 | 8.0.28 | CentOS | x86 | two client can both grant "RECORD X supremum pseudo-record 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 | |
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 |
106546 | 2022-02-23 9:15 | 2022-02-24 13:50 | MySQL Server: Locking | Not a Bug (764 days) | S3 | 8.0.28 | Any | Any | The gap lock range is too large |
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 |
66966 | 2012-09-26 2:45 | 2012-09-26 8:23 | MySQL Server: Locking | Not a Bug (4202 days) | S3 | Windows | Any | System crashing due to display drivers malfunctioning |
Showing 1-30 of 75 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |