Showing 1-30 of 421 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
---|---|---|---|---|---|---|---|---|---|
90631 | 2018-04-25 12:57 | 2018-04-25 15:14 | MySQL Server: Performance Schema | Verified (2165 days) | S3 | 8.0.11 | Ubuntu (14.04) | x86 | perfschema.statement_digest_query_sample test fails sporadically |
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 |
75156 | 2014-12-10 6:54 | 2015-07-01 15:47 | MySQL Server: Performance Schema | Closed (3194 days) | S3 | 5.6,5.7 | Any | Any | statements elapsed time with good time resolution |
69727 | 2013-07-11 18:41 | 2016-02-25 12:24 | MySQL Server: Performance Schema | Closed (3822 days) | S3 | 5.6.11 | Windows | Any | --performance_schema_instrument value quoting is problematic |
84786 | 2017-02-02 8:17 | 2017-02-03 16:04 | MySQL Server: Performance Schema | Closed (2611 days) | S1 | 5.7.17-11 | Any | Any | --performance-schema-digests-size=1 leads to SIGSEGV |
80851 | 2016-03-24 15:11 | 2016-03-24 19:06 | MySQL Server: Performance Schema | Duplicate (2927 days) | S2 | 5.6.29 | Windows | Any | 'wait/io/file/innodb%' instruments is missing |
50148 | 2010-01-07 17:50 | 2011-02-16 23:44 | MySQL Server: Performance Schema | Closed (5188 days) | S2 | mysql-trunk-perfschema | Any | Any | "Error in my_thread_global_end(): 1 threads didn't exit" with perfschema |
61205 | 2011-05-17 16:32 | 2011-07-22 18:15 | MySQL Server: Performance Schema | Closed (4634 days) | S3 | 5.5.12 | Any | Any | "Queries per second avg" value in status output is incorrect |
69928 | 2013-08-05 18:10 | 2016-02-25 12:24 | MySQL Server: Performance Schema | Closed (3822 days) | S3 | Any | Any | "statement/com" event meaning is unclear | |
71298 | 2014-01-05 12:31 | 2014-03-29 18:21 | MySQL Server: Performance Schema | Closed (3703 days) | S3 | 5.6.15 | Any | Any | "Waiting to get readlock" stage is not used in 5.6 any more |
99466 | 2020-05-07 5:44 | 2020-05-07 5:57 | MySQL Server: Performance Schema | Verified (1422 days) | S4 | 8.0 | Any | Any | [Feature Request]Adding information to PS and/or SYS to confirm the maximum IOPS |
68514 | 2013-02-27 23:34 | 2015-04-07 22:26 | MySQL Server: Performance Schema | Closed (3279 days) | S4 | 5.6.10 GA | Any (Centos 5) | Any | 5.6 huge memory usage with max_connections parameter |
57524 | 2010-10-18 13:16 | 2011-02-16 23:44 | MySQL Server: Performance Schema | Duplicate (4910 days) | S3 | 5.5.7 | MacOS (10.5 x86_64) | Any | A few P_S tests crashed the server on OSX 10.5 |
99078 | 2020-03-26 10:41 | 2020-04-10 12:26 | MySQL Server: Performance Schema | Closed (1450 days) | S2 | 8.0 | Any | Any | A memory leak might happen when doing lf_hash_insert |
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 |
63340 | 2011-11-20 14:46 | 2016-08-08 15:07 | MySQL Server: Performance Schema | Closed (4320 days) | S3 | 5.5.18 | Windows | Any | Access to InnoDB data files not listed in P_S |
99180 | 2020-04-04 21:31 | 2022-01-13 15:59 | MySQL Server: Performance Schema | Duplicate (806 days) | S2 | 8.0.19 | Any | Any | Accessing freed memory in perfschema when aggregating status vars |
64129 | 2012-01-25 13:51 | 2012-01-27 5:06 | MySQL Server: Performance Schema | Not a Bug (4445 days) | S2 | 5.6.4-m7 | Windows | Any | Accounts table in Performance_Schema does not show metadata |
70942 | 2013-11-18 17:04 | 2013-11-18 20:40 | MySQL Server: Performance Schema | Closed (3784 days) | S3 | 5.6.12 | Any | Any | accounts table shows NULL users and hosts |
76403 | 2015-03-20 7:45 | 2015-04-16 9:04 | MySQL Server: Performance Schema | Verified (3270 days) | S4 | 5.6 | Any | Any | Add COUNT_ABORTED_CLIENT_ERRORS to P_S.host_cache |
72219 | 2014-04-03 12:15 | 2014-04-17 13:27 | MySQL Server: Performance Schema | Verified (3638 days) | S4 | 5.6+ | Any | Any | Add first and last connection timestamps to P_S.users table |
71698 | 2014-02-13 9:05 | 2015-11-19 17:59 | MySQL Server: Performance Schema | Verified (3305 days) | S4 | 5.6.15 | Any | Any | Add instrumentation for the doublewrite buffer and undo segments |
79102 | 2015-11-03 22:46 | 2015-11-20 9:38 | MySQL Server: Performance Schema | Verified (3052 days) | S4 | 5.6.26 | Any | Any | add max/min rows to performance schema |
77605 | 2015-07-02 18:00 | 2015-11-20 10:02 | MySQL Server: Performance Schema | Verified (3052 days) | S4 | 5.7.7 | Any | Any | Add more information to SQL thread-related P_S tables |
72561 | 2014-05-07 18:14 | 2015-10-23 9:54 | MySQL Server: Performance Schema | Closed (3080 days) | S4 | 5.7 | Any | Any | Add P_S metrics on GET_LOCK() usage |
81611 | 2016-05-26 11:13 | 2017-07-17 12:35 | MySQL Server: Performance Schema | Verified (2773 days) | S4 | 5.7 | Any | Any | Add P_S metrics to collect compressed page bytes vs other types written to relog |
80780 | 2016-03-17 11:55 | 2016-04-14 0:45 | MySQL Server: Performance Schema | Closed (2922 days) | S3 | 5.7 | Any | Any | Add Performance Schema / sys Schema Memory Monitoring Example |
108501 | 2022-09-15 23:09 | 2024-01-17 17:41 | MySQL Server: Performance Schema | Closed (130 days) | S2 | 8.0.21 | Linux | Any | Add return value check for sanitize_table_share() |
81249 | 2016-04-29 17:19 | 2022-02-13 20:45 | MySQL Server: Performance Schema | Verified (2884 days) | S4 | 5.7.12 | Any | Any | ADD SLAVE_NET_TIMEOUT TO PERFORMANCE SCHEMA FOR SLAVE THREAD VARIABLES |
78303 | 2015-09-02 10:02 | 2016-09-22 7:50 | MySQL Server: Performance Schema | Verified (3131 days) | S3 | 5.7 | Any | Any | Add some DNS latency timings to performance_schema (host_cache?) |
Showing 1-30 of 421 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |