| Showing 1-30 of 442 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
| ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
|---|---|---|---|---|---|---|---|---|---|
| 110877 | 2023-05-01 16:07 | 2023-05-03 12:43 | MySQL Server: Performance Schema | Analyzing (927 days) | S4 | 8.0.31 | Linux (Ubuntu 22.04) | Any (n.a.) | Timestamp of established connection |
| 100962 | 2020-09-26 5:17 | 2020-10-26 11:42 | MySQL Server: Performance Schema | Analyzing (1846 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 (4504 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 |
| 116153 | 2024-09-19 1:40 | 2024-09-23 12:51 | MySQL Server: Performance Schema | Can't repeat (418 days) | S3 | 8.0.24 | Any | Any | Performance_schema.processlist’s INFO column of execute command is NULL |
| 85910 | 2017-04-12 3:00 | 2023-10-24 14:22 | MySQL Server: Performance Schema | Can't repeat (753 days) | S3 | 5.6.35, 5.6.36 | Any | Any | Increased Performance_Schema overhead on Sending data |
| 77344 | 2015-06-14 2:18 | 2023-10-10 13:11 | MySQL Server: Performance Schema | Can't repeat (767 days) | S3 | 5.6.25 | Any | Any | Slow start up due to performance_schema overhead on MySQL 5.6 |
| 109490 | 2022-12-28 3:39 | 2023-04-03 12:40 | MySQL Server: Performance Schema | Can't repeat (1047 days) | S3 | 8.0.24 | CentOS (7.7.1908) | x86 (x86_64) | memory_summary_by_thread_by_event_name display wrong value |
| 104367 | 2021-07-20 13:14 | 2021-07-21 1:45 | MySQL Server: Performance Schema | Can't repeat (1578 days) | S3 | 8.0.25 | Linux | Any | Query all the locks in performance.schema.data_locks cause mysqld oom |
| 102055 | 2020-12-22 22:56 | 2021-01-25 13:04 | MySQL Server: Performance Schema | Can't repeat (1755 days) | S3 | 5.7.19-log | Windows | Any | Performance Schema does not report procedure call |
| 100883 | 2020-09-17 19:21 | 2020-09-22 12:02 | MySQL Server: Performance Schema | Can't repeat (1880 days) | S3 | 8.0.12 | Linux | Any | Performance Schema - Statement Tables - Digest is Null in Stored Procedures |
| 99077 | 2020-03-26 9:47 | 2020-04-08 13:18 | MySQL Server: Performance Schema | Can't repeat (2047 days) | S1 | 5.7.29 | CentOS | Any | Crash on concurrent access to events_statements_history_long |
| 81961 | 2016-06-21 21:39 | 2019-09-19 21:18 | MySQL Server: Performance Schema | Can't repeat (2249 days) | S3 | 5.6.29 | Any | Any | sum_rows_affected populated for simple selects |
| 96774 | 2019-09-06 7:42 | 2019-09-06 13:28 | MySQL Server: Performance Schema | Can't repeat (2262 days) | S3 | 5.6.23,5.7.21 | CentOS | Any | The timer_start in performance_schema is much smaller than mysql' uptime |
| 88960 | 2017-12-18 16:29 | 2019-01-31 12:30 | MySQL Server: Performance Schema | Can't repeat (2480 days) | S3 | 5.7 | Any | Any | Contribution: missing header on Linux |
| 78772 | 2015-10-09 7:28 | 2015-10-14 9:30 | MySQL Server: Performance Schema | Can't repeat (3685 days) | S3 | mysql5.7.8-rc | Red Hat | Any | Gtids-based replication, all tables of performance_schema will disappear |
| 77060 | 2015-05-17 7:42 | 2015-09-04 11:23 | MySQL Server: Performance Schema | Can't repeat (3725 days) | S3 | 5.6.22,5.6.24 | Any (CentOS 6) | Any | P_S.file_summary_by_instance SUM_TIMER_WAIT sometimes decreases |
| 77603 | 2015-07-02 17:25 | 2015-08-08 19:30 | MySQL Server: Performance Schema | Can't repeat (3752 days) | S3 | 5.7.7 | Any | Any | prepared_statements_instances table does not update SUM_* columns |
| 76090 | 2015-03-02 9:19 | 2015-03-19 16:39 | MySQL Server: Performance Schema | Can't repeat (3894 days) | S3 | 5.6.23 | Linux (CentOS 7) | Any | Assertion `from->m_byte_count == 0' failed in perfschema/pfs_digest.h:113 |
| 45407 | 2009-06-09 16:12 | 2011-02-16 23:44 | MySQL Server: Performance Schema | Can't repeat (5946 days) | S3 | mysql-6.0-perfschema | Linux (SUSE 10 / 64-bit) | Any | Performance Schema: replication fails |
| 44954 | 2009-05-19 14:03 | 2011-02-16 23:43 | MySQL Server: Performance Schema | Can't repeat (5958 days) | S3 | 6.0-perfschema | Linux (64bit) | Any | PerformanceSchema: --performance-schema-max-thread=0 has strange effects |
| 45420 | 2009-06-09 23:39 | 2011-02-16 23:44 | MySQL Server: Performance Schema | Can't repeat (5958 days) | S3 | mysql-6.0-perfschema | Linux (SUSE 10 / 64-bit) | Any | Performance Schema: can't update setup_instruments in a loop |
| 99121 | 2020-03-31 8:52 | 2025-09-30 11:03 | MySQL Server: Performance Schema | Closed (46 days) | S3 | 8.0, 8.0.19 | Any | Any | Performance schema does a meaningless summary according to digest |
| 117772 | 2025-03-22 8:41 | 2025-06-17 15:55 | MySQL Server: Performance Schema | Closed (151 days) | S5 | 8.0, 8.4., 9.2.0 | Any | Any | Debug code in pfs_get_thread_statement_locker_vc() leaking to release builds |
| 117625 | 2025-03-05 21:35 | 2025-06-17 15:43 | MySQL Server: Performance Schema | Closed (151 days) | S3 | 9.2.0, 8.4.4, 8.0.41 | Any | Any | Error in code comment in P_S: s/start_file_open_wait/end_file_open_wait/. |
| 116625 | 2024-11-12 7:15 | 2025-03-03 17:15 | MySQL Server: Performance Schema | Closed (347 days) | S3 | 8.0.40 | Any | Any | The LOCK_TYPE in PFS.metadata_locks not change after MDL upgrade or downgrade |
| 112035 | 2023-08-10 19:33 | 2024-09-19 9:05 | MySQL Server: Performance Schema | Closed (422 days) | S2 | 8.0.37, 8.4.0 | Any | Any | Materializing performance_schema.data_locks can lead to excessive mem usage/OOM |
| 113761 | 2024-01-25 13:33 | 2024-09-24 12:57 | MySQL Server: Performance Schema | Closed (422 days) | S5 | 8.0.36 | Any (rhel-7.4) | Any (x86-64) | Access performance_schema.data_locks causes SQL execution stuck |
| 115844 | 2024-08-15 13:09 | 2024-08-20 14:35 | MySQL Server: Performance Schema | Closed (452 days) | S3 | 9.0 | Any | Any | Contribution: Fix erroneous comment in table_hosts.h |
| 104121 | 2021-06-26 15:19 | 2024-07-02 19:31 | MySQL Server: Performance Schema | Closed (540 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. |
| 110555 | 2023-03-29 22:22 | 2024-01-17 17:33 | MySQL Server: Performance Schema | Closed (726 days) | S3 | 8.0.32 | Any | Any | Some performance schema tables return invalid rows |
| Showing 1-30 of 442 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
