| « Show Previous 30 Entries | Showing 31-46 of 46 (Edit, Save, CSV, Feed) |
| ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
|---|---|---|---|---|---|---|---|---|---|
| 81632 | 2016-05-28 15:05 | 2016-06-08 7:33 | MySQL Server: Performance Schema | Not a Bug (2877 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 (2778 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 (2771 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 (2685 days) | S3 | 5.6.35 | Debian | Any | performance_schema.socket_instances |
| 87498 | 2017-08-22 6:16 | 2018-10-25 8:47 | MySQL Server: Performance Schema | Not a Bug (2008 days) | S2 | mysql-5.7.19 | Any | Any | performance_schema_max_digest_length=1048576 could not work correctly |
| 93592 | 2018-12-13 14:32 | 2019-01-15 13:48 | MySQL Server: Performance Schema | Not a Bug (1926 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 (1793 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 |
| 95598 | 2019-06-02 11:10 | 2019-06-25 12:19 | MySQL Server: Performance Schema | Not a Bug (1783 days) | S3 | 8.0.12 | CentOS (CentOS release 6.5 (Final)) | Any | performance_shema.data_locks shows incorrect lock information |
| 105398 | 2021-11-01 13:44 | 2021-11-01 14:16 | MySQL Server: Performance Schema | Not a Bug (905 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 (894 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 (741 days) | S3 | 8.0.27, 8.0.28 | Linux | Any | performance_schema.metadata_locks wrong value for owner_thread_id |
| 108931 | 2022-10-31 7:30 | 2022-12-01 12:23 | MySQL Server: Performance Schema | Not a Bug (510 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 (540 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 (421 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 (341 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 (90 days) | S3 | 8.0.36 | Any (rhel-7.4) | Any (x86-64) | Access performance_schema.data_locks causes SQL execution stuck |
| « Show Previous 30 Entries | Showing 31-46 of 46 (Edit, Save, CSV, Feed) |
