Showing all 6 (Edit, Save, CSV, Feed) |
ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
---|---|---|---|---|---|---|---|---|---|
26826 | 2007-03-03 19:58 | 2007-04-20 14:47 | MySQL Server: Falcon storage engine | Closed (5024 days) | S2 | 5.2 | Any | Any | Falcon engine does not lock properly |
45901 | 2009-07-02 9:24 | 2009-07-02 14:03 | MySQL Server: InnoDB storage engine | Not a Bug (4220 days) | S3 | 5,1.30, 5.1.33, 5.1.35, 5.1.36 | Microsoft Windows (XP) | Any | Cannot do SELECT FOR UPDATE with small amount of records. |
48911 | 2009-11-19 15:46 | 2016-12-04 20:45 | MySQL Server: InnoDB storage engine | Duplicate (3948 days) | S2 | 5.1.41, 5.1.42-bzr | Any | Any | SELECT ... FOR UPDATE doesn't do exclusive lock when table is empty |
71580 | 2014-02-04 9:02 | 2014-02-06 17:01 | MySQL Server: Locking | Verified (2540 days) | S2 | 5.6.16, 5.5.36 | Any | Any | FLUSH TABLES WITH READ LOCK hangs when many clients run SELECT FOR UPDATE twice |
87457 | 2017-08-17 14:57 | 2018-01-29 20:56 | Connector / ODBC | Closed (1087 days) | S2 | MySQL 5.6.10 | Red Hat (RHEL 7.3) | Any | ODBC Driver Issue with SELECT for UPDATE |
91209 | 2018-06-11 10:36 | 2018-06-12 11:41 | MySQL Server | Not a Bug (953 days) | S3 | 8.0.11 | Any (CentOS Linux release 7.2.1511) | Any | SELECT FOR UPDATE is locking the very next row other than the candidate rows. |
Showing all 6 (Edit, Save, CSV, Feed) |