Showing 1-30 of 46 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
---|---|---|---|---|---|---|---|---|---|
113761 | 2024-01-25 13:33 | 2024-01-25 14:09 | MySQL Server: Performance Schema | Not a Bug (64 days) | S3 | 8.0.36 | Any (rhel-7.4) | Any (x86-64) | Access performance_schema.data_locks causes SQL execution stuck |
111082 | 2023-05-19 0:37 | 2023-05-25 8:11 | MySQL Server: Performance Schema | Not a Bug (315 days) | S3 | 8.0.25 | Linux (RDS) | x86 | Queries to the Performance Schema Lock up all transactions until KILL |
110223 | 2023-02-27 11:33 | 2023-02-28 17:35 | MySQL Server: Performance Schema | Not a Bug (395 days) | S3 | 5.7.36 | Any | Any | Steady increase in memory usage in innodb/mem0mem |
108931 | 2022-10-31 7:30 | 2022-12-01 12:23 | MySQL Server: Performance Schema | Not a Bug (484 days) | S2 | 5.7 | Any | Any | The overflow of "unsigned long long int " causes wrong value of TIMER_START. |
108935 | 2022-10-31 11:31 | 2022-11-01 13:09 | MySQL Server: Performance Schema | Not a Bug (514 days) | S3 | 8.0.* | Any | Any | Don't show the right type of MDL in performance_schema.metadata_locks table |
106897 | 2022-04-02 0:14 | 2022-04-14 10:10 | MySQL Server: Performance Schema | Not a Bug (715 days) | S3 | 8.0.27, 8.0.28 | Linux | Any | performance_schema.metadata_locks wrong value for owner_thread_id |
105465 | 2021-11-05 3:38 | 2021-11-12 13:31 | MySQL Server: Performance Schema | Not a Bug (868 days) | S3 | 5.7.35-log | Linux | Any | Performance_schema stops to instrument some statistics and lost them |
105398 | 2021-11-01 13:44 | 2021-11-01 14:16 | MySQL Server: Performance Schema | Not a Bug (879 days) | S3 | 8.0.25 | Any | Any | Updating performance_schema succeeded but did not take effect |
95598 | 2019-06-02 11:10 | 2019-06-25 12:19 | MySQL Server: Performance Schema | Not a Bug (1757 days) | S3 | 8.0.12 | CentOS (CentOS release 6.5 (Final)) | Any | performance_shema.data_locks shows incorrect lock information |
95504 | 2019-05-23 16:58 | 2019-05-28 13:32 | MySQL Server: Performance Schema | Not a Bug (1767 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 |
93592 | 2018-12-13 14:32 | 2019-01-15 13:48 | MySQL Server: Performance Schema | Not a Bug (1900 days) | S3 | 5.7.21 | Linux | x86 | mysql crash got signal 6 ,free(): invalid next size (normal): |
87498 | 2017-08-22 6:16 | 2018-10-25 8:47 | MySQL Server: Performance Schema | Not a Bug (1982 days) | S2 | mysql-5.7.19 | Any | Any | performance_schema_max_digest_length=1048576 could not work correctly |
84223 | 2016-12-16 3:03 | 2016-12-17 3:40 | MySQL Server: Performance Schema | Not a Bug (2659 days) | S3 | 5.6.35 | Debian | Any | performance_schema.socket_instances |
83084 | 2016-09-21 16:18 | 2016-09-22 16:02 | MySQL Server: Performance Schema | Not a Bug (2745 days) | S3 | 5.7.15 | Any | Any | sys.memory_global_% tables reduced usability due to max BP being returned |
82963 | 2016-09-13 2:53 | 2016-09-15 9:53 | MySQL Server: Performance Schema | Not a Bug (2752 days) | S3 | 5.7.15 | Any | Any | Rows appear in P_S when using DISTINCT, GROUP_BY, or UNION |
81632 | 2016-05-28 15:05 | 2016-06-08 7:33 | MySQL Server: Performance Schema | Not a Bug (2851 days) | S3 | 5.7.11, 5.7.12 | Any | Any | MySQL 5.7 GLOBAL_STATUS table lost much of the data |
80366 | 2016-02-15 10:10 | 2016-02-15 13:18 | MySQL Server: Performance Schema | Not a Bug (2965 days) | S3 | 5.7.11, 5.7.12 | Any | Any | P_S does not show all Com_ status |
79660 | 2015-12-16 9:02 | 2015-12-24 7:22 | MySQL Server: Performance Schema | Not a Bug (3018 days) | S3 | 5.7.10 | Any | Any | performance_schema transactions timer is inconsistent |
79658 | 2015-12-16 8:49 | 2015-12-24 7:18 | MySQL Server: Performance Schema | Not a Bug (3018 days) | S3 | 5.7.10 | Any | Any | performance_schema statements by thread limited instrumentation |
76428 | 2015-03-22 16:07 | 2015-03-31 12:22 | MySQL Server: Performance Schema | Not a Bug (3286 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 |
75794 | 2015-02-05 13:32 | 2015-02-16 23:50 | MySQL Server: Performance Schema | Not a Bug (3329 days) | S3 | 5.6.23/5.7 | Any | Any | Performance Schema statement digest generation is broken with ALTER PARTITION |
71641 | 2014-02-09 23:49 | 2014-10-01 13:34 | MySQL Server: Performance Schema | Not a Bug (3467 days) | S5 | 5.7.3, 5.7.4 | Linux | Any | table_setup_actors::update_row_values function is unnecessary. |
73954 | 2014-09-17 17:25 | 2014-09-18 11:44 | MySQL Server: Performance Schema | Not a Bug (3480 days) | S2 | 5.6 | Any | Any | Performance schema digest_text does not contain same text as original sql |
72229 | 2014-04-03 19:57 | 2014-04-04 19:16 | MySQL Server: Performance Schema | Not a Bug (3647 days) | S3 | any that has P_S | Any | Any | It is confusing that P_S records impacts of itself in P_S tables. |
72218 | 2014-04-03 11:37 | 2014-04-04 19:06 | MySQL Server: Performance Schema | Not a Bug (3647 days) | S3 | 5.6.17 | Any | Any | Bogus connections in P_S.users? |
72138 | 2014-03-26 22:41 | 2014-03-27 15:37 | MySQL Server: Performance Schema | Not a Bug (3655 days) | S3 | 5.7.3 | Linux | Any | There art no MYSQL_SET_TRANSACTION_TRXID in source code. |
71818 | 2014-02-24 15:23 | 2014-02-25 9:04 | MySQL Server: Performance Schema | Not a Bug (3685 days) | S3 | 5.6.16/5.7 | Any | Any | Type column in SHOW PERFORMANCE_SCHEMA STATUS is redundant |
71733 | 2014-02-16 6:39 | 2014-02-21 4:24 | MySQL Server: Performance Schema | Not a Bug (3689 days) | S3 | 5.7.3 | Linux | Any | I cannot get result of performance_schema.socket_instances |
45922 | 2009-07-02 20:50 | 2014-01-20 9:29 | MySQL Server: Performance Schema | Not a Bug (3721 days) | S3 | 6.0-perfschema | Linux | Any | Performance schema: LOCK_event_loop showing up in events though should not be |
71292 | 2014-01-04 18:09 | 2014-01-06 13:17 | MySQL Server: Performance Schema | Not a Bug (3735 days) | S3 | 5.6.15 | Any | Any | Wrong length is used for FILE_NAME column in FILE_INSTANCES table |
Showing 1-30 of 46 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |