| Showing 1-30 of 47 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
| ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
|---|---|---|---|---|---|---|---|---|---|
| 100962 | 2020-09-26 5:17 | 2020-10-26 11:42 | MySQL Server: Performance Schema | Analyzing (1135 days) | S3 | 5.7 | Any | Any | memory_summary_%_by_event_name Have different values |
| 69755 | 2013-07-16 12:58 | 2015-05-04 8:59 | MySQL Server: Performance Schema | Analyzing (3793 days) | S3 | 5.5.31-0ubuntu0.12.04.2 | Linux (Linux xxx 3.5.0-34-generic #55~precise1-Ubuntu SMP Fri Jun 7 16:25:50 UTC 2013 x86_64 x86_64 ) | Any | file_instances leaks with innodb_file_per_table |
| 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 |
| 112959 | 2023-11-03 17:53 | 2023-11-07 10:41 | MySQL Server: Performance Schema | Verified (29 days) | S3 | 8.0 | Any | Any | Wrong rows examined in P_S and slow log for Index Merge. |
| 81394 | 2016-05-12 13:40 | 2023-09-18 15:54 | MySQL Server: Performance Schema | Verified (78 days) | S3 | 5.7.12,5.7.15 | Any | Any | Unable to change performance_schema whilst super_read_only is enabled |
| 110857 | 2023-04-28 5:56 | 2023-05-02 13:01 | MySQL Server: Performance Schema | Verified (221 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. |
| 110405 | 2023-03-17 4:52 | 2023-03-20 5:46 | MySQL Server: Performance Schema | Verified (260 days) | S3 | 8.0 | Any | Any | Memory allocation by UT_NEW_THIS_FILE_PSI_KEY at startup cannot be instrumented |
| 110045 | 2023-02-13 11:07 | 2023-02-13 11:35 | MySQL Server: Performance Schema | Verified (295 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 (349 days) | S3 | 8.0.31 | Any | Any | Misleading error message on storage engine failing to collect its log info |
| 108533 | 2022-09-19 12:04 | 2022-09-20 6:56 | MySQL Server: Performance Schema | Verified (441 days) | S3 | 8.0, 8.0.30 | Any | Any | NULL query text in performance schema after thread killed |
| 106985 | 2022-04-12 1:11 | 2022-04-12 7:44 | MySQL Server: Performance Schema | Verified (602 days) | S3 | 8.0,5.7 | Any | Any | performance_schema.global_variables table shows trimmed data. |
| 104121 | 2021-06-26 15:19 | 2023-06-27 18:30 | MySQL Server: Performance Schema | Verified (840 days) | S3 | >=5.7.28 , >=8.0.18, 8.0.25, 5.7.34 | Any | Any | PSI_THREAD_INFO not updated while executing PREPARED STATEMENTS. |
| 101716 | 2020-11-23 9:30 | 2020-12-29 14:10 | MySQL Server: Performance Schema | Verified (1071 days) | S3 | 8.0.22,5.7.32 | Any | Any | P_S memory_summary_by_account_by_event_name table showing incorrect memory stats |
| 101391 | 2020-10-30 3:04 | 2020-11-19 16:59 | MySQL Server: Performance Schema | Verified (1111 days) | S5 | 8.0, 8.0.22 | Any | Any | Performance Schema storage engine doesn't use index optimizations on group by |
| 100432 | 2020-08-05 7:55 | 2020-08-05 14:03 | MySQL Server: Performance Schema | Verified (1217 days) | S5 | 8.0.21 | Any | ARM | Optimal memory-barrier for performance-schema counter |
| 100336 | 2020-07-27 15:58 | 2020-07-28 13:45 | MySQL Server: Performance Schema | Verified (1225 days) | S3 | 5.7 | Any | Any | performance_schema.status_by_thread table not populating on Linux |
| 100165 | 2020-07-09 2:41 | 2020-07-09 6:32 | MySQL Server: Performance Schema | Verified (1244 days) | S3 | 5.7.29, 5.7.30, 8.0.20 | Any | Any | The table is visible in performance_schema after renaming it |
| 99204 | 2020-04-07 20:52 | 2020-04-13 15:53 | MySQL Server: Performance Schema | Verified (1336 days) | S3 | 5.7.29, 8.0.19 | Any | Any | performance_schema threads table PROCESSLIST_INFO incorrect behaviour |
| 99121 | 2020-03-31 8:52 | 2020-06-23 2:23 | MySQL Server: Performance Schema | Verified (1344 days) | S3 | 8.0, 8.0.19 | Any | Any | Performance schema does a meaningless summary according to digest |
| 99039 | 2020-03-23 14:29 | 2020-03-27 1:33 | MySQL Server: Performance Schema | Verified (1351 days) | S3 | >= 5.6.46 , >=5.7.28, >=8.0.18, 5.6.47, 5.7.29, 8.0.19 | Any | Any | PSI thread info not getting updated after statement execution |
| 98734 | 2020-02-25 11:51 | 2020-02-25 14:32 | MySQL Server: Performance Schema | Verified (1379 days) | S3 | 5.7.29,8.0.19 | Any | Any | Same digest for different queries if we use integer value in ORDER BY caluse |
| 98498 | 2020-02-06 9:41 | 2020-02-07 13:01 | MySQL Server: Performance Schema | Verified (1398 days) | S3 | 5.7, 8.0 | Any (n.a.) | Any (n.a.) | P_S view status_by_thread does not reflect correct results |
| 77293 | 2015-06-10 9:42 | 2022-08-02 8:57 | MySQL Server: Performance Schema | Verified (1526 days) | S3 | 5.6.16 | Linux (CentOS6.5) | Any | Wrong processlist_user in threads table for replication threads |
| 96196 | 2019-07-13 7:17 | 2019-07-16 10:28 | MySQL Server: Performance Schema | Verified (1604 days) | S3 | 5.7.26, 8.0.16 | Any | Any | performance_schema_accounts_size and p_s_hosts_size limited by 16384 |
| 94925 | 2019-04-06 0:15 | 2019-04-24 13:37 | MySQL Server: Performance Schema | Verified (1686 days) | S3 | 8.0.15 | Any | Any | Wrong Query Sample Text in Performance Query |
| 91825 | 2018-07-30 6:16 | 2020-06-16 8:44 | MySQL Server: Performance Schema | Verified (1954 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 |
| 90631 | 2018-04-25 12:57 | 2018-04-25 15:14 | MySQL Server: Performance Schema | Verified (2050 days) | S3 | 8.0.11 | Ubuntu (14.04) | x86 | perfschema.statement_digest_query_sample test fails sporadically |
| 89607 | 2018-02-09 13:47 | 2018-06-14 5:03 | MySQL Server: Performance Schema | Verified (2122 days) | S2 | 5.7 | Any | Any | MySQL crash in debug, PFS thread not handling singals. |
| 89379 | 2018-01-24 11:41 | 2022-03-31 8:21 | MySQL Server: Performance Schema | Verified (2141 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 (2505 days) | S3 | 5.7.17 | Any | Any | replication worker thread status not showing on performance_schema.threads |
| Showing 1-30 of 47 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
