Showing 1-30 of 53 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
---|---|---|---|---|---|---|---|---|---|
114545 | 2024-04-03 17:26 | 2024-04-04 9:40 | MySQL Server: Performance Schema | Verified (14 days) | S3 | 8.0.35, 8.0.36 | Any | Any | performance_schema.processlist tuncates query info |
112035 | 2023-08-10 19:33 | 2024-02-21 1:00 | MySQL Server: Performance Schema | Verified (85 days) | S2 | 8.0.34 | Any | Any | Materializing performance_schema.data_locks can lead to excessive mem usage/OOM |
110045 | 2023-02-13 11:07 | 2023-02-13 11:35 | MySQL Server: Performance Schema | Verified (430 days) | S3 | 8.0.32 | Linux | x86 | Negative numbers on digests |
109452 | 2022-12-21 10:22 | 2022-12-21 12:12 | MySQL Server: Performance Schema | Verified (484 days) | S3 | 8.0.31 | Any | Any | Misleading error message on storage engine failing to collect its log info |
110857 | 2023-04-28 5:56 | 2023-05-02 13:01 | MySQL Server: Performance Schema | Verified (356 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. |
101716 | 2020-11-23 9:30 | 2020-12-29 14:10 | MySQL Server: Performance Schema | Verified (1206 days) | S3 | 8.0.22,5.7.32 | Any | Any | P_S memory_summary_by_account_by_event_name table showing incorrect memory stats |
100432 | 2020-08-05 7:55 | 2020-08-05 14:03 | MySQL Server: Performance Schema | Verified (1352 days) | S5 | 8.0.21 | Any | ARM | Optimal memory-barrier for performance-schema counter |
94925 | 2019-04-06 0:15 | 2019-04-24 13:37 | MySQL Server: Performance Schema | Verified (1821 days) | S3 | 8.0.15 | Any | Any | Wrong Query Sample Text in Performance Query |
90631 | 2018-04-25 12:57 | 2018-04-25 15:14 | MySQL Server: Performance Schema | Verified (2185 days) | S3 | 8.0.11 | Ubuntu (14.04) | x86 | perfschema.statement_digest_query_sample test fails sporadically |
80523 | 2016-02-26 9:23 | 2020-12-30 4:05 | MySQL Server: Performance Schema | Verified (2974 days) | S3 | 8.0.0, 8.0.11 | Windows | Any | current_memory in sys.session can go negative! |
80372 | 2016-02-15 12:58 | 2017-06-27 7:25 | MySQL Server: Performance Schema | Verified (2984 days) | S3 | 8.0.0-m17-enterprise-commercial-advanced | Any | Any | Built-in mysql functions are case sensitive when used in query digest hash |
106985 | 2022-04-12 1:11 | 2022-04-12 7:44 | MySQL Server: Performance Schema | Verified (737 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 (576 days) | S3 | 8.0, 8.0.30 | Any | Any | NULL query text in performance schema after thread killed |
101391 | 2020-10-30 3:04 | 2020-11-19 16:59 | MySQL Server: Performance Schema | Verified (1246 days) | S5 | 8.0, 8.0.22 | Any | Any | Performance Schema storage engine doesn't use index optimizations on group by |
99121 | 2020-03-31 8:52 | 2020-06-23 2:23 | MySQL Server: Performance Schema | Verified (1479 days) | S3 | 8.0, 8.0.19 | Any | Any | Performance schema does a meaningless summary according to digest |
113930 | 2024-02-08 11:41 | 2024-02-09 8:37 | MySQL Server: Performance Schema | Verified (69 days) | S3 | 8.0 | Any | Any | performance_schema_show_processlist = ON generates inconsistent output |
114598 | 2024-04-09 15:19 | 2024-04-10 14:14 | MySQL Server: Performance Schema | Verified (8 days) | S3 | 8.0 | Windows | Any | The `variables_info` table in MySQL for Windows shows incorrect results. |
114480 | 2024-03-26 7:36 | 2024-03-26 13:30 | MySQL Server: Performance Schema | Verified (23 days) | S3 | 8.0 | Any | Any | P_S doesn't record SQL or digest for prepared statements for Non-mysql client |
114300 | 2024-03-11 13:45 | 2024-03-11 14:41 | MySQL Server: Performance Schema | Verified (38 days) | S3 | 8.0 | Any | Any | The "fake index" of performance_schema.data_lock_waits causes slow sql |
112959 | 2023-11-03 17:53 | 2023-11-07 10:41 | MySQL Server: Performance Schema | Verified (164 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 (91 days) | S3 | 8.0 | Any | Any | explain output "Using temporary" but query dosent create temporary table |
78068 | 2015-08-14 12:21 | 2015-08-18 13:08 | MySQL Server: Performance Schema | Verified (3169 days) | S3 | 5.7.8 | Any | Any | replication_* tables miss information about binary log position and other |
72825 | 2014-06-01 3:47 | 2014-08-10 8:15 | MySQL Server: Performance Schema | Verified | S3 | 5.7.4 | Linux (OL6) | Any | WORKER_ID in replication_execute_status_by_worker is always 1 SQL Not Running |
98734 | 2020-02-25 11:51 | 2020-02-25 14:32 | MySQL Server: Performance Schema | Verified (1514 days) | S3 | 5.7.29,8.0.19 | Any | Any | Same digest for different queries if we use integer value in ORDER BY caluse |
99204 | 2020-04-07 20:52 | 2020-04-13 15:53 | MySQL Server: Performance Schema | Verified (1471 days) | S3 | 5.7.29, 8.0.19 | Any | Any | performance_schema threads table PROCESSLIST_INFO incorrect behaviour |
100165 | 2020-07-09 2:41 | 2020-07-09 6:32 | MySQL Server: Performance Schema | Verified (1379 days) | S3 | 5.7.29, 5.7.30, 8.0.20 | Any | Any | The table is visible in performance_schema after renaming it |
96196 | 2019-07-13 7:17 | 2019-07-16 10:28 | MySQL Server: Performance Schema | Verified (1739 days) | S3 | 5.7.26, 8.0.16 | Any | Any | performance_schema_accounts_size and p_s_hosts_size limited by 16384 |
91825 | 2018-07-30 6:16 | 2020-06-16 8:44 | MySQL Server: Performance Schema | Verified (2089 days) | S3 | 5.7.23, 8.0.12, 5.7.22 | Any | Any | The user table is renamed as "SYSTEM_USER" in DIGEST_TEXT of history tables |
89379 | 2018-01-24 11:41 | 2022-03-31 8:21 | MySQL Server: Performance Schema | Verified (2276 days) | S5 | 5.7.20, 5.7.21 | Any | Any | summary_by_user tables get extremely slow with many users. |
84655 | 2017-01-24 22:59 | 2017-06-27 7:44 | MySQL Server: Performance Schema | Verified (2640 days) | S3 | 5.7.17 | Any | Any | replication worker thread status not showing on performance_schema.threads |
Showing 1-30 of 53 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |