| Showing all 5 (Edit, Save, CSV, Feed) |
| ID# | Date | Type | Status | Sev | Version | Target | OS | Summary | Assigned |
|---|---|---|---|---|---|---|---|---|---|
| 43766 | 2009-03-20 11:19 | Server: Locking | Verified (249 days) | S3 | 5.1.25, 5.1.31, 4.1, 5.0, 5.1, 6.0 bzr | Linux | unnecessary locking on update even with tx_isolation=READ-COMMITTED or | ||
| 44613 | 2009-05-01 19:38 | Server: SP | Verified (189 days) | S2 | 5.1.34, 5.0, 5.1 bzr | Linux (Debian ) | SELECT statement inside FUNCTION takes a shared lock | Dmitri Lenev | |
| 47814 | 2009-10-04 20:33 | Server: InnoDB | In review (25 days) | S2 | 5.0.44 | 5.0+ | Linux | Diagnostics are frequently not printed after a long lock wait in InnoDB | Jimmy Yang |
| 48675 | 2009-11-10 22:26 | Server: Locking | Open (13 days) | S2 | 5.1.40 | Microsoft Windows (XP SP2) | Broken Phantom lock breaks ACID compliance | ||
| 48911 | 2009-11-19 16:46 | Server: InnoDB | Verified (5 days) | S2 | 5.1.41, 5.1.42-bzr | Any | SELECT ... FOR UPDATE doesn't do exclusive lock when table is empty | Marko Mäkelä |
| Showing all 5 (Edit, Save, CSV, Feed) |
