Showing 1-30 of 46 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
---|---|---|---|---|---|---|---|---|---|
59152 | 2010-12-24 8:52 | 2011-01-05 11:10 | MySQL Server: Performance Schema | Not a Bug (4831 days) | S1 | 5.6.1 | Any | Any | Valgrind warning in P_S in release build |
73954 | 2014-09-17 17:25 | 2014-09-18 11:44 | MySQL Server: Performance Schema | Not a Bug (3479 days) | S2 | 5.6 | Any | Any | Performance schema digest_text does not contain same text as original sql |
76428 | 2015-03-22 16:07 | 2015-03-31 12:22 | MySQL Server: Performance Schema | Not a Bug (3285 days) | S2 | 5.7.6-m16-log MySQL Community Server (GP | Any | Any | pre filtering is not working as it should in MySQL 5.7.6 |
108931 | 2022-10-31 7:30 | 2022-12-01 12:23 | MySQL Server: Performance Schema | Not a Bug (483 days) | S2 | 5.7 | Any | Any | The overflow of "unsigned long long int " causes wrong value of TIMER_START. |
63328 | 2011-11-19 15:57 | 2011-11-19 16:26 | MySQL Server: Performance Schema | Not a Bug (4513 days) | S2 | 5.5.18 | Windows (7/64 bit) | Any | Performance_Schema fails to load |
64129 | 2012-01-25 13:51 | 2012-01-27 5:06 | MySQL Server: Performance Schema | Not a Bug (4444 days) | S2 | 5.6.4-m7 | Windows | Any | Accounts table in Performance_Schema does not show metadata |
87498 | 2017-08-22 6:16 | 2018-10-25 8:47 | MySQL Server: Performance Schema | Not a Bug (1981 days) | S2 | mysql-5.7.19 | Any | Any | performance_schema_max_digest_length=1048576 could not work correctly |
95598 | 2019-06-02 11:10 | 2019-06-25 12:19 | MySQL Server: Performance Schema | Not a Bug (1756 days) | S3 | 8.0.12 | CentOS (CentOS release 6.5 (Final)) | Any | performance_shema.data_locks shows incorrect lock information |
79658 | 2015-12-16 8:49 | 2015-12-24 7:18 | MySQL Server: Performance Schema | Not a Bug (3017 days) | S3 | 5.7.10 | Any | Any | performance_schema statements by thread limited instrumentation |
79660 | 2015-12-16 9:02 | 2015-12-24 7:22 | MySQL Server: Performance Schema | Not a Bug (3017 days) | S3 | 5.7.10 | Any | Any | performance_schema transactions timer is inconsistent |
80366 | 2016-02-15 10:10 | 2016-02-15 13:18 | MySQL Server: Performance Schema | Not a Bug (2964 days) | S3 | 5.7.11, 5.7.12 | Any | Any | P_S does not show all Com_ status |
81632 | 2016-05-28 15:05 | 2016-06-08 7:33 | MySQL Server: Performance Schema | Not a Bug (2850 days) | S3 | 5.7.11, 5.7.12 | Any | Any | MySQL 5.7 GLOBAL_STATUS table lost much of the data |
82963 | 2016-09-13 2:53 | 2016-09-15 9:53 | MySQL Server: Performance Schema | Not a Bug (2751 days) | S3 | 5.7.15 | Any | Any | Rows appear in P_S when using DISTINCT, GROUP_BY, or UNION |
83084 | 2016-09-21 16:18 | 2016-09-22 16:02 | MySQL Server: Performance Schema | Not a Bug (2744 days) | S3 | 5.7.15 | Any | Any | sys.memory_global_% tables reduced usability due to max BP being returned |
84223 | 2016-12-16 3:03 | 2016-12-17 3:40 | MySQL Server: Performance Schema | Not a Bug (2658 days) | S3 | 5.6.35 | Debian | Any | performance_schema.socket_instances |
93592 | 2018-12-13 14:32 | 2019-01-15 13:48 | MySQL Server: Performance Schema | Not a Bug (1899 days) | S3 | 5.7.21 | Linux | x86 | mysql crash got signal 6 ,free(): invalid next size (normal): |
95504 | 2019-05-23 16:58 | 2019-05-28 13:32 | MySQL Server: Performance Schema | Not a Bug (1766 days) | S3 | 5.7.20-log | CentOS (CentOS (CentOS release 6.5 (Final))) | x86 (x86 (Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz)) | memory/performance_schema/table_handles has been allocated 9.06 GiB memory |
72229 | 2014-04-03 19:57 | 2014-04-04 19:16 | MySQL Server: Performance Schema | Not a Bug (3646 days) | S3 | any that has P_S | Any | Any | It is confusing that P_S records impacts of itself in P_S tables. |
105398 | 2021-11-01 13:44 | 2021-11-01 14:16 | MySQL Server: Performance Schema | Not a Bug (878 days) | S3 | 8.0.25 | Any | Any | Updating performance_schema succeeded but did not take effect |
105465 | 2021-11-05 3:38 | 2021-11-12 13:31 | MySQL Server: Performance Schema | Not a Bug (867 days) | S3 | 5.7.35-log | Linux | Any | Performance_schema stops to instrument some statistics and lost them |
106897 | 2022-04-02 0:14 | 2022-04-14 10:10 | MySQL Server: Performance Schema | Not a Bug (714 days) | S3 | 8.0.27, 8.0.28 | Linux | Any | performance_schema.metadata_locks wrong value for owner_thread_id |
108935 | 2022-10-31 11:31 | 2022-11-01 13:09 | MySQL Server: Performance Schema | Not a Bug (513 days) | S3 | 8.0.* | Any | Any | Don't show the right type of MDL in performance_schema.metadata_locks table |
110223 | 2023-02-27 11:33 | 2023-02-28 17:35 | MySQL Server: Performance Schema | Not a Bug (394 days) | S3 | 5.7.36 | Any | Any | Steady increase in memory usage in innodb/mem0mem |
111082 | 2023-05-19 0:37 | 2023-05-25 8:11 | MySQL Server: Performance Schema | Not a Bug (314 days) | S3 | 8.0.25 | Linux (RDS) | x86 | Queries to the Performance Schema Lock up all transactions until KILL |
113761 | 2024-01-25 13:33 | 2024-01-25 14:09 | MySQL Server: Performance Schema | Not a Bug (63 days) | S3 | 8.0.36 | Any (rhel-7.4) | Any (x86-64) | Access performance_schema.data_locks causes SQL execution stuck |
70252 | 2013-09-05 17:36 | 2013-09-06 18:07 | MySQL Server: Performance Schema | Not a Bug (3856 days) | S3 | 5.6.13 | Any | Any | How much does SUM_TIMER_WAIT from performance schema overstate waits? |
45552 | 2009-06-17 8:24 | 2009-06-18 0:34 | MySQL Server: Performance Schema | Not a Bug (5397 days) | S3 | mysql-6.0-perfschema | Any | Any | Performance schema: --performance_schema_max_mutex=1 gives no mutex waits events |
45922 | 2009-07-02 20:50 | 2014-01-20 9:29 | MySQL Server: Performance Schema | Not a Bug (3720 days) | S3 | 6.0-perfschema | Linux | Any | Performance schema: LOCK_event_loop showing up in events though should not be |
46351 | 2009-07-23 11:56 | 2009-07-24 18:45 | MySQL Server: Performance Schema | Not a Bug (5361 days) | S3 | Any | Any | PERFORMANCE_SCHEMA: Inconsistency between SUMMARY tables | |
46352 | 2009-07-23 11:59 | 2009-07-24 18:47 | MySQL Server: Performance Schema | Not a Bug (5361 days) | S3 | Any | Any | PERFORMANCE_SCHEMA: Inconsistencies in EVENTS_WAITS_SUMMARY |
Showing 1-30 of 46 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |