| « Show Previous 30 Entries | Showing 31-58 of 58 (Edit, Save, CSV, Feed) |
| ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
|---|---|---|---|---|---|---|---|---|---|
| 100432 | 2020-08-05 7:55 | 2020-08-05 14:03 | MySQL Server: Performance Schema | Verified (1806 days) | S5 | 8.0.21 | Any | ARM | Optimal memory-barrier for performance-schema counter |
| 100962 | 2020-09-26 5:17 | 2020-10-26 11:42 | MySQL Server: Performance Schema | Analyzing (1724 days) | S3 | 5.7 | Any | Any | memory_summary_%_by_event_name Have different values |
| 101391 | 2020-10-30 3:04 | 2020-11-19 16:59 | MySQL Server: Performance Schema | Verified (1700 days) | S5 | 8.0, 8.0.22 | Any | Any | Performance Schema storage engine doesn't use index optimizations on group by |
| 101716 | 2020-11-23 9:30 | 2020-12-29 14:10 | MySQL Server: Performance Schema | Verified (1660 days) | S3 | 8.0.22,5.7.32 | Any | Any | P_S memory_summary_by_account_by_event_name table showing incorrect memory stats |
| 80523 | 2016-02-26 9:23 | 2020-12-30 4:05 | MySQL Server: Performance Schema | Verified (3428 days) | S3 | 8.0.0, 8.0.11 | Windows | Any | current_memory in sys.session can go negative! |
| 71293 | 2014-01-04 18:35 | 2021-08-08 20:45 | MySQL Server: Performance Schema | Verified (4209 days) | S3 | 5.6 | Any | Any | Manual page for P_S.FILE_INSTANCES table does not explain EVENT_NAME values |
| 89379 | 2018-01-24 11:41 | 2022-03-31 8:21 | MySQL Server: Performance Schema | Verified (2730 days) | S5 | 5.7.20, 5.7.21 | Any | Any | summary_by_user tables get extremely slow with many users. |
| 106985 | 2022-04-12 1:11 | 2022-04-12 7:44 | MySQL Server: Performance Schema | Verified (1191 days) | S3 | 8.0,5.7 | Any | Any | performance_schema.global_variables table shows trimmed data. |
| 108533 | 2022-09-19 12:04 | 2022-09-20 6:56 | MySQL Server: Performance Schema | Verified (1030 days) | S3 | 8.0, 8.0.30 | Any | Any | NULL query text in performance schema after thread killed |
| 109452 | 2022-12-21 10:22 | 2022-12-21 12:12 | MySQL Server: Performance Schema | Verified (938 days) | S3 | 8.0.31 | Any | Any | Misleading error message on storage engine failing to collect its log info |
| 110045 | 2023-02-13 11:07 | 2023-02-13 11:35 | MySQL Server: Performance Schema | Verified (884 days) | S3 | 8.0.32 | Linux | x86 | Negative numbers on digests |
| 110857 | 2023-04-28 5:56 | 2023-05-02 13:01 | MySQL Server: Performance Schema | Verified (810 days) | S3 | 8.0.30, 8.0.33, 5.7.42 | CentOS (CentOS (CentOS Linux 7 (Core))) | Any ((Linux 3.10.0-1160.49.1.el7.x86_64)) | invalid NO_INDEX_USED=1 metric when using UNION in queries. |
| 81394 | 2016-05-12 13:40 | 2023-09-18 15:54 | MySQL Server: Performance Schema | Verified (667 days) | S3 | 5.7.12,5.7.15 | Any | Any | Unable to change performance_schema whilst super_read_only is enabled |
| 112959 | 2023-11-03 17:53 | 2023-11-07 10:41 | MySQL Server: Performance Schema | Verified (618 days) | S3 | 8.0 | Any | Any | Wrong rows examined in P_S and slow log for Index Merge. |
| 113659 | 2024-01-17 7:55 | 2024-01-18 11:22 | MySQL Server: Performance Schema | Verified (545 days) | S3 | 8.0 | Any | Any | explain output "Using temporary" but query dosent create temporary table |
| 77293 | 2015-06-10 9:42 | 2024-01-25 17:10 | MySQL Server: Performance Schema | Verified (2115 days) | S3 | 5.6.16 | Linux (CentOS6.5) | Any | Wrong processlist_user in threads table for replication threads |
| 114300 | 2024-03-11 13:45 | 2024-03-11 14:41 | MySQL Server: Performance Schema | Verified (492 days) | S3 | 8.0 | Any | Any | The "fake index" of performance_schema.data_lock_waits causes slow sql |
| 114480 | 2024-03-26 7:36 | 2024-03-26 13:30 | MySQL Server: Performance Schema | Verified (477 days) | S3 | 8.0 | Any | Any | P_S doesn't record SQL or digest for prepared statements for Non-mysql client |
| 114545 | 2024-04-03 17:26 | 2024-04-04 9:40 | MySQL Server: Performance Schema | Verified (468 days) | S3 | 8.0.35, 8.0.36 | Any | Any | performance_schema.processlist tuncates query info |
| 114598 | 2024-04-09 15:19 | 2024-04-10 14:14 | MySQL Server: Performance Schema | Verified (462 days) | S3 | 8.0 | Windows | Any | The `variables_info` table in MySQL for Windows shows incorrect results. |
| 113930 | 2024-02-08 11:41 | 2024-05-30 5:54 | MySQL Server: Performance Schema | Verified (436 days) | S3 | 8.0 | Any | Any | performance_schema_show_processlist = ON generates inconsistent output |
| 115181 | 2024-05-31 2:11 | 2024-06-03 13:36 | MySQL Server: Performance Schema | Verified (408 days) | S3 | 8.0 | Any | Any | performance_schema.metadata_locks table doesn't show EXCLUSIVE locks correctly |
| 115298 | 2024-06-12 10:21 | 2024-06-12 14:04 | MySQL Server: Performance Schema | Verified (399 days) | S3 | 8.0 | Any | Any | partition table's io wait summary is not updated correct in PERFORMANCE_SCHEMA |
| 116328 | 2024-10-10 6:36 | 2024-10-10 9:09 | MySQL Server: Performance Schema | Verified (279 days) | S3 | 8.0.39 | Any | Any | Incorrect result performance_schema.events_waits_current when using PK index |
| 116526 | 2024-11-01 10:40 | 2024-11-04 9:59 | MySQL Server: Performance Schema | Verified (257 days) | S3 | 8.0 | Any | Any | Performance_schema consumer not affecting immediately |
| 117176 | 2025-01-10 6:20 | 2025-01-10 7:00 | MySQL Server: Performance Schema | Verified (187 days) | S3 | 8.0.40 | Any | Any | The stages about DDL in PFS.events_stages_history_long are wrong |
| 118114 | 2025-05-05 12:38 | 2025-05-05 13:01 | MySQL Server: Performance Schema | Verified (72 days) | S3 | 8.0.42 | Any | Any | INFO column in processlist tables truncates long queries despite using longtext type |
| 115943 | 2024-08-28 6:50 | 2025-07-11 5:06 | MySQL Server: Performance Schema | Verified (322 days) | S3 | 8.0, 8.4, 9.0, 8.0.39, 8.4.2 | Any | Any | STATEMENT_DIGEST() adds trailing semicolon to digest |
| « Show Previous 30 Entries | Showing 31-58 of 58 (Edit, Save, CSV, Feed) |
