Showing all 17 (Edit, Save, CSV, Feed) |
ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
---|---|---|---|---|---|---|---|---|---|
45407 | 2009-06-09 16:12 | 2011-02-16 23:44 | MySQL Server: Performance Schema | Can't repeat (5371 days) | S3 | mysql-6.0-perfschema | Linux (SUSE 10 / 64-bit) | Any | Performance Schema: replication fails |
104367 | 2021-07-20 13:14 | 2021-07-21 1:45 | MySQL Server: Performance Schema | Can't repeat (1003 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 (1180 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 (1305 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 (1472 days) | S1 | 5.7.29 | CentOS | Any | Crash on concurrent access to events_statements_history_long |
96774 | 2019-09-06 7:42 | 2019-09-06 13:28 | MySQL Server: Performance Schema | Can't repeat (1687 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 (1905 days) | S3 | 5.7 | Any | Any | Contribution: missing header on Linux |
85910 | 2017-04-12 3:00 | 2023-10-24 14:22 | MySQL Server: Performance Schema | Can't repeat (178 days) | S3 | 5.6.35, 5.6.36 | Any | Any | Increased Performance_Schema overhead on Sending data |
81961 | 2016-06-21 21:39 | 2019-09-19 21:18 | MySQL Server: Performance Schema | Can't repeat (1674 days) | S3 | 5.6.29 | Any | Any | sum_rows_affected populated for simple selects |
78772 | 2015-10-09 7:28 | 2015-10-14 9:30 | MySQL Server: Performance Schema | Can't repeat (3110 days) | S3 | mysql5.7.8-rc | Red Hat | Any | Gtids-based replication, all tables of performance_schema will disappear |
77603 | 2015-07-02 17:25 | 2015-08-08 19:30 | MySQL Server: Performance Schema | Can't repeat (3177 days) | S3 | 5.7.7 | Any | Any | prepared_statements_instances table does not update SUM_* columns |
77344 | 2015-06-14 2:18 | 2023-10-10 13:11 | MySQL Server: Performance Schema | Can't repeat (192 days) | S3 | 5.6.25 | Any | Any | Slow start up due to performance_schema overhead on MySQL 5.6 |
77060 | 2015-05-17 7:42 | 2015-09-04 11:23 | MySQL Server: Performance Schema | Can't repeat (3150 days) | S3 | 5.6.22,5.6.24 | Any (CentOS 6) | Any | P_S.file_summary_by_instance SUM_TIMER_WAIT sometimes decreases |
76090 | 2015-03-02 9:19 | 2015-03-19 16:39 | MySQL Server: Performance Schema | Can't repeat (3319 days) | S3 | 5.6.23 | Linux (CentOS 7) | Any | Assertion `from->m_byte_count == 0' failed in perfschema/pfs_digest.h:113 |
45420 | 2009-06-09 23:39 | 2011-02-16 23:44 | MySQL Server: Performance Schema | Can't repeat (5383 days) | S3 | mysql-6.0-perfschema | Linux (SUSE 10 / 64-bit) | Any | Performance Schema: can't update setup_instruments in a loop |
44954 | 2009-05-19 14:03 | 2011-02-16 23:43 | MySQL Server: Performance Schema | Can't repeat (5383 days) | S3 | 6.0-perfschema | Linux (64bit) | Any | PerformanceSchema: --performance-schema-max-thread=0 has strange effects |
109490 | 2022-12-28 3:39 | 2023-04-03 12:40 | MySQL Server: Performance Schema | Can't repeat (472 days) | S3 | 8.0.24 | CentOS (7.7.1908) | x86 (x86_64) | memory_summary_by_thread_by_event_name display wrong value |
Showing all 17 (Edit, Save, CSV, Feed) |