| « Show Previous 30 Entries | Showing 31-44 of 44 (Edit, Save, CSV, Feed) |
| ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
|---|---|---|---|---|---|---|---|---|---|
| 96237 | 2019-07-17 15:08 | 2019-07-18 6:50 | MySQL Server: Performance Schema | Verified (362 days) | S3 | 8.0.16, 5.7.26 | Any | Any | PFS didn't display metadata lock correctly |
| 77293 | 2015-06-10 9:42 | 2019-10-01 9:49 | MySQL Server: Performance Schema | Verified (287 days) | S3 | 5.6.16 | Linux (CentOS6.5) | Any | Wrong processlist_user in threads table for replication threads |
| 98434 | 2020-01-30 0:13 | 2020-01-30 6:27 | MySQL Server: Performance Schema | Verified (166 days) | S3 | 8.0.19, 5.7.29 | Any | Any | Slave threads not instrumented in perfschema for variables |
| 98498 | 2020-02-06 9:41 | 2020-02-07 13:01 | MySQL Server: Performance Schema | Verified (159 days) | S3 | 5.7, 8.0 | Any (n.a.) | Any (n.a.) | P_S view status_by_thread does not reflect correct results |
| 98545 | 2020-02-10 23:45 | 2020-02-11 4:55 | MySQL Server: Performance Schema | Verified (154 days) | S3 | 8.0.19 | Any | Any | Perfschema tables are not collation aware |
| 98734 | 2020-02-25 11:51 | 2020-02-25 14:32 | MySQL Server: Performance Schema | Verified (140 days) | S3 | 5.7.29,8.0.19 | Any | Any | Same digest for different queries if we use integer value in ORDER BY caluse |
| 83912 | 2016-11-21 15:28 | 2020-03-09 16:52 | MySQL Server: Performance Schema | Verified (1329 days) | S3 | 5.6, 5.7, 5.6.34 | Any | Any | Time spent sleeping before entering InnoDB is not measured/reported separately |
| 99039 | 2020-03-23 14:29 | 2020-03-27 1:33 | MySQL Server: Performance Schema | Verified (112 days) | S3 | >= 5.6.46 , >=5.7.28, >=8.0.18, 5.6.47, 5.7.29, 8.0.19 | Any | Any | PSI thread info not getting updated after statement execution |
| 99204 | 2020-04-07 20:52 | 2020-04-13 15:53 | MySQL Server: Performance Schema | Verified (97 days) | S3 | 5.7.29, 8.0.19 | Any | Any | performance_schema threads table PROCESSLIST_INFO incorrect behaviour |
| 99180 | 2020-04-04 21:31 | 2020-04-17 19:24 | MySQL Server: Performance Schema | Verified (88 days) | S2 | 8.0.19 | Any | Any | Accessing freed memory in perfschema when aggregating status vars |
| 91825 | 2018-07-30 6:16 | 2020-06-16 8:44 | MySQL Server: Performance Schema | Verified (715 days) | S3 | 5.7.23, 8.0.12, 5.7.22 | Any | Any | The user table is renamed as "SYSTEM_USER" in DIGEST_TEXT of history tables |
| 99121 | 2020-03-31 8:52 | 2020-06-23 2:23 | MySQL Server: Performance Schema | Verified (105 days) | S3 | 8.0, 8.0.19 | Any | Any | Performance schema does a meaningless summary according to digest |
| 99989 | 2020-06-26 1:06 | 2020-07-05 11:21 | MySQL Server: Performance Schema | Verified (18 days) | S3 | 8.0.x, 8.0.20 | Any | Any | Inconsistency when joining Perf Schema schema tables when PK is larger than 48 c |
| 100165 | 2020-07-09 2:41 | 2020-07-09 6:32 | MySQL Server: Performance Schema | Verified (5 days) | S3 | 5.7.29, 5.7.30, 8.0.20 | Any | Any | The table is visible in performance_schema after renaming it |
| « Show Previous 30 Entries | Showing 31-44 of 44 (Edit, Save, CSV, Feed) |
