Showing all 6 (Edit, Save, CSV, Feed) |
ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
---|---|---|---|---|---|---|---|---|---|
85927 | 2017-04-13 8:24 | 2019-06-10 6:42 | MySQL Server: Performance Schema | Closed (1753 days) | S3 | 8.0.1 | Any | Any | data_locks table does not provide any hint that lock is "insert intention" one |
95598 | 2019-06-02 11:10 | 2019-06-25 12:19 | MySQL Server: Performance Schema | Not a Bug (1756 days) | S3 | 8.0.12 | CentOS (CentOS release 6.5 (Final)) | Any | performance_shema.data_locks shows incorrect lock information |
97944 | 2019-12-10 12:06 | 2019-12-10 14:27 | MySQL Server | Not a Bug (1570 days) | S3 | 8.0.18 Homebrew | MacOS (10.16) | Any | data_locks lack record |
110561 | 2023-03-30 7:55 | 2023-06-27 6:15 | MySQL Server: Locking | Verified (275 days) | S2 | 8.0 | Any | Any | select * from performance_schema.data_locks returns wrong result |
112035 | 2023-08-10 19:33 | 2024-02-21 1:00 | MySQL Server: Performance Schema | Verified (64 days) | S2 | 8.0.34 | Any | Any | Materializing performance_schema.data_locks can lead to excessive mem usage/OOM |
113761 | 2024-01-25 13:33 | 2024-01-25 14:09 | MySQL Server: Performance Schema | Not a Bug (63 days) | S3 | 8.0.36 | Any (rhel-7.4) | Any (x86-64) | Access performance_schema.data_locks causes SQL execution stuck |
Showing all 6 (Edit, Save, CSV, Feed) |