Showing 1-30 of 49 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
---|---|---|---|---|---|---|---|---|---|
101716 | 2020-11-23 9:30 | 2020-12-29 14:10 | MySQL Server: Performance Schema | Verified (1186 days) | S3 | 8.0.22,5.7.32 | Any | Any | P_S memory_summary_by_account_by_event_name table showing incorrect memory stats |
68413 | 2013-02-18 2:45 | 2013-09-25 2:58 | MySQL Server: Performance Schema | Verified (3838 days) | S5 | 5.6.10, 5.6.13 | Any | Any | performance_schema overhead is at least 10% |
94925 | 2019-04-06 0:15 | 2019-04-24 13:37 | MySQL Server: Performance Schema | Verified (1801 days) | S3 | 8.0.15 | Any | Any | Wrong Query Sample Text in Performance Query |
96196 | 2019-07-13 7:17 | 2019-07-16 10:28 | MySQL Server: Performance Schema | Verified (1719 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 (1513 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 (1494 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 (1466 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 |
99121 | 2020-03-31 8:52 | 2020-06-23 2:23 | MySQL Server: Performance Schema | Verified (1459 days) | S3 | 8.0, 8.0.19 | Any | Any | Performance schema does a meaningless summary according to digest |
99204 | 2020-04-07 20:52 | 2020-04-13 15:53 | MySQL Server: Performance Schema | Verified (1451 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 (1359 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 (1340 days) | S3 | 5.7 | Any | Any | performance_schema.status_by_thread table not populating on Linux |
100432 | 2020-08-05 7:55 | 2020-08-05 14:03 | MySQL Server: Performance Schema | Verified (1332 days) | S5 | 8.0.21 | Any | ARM | Optimal memory-barrier for performance-schema counter |
91825 | 2018-07-30 6:16 | 2020-06-16 8:44 | MySQL Server: Performance Schema | Verified (2069 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 |
106985 | 2022-04-12 1:11 | 2022-04-12 7:44 | MySQL Server: Performance Schema | Verified (717 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 (556 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 (464 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 (410 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 (336 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. |
112035 | 2023-08-10 19:33 | 2024-02-21 1:00 | MySQL Server: Performance Schema | Verified (65 days) | S2 | 8.0.34 | Any | Any | Materializing performance_schema.data_locks can lead to excessive mem usage/OOM |
112959 | 2023-11-03 17:53 | 2023-11-07 10:41 | MySQL Server: Performance Schema | Verified (144 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 (71 days) | S3 | 8.0 | Any | Any | explain output "Using temporary" but query dosent create temporary table |
113930 | 2024-02-08 11:41 | 2024-02-09 8:37 | MySQL Server: Performance Schema | Verified (49 days) | S3 | 8.0 | Any | Any | performance_schema_show_processlist = ON generates inconsistent output |
114300 | 2024-03-11 13:45 | 2024-03-11 14:41 | MySQL Server: Performance Schema | Verified (18 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 (3 days) | S3 | 8.0 | Any | Any | P_S doesn't record SQL or digest for prepared statements for Non-mysql client |
89607 | 2018-02-09 13:47 | 2018-06-14 5:03 | MySQL Server: Performance Schema | Verified (2237 days) | S2 | 5.7 | Any | Any | MySQL crash in debug, PFS thread not handling singals. |
90631 | 2018-04-25 12:57 | 2018-04-25 15:14 | MySQL Server: Performance Schema | Verified (2165 days) | S3 | 8.0.11 | Ubuntu (14.04) | x86 | perfschema.statement_digest_query_sample test fails sporadically |
83912 | 2016-11-21 15:28 | 2020-03-09 16:52 | MySQL Server: Performance Schema | Verified (2683 days) | S3 | 5.6, 5.7, 5.6.34 | Any | Any | Time spent sleeping before entering InnoDB is not measured/reported separately |
83276 | 2016-10-06 1:03 | 2016-10-06 7:31 | MySQL Server: Performance Schema | Verified (2731 days) | S2 | 5.7,8 | Any | Any | P_S.replication_connection_status contains a zero datetime |
81394 | 2016-05-12 13:40 | 2023-09-18 15:54 | MySQL Server: Performance Schema | Verified (193 days) | S3 | 5.7.12,5.7.15 | Any | Any | Unable to change performance_schema whilst super_read_only is enabled |
71293 | 2014-01-04 18:35 | 2021-08-08 20:45 | MySQL Server: Performance Schema | Verified (3735 days) | S3 | 5.6 | Any | Any | Manual page for P_S.FILE_INSTANCES table does not explain EVENT_NAME values |
Showing 1-30 of 49 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |