Showing 1-30 of 46 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
---|---|---|---|---|---|---|---|---|---|
44465 | 2009-04-24 18:09 | 2009-04-30 16:12 | MySQL Server: Performance Schema | Not a Bug (5446 days) | S3 | mysql-6.0-perf | Any | Any | Selecting from EVENTS_WAITS_CURRENT crashes server |
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 | |
56535 | 2010-09-03 12:12 | 2010-09-03 16:39 | MySQL Server: Performance Schema | Not a Bug (4955 days) | S5 | 5.6.0-m4 | Any | Any | mysqld tries to load triggers on tables in performance_schema database |
57974 | 2010-11-04 11:44 | 2010-11-04 15:27 | MySQL Server: Performance Schema | Not a Bug (4893 days) | S3 | 5.5.3+ | Any | Any | Performance_Schema DB name |
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 |
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 |
63358 | 2011-11-21 12:31 | 2011-11-21 17:04 | MySQL Server: Performance Schema | Not a Bug (4511 days) | S3 | 5.6.3, 5.6.4 | Any | Any | Incomplete user@host information in P_S |
63377 | 2011-11-22 9:20 | 2011-11-22 9:44 | MySQL Server: Performance Schema | Not a Bug (4510 days) | S3 | 5.6.3 | Any | Any | SHOW CREATE TABLE for P_S tables fail |
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 |
66750 | 2012-09-10 7:56 | 2012-09-10 12:09 | MySQL Server: Performance Schema | Not a Bug (4217 days) | S5 | Windows | Any | Time out error while handling millions of records in MYSql | |
69992 | 2013-08-12 9:30 | 2013-08-12 13:15 | MySQL Server: Performance Schema | Not a Bug (3881 days) | S3 | 5.5, 5.6, 5.7 | Any | Any | Conflict betwee P_S and max-connections inplementations |
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? |
70697 | 2013-10-23 10:43 | 2013-11-04 8:19 | MySQL Server: Performance Schema | Not a Bug (3797 days) | S3 | 5.6.14 | Linux | Any | Performance Schema events_statements_summary_by_digest.row_size issue |
71205 | 2013-12-22 16:04 | 2013-12-27 8:00 | MySQL Server: Performance Schema | Not a Bug (3744 days) | S3 | 5.6.14 | Any | Any | Queries to P_S seems to pass extra stages related to query cache |
71292 | 2014-01-04 18:09 | 2014-01-06 13:17 | MySQL Server: Performance Schema | Not a Bug (3734 days) | S3 | 5.6.15 | Any | Any | Wrong length is used for FILE_NAME column in FILE_INSTANCES table |
71641 | 2014-02-09 23:49 | 2014-10-01 13:34 | MySQL Server: Performance Schema | Not a Bug (3466 days) | S5 | 5.7.3, 5.7.4 | Linux | Any | table_setup_actors::update_row_values function is unnecessary. |
71733 | 2014-02-16 6:39 | 2014-02-21 4:24 | MySQL Server: Performance Schema | Not a Bug (3688 days) | S3 | 5.7.3 | Linux | Any | I cannot get result of performance_schema.socket_instances |
71818 | 2014-02-24 15:23 | 2014-02-25 9:04 | MySQL Server: Performance Schema | Not a Bug (3684 days) | S3 | 5.6.16/5.7 | Any | Any | Type column in SHOW PERFORMANCE_SCHEMA STATUS is redundant |
72138 | 2014-03-26 22:41 | 2014-03-27 15:37 | MySQL Server: Performance Schema | Not a Bug (3654 days) | S3 | 5.7.3 | Linux | Any | There art no MYSQL_SET_TRANSACTION_TRXID in source code. |
72218 | 2014-04-03 11:37 | 2014-04-04 19:06 | MySQL Server: Performance Schema | Not a Bug (3646 days) | S3 | 5.6.17 | Any | Any | Bogus connections in P_S.users? |
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. |
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 |
75794 | 2015-02-05 13:32 | 2015-02-16 23:50 | MySQL Server: Performance Schema | Not a Bug (3328 days) | S3 | 5.6.23/5.7 | Any | Any | Performance Schema statement digest generation is broken with ALTER PARTITION |
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 |
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 |
Showing 1-30 of 46 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |