Showing 1-30 of 51 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
---|---|---|---|---|---|---|---|---|---|
76956 | 2015-05-06 14:34 | 2018-10-31 7:36 | MySQL Server: Performance Schema | Verified (3250 days) | S2 | 5.6, 8.0.13 | Any | Any | Threads table PROCESSLIST_INFO truncate query |
69755 | 2013-07-16 12:58 | 2015-05-04 8:59 | MySQL Server: Performance Schema | Analyzing (3908 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 |
104121 | 2021-06-26 15:19 | 2024-03-20 14:37 | MySQL Server: Performance Schema | Verified (955 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. |
89379 | 2018-01-24 11:41 | 2022-03-31 8:21 | MySQL Server: Performance Schema | Verified (2256 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 (2620 days) | S3 | 5.7.17 | Any | Any | replication worker thread status not showing on performance_schema.threads |
84609 | 2017-01-23 12:21 | 2017-06-27 7:43 | MySQL Server: Performance Schema | Verified (2622 days) | S3 | 5.7, 8.0, 5.7.17 | Any | Any | Lock information in TABLE_HANDLES misplaced |
83472 | 2016-10-20 21:39 | 2017-06-27 7:41 | MySQL Server: Performance Schema | Verified (2716 days) | S3 | 5.6.27, 5.6.34, 5.7.16 | Linux | Any | Connection Attributes were not correctly read after change user command |
101391 | 2020-10-30 3:04 | 2020-11-19 16:59 | MySQL Server: Performance Schema | Verified (1226 days) | S5 | 8.0, 8.0.22 | Any | Any | Performance Schema storage engine doesn't use index optimizations on group by |
82663 | 2016-08-20 5:12 | 2017-06-27 7:40 | MySQL Server: Performance Schema | Verified (2772 days) | S1 | 5.7.13, 5.7.14 | Any | Any | mysqld hangs when accessing Performance Schema tables |
80523 | 2016-02-26 9:23 | 2020-12-30 4:05 | MySQL Server: Performance Schema | Verified (2954 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 (2964 days) | S3 | 8.0.0-m17-enterprise-commercial-advanced | Any | Any | Built-in mysql functions are case sensitive when used in query digest hash |
79487 | 2015-12-02 6:21 | 2016-01-15 13:07 | MySQL Server: Performance Schema | Verified (3039 days) | S3 | 5.6, 5.7 | Any | Any | Provide non-Windows implementations for LF_BACKOFF |
79011 | 2015-10-28 21:53 | 2017-06-27 7:23 | MySQL Server: Performance Schema | Verified (3052 days) | S3 | 5.6.24 | Any | Any | truncated digest_text values don't always end with "..." |
78303 | 2015-09-02 10:02 | 2016-09-22 7:50 | MySQL Server: Performance Schema | Verified (3131 days) | S3 | 5.7 | Any | Any | Add some DNS latency timings to performance_schema (host_cache?) |
78068 | 2015-08-14 12:21 | 2015-08-18 13:08 | MySQL Server: Performance Schema | Verified (3149 days) | S3 | 5.7.8 | Any | Any | replication_* tables miss information about binary log position and other |
77293 | 2015-06-10 9:42 | 2024-01-25 17:10 | MySQL Server: Performance Schema | Verified (1641 days) | S3 | 5.6.16 | Linux (CentOS6.5) | Any | Wrong processlist_user in threads table for replication threads |
73967 | 2014-09-18 12:35 | 2015-07-20 8:17 | MySQL Server: Performance Schema | Verified (3363 days) | S3 | 5.6.20 | Any | Any | Incorrect string value for sql_text |
73112 | 2014-06-25 11:47 | 2016-02-23 15:52 | MySQL Server: Performance Schema | Verified (2957 days) | S3 | 5.6.16, 5.6.17, 5.6.20 | Linux | Any | Performance Schema - Statement Tables - Stored Procedures Counters are 0 |
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 |
71204 | 2013-12-22 15:42 | 2014-01-06 13:43 | MySQL Server: Performance Schema | Verified (3748 days) | S3 | 5.6.14, 5.6.16 | Any | Any | Timing for stages in P_S is different from what SHOW PROFILE reports |
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 |
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 |
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 |
100962 | 2020-09-26 5:17 | 2020-10-26 11:42 | MySQL Server: Performance Schema | Analyzing (1250 days) | S3 | 5.7 | Any | Any | memory_summary_%_by_event_name Have different values |
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 |
Showing 1-30 of 51 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |