| Showing all 25 (Edit, Save, CSV, Feed) |
| ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
|---|---|---|---|---|---|---|---|---|---|
| 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 |
| 78068 | 2015-08-14 12:21 | 2015-08-18 13:08 | MySQL Server: Performance Schema | Verified (3397 days) | S3 | 5.7.8 | Any | Any | replication_* tables miss information about binary log position and other |
| 78303 | 2015-09-02 10:02 | 2016-09-22 7:50 | MySQL Server: Performance Schema | Verified (3379 days) | S3 | 5.7 | Any | Any | Add some DNS latency timings to performance_schema (host_cache?) |
| 79487 | 2015-12-02 6:21 | 2016-01-15 13:07 | MySQL Server: Performance Schema | Verified (3287 days) | S3 | 5.6, 5.7 | Any | Any | Provide non-Windows implementations for LF_BACKOFF |
| 81394 | 2016-05-12 13:40 | 2023-09-18 15:54 | MySQL Server: Performance Schema | Verified (441 days) | S3 | 5.7.12,5.7.15 | Any | Any | Unable to change performance_schema whilst super_read_only is enabled |
| 82663 | 2016-08-20 5:12 | 2017-06-27 7:40 | MySQL Server: Performance Schema | Verified (3020 days) | S1 | 5.7.13, 5.7.14 | Any | Any | mysqld hangs when accessing Performance Schema tables |
| 83276 | 2016-10-06 1:03 | 2016-10-06 7:31 | MySQL Server: Performance Schema | Verified (2979 days) | S2 | 5.7,8 | Any | Any | P_S.replication_connection_status contains a zero datetime |
| 83472 | 2016-10-20 21:39 | 2017-06-27 7:41 | MySQL Server: Performance Schema | Verified (2964 days) | S3 | 5.6.27, 5.6.34, 5.7.16 | Linux | Any | Connection Attributes were not correctly read after change user command |
| 83912 | 2016-11-21 15:28 | 2020-03-09 16:52 | MySQL Server: Performance Schema | Verified (2931 days) | S3 | 5.6, 5.7, 5.6.34 | Any | Any | Time spent sleeping before entering InnoDB is not measured/reported separately |
| 84609 | 2017-01-23 12:21 | 2017-06-27 7:43 | MySQL Server: Performance Schema | Verified (2870 days) | S3 | 5.7, 8.0, 5.7.17 | Any | Any | Lock information in TABLE_HANDLES misplaced |
| 84655 | 2017-01-24 22:59 | 2017-06-27 7:44 | MySQL Server: Performance Schema | Verified (2868 days) | S3 | 5.7.17 | Any | Any | replication worker thread status not showing on performance_schema.threads |
| 89379 | 2018-01-24 11:41 | 2022-03-31 8:21 | MySQL Server: Performance Schema | Verified (2504 days) | S5 | 5.7.20, 5.7.21 | Any | Any | summary_by_user tables get extremely slow with many users. |
| 89607 | 2018-02-09 13:47 | 2018-06-14 5:03 | MySQL Server: Performance Schema | Verified (2485 days) | S2 | 5.7 | Any | Any | MySQL crash in debug, PFS thread not handling singals. |
| 91825 | 2018-07-30 6:16 | 2020-06-16 8:44 | MySQL Server: Performance Schema | Verified (2317 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 |
| 96196 | 2019-07-13 7:17 | 2019-07-16 10:28 | MySQL Server: Performance Schema | Verified (1967 days) | S3 | 5.7.26, 8.0.16 | Any | Any | performance_schema_accounts_size and p_s_hosts_size limited by 16384 |
| 98498 | 2020-02-06 9:41 | 2020-02-07 13:01 | MySQL Server: Performance Schema | Verified (1761 days) | S3 | 5.7, 8.0 | Any (n.a.) | Any (n.a.) | P_S view status_by_thread does not reflect correct results |
| 98734 | 2020-02-25 11:51 | 2020-02-25 14:32 | MySQL Server: Performance Schema | Verified (1742 days) | S3 | 5.7.29,8.0.19 | Any | Any | Same digest for different queries if we use integer value in ORDER BY caluse |
| 99039 | 2020-03-23 14:29 | 2020-03-27 1:33 | MySQL Server: Performance Schema | Verified (1714 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 |
| 99204 | 2020-04-07 20:52 | 2020-04-13 15:53 | MySQL Server: Performance Schema | Verified (1699 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 (1607 days) | S3 | 5.7.29, 5.7.30, 8.0.20 | Any | Any | The table is visible in performance_schema after renaming it |
| 100336 | 2020-07-27 15:58 | 2020-07-28 13:45 | MySQL Server: Performance Schema | Verified (1588 days) | S3 | 5.7 | Any | Any | performance_schema.status_by_thread table not populating on Linux |
| 100962 | 2020-09-26 5:17 | 2020-10-26 11:42 | MySQL Server: Performance Schema | Analyzing (1498 days) | S3 | 5.7 | Any | Any | memory_summary_%_by_event_name Have different values |
| 101716 | 2020-11-23 9:30 | 2020-12-29 14:10 | MySQL Server: Performance Schema | Verified (1434 days) | S3 | 8.0.22,5.7.32 | Any | Any | P_S memory_summary_by_account_by_event_name table showing incorrect memory stats |
| 106985 | 2022-04-12 1:11 | 2022-04-12 7:44 | MySQL Server: Performance Schema | Verified (965 days) | S3 | 8.0,5.7 | Any | Any | performance_schema.global_variables table shows trimmed data. |
| 110857 | 2023-04-28 5:56 | 2023-05-02 13:01 | MySQL Server: Performance Schema | Verified (584 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. |
| Showing all 25 (Edit, Save, CSV, Feed) |
