Showing 1-1000 of 2775 (Edit, Save, CSV, Feed) | Show Next 1000 Entries » |
ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
---|---|---|---|---|---|---|---|---|---|
48885 | 2009-11-18 22:32 | 2011-02-16 23:44 | Tools: Random Query Generator | Closed (5265 days) | S3 | Any | Any | gendata.pl requires a dsn input, despite the help output saying it is optional | |
53532 | 2010-05-10 8:24 | 2012-05-18 20:19 | Tools: Random Query Generator | Verified | S3 | Any | Any | RQG: internal mysqldump commands fail if mysqldump is not in PATH | |
38122 | 2008-07-15 7:41 | 2011-02-16 23:43 | Tools: Pushbuild | Closed (5287 days) | S3 | 1 | Any | Any | main.mysqlslap fails sporadically |
49837 | 2009-12-21 6:13 | 2011-02-16 23:44 | Tools: MTR / mysql-test-run | Closed (5056 days) | S3 | 5.0,5.1,6.0 | Any | Any | mysqltest exec cannot handle multi-line command correctly |
52203 | 2010-03-19 8:28 | 2018-09-25 21:51 | Tools: MTR / mysql-test-run | Closed (4820 days) | S7 | M3 (Celosia) | Any | Any | MTR sporadic bug (Could not execute 'check-testcase' before testcase) |
99010 | 2020-03-20 13:30 | 2020-04-06 13:15 | Tools: MTR / mysql-test-run | Verified (1475 days) | S7 | 8.0 | Any | Any | The mtr case --send command not use ps-protocol when run with --ps-protocol |
39003 | 2008-08-25 11:34 | 2018-09-25 21:49 | Tools: MTR / mysql-test-run | Closed (5237 days) | S7 | 5.1, 5.4 | Any | Any | mtr's diff_files command failed in pushbuild without printing a result diff |
111798 | 2023-07-18 20:11 | 2023-07-19 8:38 | Tools: MTR / mysql-test-run | Verified (276 days) | S3 | 8.0.33, 8.0.34 | Any | Any | Table access not restricted according to grants during MTR test |
46952 | 2009-08-27 12:14 | 2012-05-18 20:19 | Tools | Duplicate (5342 days) | S3 | Any | Any | backup_logs fails on Valgrind platform in PB2 | |
59063 | 2010-12-20 16:27 | 2011-02-16 23:44 | Tools | Closed (4829 days) | S1 | 5.6, 5.1, 5.5 | Any | Any | rpl_migration_crash_safe fails on Windows |
59830 | 2011-01-31 5:42 | 2011-06-30 14:57 | Tests: Server | Closed (4678 days) | S3 | mysql-trunk | Any | Any | parts.partition_debug_innodb failing due to case difference on windows |
39359 | 2008-09-10 7:14 | 2018-09-25 21:49 | Tests: Server | Can't repeat (4680 days) | S7 | 6.0 | Any | Any | main.analyze fails randomly on Pushbuild |
43716 | 2009-03-18 2:22 | 2011-02-16 23:43 | Tests: Server | Closed (5463 days) | S3 | 5.1+ | Any | Any | Test mysqlbinlog_row_big is failing, needs to be updated |
45729 | 2009-06-24 19:09 | 2012-10-15 13:44 | Tests: Server | Closed (4205 days) | S3 | 5.4 | Any | Any | Test case for Bug#28211 is disabled in query_cache.test |
47128 | 2009-09-04 10:20 | 2012-10-15 14:48 | Tests: Server | Unsupported (4205 days) | S3 | 5.4.2-beta, cluster-6.3.27a, 5.5.0-beta,5.1.43 | Any (see text) | Any | Test "binlog_unsafe" exceds default stack allocation |
40704 | 2008-11-13 16:32 | 2018-09-25 21:49 | Tests: Server | Closed (5559 days) | S7 | 5.1-rpl, 6.0-rpl | Any | Any | main.events_restart fails sporadically in pushbuild: "server has gone away" |
41181 | 2008-12-02 18:23 | 2018-09-25 21:50 | Tests: Server | Can't repeat (5541 days) | S7 | 6.0-rpl | Any | Any | events_restart failed with "query succeeded - should have failed" |
48874 | 2009-11-18 17:36 | 2011-02-16 23:44 | Tests: Server | Closed (4904 days) | S3 | 5.5.0-beta | Any (all) | Any | Test "is_triggers" fails because of wrong charset info |
32244 | 2007-11-09 19:10 | 2008-02-28 17:24 | Tests: Server | Closed (5896 days) | S3 | 6.0.4-alpha | Any | Any | Result files not updated with ".inc" file used - tests fail (2) |
37938 | 2008-07-07 16:33 | 2008-10-17 17:44 | Tests: Server | Closed (5664 days) | S3 | 5.1.26-rc | Any | Any | Test "mysqldump" lacks various INSERT statements / values |
36923 | 2008-05-23 17:21 | 2008-05-23 17:21 | Tests: Server | Closed | S3 | 5.0.62 | Any | Any | Test "nist_all" needs its result file updated |
37810 | 2008-07-02 16:55 | 2018-09-25 21:47 | Tests: Server | Closed (5430 days) | S7 | 6.0-BK | Any | Any | The server crashes sporadically in wait_until_connected_again.inc |
38270 | 2008-07-21 18:59 | 2008-10-01 17:14 | Tests: Server | Closed (5680 days) | S3 | 5.1.26-rc | Any | Any | Test "processlist_priv_ps" fails on varying "processlist" output |
41383 | 2008-12-11 1:25 | 2011-02-16 23:43 | Tests: Server | Closed (5568 days) | S3 | 5.1+ | Any | Any | Test commit1_innodb fails with binlog-format=row |
41622 | 2008-12-19 7:10 | 2018-09-25 21:50 | Tests: Server | Duplicate (5584 days) | S7 | 6.0 | Any | Any | func_str fails sporadically on pushbuild with timeout |
43801 | 2009-03-23 10:08 | 2011-02-16 23:43 | Tests: Server | Closed (5486 days) | S3 | 5.0, 5.1, 6.0 | Any | Any | mysql.test takes too long, fails due to expired timeout on debx86-b in PB |
44957 | 2009-05-19 18:11 | 2009-05-19 18:11 | Tests: Server | Won't fix | S3 | 5.0.74sp1 | Any | Any | SSL certificate for openssl is inconsistent with test case |
45712 | 2009-06-24 15:35 | 2011-08-17 14:21 | Tests: Server | Won't fix (4630 days) | S3 | 5.4 | Any | Any | A test case is disabled in backup_engines.backup_partitioning.test |
87189 | 2017-07-26 2:50 | 2017-08-04 13:07 | Tests: Server | Closed (2451 days) | S3 | 8.0.2 | Any | Any | Test main.kill is unstable |
58831 | 2010-12-09 3:30 | 2011-02-16 23:44 | Tests: Server | Closed (4870 days) | S3 | Any | Any | large_tests.alter_table crashes the server | |
41498 | 2008-12-16 12:36 | 2018-09-25 21:50 | Tests: Server | Closed (5373 days) | S7 | Any | Any | concurrent_innodb_unsafelog fails sporadically: query should have had errno 1205 | |
37775 | 2008-07-01 15:46 | 2012-10-15 14:50 | Tests: Server | Unsupported (4205 days) | S3 | 6.0-BK,5.4 | Any | Any | main.locktrans_innodb and rpl.rpl_locktrans_innodb fail randomly |
59570 | 2011-01-17 21:22 | 2012-10-15 13:41 | Tests: Server | Closed (4205 days) | S3 | 5.5.8 | Any | Any | in_multicolumn_calendar_unique_constraint_ignore fails with wrong TZ |
32458 | 2007-11-16 19:09 | 2008-08-28 16:25 | Tests: Server | Closed (5714 days) | S3 | 5.0.51 | Any (all !) | Any | Test "mysqlcheck" fails, because "mysqlcheck --repair" changed output format |
35788 | 2008-04-03 8:33 | 2018-09-25 21:47 | Tests: Server | Closed (5828 days) | S7 | 5.1-bk | Any | Any | A few tests fail due to concurrent inserts |
32653 | 2007-11-23 11:43 | 2018-09-25 21:45 | Tests: Replication | Closed (5745 days) | S7 | 5.0.54 | Any (Windows, Mac) | Any | rpl_log.test fails randomly |
37715 | 2008-06-28 10:59 | 2018-09-25 21:47 | Tests: Replication | Closed (5731 days) | S7 | 6.0 | Any | Any | rpl.rpl_dual_pos_advance 'mix' failed on pushbuild |
37933 | 2008-07-07 15:03 | 2011-02-16 23:43 | Tests: Replication | Closed (5559 days) | S3 | 5.1.26-rc | Any | Any | Test "rpl_insert" fails - timing problem in replication test ? |
38077 | 2008-07-12 19:46 | 2018-09-25 21:48 | Tests: Replication | Closed (5441 days) | S7 | 5.1-bugteam | Any | Any | rpl_incident At line 22: query 'SELECT * ...' Table 'test.t1' doesn't exist |
39858 | 2008-10-04 12:53 | 2011-02-16 23:43 | Tests: Replication | Closed (5512 days) | S3 | 5.1+ | Any | Any | rpl.rpl_rotate (rpl.rpl_rotate_logs) failed on pushbuild: result mismatch |
40926 | 2008-11-21 15:30 | 2018-09-25 21:49 | Tests: Replication | Closed (5609 days) | S7 | 6.0.9-bzr | Any | Any | rpl.rpl_truncate_falcon fails in Pushbuild due to wrong binlog-format being used |
41173 | 2008-12-02 14:14 | 2018-09-25 21:50 | Tests: Replication | Closed (5568 days) | S7 | 6.0-rpl, 5.1-rpl | Any | Any | rpl_packet fails sporadically on pushbuild: query 'DROP TABLE t1' failed |
42357 | 2009-01-26 21:55 | 2018-09-25 21:50 | Tests: Replication | Can't repeat (4939 days) | S7 | 5.1-rpl | Any | Any | rpl.rpl_slave_status: test fails with timeout on pushbuild |
42704 | 2009-02-09 16:27 | 2011-02-16 23:43 | Tests: Replication | Closed (5436 days) | S3 | cluster 6.4.2 | Any | Any | "Slave_IO_Running" differs in test result (2) |
46029 | 2009-07-08 7:18 | 2018-04-23 17:23 | Tests: Replication | Can't repeat (3693 days) | S3 | 5.1-bugteam, 5.1 | Any | Any | rpl_innodb_bug28430 times out on certain pb2 hosts |
47016 | 2009-08-31 11:47 | 2011-02-16 23:44 | Tests: Replication | Closed (5236 days) | S3 | 5.1 | Any | Any | rpl_do_grant fails on PB-2 with a failing connect |
47161 | 2009-09-07 0:09 | 2016-10-16 20:45 | Tests: Replication | Duplicate (5213 days) | S3 | 5.4 | Any | Any | rpl_backup_shutdown fails sporadically on PB2 |
37716 | 2008-06-28 11:20 | 2018-09-25 21:47 | Tests: Replication | Closed (5462 days) | S7 | 6.0, 5.1 | Any | Any | rpl.rpl_deadlock_innodb 'row' failed on pushbuild |
37879 | 2008-07-04 15:44 | 2018-09-25 21:47 | Tests: Replication | Duplicate (5735 days) | S7 | 5.1.26-rc | Any | Any | Failures in rowbased replication: Test "rpl_row_basic_{2myisam,3innodb}" (1) |
38289 | 2008-07-22 17:28 | 2018-09-25 21:48 | Tests: Replication | Can't repeat (5549 days) | S7 | 6.0-bugteam | Any | Any | rpl_temporary fails sporadically on windows: server has gone away |
38540 | 2008-08-04 14:57 | 2018-09-25 21:48 | Tests: Replication | Closed (5559 days) | S7 | 5.1 | Any | Any | rpl_server_id2 uses show slave status unnecessarily |
38558 | 2008-08-05 7:58 | 2018-09-25 21:49 | Tests: Replication | Can't repeat (5347 days) | S7 | 6.0,5.4 | Any | Any | rpl_blob_innodb_row fails sporadically in pushbuild: Lost connection to server |
38744 | 2008-08-12 8:58 | 2016-10-16 20:45 | Tests: Replication | Duplicate (5563 days) | S3 | 6.0-BK | Any | Any | rpl.rpl_stm_000001 (mix) fails sporadically |
41503 | 2008-12-16 13:12 | 2018-09-25 21:50 | Tests: Replication | Closed (5576 days) | S7 | 5.1-rpl, 6.0-rpl | Any | Any | rpl_row_log fails sporadically: query failed: "Unknown table 't1'" |
56912 | 2010-09-21 23:24 | 2011-02-16 23:44 | Tests: Replication | Closed (4905 days) | S3 | mysql-next-mr-bugfixing, 5.6.99 | Any | Any | binlog_killed fails sporadically on mysql-next-mr-bugfixing codebase. |
58784 | 2010-12-07 13:26 | 2011-02-16 23:44 | Tests: Replication | Closed (4835 days) | S3 | daily-trunk-bugfixing, 5.6 | Any | Any | rpl_row_ignorable_event fails on PB2 |
37882 | 2008-07-04 16:12 | 2018-09-25 21:47 | Tests: Replication | Duplicate (5735 days) | S7 | 5,1,26-rc | Any | Any | Failures in rowbased replication: Test "rpl_row_basic_{2myisam,3innodb}" (2) |
37940 | 2008-07-07 16:50 | 2018-09-25 21:47 | Tests: Replication | Closed (5762 days) | S7 | 6.0-rpl | Any | Any | rpl_dual_pos_advance fails on pushbuild,fail wait_for_slave_to_stop |
39014 | 2008-08-25 16:19 | 2018-09-25 21:49 | Tests: Replication | Can't repeat (5510 days) | S7 | 6.0-bugteam | Any | Any | rpl.rpl_sporadic_master failed on pushbuild: "could not parse relay log entry" |
41055 | 2008-11-26 14:11 | 2018-09-25 21:50 | Tests: Replication | Can't repeat (4881 days) | S7 | 5.1-rpl | Any | Any | rpl_sporadic_master fails in sync_slave_with_master sporadically in pushbuild |
57918 | 2010-11-02 8:54 | 2011-02-16 23:44 | Tests: Replication | Closed (4853 days) | S3 | 5.6 (Dahlia, Erica) | Any | Any | rpl_get_master_version_and_clock times out sporadically |
58083 | 2010-11-09 13:27 | 2011-02-16 23:44 | Tests: Replication | Duplicate (4910 days) | S3 | 5.6 | Any | Any | Test rpl.rpl_server_uuid fails after 5 minutes in trunk-bugfixing |
113257 | 2023-11-28 14:29 | 2023-12-08 9:43 | Tests: Replication | Verified (142 days) | S6 | 8.2.0 | Any | Any | Assertion on rpl.rpl_replication_observers_example_plugin_ongoing_transaction |
37713 | 2008-06-28 10:27 | 2018-09-25 21:47 | Tests: Replication | Can't repeat (5549 days) | S7 | 6.0-rpl | Any | Any | rpl.rpl_known_bugs_detection failed in pushbuild |
37712 | 2008-06-28 10:19 | 2018-09-25 21:47 | Tests: Replication | Closed (5559 days) | S7 | 6.0 | Any | Any | rpl.rpl_locktrans_innodb fails sporadically on pushbuild |
54122 | 2010-06-01 3:23 | 2018-09-25 21:51 | Tests: Replication | Closed (4733 days) | S7 | 5.6.1 | Any | Any | Race condition in mysqlbinlog_raw_mode |
36982 | 2008-05-26 15:20 | 2008-06-23 11:04 | Tests: Replication | Can't repeat (5780 days) | S3 | 6.0-engines-merge | Any | Any | rpl_found_rows.test fails in pushbuild |
48465 | 2009-11-02 12:04 | 2011-02-16 23:44 | Tests: Replication | Can't repeat (5220 days) | S3 | 5.0 | Any | Any | rpl000012 failed on PB2 |
41424 | 2008-12-12 10:52 | 2018-09-25 21:50 | Tests: Replication | Can't repeat (5020 days) | S7 | 6.0-bugteam | Any | Any | rpl_ignore_table fails, "could not execute write_rows event" |
47477 | 2009-09-21 10:13 | 2011-02-16 23:44 | Tests: Replication | Can't repeat (5192 days) | S3 | Any | Any | PB2: rpl_start_stop_slave failures | |
37883 | 2008-07-04 16:24 | 2018-09-25 21:47 | Tests: Replication | Duplicate (5735 days) | S7 | 5.1.26-rc | Any | Any | Failures in rowbased replication: Test "rpl_row_basic_{2myisam,3innodb}" (3) |
38369 | 2008-07-25 10:24 | 2018-09-25 21:48 | Tests: Replication | Closed (5680 days) | S7 | 5.1 | Any | Any | rpl_ndb.rpl_row_basic_7ndb fails |
41186 | 2008-12-02 19:54 | 2018-09-25 21:50 | Tests: Replication | Duplicate (5587 days) | S7 | 6.0-rpl, 5.1 | Any | Any | rpl_stm_mystery22 fails sporadically on pushbuild while waiting for slave start |
37718 | 2008-06-28 11:48 | 2018-09-25 21:47 | Tests: Replication | Closed (5500 days) | S7 | 5.1 | Any | Any | rpl.rpl_stm_mystery22 fails sporadically on pushbuild |
39931 | 2008-10-08 13:29 | 2011-02-16 23:43 | Tests: Replication | Closed (5562 days) | S3 | 5.0 | Any | Any | random failures of rpl.rpl_temporary |
40708 | 2008-11-13 17:10 | 2018-09-25 21:49 | Tests: Replication | Closed (5559 days) | S7 | 5.1-rpl | Any | Any | rpl_row_create_table fails sporadically in pushbuild |
40927 | 2008-11-21 15:40 | 2018-09-25 21:49 | Tests: Replication | Closed (5609 days) | S7 | 6.0.9-bzr | Any | Any | rpl.rpl_relay_space_falcon fails when binlog-format is explicitly set to mixed |
42370 | 2009-01-27 11:24 | 2018-09-25 21:50 | Tests: Replication | Closed (5559 days) | S7 | Any | Any | rpl_trigger.test: Test case timeout after 900 seconds | |
56913 | 2010-09-21 23:39 | 2011-02-16 23:44 | Tests: Replication | Closed (4905 days) | S3 | mysql-next-mr-bugfixing | Any | Any | rpl_row_ignorable_event fails sporadically on next-mr-bugfixing codebase. |
80872 | 2016-03-29 1:00 | 2016-03-29 4:30 | Tests: Replication | Verified (2944 days) | S3 | 5.7.9,5.7.11 | Any | Any | replication tests can't be run with ./mtr --repeat=2 (or more) |
38762 | 2008-08-13 7:47 | 2008-10-17 18:25 | Tests: Engine | Closed (5664 days) | S3 | 6.0-BK, 5.1, 5.0 | Any | Any | main.federated_bug_25714 fails sporadically |
39904 | 2008-10-07 9:34 | 2018-09-25 21:49 | Tests: Engine | Closed (5666 days) | S7 | 6.0-rpl | Any | Any | maria-autozerofill fails sporadically on pushbuild |
39007 | 2008-08-25 13:38 | 2018-09-25 21:49 | Tests: Cluster | Closed (5559 days) | S7 | 5.1-rpl | Any | Any | rpl_ndb.rpl_ndb_circular_2ch crashed in pushbuild |
42699 | 2009-02-09 15:58 | 2012-05-18 20:19 | Tests: Cluster | Verified | S3 | cluster 6.4.2 | Any | Any | Test "partition_mgm" does not match with current software |
45721 | 2009-06-24 17:40 | 2021-05-02 20:45 | Tests: Cluster | Verified | S3 | 5.4 | Any | Any | Test case for Bug#7798 is disabled due to WL#4284 in ndb.ndb_index_ordered.test |
47245 | 2009-09-10 10:41 | 2021-05-02 20:45 | Tests: Cluster | Verified | S3 | 5.1 | Any | Any | rpl_ndb.rpl_ndb_2other fails on PB2. |
47666 | 2009-09-28 3:02 | 2021-05-02 20:45 | Tests: Cluster | Verified (5317 days) | S3 | mysql-5.0 | Any | Any | ndb_basic test fails due to incorrect result file |
32245 | 2007-11-09 19:25 | 2015-01-09 14:32 | Tests: Cluster | Won't fix (3389 days) | S3 | 6.0.4-alpha,5.4 | Any | Any | Change in NDB is not reflected in the test results: on-line ADD COLUMN |
41183 | 2008-12-02 19:17 | 2011-02-16 23:43 | Tests: Cluster | Closed (5547 days) | S3 | 5.1 | Any | Any | rpl_ndb_circular, rpl_ndb_circular_simplex need maintenance, crash |
38370 | 2008-07-25 10:27 | 2008-10-17 18:20 | Tests: Cluster | Closed (5664 days) | S3 | 5.1 BK | Any | Any | The test ndb.ndb_index_ordered fails with the community features on |
41500 | 2008-12-16 13:05 | 2021-05-02 20:45 | Tests: Cluster | Verified | S7 | 5.1, 6.0 | Any | Any | ndb_basic fails sporadically with "lock wait timeout exceeded" |
32039 | 2007-11-02 1:12 | 2007-11-02 6:21 | Tests: Cluster | Not a Bug (6014 days) | S3 | mysql-5.1 | Any | Any | rpl_ndb_auto_inc should list error 1062 instead or 1022 |
50167 | 2010-01-08 0:18 | 2013-01-11 12:23 | Tests: Backup | Unsupported (4117 days) | S3 | 5.6.0 (mysql-backup-backport) | Any | Any | backup_triggers_and_events fails with: "backup wait timeout has expired for..." |
39008 | 2008-08-25 13:43 | 2018-09-25 21:49 | Tests | Closed (5559 days) | S7 | 5.1-rpl | Any | Any | perl warning in mtr: 'use of uninitialized value in concatenation' in mtr:3995 |
39705 | 2008-09-28 4:24 | 2011-05-12 10:52 | Tests | Duplicate (4727 days) | S3 | 6.0, 6.0-falcon, 5.1 | Any | Any | read_many_rows_innodb fails |
40160 | 2008-10-19 20:29 | 2018-09-25 21:49 | Tests | Closed (5635 days) | S7 | 6.0 | Any | Any | main.backup_progress fails sporadically on pushbuild |
76367 | 2015-03-18 4:29 | 2015-04-07 22:54 | Tests | Closed (3313 days) | S3 | Any | Any | main.ctype_ucs test fails in WL8403 | |
41017 | 2008-11-25 14:27 | 2018-09-25 21:49 | Tests | Closed (5559 days) | S7 | 6.0-rpl | Any | Any | main.events_restart fails in pushbuild: "Server failed to restart" |
41614 | 2008-12-19 6:14 | 2018-09-25 21:50 | Tests | Closed (5491 days) | S7 | 6.0, 5.1 | Any | Any | rpl_row_func003 fails sporadically: diff_files failed with error 2 |
43079 | 2009-02-21 13:41 | 2011-02-16 23:43 | Tests | Can't repeat (5399 days) | S3 | 5.1, 6.0-rpl | Any | Any | main.mysqldump fails sporadically on pushbuild |
89783 | 2018-02-23 6:55 | 2019-01-30 18:35 | MySQL Server: XA transactions | Closed (2024 days) | S3 | 8.0.4 | Any | Any | binlog.binlog_xa_commit_failure:query 'XA COMMIT 'xid1'' failed with wrong errno |
98288 | 2020-01-20 0:57 | 2020-02-13 8:23 | MySQL Server: XA transactions | Duplicate (1528 days) | S3 | 5.7.26 | Any | Any | xa commit crash lead mysql replication error |
100156 | 2020-07-08 10:30 | 2020-07-08 15:21 | MySQL Server: XA transactions | Duplicate (1382 days) | S3 | 8.0.18, 8.0.20 | Any | Any | XA COMMIT still work after stop group_replication |
110594 | 2023-04-03 11:28 | 2023-04-05 7:20 | MySQL Server: XA transactions | Verified (381 days) | S2 | 8.0.32 | Any | Any | Race condition between xa recover and xa start on Transaction_ctx object |
81375 | 2016-05-11 6:46 | 2017-02-21 16:12 | MySQL Server: XA transactions | Closed (2768 days) | S2 | 5.7 | Any | Any | Assert `m_status == DA_ERROR' in Diagnostics_area::mysql_errno:sql_error.h:385 |
94814 | 2019-03-28 11:12 | 2022-12-01 12:01 | MySQL Server: XA transactions | Closed (506 days) | S2 | 5.7, 8.0, 5.7.25 | Any | Any | slave replication lock wait timeout because of wrong trx order in binlog file |
87526 | 2017-08-24 11:55 | 2017-08-24 12:10 | MySQL Server: XA transactions | Verified (2431 days) | S3 | 5.7.19, 8.0.2 | Any | Any | The output of 'XA recover convert xid' is not useful |
87836 | 2017-09-22 8:41 | 2018-02-12 20:26 | MySQL Server: XA transactions | Closed (2297 days) | S2 | mysql-5.7.17, 5.7.19 | Any | Any | XA COMMIT/ROLLBACK rejected by non-autocommit session with no active transaction |
45806 | 2009-06-28 9:23 | 2011-02-16 23:44 | MySQL Server: Views | Closed (5395 days) | S1 | 5.0.54, 5.0.84, 5.1.30, 5.1.37 | Any | Any | crash when replacing into a view with a join! |
45832 | 2009-06-29 16:53 | 2015-08-19 13:56 | MySQL Server: Views | Closed (3167 days) | S3 | 5.1+ | Any | Any | Incorrect error message when creating unsafe view |
20543 | 2006-06-19 17:27 | 2006-08-18 12:34 | MySQL Server: Views | Closed (6455 days) | S1 | 5.0 | Any | Any | select on information_schema strange warnings, view, different schemas/users |
20203 | 2006-06-01 13:45 | 2006-07-06 1:45 | MySQL Server: Views | Not a Bug (6498 days) | S3 | 5.0.22, 4.1.21-BK | Any (All) | Any | SEC_TO_TIME(SUM(TIME_TO_SEC( doesn't work correctly with a VIEW |
48995 | 2009-11-23 14:21 | 2011-02-16 23:44 | MySQL Server: Views | Closed (5153 days) | S3 | mysql-6.0-codebase-bugfixing | Any | Any | abort missing DBUG_RETURN or .. in function "check_key_in_view" |
61112 | 2011-05-10 7:31 | 2011-05-12 9:16 | MySQL Server: Views | Verified (4729 days) | S3 | 5.1.55 | Any | Any | Unqualified table names are changed silently |
48275 | 2009-10-23 20:12 | 2011-02-16 23:44 | MySQL Server: Views | Can't repeat (5275 days) | S3 | mysql-6.0-codebase-bugfixing | Any | Any | assert in check_view_insertability |
23464 | 2006-10-19 14:02 | 2020-05-03 20:45 | MySQL Server: Views | Duplicate (6280 days) | S3 | 5.0.27-BK, 5.0.26 and 5.1.12 | Any (all) | Any | A view with an ORDER BY clause becomes non-updatable |
27713 | 2007-04-09 11:17 | 2020-05-03 20:45 | MySQL Server: Views | Verified (6220 days) | S3 | 5.0.38, 5.1, 5.2 | Any | Any | INSERTs fail for empty table using WITH_CHECK_OPTION |
35869 | 2008-04-07 9:12 | 2020-05-03 20:45 | MySQL Server: Views | Verified (5857 days) | S2 | 5.0/5.1/6.0 | Any | Any | Defining a view over an aggregate view renders the view definition invalid |
41760 | 2008-12-27 2:01 | 2020-05-03 20:45 | MySQL Server: Views | Verified (5296 days) | S3 | 5.0 and up | Any | Any | Inserting into multiple-table views is not working |
46616 | 2009-08-08 10:48 | 2011-02-16 23:44 | MySQL Server: Views | Closed (5328 days) | S2 | 5.1,5.4 | Any | Any | Assertion `!table->auto_increment_field_not_null' on view manipulations |
27838 | 2007-04-15 23:01 | 2007-04-16 4:33 | MySQL Server: Data Types | Duplicate (6214 days) | S2 | 5.0.24a | Any | Any | DateTime and Timestamp do not work with Milliseconds |
27906 | 2007-04-17 23:27 | 2017-10-20 15:16 | MySQL Server: Data Types | Verified (6213 days) | S4 | 5.0 | Any | Any | MySQL doesn't accept ISO8601 date |
30987 | 2007-09-12 17:46 | 2007-10-31 19:31 | MySQL Server: Data Types | Can't repeat (6016 days) | S3 | 5.0.44 | Any | Any | mysql Error: Warning | 1366 | Incorrect string value: '\xB4 FFFF...' for column |
40747 | 2008-11-14 15:03 | 2020-05-03 20:45 | MySQL Server: Data Types | Verified (5636 days) | S3 | 5.0.70, 5.1.29, 6.0.7 | Any | Any | Duplicate datetime truncation warning if a range optimizer is used. |
41370 | 2008-12-10 18:13 | 2011-02-16 23:43 | MySQL Server: Data Types | Closed (5547 days) | S2 | 5.0.60sp1, 5.1.30 | Any | Any | TIMESTAMP field does not accepts NULL from FROM_UNIXTIME() |
46037 | 2009-07-08 11:11 | 2018-11-04 20:45 | MySQL Server: Data Types | Verified (5400 days) | S3 | mysql-azalea/5.1 | Any | Any | Inconsistent behavior when casting floating point numbers to integer |
50231 | 2010-01-11 13:10 | 2011-02-16 23:44 | MySQL Server: Data Types | Can't repeat (5209 days) | S3 | 5.1-bugteam | Any | Any | Select shows different outputs for 'bigint' column containing 'null' values |
50293 | 2010-01-12 22:23 | 2010-01-14 23:41 | MySQL Server: Data Types | Not a Bug (5210 days) | S3 | 5.1-bugteam, 5.5.99 | Any | Any | Difference in SELECT output when search is based on an invalid DATE/DATETIME |
54125 | 2010-06-01 6:15 | 2010-06-01 12:08 | MySQL Server: Data Types | Not a Bug (5072 days) | S5 | 5.5 | Any | Any | year(4) datatype not taking values before 19th century. |
59173 | 2010-12-26 12:26 | 2011-02-16 23:44 | MySQL Server: Data Types | Closed (4830 days) | S3 | 5.1.54, 5.1.55, 5.5.8 | Any | Any | Failure to handle DATE(TIME) values where Year, Month or Day is ZERO |
61408 | 2011-06-04 18:37 | 2011-06-05 17:06 | MySQL Server: Data Types | Not a Bug (4703 days) | S3 | 5.0.90 | Any | Any | incorrect behaviour of user-defined variables |
64224 | 2012-02-03 22:15 | 2016-02-04 10:22 | MySQL Server: Data Types | Verified (4459 days) | S2 | 5.1.52, 5.1.56, 5.5.20, 5.6.28 | Any | Any | bug in fractional part of unsigned decimals |
66034 | 2012-07-26 19:01 | 2012-08-01 7:08 | MySQL Server: Data Types | Verified (4285 days) | S3 | 5.1, 5.5, 5.6 | Any | Any | Inconsistent results while comparing time fields with string and number literals |
67984 | 2012-12-28 17:51 | 2012-12-28 17:54 | MySQL Server: Data Types | Verified | S4 | 5.5.30, all | Any | Any | Don't allow insertion of not supported dates |
68577 | 2013-03-05 19:29 | 2019-12-12 16:14 | MySQL Server: Data Types | Verified (4064 days) | S3 | 5.1, 5.5, 5.6 | Any | Any | Incorrect enum values returned when using UNION after CREATE AS SELECT |
68931 | 2013-04-11 10:49 | 2013-04-12 12:12 | MySQL Server: Data Types | Not a Bug (4026 days) | S3 | 5.5.29 | Any | Any | saving some timestamp values are incorrect in mysql 5.5.29 |
72628 | 2014-05-13 7:56 | 2014-07-30 10:02 | MySQL Server: Data Types | Not a Bug (3552 days) | S3 | 5.6 | Any | Any | MySQL is not inserting Default value for datetime column when null value passed |
78914 | 2015-10-22 6:08 | 2015-11-05 15:28 | MySQL Server: Data Types | Closed (3089 days) | S3 | 5.7.8, 5.7.9, 5.6.28, 5.5.47 | Any | Any | Flags info in result meta data is incorrect ( negative num w/ "UNSIGNED") |
79628 | 2015-12-14 9:28 | 2018-11-13 13:00 | MySQL Server: Data Types | Not a Bug (1985 days) | S3 | 5.7.8 | Any | Any | Result type for max(float column) is FLOAT, while expecting DOUBLE |
85641 | 2017-03-27 9:17 | 2017-03-27 15:49 | MySQL Server: Data Types | Verified (2581 days) | S3 | 5.7.17 | Any | Any | MySQL is not consequent in handling non existing time between 2 and 3 o'clock |
92540 | 2018-09-24 8:01 | 2018-09-24 8:57 | MySQL Server: Data Types | Verified (2035 days) | S3 | 5.7, 8.0.12, 5.7.23, 5.6.41 | Any | Any | Comparison between DATE and DECIMAL does not round nanoseconds |
98211 | 2020-01-13 18:47 | 2020-06-19 12:06 | MySQL Server: Data Types | Closed (1402 days) | S2 | 8.0.19 | Any | Any | Auto increment value didn't reset correctly. |
99422 | 2020-05-03 11:25 | 2020-06-11 14:46 | MySQL Server: Data Types | Verified (1409 days) | S4 | Any | Any | Feature request: better UUID support | |
100307 | 2020-07-23 14:08 | 2020-07-28 15:46 | MySQL Server: Data Types | Verified (1367 days) | S3 | 5.7.30 | Any | Any | JSON field datatype changes unexpectedly |
103289 | 2021-04-12 15:00 | 2021-05-11 5:28 | MySQL Server: Data Types | Verified (1075 days) | S3 | 8.0 | Any | Any | bit type display confusing |
108098 | 2022-08-09 15:49 | 2022-08-10 1:41 | MySQL Server: Data Types | Not a Bug (619 days) | S5 | Any | Any | double unsigned use key select result error | |
112102 | 2023-08-18 1:48 | 2023-08-21 12:34 | MySQL Server: Data Types | Not a Bug (244 days) | S3 | 8.0 | Any | Any | The ifnull function query result is not as expected |
25010 | 2006-12-12 14:34 | 2011-02-16 23:43 | MySQL Server: Data Types | Verified | S4 | 5.0 | Any (any) | Any | There is no way to display TIMESTAMP values in UTC without setting variables |
26799 | 2007-03-02 16:02 | 2011-02-16 23:43 | MySQL Server: Data Types | Verified (5671 days) | S4 | * | Any (*) | Any | Char and binary types without padding/stripping |
28697 | 2007-05-26 3:39 | 2007-05-26 5:34 | MySQL Server: Data Types | Not a Bug (6174 days) | S2 | 5.0.41 | Any | Any | UNIQUE inded on VARCHAR(X) column disallowes proper values on insert. |
31152 | 2007-09-23 7:05 | 2012-05-18 20:19 | MySQL Server: Data Types | Duplicate (6045 days) | S2 | 5.1.23-debug, 5.0.48-debug | Any | Any | virtual int Field_str::store(double): Assertion `local_char_length < 5 || length |
31349 | 2007-10-02 18:13 | 2007-12-20 0:43 | MySQL Server: Data Types | Closed (5966 days) | S3 | 5.1.23-debug, 5.0.48-debug | Any | Any | ERROR 1062 (23000): Duplicate entry '' for key 'group_key' |
34693 | 2008-02-20 14:50 | 2008-02-20 15:23 | MySQL Server: Data Types | Closed (5904 days) | S2 | 5.1.23 | Any | Any | DECIMAL(65) colum can accept out of range value in TRADITIONAL mode |
45903 | 2009-07-02 10:42 | 2009-07-03 8:59 | MySQL Server: Data Types | Not a Bug (5405 days) | S3 | 5.1 | Any (SQL) | Any | insert date fields should give an error if inserted Data is not formated correct |
68192 | 2013-01-27 20:52 | 2013-01-28 15:40 | MySQL Server: Data Types | Verified (4100 days) | S3 | 5.1, 5.5, 5.6.9 | Any | Any | Limitation on DOUBLE or REAL length is ignored with INSERT .. SELECT |
68472 | 2013-02-23 15:45 | 2013-03-07 16:25 | MySQL Server: Data Types | Closed (4062 days) | S3 | 5.6.10 | Any | Any | TIMESTAMP logic remains partly non-standard with explicit_defaults_for_timestamp |
81642 | 2016-05-30 11:26 | 2016-05-30 16:02 | MySQL Server: Data Types | Not a Bug (2882 days) | S3 | 5.7.8 | Any | Any | union of decimal(10,1) and decimal(10,9) is not expected decimal(18,9) |
82325 | 2016-07-22 18:08 | 2016-07-25 18:50 | MySQL Server: Data Types | Duplicate (2826 days) | S3 | 5.7.9 | Any | Any | DateTime values rounded in set/insert clause but not in where clause |
92501 | 2018-09-19 12:47 | 2019-05-22 5:53 | MySQL Server: Data Types | Closed (1929 days) | S3 | 5.7, 5.7.23, 8.0.12, 5.6.41 | Any | Any | FROM_UNIXTIME accepts an out of range parameter through rounding |
105819 | 2021-12-07 9:48 | 2021-12-07 14:38 | MySQL Server: Data Types | Verified (865 days) | S3 | 8.0 | Any | Any | Conversion from Blob/Text column value to double does not return a truncation er |
111675 | 2023-07-06 8:36 | 2023-07-07 12:17 | MySQL Server: Data Types | Verified (289 days) | S3 | 8.0 | Any | Any | wrong result when compare timestamp with undependent subselect that return time |
36214 | 2008-04-19 9:04 | 2008-04-25 9:52 | MySQL Server: Data Types | Not a Bug (5839 days) | S3 | ALL | Any | Any | Timestamp column type limitation |
39146 | 2008-09-01 5:08 | 2008-09-11 10:10 | MySQL Server: Data Types | Not a Bug (5700 days) | S3 | 4.1.22-standard-log, 4.1, 5.0, 5.1, 6.0 bzr | Any | Any | Convertion to unsigned bigint where it must be signed int |
41137 | 2008-11-30 16:17 | 2014-01-16 18:01 | MySQL Server: Data Types | Closed (3747 days) | S4 | Any | Any | TIMESTAMP column with no default value | |
30059 | 2007-07-26 3:01 | 2011-02-16 23:43 | MySQL Server: Data Types | Closed (5056 days) | S3 | 5.0 and up | Any | Any | End-space truncation is inconsistent or incorrect |
63126 | 2011-11-07 2:16 | 2011-12-07 7:00 | MySQL Server: Data Types | No Feedback (4518 days) | S3 | 5.5.16 | Any | Any | cannot perform a precise calculation with decimal data |
69228 | 2013-05-14 14:56 | 2022-05-23 9:39 | MySQL Server: Data Types | Verified (3994 days) | S2 | 5.6, probably since 4.1 | Any | Any | Last insert ID incorrectly delivered to the client |
40365 | 2008-10-28 7:55 | 2011-02-16 23:43 | MySQL Server: Data Types | Closed (5612 days) | S3 | any | Any | Any | Prepared statements may insert invalid dates. |
99513 | 2020-05-11 13:21 | 2020-06-09 12:10 | MySQL Server: Data Types | Closed (1412 days) | S3 | Any | Any | "ALTER TABLE ... ADD ... DEFAULT now()" generates wrong time at first INSERT | |
105517 | 2021-11-10 13:36 | 2021-11-10 14:36 | MySQL Server: Data Types | Verified (892 days) | S2 | 8.0 | Any (20.0.4.1) | Any | INSERT of CURRENT_TIMESTAMP() vs. DEFAULT differs for TIMESTAMP field |
87678 | 2017-09-06 9:16 | 2018-02-13 8:22 | MySQL Server: Data Types | Verified (2258 days) | S4 | 5.7.18 | Any | Any | Improve the strict mode for DECIMAL |
106980 | 2022-04-11 12:43 | 2022-04-20 10:23 | MySQL Server: Data Types | Not a Bug (732 days) | S3 | 5.7 | Any | Any | Query parsed as UPDATE calculates a different value from same query as INSERT |
111354 | 2023-06-12 2:37 | 2023-06-12 13:00 | MySQL Server: Data Types | Not a Bug (313 days) | S3 | Any | Any | varbinary result incorrect | |
111385 | 2023-06-13 6:35 | 2023-06-13 12:34 | MySQL Server: Data Types | Not a Bug (312 days) | S3 | Any | Any | varbinary_col in (0) result incorrect | |
8376 | 2005-02-08 22:27 | 2011-02-16 23:43 | MySQL Server: Data Types | Verified (6426 days) | S4 | Any | Any | Adding a Time/Date Range Column Type | |
113384 | 2023-12-09 8:05 | 2023-12-11 11:42 | MySQL Server: Data Types | Verified (131 days) | S3 | 8.0 | Any | Any | Queried with partitions,returned result is error |
49910 | 2009-12-24 6:13 | 2011-02-16 23:44 | MySQL Server: Data Types | Closed (4819 days) | S3 | 5.1.42, next-mr | Any | Any | Behavioural change in SELECT/WHERE on YEAR(4) data type |
52430 | 2010-03-29 11:01 | 2011-02-16 23:44 | MySQL Server: Data Types | Closed (5036 days) | S3 | 5.5.3-m3 | Any | Any | Incorrect key in the error message for duplicate key error involving BINARY type |
57298 | 2010-10-07 8:23 | 2011-02-16 23:44 | MySQL Server: Data Types | Can't repeat (4944 days) | S3 | 5.1.51 | Any | Any | ENUMs do not obey strict sql_mode and empty string can insert when not specified |
57784 | 2010-10-27 20:42 | 2010-10-28 4:00 | MySQL Server: Data Types | Not a Bug (4923 days) | S2 | Any | Any | where clause dangerous | |
63502 | 2011-11-30 10:23 | 2012-01-27 19:06 | MySQL Server: Data Types | Closed (4467 days) | S3 | 5.1.58 | Any | Any | Incorrect results of BIGINT and DECIMAL comparison |
68759 | 2013-03-24 12:49 | 2013-03-25 5:31 | MySQL Server: Data Types | Verified (4044 days) | S3 | 5.6.10 | Any | Any | Inconsistent results on comparison a time field with a non-time literal |
78697 | 2015-10-05 7:17 | 2020-11-04 14:37 | MySQL Server: Data Types | Closed (1263 days) | S2 | 5.7.8, 5.7.10, 8.0.0, 5.6.28, 5.5.47 | Any | Any | failed cast of string-returning function to DOUBLE emits no warning |
78933 | 2015-10-23 4:07 | 2015-11-04 18:43 | MySQL Server: Data Types | Not a Bug (3090 days) | S3 | 5.7.8, 5.7.9, 5.6.28, 5.5.47 | Any | Any | Negative zero(-0) is returned for mod(%) operation |
79317 | 2015-11-17 22:15 | 2016-04-25 13:30 | MySQL Server: Data Types | Not a Bug (3048 days) | S3 | 5.5.46, 5.6.27, 5.7.9.1 | Any | Any | MySQL 5.6.27 trying to validate binary data as UTF-8 |
37480 | 2008-06-18 13:45 | 2018-09-25 21:47 | MySQL Server: Tests | Closed (5784 days) | S7 | 6.0 | Any | Any | commit_1innodb.test fails randomly |
37803 | 2008-07-02 11:09 | 2008-10-17 17:40 | MySQL Server: Tests | Closed (5664 days) | S3 | 5.1.26,6.0.6 | Any | Any | Test "partition_alter2_innodb" exhausts resources (time and/or memory) |
37932 | 2008-07-07 15:03 | 2018-09-25 21:47 | MySQL Server: Tests | Closed (5534 days) | S7 | 5.1+ | Any | Any | binlog_killed_simulate fails sporadically on pushbuild |
38106 | 2008-07-14 15:21 | 2012-05-18 20:19 | MySQL Server: Tests | Duplicate (5664 days) | S3 | 6.0-BK | Any | Any | main.crash_commit_before crashes the server sporadically |
41111 | 2008-11-28 18:18 | 2011-02-16 23:43 | MySQL Server: Tests | Closed (5568 days) | S3 | 5.1 | Any | Any | events_bugs fails sporadically on pushbuild |
28895 | 2007-06-05 12:52 | 2018-09-25 21:45 | MySQL Server: Tests | Closed (6151 days) | S7 | 5.0, 5.1 | Any | Any | Test 'information_schema_db' fails on i5/OS 32 bit |
31408 | 2007-10-04 20:31 | 2007-11-01 12:51 | MySQL Server: Tests | Closed (6015 days) | S3 | 5.1 | Any | Any | funcs_1: <engine>_trig_03e test fail |
33971 | 2008-01-22 2:06 | 2011-06-25 0:45 | MySQL Server: Tests | Closed (4683 days) | S3 | 5.1, 6.0 | Any | Any | Test of using (default) for INSERT with an enum column not enabled. |
41776 | 2008-12-29 3:45 | 2011-02-16 23:43 | MySQL Server: Tests | Closed (5373 days) | S3 | 5.0, 5.1, 6.0 bzr | Any | Any | type_date.test may fail if run around midnight. |
45890 | 2009-07-01 22:27 | 2009-07-04 12:49 | MySQL Server: Tests | Not a Bug (5404 days) | S3 | 5.1.36 | Any | Any | main.grant failes |
51049 | 2010-02-10 7:23 | 2011-02-16 23:44 | MySQL Server: Tests | Closed (5052 days) | S3 | 5.1-bugteam | Any | Any | main.bug39022 fails in mysql-trunk-merge |
51907 | 2010-03-10 12:26 | 2021-05-02 20:45 | MySQL Server: Tests | Verified (5128 days) | S3 | 5.5.3 | Any | Any | main.ctype_utf8mb4_ndb fails persistently |
75189 | 2014-12-12 7:09 | 2014-12-19 22:15 | MySQL Server: Tests | Verified (3410 days) | S3 | 5.6 | Any | Any | engines suite tests depending on InnoDB implementation details |
77959 | 2015-08-06 10:45 | 2021-02-18 9:57 | MySQL Server: Tests | Duplicate (1157 days) | S3 | 5.7.8, 5.7.9 | Any | Any | max_statement_time test is unstable |
92105 | 2018-08-21 16:28 | 2019-04-26 11:47 | MySQL Server: Tests | Verified (2069 days) | S5 | 5.7.23 | Any | Any | Speed up innodb.fts_exec_interrupt |
103764 | 2021-05-21 8:10 | 2021-05-21 8:25 | MySQL Server: Tests | Verified (1065 days) | S7 | 8.0.22/8.0.23+, 8.0.25 | Any | Any | show create table processlist fields do not match |
22552 | 2006-09-21 16:14 | 2018-09-25 21:44 | MySQL Server: Tests | No Feedback (4219 days) | S7 | 5.1.14, 5.1.65 | Any (Sun Solaris 10 Sparc) | Any | 5.1.12-beta build on Solaris 10 - client_xml test fail with core dump |
29046 | 2007-06-12 8:06 | 2018-09-25 21:45 | MySQL Server: Tests | Closed (5989 days) | S7 | 5.1.20 | Any | Any | rpl_stm_mystery22 unstable |
29049 | 2007-06-12 12:30 | 2007-08-11 10:12 | MySQL Server: Tests | Closed (6097 days) | S3 | Any | Any | lock_multi fails in rare case | |
30560 | 2007-08-22 11:33 | 2007-12-08 15:39 | MySQL Server: Tests | Closed (5978 days) | S3 | Any | Any | Valgrind option to mysql-test-run with spaces in cause strange error | |
33266 | 2007-12-16 7:33 | 2018-09-25 21:47 | MySQL Server: Tests | Closed (5862 days) | S7 | 5.0.54,5.1.23, 5.1.24-BK, 6.0-BK | Any | Any | regression test subselect fails |
34889 | 2008-02-27 14:27 | 2018-09-25 21:47 | MySQL Server: Tests | Closed (5854 days) | S7 | 5.0 | Any | Any | mysql_client_test::test_mysql_insert_id test fails sporadically |
80219 | 2016-02-01 8:26 | 2018-04-18 8:38 | MySQL Server: Tests | Can't repeat (2194 days) | S3 | 5.6.28 | Any | Any | rpl_stm_mixed_crash_safe mtr test fails |
30212 | 2007-08-02 20:31 | 2018-09-25 21:45 | MySQL Server: Tests | Closed (6098 days) | S7 | Any | Any | events_logs_tests not deterministic; SLEEP(2), others | |
33790 | 2008-01-10 11:12 | 2008-02-15 13:03 | MySQL Server: Tests | Can't repeat (5909 days) | S3 | 5.1 | Any | Any | Fix innodb_mysql test |
39903 | 2008-10-07 9:18 | 2018-09-25 21:49 | MySQL Server: Tests | Closed (5559 days) | S7 | 6.0-rpl | Any | Any | Tests that restart server fail sporadically on pushbuild |
37741 | 2008-06-30 14:12 | 2008-06-30 14:41 | MySQL Server: Tests | Duplicate (5773 days) | S3 | 5.1.25 | Any | Any | Test concurrent_innodb fails with invalid login |
76710 | 2015-04-15 14:48 | 2015-04-16 7:36 | MySQL Server: Tests | Verified (3292 days) | S3 | 5.7.7 | Any | Any | myisam_views-big fails |
22436 | 2006-09-18 9:55 | 2006-11-06 14:46 | MySQL Server: Tests | Closed (6375 days) | S3 | 5.0.25 | Any (All) | Any | Four tests require "innodb" to be configured, fail in "classic" build |
29290 | 2007-06-22 0:06 | 2007-11-21 20:23 | MySQL Server: Tests | Closed (5995 days) | S3 | 5.1 | Any | Any | type_datetime.test failure in 5.1 |
30408 | 2007-08-14 15:48 | 2007-08-29 18:47 | MySQL Server: Tests | Closed (6079 days) | S3 | 5.1.21 | Any | Any | Suite "parts" needs bug numbers updated |
31243 | 2007-09-27 14:40 | 2007-11-01 12:49 | MySQL Server: Tests | Closed (6015 days) | S3 | 5.1.22 | Any | Any | Test "partition_basic_myisam" truncates path names |
81467 | 2016-05-17 14:33 | 2016-05-18 9:43 | MySQL Server: Tests | Verified (2894 days) | S3 | 5.7, 5.7.12 | Any | Any | innodb_fts.sync_block test unstable due to slow query log nondeterminism |
55595 | 2010-07-28 3:30 | 2014-03-14 19:04 | MySQL Server: Storage Engines | Verified (3690 days) | S1 | Any | Any | Lots of data differences between MyISAM and InnoDB where there shouldn't be | |
42491 | 2009-01-30 19:44 | 2011-02-16 23:43 | MySQL Server: Storage Engines | Duplicate (5559 days) | S2 | 5.1.30 | Any | Any | INSERT on temporary table may pass incorrect lock type to storage engine |
46374 | 2009-07-24 16:29 | 2018-10-01 16:17 | MySQL Server: Stored Routines | Closed (5158 days) | S6 | 5.4 | Any | Any | crash, INSERT INTO t1 uses function, function modifies t1 |
53441 | 2010-05-05 15:45 | 2011-02-16 23:44 | MySQL Server: Stored Routines | Duplicate (5098 days) | S3 | 5.1.42 | Any | Any | Cursor does not fetch ts value from int column |
27006 | 2007-03-09 16:19 | 2007-03-20 16:34 | MySQL Server: Stored Routines | Closed (6241 days) | S1 | 5.0.36 | Any (All) | Any | AFTER UPDATE triggers not fired with INSERT ... ON DUPLICATE KEY UPDATE |
28650 | 2007-05-24 11:09 | 2007-06-24 12:29 | MySQL Server: Stored Routines | No Feedback (6145 days) | S3 | 5.0 | Any | Any | problem facing with triggers |
58674 | 2010-12-02 20:42 | 2011-04-21 0:37 | MySQL Server: Stored Routines | Closed (4748 days) | S3 | 5.5.6, 5.5.8 | Any | Any | Unsafe warnings are still produced after unsafety has been eliminated |
46179 | 2009-07-14 18:07 | 2022-12-04 20:45 | MySQL Server: Stored Routines | Verified (1937 days) | S2 | 5.6, 5.7, 8.0 | Any | Any | set new.colname = default(colname) in trigger elicits a crazy error message |
49625 | 2009-12-11 15:28 | 2009-12-14 18:03 | MySQL Server: Stored Routines | Not a Bug (5241 days) | S1 | 5.0.51 | Any (Unknown host OS) | Any | Stored procedure that calls UUID() calls resuting Insert Statement multipe times |
83227 | 2016-09-30 16:10 | 2016-11-16 6:12 | MySQL Server: Stored Routines | Can't repeat (2712 days) | S3 | 5.5, 5.6, 5.7, 5.6.33 | Any | Any | Concurrent trigger creation causes errors and corrupts the trigger |
102638 | 2021-02-18 9:36 | 2021-04-15 13:06 | MySQL Server: Stored Routines | Verified (1101 days) | S4 | 8.0 | Any | Any | improvements for TRIGGER |
36348 | 2008-04-25 15:37 | 2008-04-27 7:15 | MySQL Server: Stored Routines | Duplicate (5837 days) | S3 | 5.0 and 5.1 | Any | Any | SQLWARNING and SQLEXCEPTIONs treated differently |
70983 | 2013-11-22 16:58 | 2014-01-16 5:43 | MySQL Server: Stored Routines | Closed (3747 days) | S3 | 5.6 | Any | Any | Assertion `0' fails on creating a temporary table via trigger |
72318 | 2014-04-11 17:36 | 2017-12-23 10:47 | MySQL Server: Stored Routines | Verified (3659 days) | S3 | 5.6.14-log | Any | Any | Stored function throws error 1137 if temporary table was not created right then |
73207 | 2014-07-05 12:21 | 2017-04-27 14:36 | MySQL Server: Stored Routines | Closed (3435 days) | S3 | 5.7.4 | Any | Any | 5.7 triggers handle not null differently to older versions; breaks compatibility |
84037 | 2016-12-02 6:51 | 2021-09-09 14:05 | MySQL Server: Stored Routines | Verified (2696 days) | S3 | 5.7.17, 5.7.16 | Any | Any | Error on insert JSON data to a table with generated columns from a SP |
84077 | 2016-12-06 13:19 | 2018-01-02 9:52 | MySQL Server: Stored Routines | Closed (2528 days) | S2 | 5.7.11 | Any | Any | CURRENT_TIMESTAMP produces zeros in TRIGGER |
58709 | 2010-12-03 16:44 | 2011-03-24 22:45 | MySQL Server: Stored Routines | Closed (4776 days) | S3 | 5.6.1-m5-debug-log | Any | Any | assert in mysql_execute_command |
72335 | 2014-04-14 6:16 | 2014-04-21 8:47 | MySQL Server: Stored Routines | Not a Bug (3652 days) | S2 | Any | Any | INCORRECT BIT COLUMN VALUE RETURNED IN THE STORED PROCEDURE OUT PARAM | |
73991 | 2014-09-21 10:39 | 2023-11-12 14:57 | MySQL Server: Stored Routines | Open | S4 | Any | Any | Named parameter CALL syntax | |
28280 | 2007-05-07 13:47 | 2007-05-29 13:29 | MySQL Server: Stored Routines | Duplicate (6171 days) | S1 | 5.0.42BK, 5.1.18BK | Any | Any | insert delayed on a table containing trigger leads to server crash |
30400 | 2007-08-14 8:03 | 2007-09-30 11:08 | MySQL Server: Stored Routines | No Feedback (6047 days) | S3 | Any | Any | cursor can not support recursion. | |
32790 | 2007-11-27 20:17 | 2008-04-15 1:24 | MySQL Server: Stored Routines | Closed (5849 days) | S1 | 5.0, 5.1, 6.0 | Any | Any | crash in trigger.test with InnoDB for a table |
33774 | 2008-01-09 16:06 | 2008-01-10 13:18 | MySQL Server: Stored Routines | Not a Bug (5945 days) | S1 | Any | Any | oracle details i am using | |
35877 | 2008-04-07 12:11 | 2011-02-16 23:43 | MySQL Server: Stored Routines | Closed (5273 days) | S3 | 5.1 | Any | Any | Update .. WHERE with function, constraint violation, crash |
39660 | 2008-09-26 8:13 | 2012-05-18 20:19 | MySQL Server: Stored Routines | Duplicate (5685 days) | S2 | 5.1 | Any | Any | Before Trigger in combination with NOT NULL behaves wrong |
73399 | 2014-07-25 18:32 | 2014-07-25 18:56 | MySQL Server: Stored Routines | Verified (3557 days) | S1 | 5.6.14, 5.0.97, 5.1.74, 5.5.39, 5.6.21, 5.7.5 | Any | Any | BEFORE INSERT TRIGGER not fired |
86821 | 2017-06-26 4:06 | 2023-02-10 10:55 | MySQL Server: Stored Routines | Not a Bug (1923 days) | S2 | 5.6, 5.7 | Any | Any | Trigger allocates memory during SELECT |
14053 | 2005-10-15 23:44 | 2022-12-04 20:45 | MySQL Server: Stored Routines | Verified (5281 days) | S4 | 5.0.13-rc-standard-log | Any (any) | Any | Impossible to access auto_increment values in triggers on insert |
18914 | 2006-04-09 4:33 | 2007-03-09 3:14 | MySQL Server: Stored Routines | Closed (6252 days) | S3 | 5.0.21-BK, 5.0+ | Any (ALL) | Any | Calling certain SPs from triggers fail |
50423 | 2010-01-18 16:41 | 2011-02-16 23:44 | MySQL Server: Stored Routines | Closed (5054 days) | S3 | 5.1.43 | Any | Any | Crash on second call of a procedure dropping a trigger |
51234 | 2010-02-17 10:18 | 2012-06-11 16:51 | MySQL Server: Stored Routines | Won't fix (4331 days) | S1 | 5.1.43, 5.5.1-m2 | Any | Any | crash with --skip-grant-tables and insert delayed,trigger,function in other db |
54375 | 2010-06-09 17:38 | 2016-02-25 12:24 | MySQL Server: Stored Routines | Closed (4875 days) | S1 | 5.1.47 | Any | Any | Error in stored procedure leaves connection in different default schema |
56361 | 2010-08-30 11:04 | 2012-05-30 7:04 | MySQL Server: Stored Routines | Verified (4344 days) | S4 | Any | Any | Table Methods | |
60980 | 2011-04-26 14:54 | 2011-04-26 15:38 | MySQL Server: Stored Routines | Not a Bug (4743 days) | S3 | 5.1.47 | Any | Any | SHOW PROCEDURE CODE example returns an error |
61711 | 2011-06-30 16:45 | 2012-12-24 9:36 | MySQL Server: Stored Routines | Duplicate (4135 days) | S3 | 5.5.13, 5.5.15 | Any | Any | CURSOR does not accept variables in LIMIT clause |
68662 | 2013-03-13 19:16 | 2013-03-13 19:16 | MySQL Server: Stored Routines | Open | S4 | Any | Any | Request for the ability to run self-locking/self-altering triggers (known risks) | |
15014 | 2005-11-17 12:51 | 2006-02-02 13:58 | MySQL Server: Stored Routines | Closed (6652 days) | S2 | 5.0 | Any (Any) | Any | Performance problems with functions |
23311 | 2006-10-15 22:28 | 2012-05-18 20:19 | MySQL Server: Stored Routines | Duplicate (6372 days) | S2 | 5.0.24a | Any (Any) | Any | Queries within triggers give unexpected results |
24117 | 2006-11-08 23:51 | 2007-02-01 1:03 | MySQL Server: Stored Routines | Closed (6288 days) | S2 | 5.0.26,5.0.28 | Any (*) | Any | server crash on a FETCH with a cursor on a table which is not in the table cache |
25435 | 2007-01-05 15:11 | 2012-05-18 20:19 | MySQL Server: Stored Routines | Duplicate (6310 days) | S3 | 5.0.32, 5.1.14 | Any (Any) | Any | All triggers evaluated for statement even if out of scope of the statement |
27563 | 2007-03-31 14:09 | 2007-06-18 17:57 | MySQL Server: Stored Routines | Closed (6151 days) | S3 | 5.0.38 | Any | Any | killing noticed in SF() stack but the error gets missed in action and wrong rslt |
30132 | 2007-07-31 0:29 | 2016-02-25 12:24 | MySQL Server: Stored Routines | Not a Bug (6101 days) | S2 | Any | Any | CREATE ROUTINE privilege not needed to create/alter stored procedures | |
31539 | 2007-10-11 15:59 | 2007-12-11 20:13 | MySQL Server: Stored Routines | Closed (5975 days) | S2 | 5.1.22 | Any | Any | ALTER EVENT RENAME TO... resets STATUS to 'ENAMLE' |
31643 | 2007-10-16 15:26 | 2022-12-12 5:54 | MySQL Server: Stored Routines | Verified (5617 days) | S3 | 5.1.22 | Any | Any | Setting an event to 'disable on slave' disables it on the master |
33083 | 2007-12-08 1:22 | 2012-06-20 16:48 | MySQL Server: Stored Routines | Closed (4322 days) | S1 | 5.0, 5.1, 5.2 | Any | Any | Stored Function: error and crash if a temporary table is dropped in a loop |
45231 | 2009-06-01 3:07 | 2022-12-04 20:45 | MySQL Server: Stored Routines | Verified (5437 days) | S4 | 5.0.60 | Any | Any | Cannot change LAST_INSERT_ID value within before update trigger |
19565 | 2006-05-05 17:07 | 2022-08-21 20:45 | MySQL Server: Stored Routines | Duplicate (6108 days) | S1 | 5.0, 5.1 | Any | Any | crash in system test, trigger, InnoDB transaction deadlock |
29771 | 2007-07-12 19:50 | 2007-07-17 11:25 | MySQL Server: Stored Routines | Not a Bug (6122 days) | S2 | 5.045 | Any | Any | The cursor is automatically closed. |
33515 | 2007-12-26 13:29 | 2008-06-13 16:09 | MySQL Server: Stored Routines | Closed (5790 days) | S1 | 6.0.4 | Any | Any | Create trigger, partition, insert = crash |
111849 | 2023-07-21 20:29 | 2024-03-19 12:37 | Shell Upgrade Checker | Verified (270 days) | S3 | 8.0 | Any | Any | checkForServerUpgrade fails for INSERT INTO.SELECT FOR UPDATE routines |
92804 | 2018-10-16 19:48 | 2018-10-19 15:09 | Shell Upgrade Checker | Not a Bug (2010 days) | S3 | 5.7.23 | Any | Any | mysql_upgrade not validate sql_mode |
106463 | 2022-02-15 10:55 | 2022-08-08 9:39 | Shell AdminAPI InnoDB Cluster / ReplicaSet | Closed (621 days) | S4 | 8.0.28 | Any | Any | Running DDL queries in a Multi-Primary Cluster |
86155 | 2017-05-02 6:56 | 2017-06-30 9:58 | Shell AdminAPI InnoDB Cluster / ReplicaSet | Closed (2486 days) | S2 | 1.0.9 | Any | Any | InnoDB Cluster doen not work with sql_mode="ORACLE,TRADITIONAL" |
91394 | 2018-06-24 21:41 | 2018-12-19 14:15 | Shell AdminAPI InnoDB Cluster / ReplicaSet | Closed (1949 days) | S1 | 8.0.11 | Any | Any | mysqlsh will not recognize root privileges if they are assigned with a role |
87300 | 2017-08-03 10:18 | 2017-11-09 11:24 | Shell General / Core Client | Closed (2354 days) | S2 | mysqlsh Ver 1.0.10 for Linux on x86_64 | Any | Any | mysql-shell dba.checkInstanceConfiguration() |
85562 | 2017-03-21 9:48 | 2017-12-22 8:42 | MySQL Server: Security: Roles | Can't repeat (2311 days) | S2 | 8.0 | Any | Any | dropping a role does not remove privileges from active users |
75303 | 2014-12-24 3:04 | 2015-11-19 17:52 | MySQL Server: Security: Encryption | Verified (3075 days) | S4 | Any | Any | Option in hash functions for binary output | |
44927 | 2009-05-18 8:58 | 2011-02-16 23:43 | MySQL Server: Storage Engine API | Verified (5373 days) | S4 | Any | Any | allow storage engine to maintain auto-increment counter | |
71270 | 2014-01-02 9:08 | 2015-01-28 14:50 | MySQL Server: Storage Engine API | Verified (3757 days) | S3 | 5.6.15 | Any | Any | Failures to end bulk insert for partitioned tables handled incorrectly |
111184 | 2023-05-29 12:20 | 2023-05-29 13:23 | MySQL Server: Storage Engine API | Verified (327 days) | S3 | 8.0 | Any | Any | Execution plan display error |
87326 | 2017-08-05 3:21 | 2017-08-23 17:58 | MySQL Server: Replication | Verified (2432 days) | S2 | 5.6.27 - 5.6.35 | Any | Any | deadlock in binary log. |
87624 | 2017-08-31 11:04 | 2017-09-01 12:08 | MySQL Server: Replication | Verified (2423 days) | S2 | 5.6, 8.0.2, any?, 5.6.37 | Any | Any | Wrong statement-based binary logging for CONCAT() in stored procedure |
88120 | 2017-10-17 11:22 | 2018-04-16 13:40 | MySQL Server: Replication | Closed (2249 days) | S3 | 5.7.17 | Any | Any | Backport BUG#26277771 to 5.7 |
96026 | 2019-06-28 12:40 | 2019-07-01 13:21 | MySQL Server: Replication | Not a Bug (1755 days) | S3 | Any | Any | The HA instance causes FEDERATED engine operations to be performed multiple time | |
98069 | 2019-12-25 10:12 | 2020-01-09 4:53 | MySQL Server: Replication | Not a Bug (1572 days) | S3 | 5.7 | Any | Any | No error on slave while trigger for binlog_format="statement" and read_only is 1 |
106113 | 2022-01-08 6:52 | 2022-01-08 9:45 | MySQL Server: Replication | Verified (833 days) | S2 | 8.0.27, 5.7.36 | Any | x86 | Contribution by Tencent: insert on duplicate key cause 1032 replication error in |
114074 | 2024-02-21 8:35 | 2024-02-27 14:20 | MySQL Server: Replication | Verified (59 days) | S5 | 8.0.32 | Any | Any | optimize for Writeset_trx_dependency_tracker::get_dependency |
82 | 2003-02-18 14:07 | 2003-03-03 5:52 | MySQL Server: Replication | Closed (7719 days) | S2 | 4.0 | Any (all) | Any | LOAD DATA *LOCAL* INFILE is not properly written to the binary log |
88 | 2003-02-21 6:41 | 2008-09-27 8:44 | MySQL Server: Replication | Closed (5684 days) | S3 | 5.0 | Any (all) | Any | Some SET commands should be written to the binlog as they affect next updates |
177 | 2003-03-21 13:09 | 2003-05-13 14:17 | MySQL Server: Replication | Closed (7648 days) | S3 | 4.0 | Any (all) | Any | CONNECTION_ID() is badly replicated |
319 | 2003-04-23 14:32 | 2011-02-16 23:40 | MySQL Server: Replication | Closed (5463 days) | S3 | 4.0, 4.1, 5.1 | Any (all) | Any | if while a non-transactional slave is replicating a transaction, possiblproblem |
4463 | 2004-07-08 15:01 | 2007-05-04 12:13 | MySQL Server: Replication | Not a Bug (6196 days) | S4 | <4.1 | Any (doesn't matter) | Any | GROUP takes the first-found values |
10048 | 2005-04-20 22:45 | 2017-05-21 20:45 | MySQL Server: Replication | Verified (6632 days) | S4 | 4.1.11, 5.0.x | Any (Any) | Any | 4.1 datetime fields aren't as 'relaxed' as 4.0; can cause replication issues |
11338 | 2005-06-15 4:55 | 2005-08-24 17:59 | MySQL Server: Replication | Closed (6814 days) | S2 | 4.1.12, 5.0.9 | Any (any) | Any | logging of prepared statement w/ blob type |
37148 | 2008-06-03 3:21 | 2011-02-16 23:43 | MySQL Server: Replication | Closed (5150 days) | S3 | 5.0.37, 5.0.64, 5.1.26 | Any | Any | Most callers of mysql_bin_log.write ignore the return result |
37417 | 2008-06-16 1:47 | 2012-05-18 20:19 | MySQL Server: Replication | No Feedback (5643 days) | S3 | 5.0.64 | Any | Any | Master/Slave INSERT/SELECT results differ |
37733 | 2008-06-30 7:21 | 2008-08-12 17:26 | MySQL Server: Replication | Closed (5730 days) | S2 | 5.1, 6.0 | Any | Any | rpl.rpl_flushlog_loop 'row' fails sporadically on pushbuild |
37768 | 2008-07-01 15:01 | 2011-02-16 23:43 | MySQL Server: Replication | Can't repeat (5394 days) | S3 | 5.1.26,6.0-BK | Any | Any | rpl_flushlog_loop/row fails randomly |
39197 | 2008-09-02 18:20 | 2008-11-27 22:30 | MySQL Server: Replication | Not a Bug (5623 days) | S1 | 5.1.26,5.1.28, 5.0.67 | Any (Mac OSX and Linux) | Any | replication breaks with large load with InnoDB, flush logs, and slave stop/start |
40306 | 2008-10-24 13:53 | 2016-10-16 20:45 | MySQL Server: Replication | Verified (5639 days) | S4 | 5.1.x, 6.x | Any | Any | Replication of externally build tables (like "myisampack"ed ones) |
42956 | 2009-02-18 5:10 | 2011-02-16 23:43 | MySQL Server: Replication | Can't repeat (5422 days) | S3 | 5.1-bugteam, 5.1, 6.0 bzr | Any | Any | SBL, INSERT .. SELECT .. LIMIT error,STRICT_TRANS_TABLES mode, even MyISAM table |
43929 | 2009-03-28 8:57 | 2011-02-16 23:43 | MySQL Server: Replication | Closed (5395 days) | S2 | 5.0.78,5.1.32 | Any | Any | binlog corruption when max_binlog_cache_size is exceeded |
45636 | 2009-06-21 10:24 | 2016-10-16 20:45 | MySQL Server: Replication | Verified | S4 | Any | Any | allow alter table to record changes to binary log when using rbr | |
45670 | 2009-06-23 8:43 | 2012-04-25 16:39 | MySQL Server: Replication | Closed (4378 days) | S2 | 5.1.35, 5.5.13 | Any | Any | Secondary auto-incremented primary fields on replicas end up with wrong value |
46697 | 2009-08-13 13:43 | 2011-02-16 23:44 | MySQL Server: Replication | Closed (4853 days) | S3 | 5.0, 5.1, 5.4.4 | Any | Any | Table name in error message is not populated |
46861 | 2009-08-21 21:52 | 2011-02-16 23:44 | MySQL Server: Replication | Closed (5330 days) | S3 | 5.0, 5.1 | Any | Any | Auto-closing of temporary tables broken by replicate-rewrite-db |
46862 | 2009-08-21 21:56 | 2011-02-16 23:44 | MySQL Server: Replication | Duplicate (5354 days) | S3 | 5.0.72sp1 | Any | Any | Auto-closing of temporary tables broken by replicate-rewrite-db |
47160 | 2009-09-06 23:19 | 2023-02-12 20:45 | MySQL Server: Replication | Duplicate (5314 days) | S3 | 5.1+ | Any | Any | rpl_binlog_max_cache_size fails sporadically on PB2 |
47307 | 2009-09-14 11:15 | 2011-02-16 23:44 | MySQL Server: Replication | Won't fix (5303 days) | S3 | 5.0.66, 5.1.38, 5.0, 5.1, next bzr | Any | Any | slave breaks if larger session group_concat_max_len is set on master |
47868 | 2009-10-06 16:18 | 2011-12-21 16:14 | MySQL Server: Replication | Closed (4504 days) | S4 | any | Any | Any | statement based logging of partially failed statements |
48183 | 2009-10-20 13:36 | 2013-01-10 9:30 | MySQL Server: Replication | Closed (4118 days) | S2 | 5.1+ | Any | Any | statements using fulltext parser plugins should be marked unsafe |
37200 | 2008-06-04 17:23 | 2008-07-29 9:52 | MySQL Server: Replication | Closed (5744 days) | S3 | 5.1, 6.0 | Any | Any | rpl_switch_stm_row_mixed fails sporadically in pushbuild |
333 | 2003-04-26 13:49 | 2003-08-22 7:08 | MySQL Server: Replication | Won't fix (7547 days) | S2 | 4.0 | Any (all) | Any | 3 binlogging bugs when doing INSERT with mixed InnoDB / MyISAM |
56184 | 2010-08-23 5:27 | 2011-05-13 10:26 | MySQL Server: Replication | Closed (4726 days) | S3 | 5.1, 5.5 | Any | Any | Rolled back transaction without non-trasactional table updated was binlogged |
46129 | 2009-07-11 12:44 | 2011-02-16 23:44 | MySQL Server: Replication | Closed (5372 days) | S3 | 5.1+ | Any | Any | Failing mixed stm (with trans and non-trans tables) causes wrong seq in binlog |
29571 | 2007-07-05 12:06 | 2007-08-03 15:39 | MySQL Server: Replication | Closed (6105 days) | S3 | 4.1,5.0 | Any | Any | INSERT DELAYED IGNORE written to binary log on the master but on the slave |
47835 | 2009-10-05 13:19 | 2011-02-16 23:44 | MySQL Server: Replication | Can't repeat (4873 days) | S3 | 5.1.37sp1 | Any | Any | MBR replication failure under concurrent load with OFFSET in subselect |
51564 | 2010-02-26 20:10 | 2011-02-16 23:44 | MySQL Server: Replication | Closed (5108 days) | S3 | 5.5.99-m3 | Any | Any | Error ER_BINLOG_UNSAFE_NONTRANS_AFTER_TRANS is too eager after BUG#46364 |
70923 | 2013-11-15 16:59 | 2013-11-18 19:03 | MySQL Server: Replication | Verified (3806 days) | S2 | 5.5.34, 5.6.16 | Any | Any | Replication failure on multi-statement INSERT DELAYED queries |
43457 | 2009-03-06 14:24 | 2018-04-11 13:22 | MySQL Server: Replication | Not a Bug (2201 days) | S3 | 5.1, 6.0 | Any | Any | replicate-ignore-db behaves differently with different binlog formats |
57892 | 2010-11-01 12:02 | 2017-05-21 20:45 | MySQL Server: Replication | Duplicate (4910 days) | S1 | 5.6.99 (bzr_mysql-next-mr-wl2540) | Any | Any | Crash in my_b_write_quoted (log_event.cc) from mysqlbinlog with checksum |
86486 | 2017-05-28 1:01 | 2017-11-16 10:02 | MySQL Server: Replication | Duplicate (2347 days) | S3 | 5.7.x | Any | Any | XA Transactions in binlog cause replication broken |
50192 | 2010-01-08 19:21 | 2011-02-16 23:44 | MySQL Server: Replication | Closed (5157 days) | S3 | 5.5.99-m3 | Any | Any | Strange effect in replication test, trigger, auto_increment |
69185 | 2013-05-09 15:23 | 2014-02-24 12:33 | MySQL Server: Replication | Verified (3708 days) | S2 | 5.1.69 | Any | Any | Replication breaks during concurrent INSERTs and LOAD DATA in a auto_inc table |
109217 | 2022-11-28 9:51 | 2022-12-12 3:19 | MySQL Server: Replication | Verified (495 days) | S2 | 5.7.40 | Any | Any | The datas of master and standby are inconsistent for Spatial Data Formats |
1331 | 2003-09-18 5:39 | 2003-10-04 6:44 | MySQL Server: Replication | Closed (7504 days) | S2 | 4.1 | Any (all) | Any | Unexistent user variable is not replicated |
2491 | 2004-01-23 5:54 | 2004-03-11 10:27 | MySQL Server: Replication | Closed (7345 days) | S2 | 4.0 | Any (all) | Any | INSERT DELAYED causes binary log unusable by mysqlbinlog (replication is ok) |
28829 | 2007-06-01 10:01 | 2012-05-18 20:19 | MySQL Server: Replication | Duplicate (6156 days) | S2 | 4.1.21,5.0.44 | Any | Any | replication breaks due to binlogs events written in wrong order |
34447 | 2008-02-10 14:46 | 2012-05-18 20:19 | MySQL Server: Replication | Duplicate (5876 days) | S1 | 5.1-BK | Any | Any | replication failure on DELETE after INSERT on an unrelated table |
35178 | 2008-03-10 9:12 | 2008-04-05 7:01 | MySQL Server: Replication | Closed (5859 days) | S1 | 5.0.51a | Any | Any | INSERT_ID not written to binary log for inserts against BLACKHOLE backed tables |
36443 | 2008-04-30 22:14 | 2011-02-16 23:43 | MySQL Server: Replication | Closed (5745 days) | S1 | 5.1.24-rc-community-log, 5.1.26 | Any | Any | Server crashes when executing insert when insert trigger on table |
46130 | 2009-07-11 13:34 | 2011-02-16 23:44 | MySQL Server: Replication | Closed (5330 days) | S3 | 5.1+ | Any | Any | Slave does not correctly handle "expected errors" |
49186 | 2009-11-29 13:52 | 2011-02-16 23:44 | MySQL Server: Replication | Can't repeat (5241 days) | S3 | 5.1.41, 5.5.0 | Any | Any | Concurrent insert/select causes slave abort if select is under read committed |
86078 | 2017-04-25 19:14 | 2018-04-12 7:51 | MySQL Server: Replication | Closed (2200 days) | S2 | 8.0.1 | Any | Any | Bad Write Set tracking with UNIQUE KEY on a DELETE followed by an INSERT. |
25507 | 2007-01-09 22:46 | 2011-02-16 23:43 | MySQL Server: Replication | Closed (5052 days) | S2 | 4.1-bk,5.0.34 | Any (*) | Any | multi-row insert delayed + auto increment causes duplicate key entries on slave |
30200 | 2007-08-02 8:33 | 2007-08-03 2:18 | MySQL Server: Replication | Closed (6105 days) | S2 | Any | Any | mysqlbinlog.test: connection_id() not restored under ps-protocol | |
30209 | 2007-08-02 18:13 | 2007-11-28 16:29 | MySQL Server: Replication | Closed (5988 days) | S2 | 5.0, 5.1 | Any | Any | rpl_packet.test: Slave_running mismatch (timing bug?) |
32606 | 2007-11-21 23:27 | 2007-11-29 12:58 | MySQL Server: Replication | Can't repeat (5987 days) | S2 | 5.0.45 | Any | Any | auto_increment on slave doesn`t work expected after null insert |
34289 | 2008-02-04 16:58 | 2008-03-29 17:10 | MySQL Server: Replication | Closed (5866 days) | S2 | 5.0.45, 5.0, 5.1, 6.0 BK | Any (Linux) | Any | Incorrect NAME_CONST substitution in stored procedures breaks replication |
34768 | 2008-02-22 21:19 | 2008-03-29 18:24 | MySQL Server: Replication | Closed (5866 days) | S2 | 5.1, 6.0 BK | Any | Any | nondeterministic INSERT using LIMIT logged in stmt mode if binlog_format=mixed |
36570 | 2008-05-07 16:36 | 2008-05-24 17:39 | MySQL Server: Replication | Closed (5810 days) | S3 | 5.0.60 | Any | Any | Parse error of CREATE PROCEDURE stmt with comments on slave |
36852 | 2008-05-21 13:28 | 2017-05-21 20:45 | MySQL Server: Replication | Verified (5813 days) | S4 | any | Any | Any | Option to strip LOW_PRIORITY for replication |
38068 | 2008-07-12 12:37 | 2008-09-15 17:15 | MySQL Server: Replication | Closed (5696 days) | S2 | 6.0, 5.1 | Any | Any | binlog_stm_binlog fails sporadically in pushbuild |
38148 | 2008-07-15 18:42 | 2008-07-15 20:52 | MySQL Server: Replication | Can't repeat (5758 days) | S3 | 5.0.37 | Any | Any | insert user() references uninitialized fields on a slave |
38854 | 2008-08-18 13:15 | 2016-10-16 20:45 | MySQL Server: Replication | Verified (5724 days) | S3 | 5.1.26, 5.1, 6.0 bzr | Any | Any | wrong data if SIGNED/UNSIGNED bit doesn't match |
39993 | 2008-10-13 6:16 | 2012-05-18 20:19 | MySQL Server: Replication | Duplicate (5286 days) | S4 | 4.1, 5.0, 5,1, 6.0 bzr | Any | Any | set binlog-do-db parameter by command line |
40116 | 2008-10-17 16:57 | 2011-02-16 23:43 | MySQL Server: Replication | Closed (5273 days) | S2 | 5.0.70, 5.0.74, 5.1.26, 5.1.29 | Any | Any | Uncommited changes are replicated and stay on slave after rollback on master |
41754 | 2008-12-26 12:03 | 2017-05-21 20:45 | MySQL Server: Replication | Duplicate (5506 days) | S2 | 5.0.70, 5.1.30, 6.0.9 | Any | Any | 'Cannot add or update a child row: a foreign key constraint fails' on SBR+Innodb |
43263 | 2009-02-27 14:39 | 2011-02-16 23:43 | MySQL Server: Replication | Closed (5413 days) | S3 | 5.0, 5.1 | Any | Any | BEGIN skipped in some replicate-do-db cases |
43402 | 2009-03-05 8:31 | 2009-03-05 13:18 | MySQL Server: Replication | Not a Bug (5525 days) | S2 | 5.0.45 | Any | Any | mysqlbinlog ignores data added using "insert into database.table values(...) |
44978 | 2009-05-20 9:38 | 2023-02-12 20:45 | MySQL Server: Replication | Duplicate (5448 days) | S3 | Any | Any | Valgrind failure: Source and destination overlap in strcpy | |
45292 | 2009-06-03 9:58 | 2011-02-16 23:44 | MySQL Server: Replication | Closed (5150 days) | S2 | mysql-5.1-telco-7.0 | Any | Any | orphan binary log created when starting server twice |
41980 | 2009-01-08 20:10 | 2011-02-16 23:43 | MySQL Server: Replication | Closed (5512 days) | S2 | 5.1.30, 5.1, 6.0 bzr | Any | Any | SBL, INSERT .. SELECT .. LIMIT = ERROR, even when @@SQL_LOG_BIN is 0 ! |
45825 | 2009-06-29 14:55 | 2011-02-16 23:44 | MySQL Server: Replication | Closed (4978 days) | S2 | 5.1+ | Any | Any | INSERT DELAYED is not unsafe: logged in statement format |
50620 | 2010-01-26 11:36 | 2011-02-16 23:44 | MySQL Server: Replication | Closed (5052 days) | S3 | 5.5.99, next-mr, 5.1 | Any | Any | Adding an index to a table prevents slave from logging into slow log |
50917 | 2010-02-04 15:23 | 2012-05-18 20:19 | MySQL Server: Replication | Verified (4887 days) | S3 | 5.1.43,5.5.2-m2 | Any | Any | slave stops with HA_ERR_KEY_NOT_FOUND |
51426 | 2010-02-23 15:57 | 2011-02-16 23:44 | MySQL Server: Replication | Closed (5008 days) | S3 | 5.1.44,5.5.99-m3 | Any | Any | User var unsigned_flag value not preserved until binlog time |
53421 | 2010-05-04 20:28 | 2011-02-16 23:44 | MySQL Server: Replication | Closed (5030 days) | S2 | 5.5.5-m3, 5.6.99-m4 | Any | Any | Part of transaction not written in binlog after deadlock, replication breaks |
55211 | 2010-07-13 13:50 | 2017-05-21 20:45 | MySQL Server: Replication | Verified (5030 days) | S2 | 5.1+ | Any | Any | INSERT...SELECT...LIMIT...UNION should be marked unsafe |
57666 | 2010-10-22 17:16 | 2011-02-16 23:44 | MySQL Server: Replication | Closed (4853 days) | S3 | 5.5.7, 5.6.99 | Any | Any | Unclear warning with broken text in error log on INSERT DELAYED |
58637 | 2010-12-01 19:44 | 2014-06-25 14:34 | MySQL Server: Replication | Closed (4383 days) | S2 | 5.1+, 5.0, 5.6.1 | Any | Any | Mark INSERT...ON DUPLICATE KEY UPDATE unsafe when there is more than one key |
59205 | 2010-12-29 6:14 | 2011-03-30 7:58 | MySQL Server: Replication | Closed (4770 days) | S3 | 5.6 | Any | Any | Test rpl.rpl_stm_000001 fail on Valgrind with binlog-checksum enabled |
60173 | 2011-02-18 20:54 | 2013-05-30 19:33 | MySQL Server: Replication | Closed (3978 days) | S2 | 5.1.47, 5.1.64, 5.5.27 | Any | Any | Partially written insert statement in binlog -- no errors reported |
61548 | 2011-06-17 8:55 | 2012-11-16 13:07 | MySQL Server: Replication | Closed (4173 days) | S3 | 5.1 and others | Any | Any | autoinc value persistency breaks certain replication scenarios |
70583 | 2013-10-10 8:14 | 2014-08-06 17:08 | MySQL Server: Replication | Closed (3580 days) | S2 | 5.6.14 | Any | Any | INSERT ON DUPLICATE KEY UPDATE failing after MySQL 5.6 upgrade. |
72314 | 2014-04-11 5:04 | 2015-02-25 5:01 | MySQL Server: Replication | Closed (3342 days) | S1 | Any | Any | stop io_thread, start io_thread with GTID may cause data inconsistencies | |
73601 | 2014-08-15 12:33 | 2016-04-27 15:03 | MySQL Server: Replication | Closed (3313 days) | S2 | 5.7 | Any | Any | Crash on direct insert into mysql.gtid_executed table |
81628 | 2016-05-27 17:25 | 2016-12-12 16:42 | MySQL Server: Replication | Closed (2812 days) | S3 | 5.7.14 | Any | Any | Assertion failure in 'MYSQL_BIN_LOG::prepare()' if DML is passed in --init-file |
87734 | 2017-09-12 9:02 | 2017-10-24 14:17 | MySQL Server: Replication | Closed (2388 days) | S3 | 8.0 | Any | Any | Replication does not handle NULL inserted in JSON NOT NULL column correctly |
90448 | 2018-04-16 12:09 | 2018-04-20 5:46 | MySQL Server: Replication | Verified (2192 days) | S3 | 5.7.21 | Any | Any | INSERT IGNORE not ignored on SQL thread |
98651 | 2020-02-18 23:49 | 2020-02-19 12:05 | MySQL Server: Replication | Verified (1522 days) | S2 | 8.0, 8.0.19 | Any | Any | Inserting into temporary table from function breaks replication in MIXED mode |
106671 | 2022-03-08 12:12 | 2022-03-11 8:00 | MySQL Server: Replication | Verified (771 days) | S3 | 5.7.35, 5.7.37 | Any | Any | Contribution by Tencent: mark insert select with autoinc column unsafe |
490 | 2003-05-24 7:09 | 2003-07-01 6:14 | MySQL Server: Replication | Closed (7599 days) | S2 | 4.0.13 | Any (all) | Any | Accidental introduction of a bug with auto_increment and INSERT SELECT |
7947 | 2005-01-16 20:40 | 2005-12-21 13:53 | MySQL Server: Replication | Closed (6695 days) | S3 | 4.0 | Any (all) | Any | Wrong binlogging of CREATE [LIKE] | DROP TABLE if TEMPORARY and transaction |
18906 | 2006-04-08 13:09 | 2006-04-10 20:05 | MySQL Server: Replication | Closed (6585 days) | S3 | 5.0.21 | Any (all) | Any | Test case rpl_temporary fails when using --vardir option |
20887 | 2006-07-06 11:44 | 2015-03-15 20:45 | MySQL Server: Replication | No Feedback (6390 days) | S3 | 4.1 and up | Any (ALL) | Any | INSERT DELAYED is not logged write-behind to binary log |
69944 | 2013-08-07 6:16 | 2014-03-06 13:20 | MySQL Server: Replication | Verified (3698 days) | S4 | All Versions | Any | Any | Processlist shows Second Behind Master instead of Query time for Replication |
70346 | 2013-09-15 4:04 | 2013-12-10 6:47 | MySQL Server: Replication | Verified (3784 days) | S1 | 5.6.16 | Any | Any | Illegal mix of collations (gbk_chinese_ci,COERCIBLE) |
70711 | 2013-10-23 18:21 | 2015-06-24 4:30 | MySQL Server: Replication | Closed (3286 days) | S3 | 5.6.14 | Any | Any | mysqlbinlog prints invalid SQL from relay logs when GTID is enabled |
74177 | 2014-10-01 13:51 | 2015-06-26 16:01 | MySQL Server: Replication | Closed (3221 days) | S2 | 5.7.5, 5.7.6 | Any | Any | --slave-preserve-commit-order causes slave to deadlock and break for some querie |
75772 | 2015-02-04 19:07 | 2015-04-07 21:01 | MySQL Server: Replication | Closed (3307 days) | S1 | 5.7.6 | Any | Any | 5.7.6->5.6 replication fails |
77392 | 2015-06-17 16:22 | 2016-04-27 15:05 | MySQL Server: Replication | Closed (3148 days) | S3 | 5.7.7 | Any | Any | Slave group event parser does not recognize XA ROLLBACK as a boundary |
77673 | 2015-07-09 18:30 | 2017-11-16 7:49 | MySQL Server: Replication | Closed (2347 days) | S2 | 5.1.73, 5.5.44, 5.6.24, 5.6.27, 5.5.46, 5.7.7-rc | Any | Any | Option "replicate_do_db" does not cause "create table" to replicate ('row' log) |
77841 | 2015-07-27 9:36 | 2015-07-28 10:07 | MySQL Server: Replication | Can't repeat (3189 days) | S3 | MySQL5.6.11 | Any | Any | There is an bug on slave about 'Last_Error' and ‘Last_SQL_Error’ , |
78389 | 2015-09-10 8:38 | 2017-11-21 14:52 | MySQL Server: Replication | Closed (3141 days) | S2 | 5.6.24,5.6.25,5.6.26 | Any | Any | 5.6.24: Lost data during master restart if partial transact has been downloaded |
80394 | 2016-02-16 12:37 | 2016-03-07 9:33 | MySQL Server: Replication | Not a Bug (2966 days) | S2 | 5.7.11 | Any | Any | incorrect semi-sync replication status handling |
80651 | 2016-03-08 3:45 | 2016-04-07 5:46 | MySQL Server: Replication | Duplicate (2935 days) | S3 | 5.5 5.6 | Any | Any | larget rpl_semi_sync_master_timeout will affect performance |
82283 | 2016-07-19 15:13 | 2017-07-14 14:27 | MySQL Server: Replication | Closed (2472 days) | S3 | 5.6,5.7, 5.7.13 | Any | Any | main.mysqlbinlog_debug fails with a LeakSanitizer error |
84153 | 2016-12-09 19:05 | 2017-07-17 12:30 | MySQL Server: Replication | Closed (2507 days) | S2 | 5.7.18 | Any | Any | ASSERT "!contains_gtid(gtid)" rpl_gtid_owned.cc:94 Owned_gtids::add_gtid_owner |
84748 | 2017-01-31 16:57 | 2017-02-06 7:29 | MySQL Server: Replication | Verified (2630 days) | S4 | 5.7 | Any | Any | Request transaction GTID in OK packet on COMMIT(without needing a round-trip). |
84934 | 2017-02-10 4:23 | 2017-02-10 8:35 | MySQL Server: Replication | Verified (2626 days) | S3 | 5.7.17 | Any | Any | Column order is not important for replication to function |
85447 | 2017-03-14 13:09 | 2018-10-25 9:37 | MySQL Server: Replication | Closed (2004 days) | S3 | 5.7, 5.7.17 | Any | Any | Slave SQL thread locking issue on a certain XA workload on master |
89272 | 2018-01-16 22:52 | 2018-06-19 10:29 | MySQL Server: Replication | Closed (2165 days) | S2 | 5.6.39 | Any | Any | Binlog and Engine become inconsistent when binlog cache file gets out of space |
90578 | 2018-04-23 16:44 | 2018-04-24 11:31 | MySQL Server: Replication | Closed (2188 days) | S3 | 8.0.11 | Any | Any | rpl.rpl_column_stats_table test fails |
90959 | 2018-05-22 6:40 | 2018-06-11 11:23 | MySQL Server: Replication | Won't fix (2140 days) | S2 | 5.7.22 | Any | Any | XA transactions can lock forever if a gap lock is also taken on the slave |
90980 | 2018-05-23 2:16 | 2018-07-19 13:12 | MySQL Server: Replication | Closed (2102 days) | S3 | 5.6, 5.7, 5.7.22 | Any | Any | Duplicate error on Slave when drop temporary tables |
93089 | 2018-11-06 3:37 | 2018-11-07 7:45 | MySQL Server: Replication | Can't repeat (1991 days) | S2 | 5.7 | Any | Any | parallel workers+slave_preserve_commit_order+flushtables with read lock deadlock |
94476 | 2019-02-26 18:44 | 2019-03-14 17:05 | MySQL Server: Replication | Can't repeat (1864 days) | S2 | 5.7.21 | Any | Any | mysql semisync replication stuck with master in Waiting to finalize termination |
97531 | 2019-11-07 11:22 | 2020-02-29 17:35 | MySQL Server: Replication | Closed (1565 days) | S1 | 5.7.28, 8.0.18 | Any | Any | 5.7 replication breakage with syntax error with GRANT management |
97985 | 2019-12-13 13:59 | 2019-12-30 6:49 | MySQL Server: Replication | Duplicate (1573 days) | S2 | 5.7.x 5.5.x | Any | Any | create table like temporary table creates different charset on master and slave |
98702 | 2020-02-21 6:36 | 2020-02-21 6:54 | MySQL Server: Replication | Duplicate (1520 days) | S3 | 8.0 | Any | Any | grant grant option statements are binlogged wrongly |
102653 | 2021-02-18 19:28 | 2021-02-22 14:33 | MySQL Server: Replication | Verified (1153 days) | S4 | 8.0 | Any | Any | Feature enhancement for the GTID_NEXT variable to support '<uuid>:AUTOMATIC' |
104153 | 2021-06-29 14:34 | 2022-01-26 9:55 | MySQL Server: Replication | Closed (962 days) | S2 | 8.0.21, 8.0.25 | Any | Any | CREATE...SELECT statements break replication when ANSI mode is enabled |
491 | 2003-05-24 7:40 | 2003-07-01 5:38 | MySQL Server: Replication | Closed (7599 days) | S3 | 4.0.13 | Any (all) | Any | If INSERT SELECT fails in a MyISAM table but has changed row, nothing in binlog |
4124 | 2004-06-14 7:16 | 2004-06-21 10:28 | MySQL Server: Replication | Closed (7243 days) | S4 | All | Any (All) | Any | Replication Optimization |
26418 | 2007-02-15 18:00 | 2007-07-18 16:46 | MySQL Server: Replication | Closed (6121 days) | S2 | 5.1 | Any | Any | Slave out of sync after CREATE/DROP TEMPORARY TABLE + ROLLBACK on master |
40119 | 2008-10-17 18:29 | 2008-10-17 18:36 | MySQL Server: Replication | Not a Bug (5664 days) | S2 | 5.0.67 | Any | Any | auto-increment-increment and auto-increment-offset it does not function |
41719 | 2008-12-23 19:08 | 2011-02-16 23:43 | MySQL Server: Replication | Closed (5484 days) | S3 | 5.0, 5.1 bzr | Any | Any | delayed INSERT into timestamp col needs set time_zone for concurrent binlogging |
44976 | 2009-05-20 9:09 | 2011-02-16 23:43 | MySQL Server: Replication | Duplicate (4978 days) | S2 | 5.0.77 | Any | Any | Incorrect INSERT_ID in binary log |
45677 | 2009-06-23 13:08 | 2011-02-16 23:44 | MySQL Server: Replication | Closed (4916 days) | S2 | 5.1.35 and 5.4.0 | Any | Any | Slave stops with Duplicate entry for key PRIMARY when using trigger |
45784 | 2009-06-26 10:19 | 2016-10-16 20:45 | MySQL Server: Replication | Duplicate (5395 days) | S2 | 5.1+ | Any | Any | INSERT DELAYED in SP does not cause RBL if binlog_format=MIXED |
49020 | 2009-11-24 3:51 | 2011-02-16 23:44 | MySQL Server: Replication | Closed (5180 days) | S1 | 5.5.0 | Any | Any | Semi-sync master crashed with free_pool == NULL, assertion `free_pool_' |
49533 | 2009-12-08 13:08 | 2017-05-21 20:45 | MySQL Server: Replication | Verified (5247 days) | S3 | 5.1,mysql-5.1-rep+3,mysql-6.0-codebase-b | Any | Any | Overflow in DECIMAL, SBR out of sync |
49562 | 2009-12-09 14:30 | 2011-02-16 23:44 | MySQL Server: Replication | Closed (5008 days) | S3 | 5.1,mysql-5.1-rep+3,mysql-6.0-codebase-b | Any | Any | SBR out of sync when using numeric data types + user variable |
49567 | 2009-12-09 16:37 | 2015-01-12 15:27 | MySQL Server: Replication | Won't fix (3386 days) | S2 | 5.1+ | Any | Any | INSERT DELAYED uses global binlog_format, should use session |
52868 | 2010-04-15 21:03 | 2011-02-16 23:44 | MySQL Server: Replication | Closed (4937 days) | S2 | 5.1.37, 5.1.47,5.5.5-m3,5.6.99-m4 | Any | Any | Wrong handling of NULL value during update, replication out of sync |
53075 | 2010-04-22 18:12 | 2011-02-16 23:44 | MySQL Server: Replication | Closed (5096 days) | S3 | 5.6.99-m4 | Any | Any | SBR: Strange warning around CONNECTION_ID() |
54579 | 2010-06-17 9:45 | 2011-02-16 23:44 | MySQL Server: Replication | Closed (4905 days) | S3 | 5.5+ | Any | Any | Wrong unsafe warning for INSERT DELAYED in SBR |
57250 | 2010-10-05 14:07 | 2017-05-21 20:45 | MySQL Server: Replication | Verified (4946 days) | S2 | 5.1+ | Any | Any | mark INSERT...SELECT with autoinc column unsafe when innodb_autoinc_lock_mode=2 |
58678 | 2010-12-02 22:36 | 2023-02-12 20:45 | MySQL Server: Replication | Verified | S3 | 5.5.6, 5.5.8 | Any | Any | Wrong statement quoted in unsafety warning upon event execution |
60425 | 2011-03-11 2:58 | 2012-01-19 18:46 | MySQL Server: Replication | Not a Bug (4475 days) | S3 | mysql5.5 | Any | Any | The rpl_semi_sync_master_wait_no_slave variable is invalid |
72195 | 2014-04-01 18:50 | 2016-02-25 12:24 | MySQL Server: Replication | Verified | S3 | 5.6.17 | Any | Any | GTID restriction with non-transactional storage engines unclear |
101907 | 2020-12-08 11:39 | 2021-02-12 1:00 | MySQL Server: Replication | No Feedback (1164 days) | S2 | 5.7 | Any | Any | Replication sql_thread hung while executing DML in init state |
109857 | 2023-01-31 8:55 | 2023-02-03 4:54 | MySQL Server: Replication | Duplicate (442 days) | S2 | 5.7.38 | Any | Any | Truncate table with foreign key crash replication. |
3081 | 2004-03-06 6:48 | 2004-03-08 5:51 | MySQL Server: Replication | Closed (7348 days) | S3 | 4.0 | Any (all) | Any | if an INSERT DELAYED is killed, it is binlogged as killed but it's not needed |
4380 | 2004-07-02 14:26 | 2004-08-01 17:00 | MySQL Server: Replication | Not a Bug (7202 days) | S2 | 4.0 | Any (all) | Any | One-row INSERT/UPDATE/DELETE needn't be binlogged as 'killed' |
12092 | 2005-07-21 20:40 | 2007-11-29 11:23 | MySQL Server: Replication | Closed (5987 days) | S3 | 4.0, 4.1, 5.0 | Any (all) | Any | FOUND_ROWS() not replicated |
47323 | 2009-09-15 12:27 | 2011-02-16 23:44 | MySQL Server: Replication | Closed (5236 days) | S3 | mysql-5.1-telco-6.2 | Any | Any | mysqlbinlog --verbose displays bad output when events contain subset of columns |
48382 | 2009-10-28 16:12 | 2016-10-16 20:45 | MySQL Server: Replication | Verified | S2 | 5.1+ | Any | Any | mark reads from mysql.* and information_schema.* as unsafe |
49620 | 2009-12-11 12:21 | 2011-02-16 23:44 | MySQL Server: Replication | Can't repeat (5234 days) | S3 | 5.1.43, 5.1, next-mr bzr | Any | Any | Repl diff with concurrent transactions with trigger+savepoint+lock wait timeout |
50163 | 2010-01-07 21:15 | 2016-10-16 20:45 | MySQL Server: Replication | Duplicate (5204 days) | S2 | 5.5.1-m2 | Any | Any | Server with semi-sync crashes in ActiveTranx::clear_active_tranx_nodes |
50439 | 2010-01-19 11:16 | 2011-09-30 18:19 | MySQL Server: Replication | Closed (4586 days) | S2 | 5.1+ | Any | Any | mark INSERT...SEL...ON DUP KEY UPD,REPLACE...SEL,CREATE...[IGN|REPL] SEL unsafe |
50440 | 2010-01-19 11:26 | 2012-02-10 14:23 | MySQL Server: Replication | Closed (4453 days) | S2 | 5.1+ | Any | Any | mark [INSERT|REPLACE|CREATE]...SELECT unsafe if updated table has autoinc column |
50670 | 2010-01-27 17:55 | 2011-02-16 23:44 | MySQL Server: Replication | Closed (5008 days) | S3 | 5.5.99-m3 | Any | Any | Slave stops with error code 1644 |
51716 | 2010-03-04 11:36 | 2011-02-16 23:44 | MySQL Server: Replication | Closed (5141 days) | S3 | 5.5.99-m3 (Celosia) | Any | Any | Char column with utf16 character set gives wrong padding on slave |
53079 | 2010-04-22 19:04 | 2023-02-12 20:45 | MySQL Server: Replication | Duplicate (4917 days) | S2 | 5.1.45, 5.1, 5.6.99 | Any | Any | due to a trigger, replication fails with DUPLICATE KEY error for an UPDATE |
53259 | 2010-04-28 16:46 | 2011-02-16 23:44 | MySQL Server: Replication | Closed (4979 days) | S3 | 5.5.5-m3 | Any | Any | Unsafe statement binlogged in statement format w/MyIsam temp tables |
55387 | 2010-07-20 6:44 | 2011-02-16 23:44 | MySQL Server: Replication | Closed (5008 days) | S1 | M3 (Celosia), M4 (Dahlia) | Any | Any | binlog.binlog_tmp_table crashes the server sporadically |
55481 | 2010-07-22 13:53 | 2023-02-12 20:45 | MySQL Server: Replication | Verified (5021 days) | S2 | 5.1+ | Any | Any | Mark INSERT...SELECT into non-transactional table unsafe |
55625 | 2010-07-29 12:25 | 2011-02-16 23:44 | MySQL Server: Replication | Closed (4905 days) | S3 | 5.1.49 | Any | Any | RBR breaks on failing 'CREATE TABLE' |
58053 | 2010-11-08 14:32 | 2012-10-02 9:52 | MySQL Server: Replication | Closed (4218 days) | S3 | 5.6 | Any | Any | rpl_seconds_behind_master fails mysqltest: At line 66 |
59177 | 2010-12-27 5:10 | 2011-02-16 23:44 | MySQL Server: Replication | Closed (4831 days) | S3 | 5.1, 5.5, 5.6 | Any | Any | mysqlbinlog_row_big fails on Windows with out of memory |
59240 | 2010-12-31 0:50 | 2011-02-16 23:44 | MySQL Server: Replication | Won't fix (4831 days) | S3 | 5.6 | Any | Any | Inconsistent case of identifiers in binlog when lower_case_table_name=1 |
62829 | 2011-10-19 18:58 | 2011-10-20 13:13 | MySQL Server: Replication | Verified (4566 days) | S2 | 5.1.57 | Any | Any | INSERT/SELECT between Blackhole tables loses INSERT_ID |
70307 | 2013-09-12 0:33 | 2015-02-12 12:37 | MySQL Server: Replication | Closed (3418 days) | S2 | 5.6.13 | Any | Any | Another deadlock on FLUSH TABLES WITH READ LOCK + SHOW SLAVE STATUS |
70342 | 2013-09-13 22:18 | 2013-09-21 15:44 | MySQL Server: Replication | Verified (3864 days) | S5 | 5.6.13 | Any | Any | master_info_repository=FILE calls my_b_printf too often |
71111 | 2013-12-09 2:45 | 2014-03-25 6:54 | MySQL Server: Replication | Verified (3783 days) | S3 | 5.6.15 | Any | Any | strange replication broken on slave |
71575 | 2014-02-04 3:59 | 2015-02-25 4:54 | MySQL Server: Replication | Closed (3342 days) | S3 | Any | Any | Master logs two consecutive GTIDs causing slaves to miss the first GTID | |
72313 | 2014-04-11 4:43 | 2014-09-30 12:27 | MySQL Server: Replication | Closed (3524 days) | S1 | 5.6.16 | Any | Any | stop sql_thread, start sql_thread causes a trx to log with a different GTID |
73936 | 2014-09-16 16:50 | 2019-01-22 15:35 | MySQL Server: Replication | Closed (1915 days) | S3 | 5.6.20 | Any | Any | If the storage engine supports RBR, unsafe SQL statementes end up in binlog |
74538 | 2014-10-24 7:38 | 2014-11-03 15:15 | MySQL Server: Replication | Open | S4 | All | Any | Any | Need to change the style of SQL apply on slave mode for Update statement |
16766 | 2006-01-25 2:40 | 2012-05-18 20:19 | MySQL Server: Replication | Duplicate (6660 days) | S2 | 4.1.16, 5.0.18 | Any (all) | Any | binlog stores updates to already-dropped table |
23553 | 2006-10-23 14:32 | 2012-05-18 20:19 | MySQL Server: Replication | Verified (6381 days) | S4 | 5.0.26 | Any (Any) | Any | SBR needs to recognize appropriate cross-database DML |
24860 | 2006-12-06 18:17 | 2007-11-28 19:03 | MySQL Server: Replication | Closed (5988 days) | S3 | 5.1.12 | Any | Any | Incorrect SLAVE_TRANSACTION_RETRIES code can result in slave stuck |
25597 | 2007-01-12 21:55 | 2017-05-21 20:45 | MySQL Server: Replication | In progress (6280 days) | S3 | 5.0, 5.1 | Any (All) | Any | Extraneous error message displayed for slave SQL thread errors. |
26193 | 2007-02-08 19:26 | 2007-06-25 14:17 | MySQL Server: Replication | Can't repeat (6144 days) | S3 | 5.1-bk | Any | Any | Assertion fails in my_tz_select() |
26361 | 2007-02-14 10:08 | 2008-02-13 21:43 | MySQL Server: Replication | Closed (5911 days) | S3 | 5.1.15 | Any | Any | Valgrind complains about invalid reads inside mysql_client_binlog_statement() |
28777 | 2007-05-30 15:20 | 2011-02-16 23:43 | MySQL Server: Replication | Closed (5273 days) | S3 | 5.0.42 | Any | Any | SHOW BINLOG EVENTS does not work on relay log files |
28960 | 2007-06-07 21:05 | 2017-05-21 20:45 | MySQL Server: Replication | Duplicate (6157 days) | S3 | <= 5.0.42, 5.1.x | Any | Any | non-trans temp table changes with insert .. select not binlogged after rollback |
31168 | 2007-09-24 8:17 | 2008-03-26 18:08 | MySQL Server: Replication | Closed (5869 days) | S2 | 5.0.38, 5.0.44, 5.1 | Any | Any | @@hostname does not replicate |
31686 | 2007-10-18 7:07 | 2007-11-18 8:23 | MySQL Server: Replication | No Feedback (5998 days) | S1 | 5.0.45 | Any | Any | sql syntax error on replication slave |
31756 | 2007-10-22 15:36 | 2007-10-22 16:08 | MySQL Server: Replication | Not a Bug (6025 days) | S2 | 4.1.11 | Any | Any | binlog-ignore-db is ignored in certain cases |
31840 | 2007-10-25 10:00 | 2007-12-14 17:42 | MySQL Server: Replication | Not a Bug (5972 days) | S3 | 4.1,5.0 | Any | Any | Slave displays queries that should be filtered out in SHOW PROCESSLIST |
32046 | 2007-11-02 6:11 | 2012-05-18 20:19 | MySQL Server: Replication | Duplicate (5927 days) | S2 | 5.1.23 | Any | Any | slave fails with 'Relay log read failure: Could not parse relay log event entry' |
32200 | 2007-11-08 21:28 | 2016-10-16 20:45 | MySQL Server: Replication | Verified (6003 days) | S3 | 5.0.50,5.1.22 | Any | Any | National characters in table/view names and replication |
33029 | 2007-12-06 0:59 | 2008-04-05 7:34 | MySQL Server: Replication | Closed (5859 days) | S2 | 5.0.52 / 5.1.22 | Any | Any | 5.0 to 5.1 replication fails on dup key when inserting using a trig in SP |
34050 | 2008-01-25 4:40 | 2008-07-25 19:31 | MySQL Server: Replication | Can't repeat (5748 days) | S2 | 5.1.23 | Any | Any | I/O thread disconnects/killed when replicating under load with partition tables |
34132 | 2008-01-29 13:58 | 2012-05-18 20:19 | MySQL Server: Replication | Duplicate (5890 days) | S1 | 5.1-BK | Any | Any | Crash when replaying binary log |
35762 | 2008-04-02 5:57 | 2008-04-24 20:01 | MySQL Server: Replication | Closed (5840 days) | S2 | 5.1 BK | Any | Any | Failing CREATE-SELECT steels Table map of the following query |
36118 | 2008-04-16 8:39 | 2008-05-09 15:31 | MySQL Server: Replication | Closed (5825 days) | S2 | 5.1, 6.0 | Any | Any | RBR used for mysql database tables |
51055 | 2010-02-10 10:43 | 2011-02-16 23:44 | MySQL Server: Replication | Closed (5052 days) | S3 | mysql-5.1 | Any | Any | Replication failure on duplicate key + traditional SQL mode |
51226 | 2010-02-16 23:18 | 2011-02-16 23:44 | MySQL Server: Replication | Closed (5052 days) | S3 | 5.1.44, 6.0-backup | Any | Any | mysqlbinlog replay: ERROR 1146 when using temp tables + failing statements |
53437 | 2010-05-05 15:22 | 2011-02-16 23:44 | MySQL Server: Replication | Closed (5030 days) | S3 | Any | Any | @@session.sql_bin_log support in substatements is incorrect | |
54201 | 2010-06-03 12:18 | 2015-08-26 20:25 | MySQL Server: Replication | Closed (4376 days) | S2 | 5.1.47 | Any | Any | "SET INSERT_ID" event must be ignored if corresponding event is ignored |
54250 | 2010-06-05 3:18 | 2018-12-09 9:12 | MySQL Server: Replication | Verified (5067 days) | S4 | Any | Any | Feature request for RBR auto-fix slave functionality | |
54562 | 2010-06-16 19:18 | 2023-02-12 20:45 | MySQL Server: Replication | Verified | S3 | 5.5.3-m3, 5.5.5-m3 | Any | Any | SBR mistakes SAVEPOINT statement for accessing a transactional table |
54866 | 2010-06-28 17:53 | 2011-02-16 23:44 | MySQL Server: Replication | Closed (4978 days) | S3 | 5.1, 5.5 | Any | Any | Partially failed REVOKE not binlogged, causes inconsistency or replication abort |
55605 | 2010-07-28 14:12 | 2012-05-18 20:19 | MySQL Server: Replication | Duplicate (5013 days) | S3 | 5.1, 5.5, 5.1-wl5370 | Any | Any | Erroneous CREATE TABLE IF NOT EXISTS not written to binlog makes servers diverge |
55798 | 2010-08-06 10:17 | 2011-05-13 10:28 | MySQL Server: Replication | Closed (4726 days) | S3 | 5.1.50-bzr | Any | Any | Slave SQL retry on transaction inserts extra data into non-transaction table |
55876 | 2010-08-10 10:51 | 2011-03-22 12:45 | MySQL Server: Replication | Closed (4778 days) | S3 | 5.6.99 | Any | Any | Table map events of 'CREATE TABLE SELECT' are disorderly, it interrupts replicat |
55877 | 2010-08-10 11:20 | 2016-10-16 20:45 | MySQL Server: Replication | Duplicate (5001 days) | S3 | 5.1 only | Any | Any | Row events of 'CREATE TABLE ...SELECT' are binlogged disorderly. |
58684 | 2010-12-02 23:45 | 2023-02-12 20:45 | MySQL Server: Replication | Verified | S3 | 5.5.6, 5.5.8 | Any | Any | Unexpected unsafety warning on automatic event drop |
59204 | 2010-12-29 5:55 | 2023-02-12 20:45 | MySQL Server: Replication | No Feedback (4220 days) | S3 | 5.6 | Any (Windows) | Any | main.create with binlog-checksum enabled fail on Windows (x86_64) |
59338 | 2011-01-06 19:05 | 2011-02-16 23:44 | MySQL Server: Replication | Closed (4819 days) | S3 | 5.1.50 | Any | Any | Inconsistency in binlog for statements that don't change any rows STATEMENT SBR |
59647 | 2011-01-21 7:51 | 2011-10-17 12:05 | MySQL Server: Replication | Can't repeat (4569 days) | S2 | mysql-trunk, 5.6 | Any | Any | rpl.rpl_semi_sync[_event] crashes debug server when using release plugins |
62557 | 2011-09-27 20:52 | 2012-09-07 13:59 | MySQL Server: Replication | Closed (4243 days) | S2 | 5.1, 5.5 | Any | Any | SHOW SLAVE STATUS gives wrong output with master-master and using SET uservars |
64511 | 2012-03-01 10:47 | 2012-03-06 13:06 | MySQL Server: Replication | Closed (4428 days) | S3 | any | Any | Any | binlog_ignore_db and binlog_do_db at the same time |
65025 | 2012-04-18 19:10 | 2012-04-27 18:52 | MySQL Server: Replication | Won't fix (4376 days) | S2 | 5.1.48, 5.1.62 | Any (CentOS 5, RHEL 6, MacOSx 10.7) | Any | The maximum floating point value breaks replication. |
68609 | 2013-03-08 0:28 | 2014-10-09 16:07 | MySQL Server: Replication | Won't fix (3481 days) | S3 | 5.5.30, 5.6.10 | Any | Any | MBR: Unique key updates are not marked unsafe, replication fails |
48845 | 2009-11-17 18:21 | 2015-11-07 8:10 | MySQL Server: Row Based Replication ( RBR ) | Can't repeat (3087 days) | S2 | 5.1-rep+3 | Any | Any | Slave crash during update of char column if size of column less than on master |
49481 | 2009-12-06 2:03 | 2011-02-16 23:44 | MySQL Server: Row Based Replication ( RBR ) | Closed (5150 days) | S3 | 5.1, next-mr | Any | Any | RBR: MyISAM and bit fields may cause slave to stop on delete: cant find record |
49482 | 2009-12-06 4:05 | 2011-02-16 23:44 | MySQL Server: Row Based Replication ( RBR ) | Closed (5150 days) | S3 | 5.1, next-mr | Any | Any | RBR: Replication may break on deletes when MyISAM tables + char field are used |
50760 | 2010-01-30 19:17 | 2017-05-21 20:45 | MySQL Server: Row Based Replication ( RBR ) | Duplicate (5188 days) | S3 | 5.5.2-m2,5.5.99-m3,6.0.14-alpha | Any | Any | rbr+myisam+npk+update to/from NULL -> Slave stops with HA_ERR_END_OF_FILE |
51501 | 2010-02-25 12:44 | 2016-10-16 20:45 | MySQL Server: Row Based Replication ( RBR ) | Duplicate (4996 days) | S3 | 5.1.37, 5.1.44, 5.1.45,5.5.99-m3 | Any | Any | RBR, slave stops with HA_ERR_KEY_NOT_FOUND |
51787 | 2010-03-06 2:34 | 2011-02-16 23:44 | MySQL Server: Row Based Replication ( RBR ) | Closed (5150 days) | S2 | mysql-next-mr-bugfixing | Any | Any | Assertion `(n % 4) == 0' on slave upon INSERT into a table with UTF32 charset |
53643 | 2010-05-14 10:43 | 2011-02-16 23:44 | MySQL Server: Row Based Replication ( RBR ) | Closed (4905 days) | S3 | mysql-5.1-rpl-wl5092 | Any | Any | assert in Field_new_decimal::store_value on slave server |
53889 | 2010-05-21 15:30 | 2011-02-16 23:44 | MySQL Server: Row Based Replication ( RBR ) | Closed (4904 days) | S3 | mysql-next-mr-wl5092 | Any | Any | slaves stops with 1032; handler error HA_ERR_KEY_NOT_FOUND |
53893 | 2010-05-21 17:44 | 2011-02-16 23:44 | MySQL Server: Row Based Replication ( RBR ) | Closed (4937 days) | S3 | 5.1.48-bzr | Any | Any | RBR: nullable unique key can lead to out-of-sync slave |
67942 | 2012-12-18 21:34 | 2012-12-20 16:56 | MySQL Server: Row Based Replication ( RBR ) | Verified (4139 days) | S3 | 5.5, 5.6, 5.5.30 | Any | Any | CREATE TABLE is not written in binary log if connection is killed in the process |
110071 | 2023-02-15 6:41 | 2023-02-15 8:11 | MySQL Server: Row Based Replication ( RBR ) | Verified (430 days) | S2 | Any, 5.7, 8.0 | Any | Any | Foreign Key should not be added to Writeset-based Dependency Tracking. |
47175 | 2009-09-07 13:25 | 2011-02-16 23:44 | MySQL Server: Row Based Replication ( RBR ) | Closed (5158 days) | S3 | 5.1,5.4 | Any | Any | failing INSERT, transaction, replication out of sync |
83090 | 2016-09-22 2:13 | 2016-09-22 7:26 | MySQL Server: Row Based Replication ( RBR ) | Verified (2767 days) | S1 | 5.7.13, 5.7.15 | Any | Any | AUTO_INCREMENT not updated when using INSERT ON DUPLICATE KEY UPDATE |
106918 | 2022-04-05 17:46 | 2022-05-25 10:19 | MySQL Server: Row Based Replication ( RBR ) | Verified (696 days) | S3 | 8.0.25 | Any | Any | master and slave may get serious in-consistence after add auto-increment as pk |
37076 | 2008-05-29 19:27 | 2011-02-16 23:43 | MySQL Server: Row Based Replication ( RBR ) | Closed (5750 days) | S2 | 5.1.24 | Any | Any | TIMESTAMP values not replicated correctly for big-endian machines |
38074 | 2008-07-12 18:36 | 2023-02-12 20:45 | MySQL Server: Row Based Replication ( RBR ) | Duplicate (5353 days) | S3 | 6.0,5.4,5.0 | Any | Any | rpl_row_mysqlbinlog at line 235: could not sync with master |
38262 | 2008-07-21 14:37 | 2016-10-16 20:45 | MySQL Server: Row Based Replication ( RBR ) | Duplicate (5492 days) | S2 | 6.0 BZR | Any | Any | Replication failure when comparing integer column to string literal |
38850 | 2008-08-18 11:52 | 2023-02-12 20:45 | MySQL Server: Row Based Replication ( RBR ) | Duplicate (5496 days) | S1 | 5.1.26, 5.1, 6.0 bzr | Any | Any | wrong data on NULL definition doesn't match |
40146 | 2008-10-19 16:51 | 2009-03-24 14:42 | MySQL Server: Row Based Replication ( RBR ) | Not a Bug (5506 days) | S1 | 5.1.29, 5.1, 6.0 bzr | Any | Any | log_slave_updates uses MIXED mode for binlog regardless of binlog_format |
40184 | 2008-10-20 17:11 | 2016-10-16 20:45 | MySQL Server: Row Based Replication ( RBR ) | Duplicate (5532 days) | S2 | 5.1-bzr | Any | Any | Replication failure with RBR + Innodb + TRUNCATE |
40186 | 2008-10-20 18:41 | 2011-02-16 23:43 | MySQL Server: Row Based Replication ( RBR ) | Can't repeat (5532 days) | S2 | 5.1, 6.0-bzr | Any | Any | Replication failure on RBR + Innodb + SET AUTOCOMMIT=OFF + DROP TABLE |
40251 | 2008-10-22 13:56 | 2011-02-16 23:43 | MySQL Server: Row Based Replication ( RBR ) | Can't repeat (5479 days) | S2 | 5.1-rpl | Any | Any | Replication failure on RBR + Innodb + PARTITIONs |
42749 | 2009-02-11 6:59 | 2011-02-16 23:43 | MySQL Server: Row Based Replication ( RBR ) | Closed (5413 days) | S1 | 5.1.30, 5.1.32, 6.0.10 | Any (Windows, Linux) | Any | infinite loop writing to row based binlog - processlist shows "freeing items" |
43975 | 2009-03-31 8:07 | 2013-01-30 14:40 | MySQL Server: Row Based Replication ( RBR ) | Closed (4098 days) | S1 | 5.1.33, mysql-5.1.32-ndb-6.4.3-innodb-linux-i686 | Any | Any | Slave crashes if RBR has as destination a view rather than a table |
47067 | 2009-09-02 15:06 | 2011-07-28 9:15 | MySQL Server: Row Based Replication ( RBR ) | Can't repeat (4650 days) | S3 | 5.1, next bzr | Any | Any | DELETE logged as statement even though binlog_format=ROW |
47103 | 2009-09-03 15:57 | 2011-02-16 23:44 | MySQL Server: Row Based Replication ( RBR ) | Closed (5285 days) | S3 | 5.4 | Any | Any | RBR slave crash in table_def::type when modifying a merge table |
47200 | 2009-09-08 22:38 | 2011-03-24 15:50 | MySQL Server: Row Based Replication ( RBR ) | Closed (4776 days) | S3 | 6.0 codebase | Any | Any | RBR: Absence of PK on slave leads to slave stop. |
47557 | 2009-09-23 15:50 | 2011-02-16 23:44 | MySQL Server: Row Based Replication ( RBR ) | Closed (4832 days) | S2 | 5.1+ | Any | Any | mysqlbinlog -v should output 'limit 1' for update and delete row events |
72074 | 2014-03-19 10:35 | 2016-09-01 15:53 | MySQL Server: Row Based Replication ( RBR ) | Duplicate (3683 days) | S2 | 5.5+ | Any | Any | the third cascade slave crash when MRG_MyISAM used |
83418 | 2016-10-18 0:46 | 2016-10-18 8:51 | MySQL Server: Row Based Replication ( RBR ) | Verified (2741 days) | S5 | 5.6, 5.6.34 | Any | Any | When binlog_row_image is MINIMAL, some updates queries logs redundant columns |
88057 | 2017-10-11 12:42 | 2018-06-13 12:32 | MySQL Server: Row Based Replication ( RBR ) | Verified (2383 days) | S3 | 5.7.19, 8.0.3 | Any | Any | Intermediary slave does not log master changes with binlog_rows_query_log_events |
88223 | 2017-10-25 11:48 | 2019-01-08 16:10 | MySQL Server: Row Based Replication ( RBR ) | Verified (1929 days) | S3 | 5.7.19, 8.0.3, 5.7.24, 8.0.13 | Any | Any | Replication with no tmpdir space and InnoDB as tmp_storage_engine can break |
29020 | 2007-06-11 16:13 | 2008-03-31 19:09 | MySQL Server: Row Based Replication ( RBR ) | Closed (5864 days) | S2 | 5.1.20 | Any | Any | Event results not correctly replicated to slave in RBR |
38071 | 2008-07-12 14:37 | 2017-05-21 20:45 | MySQL Server: Row Based Replication ( RBR ) | Duplicate (5756 days) | S3 | 6.0 | Any | Any | rpl_row_basic_2myisam: results mismatch in row mode |
44752 | 2009-05-08 14:46 | 2016-10-16 20:45 | MySQL Server: Row Based Replication ( RBR ) | Duplicate (5457 days) | S1 | 5.1.34 | Any | Any | binary log corruption with RBR and trigger |
49100 | 2009-11-25 13:17 | 2011-02-16 23:44 | MySQL Server: Row Based Replication ( RBR ) | Closed (4891 days) | S3 | 6.0-codebase, mysql-5.1-rpl-wl5092 | Any | Any | RBR: Unexpected behavior when AI contains no usable data for slave columns |
54249 | 2010-06-05 2:32 | 2017-05-21 20:45 | MySQL Server: Row Based Replication ( RBR ) | Verified (5067 days) | S3 | 5.1 | Any | Any | More verbose RBR error logging |
57166 | 2010-10-01 12:58 | 2011-02-16 23:44 | MySQL Server: Row Based Replication ( RBR ) | Won't fix (4943 days) | S3 | mysql-5.1 (any) | Any | Any | Row based replication not able to convert from 'old' to 'new' DECIMAL |
97027 | 2019-09-26 10:02 | 2021-01-15 16:47 | MySQL Server: Row Based Replication ( RBR ) | Verified (1191 days) | S2 | 5.7.* | Any | x86 | Bulk insert with ON DUPLICATE KEY UPDATE breaks replicaiton |
20151 | 2006-05-30 16:43 | 2012-05-18 20:19 | MySQL Server: Row Based Replication ( RBR ) | No Feedback (5794 days) | S2 | 5.1.12pre | Any (All) | Any | Slave instance crashed during exection of SP |
13265 | 2005-09-16 13:16 | 2012-05-18 20:19 | MySQL Server: Row Based Replication ( RBR ) | Duplicate (5064 days) | S4 | Any | Any | Adding --hex-blob to mysqlbinlog | |
21479 | 2006-08-07 12:29 | 2007-06-02 17:22 | MySQL Server: Row Based Replication ( RBR ) | Not a Bug (6167 days) | S2 | 5.1 | Any (ALL) | Any | Binary log rotation cause "orphan" table map event |
31603 | 2007-10-15 11:20 | 2012-05-18 20:19 | MySQL Server: Row Based Replication ( RBR ) | No Feedback (5999 days) | S1 | mysql-5.1-wl2325-5.0-drop6 | Any | Any | Master crashes during execution of rpl_user_variables test case |
33376 | 2007-12-19 17:35 | 2016-10-16 20:45 | MySQL Server: Row Based Replication ( RBR ) | Verified (4481 days) | S2 | 5.1, 6.0 bzr | Any | Any | Write set for table not set correctly when inserting an empty set |
33670 | 2008-01-03 18:54 | 2016-10-16 20:45 | MySQL Server: Row Based Replication ( RBR ) | Duplicate (5339 days) | S3 | 6.0.4 | Any | Any | binlog_stm_ctype_cp932 test fails under Falcon |
36101 | 2008-04-15 20:21 | 2008-04-30 7:25 | MySQL Server: Row Based Replication ( RBR ) | Closed (5834 days) | S2 | 5.1.23, 6.0.4 | Any | Any | Row-based replication drops events when using multiple tables |
37884 | 2008-07-04 16:31 | 2008-08-12 17:25 | MySQL Server: Row Based Replication ( RBR ) | Closed (5730 days) | S2 | 5.1.26-rc | Any | Any | rpl_row_basic_2myisam and rpl_row_basic_3innodb fail sporadically in pushbuild |
38241 | 2008-07-19 17:24 | 2008-09-25 16:24 | MySQL Server: Row Based Replication ( RBR ) | Can't repeat (5686 days) | S1 | 5.1 | Any | Any | replication failure with a very simple mix of INSERT / UPDATE / DELETE |
39701 | 2008-09-27 16:59 | 2011-02-16 23:43 | MySQL Server: Row Based Replication ( RBR ) | Closed (5484 days) | S2 | 5.1.28, 5.1, 6.0 bzr | Any | Any | Mixed binlog format does not switch to row mode on LOAD_FILE |
44520 | 2009-04-28 14:29 | 2023-02-12 20:45 | MySQL Server: Row Based Replication ( RBR ) | Verified (5470 days) | S4 | 5.1.33, 5.1, 6.0 bzr | Any | Any | INSERT ignored silently if CREATE and INSERT are bundled in one BINLOG stmt |
47442 | 2009-09-18 14:06 | 2011-02-16 23:44 | MySQL Server: Row Based Replication ( RBR ) | Closed (4979 days) | S3 | 5.1,5.4 | Any | Any | RBR breaks on CREATE TABLE IF EXISTS <existing VIEW> AS SELECT |
69253 | 2013-05-16 7:31 | 2014-08-27 4:50 | MySQL Server: Row Based Replication ( RBR ) | Closed (3524 days) | S3 | 5.6.11 | Any | Any | mysqlbinlog prints incorrect value while using decimal |
51282 | 2010-02-18 14:02 | 2011-02-16 23:44 | MySQL Server: Row Based Replication ( RBR ) | Can't repeat (4839 days) | S1 | 5.1.34-debug, 5.1.44-debug, 5.1.45-debug, 5.5.1-m2-debug | Any | Any | insert delayed thread asserts when binlog is closed due to reset master! |
55016 | 2010-07-06 4:29 | 2011-02-16 23:44 | MySQL Server: Query Cache | Duplicate (5037 days) | S5 | Any | Any | Any | Doesn't search but insert in query cache queries leading one-line comment |
41098 | 2008-11-28 14:33 | 2011-02-16 23:43 | MySQL Server: Query Cache | Closed (5512 days) | S3 | 5.1,6.0 | Any | Any | Query Cache returns wrong result with concurrent insert |
60560 | 2011-03-21 3:49 | 2011-03-26 10:13 | MySQL Server: Query Cache | Unsupported (4774 days) | S4 | any | Any | Any | insert and query cache |
55032 | 2010-07-06 16:52 | 2017-07-07 9:45 | MySQL Server: Query Cache | Won't fix (2479 days) | S3 | All versions (5.1.x, 5.5.x) | Any | Any | Query cache sometime insert queries to cache, but doenn't find this queries. |
80026 | 2016-01-18 9:29 | 2016-05-31 14:41 | MySQL Server: Query Cache | Closed (2881 days) | S2 | 5.6.27 | Any | Any | "The statement (1) has no open cursor" pops sometimes with prepared+query_cache |
86046 | 2017-04-23 7:18 | 2017-08-03 3:05 | MySQL Server: Query Cache | Won't fix (2479 days) | S2 | 5.6, 5.6.36 | Any | Any | FROM sub query is cached by mistake |
86047 | 2017-04-23 7:58 | 2017-05-02 17:23 | MySQL Server: Query Cache | Closed (2545 days) | S2 | 5.6,5.7,8.0, 5.6.36 | Any | Any | FROM sub query with 'group by' is cached by mistake |
44359 | 2009-04-20 6:44 | 2011-02-16 23:43 | MySQL Server: Query Cache | No Feedback (5332 days) | S2 | 5.1.33 | Any | Any | Query cache gets fragmented when the query cache gets full |
50065 | 2010-01-04 22:59 | 2012-07-29 23:08 | MySQL Server: Query Cache | Closed (4283 days) | S4 | 5.0.89, 5.1.37, 5.5-mr2 | Any | Any | query cache invalidated in insert...select if no rows inserted |
46615 | 2009-08-08 9:03 | 2011-02-16 23:44 | MySQL Server: Query Cache | Closed (5055 days) | S3 | 5.1,5.4 | Any | Any | Assertion in Query_cache::invalidate in INSERT in a VIEW of a MERGE table |
73056 | 2014-06-19 21:34 | 2018-03-15 14:17 | MySQL Server: Prepared statements | Closed (2962 days) | S5 | 5.7, 5.7.8 | Any | Any | Prepared Statements ABSURDLY SLOW due to inefficient query creation for logging |
79122 | 2015-11-04 15:41 | 2016-02-04 20:18 | MySQL Server: Prepared statements | Closed (3084 days) | S3 | 5.7.10 | Any | Any | memory leaks when doing INSERT... UPDATE ... prepared statements |
102031 | 2020-12-19 5:23 | 2021-06-03 18:39 | MySQL Server: Prepared statements | Closed (1052 days) | S3 | 5.6, 5.7, 8.0 | Any | Any | reprepare at the beginning of an implicit trans will cause 1837 error |
114542 | 2024-04-03 8:36 | 2024-04-03 13:18 | MySQL Server: Prepared statements | Not a Bug (17 days) | S3 | 8.0.36-commercial | Any (8) | Any | Encoding issue when reusing Prepared Statement |
21205 | 2006-07-21 8:12 | 2011-02-16 23:43 | MySQL Server: Prepared statements | Closed (5458 days) | S3 | 5.0 | Any | Any | Different number of digits for float/doble/real in --ps-protocol |
24178 | 2006-11-10 10:40 | 2022-12-01 10:35 | MySQL Server: Prepared statements | Won't fix (506 days) | S3 | Any | Any | ctype_ucs.test fails wit --cursor-protocol | |
71526 | 2014-01-30 13:10 | 2014-03-01 1:00 | MySQL Server: Prepared statements | No Feedback (3704 days) | S3 | 5.6 | Any | Any | prepared statement fail on table_open_cache even when is autosize |
92029 | 2018-08-15 20:03 | 2018-10-10 22:01 | MySQL Server: Prepared statements | Closed (2019 days) | S3 | 5.7.23, 8.0.12, 5.6.41 | Any | Any | Diagnostic area not populated on prepare statement error 1615 |
101630 | 2020-11-16 15:58 | 2022-04-02 4:50 | MySQL Server: Prepared statements | Verified (1250 days) | S4 | 8.0.22 | Any | Any | Consider increasing placeholder limit to be > 64k |
103458 | 2021-04-23 15:22 | 2021-06-28 11:41 | MySQL Server: Prepared statements | Closed (1034 days) | S3 | 8.0 | Any | Any | PREPARE type checking error |
111921 | 2023-07-31 7:57 | 2023-08-11 12:14 | MySQL Server: Prepared statements | Verified (263 days) | S3 | 8.0 | Any | Any | Reusing prepared statement for different data types, different outcomes are obse |
112703 | 2023-10-12 12:13 | 2023-10-12 12:56 | MySQL Server: Prepared statements | Verified (191 days) | S3 | Any | Any | prepare statment has no warning comping to not prepare statment. | |
67676 | 2012-11-22 6:37 | 2014-07-14 12:23 | MySQL Server: Prepared statements | Closed (4044 days) | S2 | 5.6.7 | Any | Any | prepared statement is very slow while binlog was enabled |
94857 | 2019-04-01 20:37 | 2019-04-04 13:05 | MySQL Server: Prepared statements | Verified (1843 days) | S2 | 5.7.23 | Any | Any | execute statement doesn't return correct result |
6698 | 2004-11-18 16:52 | 2011-02-16 23:43 | MySQL Server: Prepared statements | Verified (6645 days) | S4 | 4.1.8 | Any (all) | Any | Native SQL prepared statements without using variables |
11589 | 2005-06-27 12:29 | 2007-10-25 0:02 | MySQL Server: Prepared statements | Closed (6022 days) | S3 | 4.1 | Any | Any | prepared statements - strange output, float/double/real with zerofill |
43833 | 2009-03-24 14:47 | 2011-02-16 23:43 | MySQL Server: Prepared statements | Closed (5450 days) | S2 | 5.0./5.1 | Any (Windows) | Any | Simple INSERT crashes the server |
19205 | 2006-04-19 20:44 | 2011-02-16 23:43 | MySQL Server: Prepared statements | Can't repeat (5243 days) | S3 | 4.1, 5.0-BK | Any (any) | Any | server provides different metadata in ps-protocol and non-ps-protocol mode |
23929 | 2006-11-03 10:15 | 2007-08-06 14:27 | MySQL Server: Prepared statements | Won't fix (6102 days) | S3 | 4.1.23 | Any | Any | prepared statement INSERT into char field, bound to MYSQL_TYPE_LONG = bad data |
26824 | 2007-03-03 14:21 | 2018-09-09 20:45 | MySQL Server: Prepared statements | Verified (3746 days) | S2 | 5.1.17-bk, probably 4.1 and 5.0 too | Any (All) | Any | Libmysql, possibly C/XYZ, does not handle error of COM_STMT_SEND_LONG_DATA |
28934 | 2007-06-06 20:38 | 2007-06-18 15:35 | MySQL Server: Prepared statements | Closed (6151 days) | S1 | 5.0 | Any | Any | server crash when receiving malformed com_execute packets |
36002 | 2008-04-11 18:21 | 2012-01-27 4:14 | MySQL Server: Prepared statements | Closed (4467 days) | S3 | 5.0,5.1,6.0 BK | Any | Any | Prepared statements: if a view used in a statement is replaced, bad data |
20989 | 2006-07-12 9:13 | 2006-08-04 19:35 | MySQL Server: Security: Privileges | Closed (6469 days) | S2 | 5.0.23,5.1 | Any (any) | Any | View '(null).(null)' references invalid table(s)... on SQL SECURITY INVOKER |
27515 | 2007-03-29 10:15 | 2007-04-27 4:25 | MySQL Server: Security: Privileges | Closed (6203 days) | S2 | 4.1, 5.0, 5.1 | Any (any) | Any | DROP previlege is not required anymore for RENAME TABLE |
29869 | 2007-07-18 13:41 | 2007-07-18 16:44 | MySQL Server: Security: Privileges | Not a Bug (6121 days) | S2 | 5.0.41 | Any | Any | Users with no privileges can do operations |
32826 | 2007-11-28 19:58 | 2007-11-30 15:58 | MySQL Server: Security: Privileges | Duplicate (5986 days) | S3 | 6.0.4-alpha-debug | Any | Any | Privileges: I can CREATE ... LIKE without SELECT privilege |
35005 | 2008-03-03 16:20 | 2011-02-16 23:43 | MySQL Server: Security: Privileges | Can't repeat (5034 days) | S3 | 5.1 | Any | Any | Possible security flaw around trigger privileges |
51770 | 2010-03-05 16:14 | 2011-02-16 23:44 | MySQL Server: Security: Privileges | Closed (5031 days) | S2 | 5.1+ | Any | Any | UNINSTALL PLUGIN requires no privileges |
59767 | 2011-01-27 2:01 | 2022-12-04 20:45 | MySQL Server: Security: Privileges | Verified (4832 days) | S4 | 5.0.67 and up | Any | Any | CREATE INDEX requires INDEX_ACL but ignore ALTER_ACL |
27159 | 2007-03-15 1:02 | 2011-02-16 23:43 | MySQL Server: Security: Privileges | Verified (6206 days) | S4 | any | Any (any) | Any | restrict permissions for table maintenance statements |
27480 | 2007-03-27 18:22 | 2011-05-12 17:21 | MySQL Server: Security: Privileges | Closed (4727 days) | S3 | 5.0,5.1 | Any (All) | Any | Extend CREATE TEMPORARY TABLES privilege to allow temp table operations |
41311 | 2008-12-08 21:39 | 2022-12-04 20:45 | MySQL Server: Security: Privileges | Verified (5611 days) | S3 | 5.0.67, 5.0.72, 5.1.30 | Any | Any | set timestamp allows unprivileged users to change per-session clock |
42540 | 2009-02-02 11:34 | 2011-02-16 23:43 | MySQL Server: Security: Privileges | Duplicate (5556 days) | S3 | 6.0.9 | Any | Any | SELECT,INSERT ... command denied to usual user for TEMPORARY table |
78846 | 2015-10-15 12:00 | 2017-11-12 20:45 | MySQL Server: Security: Privileges | Verified (2984 days) | S4 | 5.6 | Any | Any | TRIGGER privilege documentation is incorrect, and dangerous |
41049 | 2008-11-26 11:24 | 2011-02-16 23:43 | MySQL Server: Security: Privileges | Closed (5056 days) | S3 | 5.0.51b-log, all | Any (FreeBSD 6.0, Linux) | Any | does syntax "grant" case insensitive? |
50238 | 2010-01-11 15:08 | 2022-12-04 20:45 | MySQL Server: Security: Privileges | Verified | S3 | 5.5.1-m2 | Any | Any | 'GRANT SUPER' doesn't give 'TABLESPACE' priv in fresh 5.5, upgrade from 5.1 does |
59042 | 2010-12-19 18:44 | 2010-12-19 18:44 | MySQL Server: Security: Privileges | Open | S4 | 5.1.52 | Any | Any | INSERT ... ON DUPLICATE KEY UPDATE shouldn;t need UPDATE access to key columns |
89294 | 2018-01-18 2:37 | 2018-02-01 20:03 | MySQL Server: Security: Privileges | Open (2270 days) | S4 | 8.0 | Any | Any | Confusion around new CONNECTION ADMIN privilege(s) |
104118 | 2021-06-26 2:42 | 2022-08-23 8:45 | MySQL Server: Security: Privileges | Verified (1026 days) | S2 | 8.0.24 | Any | Any | MGR all second node abnormal stop |
104423 | 2021-07-27 9:12 | 2021-11-24 19:23 | MySQL Server: Security: Privileges | Closed (878 days) | S3 | 8.0.26 | Any | Any | SHOW CREATE DATABASE fails with a role that has global level privilege |
104732 | 2021-08-26 7:20 | 2022-02-25 9:53 | MySQL Server: Security: Privileges | Verified (968 days) | S3 | 8.0.25, 8.0.26, 8.0.28 | Any | Any | In the case of using the role, there is a problem with the acl check of the view |
112589 | 2023-10-02 15:16 | 2024-02-27 14:58 | MySQL Server: Security: Privileges | Closed (53 days) | S3 | 8.0.33, 8.0.34 | Any | Any | ER_ROW_IS_REFERENCED vs ER_ROW_IS_REFERENCED_2 breaks backwards compatibility |
69658 | 2013-07-03 9:39 | 2013-07-03 11:42 | MySQL Server: Security: Privileges | Duplicate (3944 days) | S3 | 5.1+ | Any | Any | can not drop user that created by mysql_install_db if hostname contains upper |
71279 | 2014-01-02 17:29 | 2014-01-08 9:33 | MySQL Server: Security: Privileges | Verified (3761 days) | S3 | 5.6 | Any | Any | Misleading error message for ANALYZE against PERFORMANCE_SCHEMA tables |
76390 | 2015-03-19 12:15 | 2016-10-11 8:19 | MySQL Server: Security: Privileges | Verified (3320 days) | S3 | 5.5/5.6/5.7 | Any | Any | wrong privileges in SHOW FULL COLUMNS |
80379 | 2016-02-15 22:22 | 2018-03-07 13:40 | MySQL Server: Security: Privileges | Not a Bug (2236 days) | S3 | 5.6.25, 5.7.17 | Any | Any | GRANT fails when table does not exist |
104238 | 2021-07-07 15:16 | 2021-07-08 6:23 | MySQL Server: Security: Privileges | Duplicate (1017 days) | S3 | 8.0.24 | Any | Any | Grants in prepare with 2 triggers on the same table |
52522 | 2010-04-01 11:43 | 2011-02-16 23:44 | MySQL Server: Security: Privileges | Duplicate (5084 days) | S3 | 5.5.3-m3 | Any | Any | Running mysql_upgrade loses trigger privileges |
40261 | 2008-10-22 17:55 | 2008-10-31 9:52 | MySQL Server: Security: Privileges | Not a Bug (5650 days) | S2 | 5.0.67, 4.1, 5.0, 5.1, 6.0 bzr | Any | Any | insertion of column privileges fail |
43918 | 2009-03-27 17:45 | 2016-12-05 10:53 | MySQL Server: Security: Privileges | Verified (5465 days) | S3 | 5.1.31sp1 | Any | Any | Generated version string is too long for the binlog |
17144 | 2006-02-05 21:31 | 2008-10-04 18:34 | MySQL Server: Security: Privileges | Unsupported (5677 days) | S4 | 4.0 and above | Any (*) | Any | Missing default values in user table complicate insert into user table |
40776 | 2008-11-17 9:38 | 2008-12-01 7:40 | MySQL Server: Security: Privileges | Duplicate (5619 days) | S2 | 5.0.67-community-nt | Any | Any | NO Privileges (insert,update,delete) for TEMPORARY table |
59038 | 2010-12-19 16:36 | 2011-04-21 0:43 | MySQL Server: Pluggable Authentication | Closed (4748 days) | S2 | 5.5.8 GA | Any | Any | mysql.user.authentication_string column causes configuration wizard to fail |
75893 | 2015-02-13 12:04 | 2015-04-07 21:14 | MySQL Server: Pluggable Authentication | Closed (3314 days) | S3 | 5.7.6 | Any | Any | server crash while connecting with cleartext-plugin user with blank pwd |
69928 | 2013-08-05 18:10 | 2016-02-25 12:24 | MySQL Server: Performance Schema | Closed (3844 days) | S3 | Any | Any | "statement/com" event meaning is unclear | |
74614 | 2014-10-29 9:15 | 2015-07-14 14:07 | MySQL Server: Performance Schema | Closed (3203 days) | S3 | 5.6.16, 5.6.22, 5.7.7 | Any | Any | events_statements_history has errors=0 when there are errors |
58620 | 2010-12-01 6:27 | 2011-02-16 23:44 | MySQL Server: Performance Schema | Closed (4879 days) | S3 | 5.6 | Any | Any | Performance schema failed assert, pfs_instr_class.cc, line 956 |
67736 | 2012-11-28 3:55 | 2012-11-28 18:24 | MySQL Server: Performance Schema | Closed (4161 days) | S1 | 5.6-head | Any | Any | default P_S configuration wastes CPU on a busy server |
60905 | 2011-04-18 14:31 | 2011-04-22 13:38 | MySQL Server: Performance Schema | Closed (4747 days) | S3 | 5.6.2 | Any | Any | table_io_waits_summary_by_index_usage aggregates non-insert DML wrongly |
79658 | 2015-12-16 8:49 | 2015-12-24 7:18 | MySQL Server: Performance Schema | Not a Bug (3040 days) | S3 | 5.7.10 | Any | Any | performance_schema statements by thread limited instrumentation |
98545 | 2020-02-10 23:45 | 2022-05-02 7:22 | MySQL Server: Performance Schema | Closed (719 days) | S3 | 8.0.19 | Any | Any | Perfschema tables are not collation aware |
73504 | 2014-08-08 0:51 | 2014-12-10 12:49 | MySQL Server: Performance Schema | Closed (3480 days) | S3 | 5.6 | Any | Any | performance_schema digests do not handle negative numbers well |
84609 | 2017-01-23 12:21 | 2017-06-27 7:43 | MySQL Server: Performance Schema | Verified (2644 days) | S3 | 5.7, 8.0, 5.7.17 | Any | Any | Lock information in TABLE_HANDLES misplaced |
85927 | 2017-04-13 8:24 | 2019-06-10 6:42 | MySQL Server: Performance Schema | Closed (1776 days) | S3 | 8.0.1 | Any | Any | data_locks table does not provide any hint that lock is "insert intention" one |
113659 | 2024-01-17 7:55 | 2024-01-18 11:22 | MySQL Server: Performance Schema | Verified (93 days) | S3 | 8.0 | Any | Any | explain output "Using temporary" but query dosent create temporary table |
83435 | 2016-10-19 0:40 | 2020-09-08 22:05 | MySQL Server: Partitions | Verified (2740 days) | S1 | 5.7.15/5.6 | Any | Any | ALTER TABLE is very slow when using PARTITIONED table |
105490 | 2021-11-08 11:28 | 2022-01-26 8:45 | MySQL Server: Partitions | Verified (894 days) | S3 | 8.0.27 | Any | Any | Empty loop brings loss to performance when pruning partitions for INSERT command |
113700 | 2024-01-22 4:13 | 2024-01-22 8:45 | MySQL Server: Partitions | Verified (89 days) | S2 | 8.0.22, 8.0.36 | Any | Any | REORGANIZE PARTITION causes losing data |
114396 | 2024-03-19 2:54 | 2024-03-19 5:53 | MySQL Server: Partitions | Verified (32 days) | S2 | 8.0.22, 8.0.35, 8.0.36 | Any | Any | NULL is not treated as 0 for tables partitioned by key |
104881 | 2021-09-09 8:25 | 2021-09-15 8:46 | MySQL Server: Partitions | Verified (954 days) | S3 | 8.0.26, 5.7.35 | Any | Any | partition_info::set_used_partition not raise error when finding no partition |
113369 | 2023-12-08 3:51 | 2024-01-05 13:06 | MySQL Server: Partitions | Verified (134 days) | S3 | 8.0.34, 8.0.35 | Any | Any | In the hash partition table, the query result is error. |
71095 | 2013-12-05 16:00 | 2014-08-01 15:52 | MySQL Server: Partitions | Closed (3627 days) | S3 | 5.5.33, 5.6.14, 5.6.15 | Any | Any | Wrong results with PARTITION BY LIST COLUMNS() |
71932 | 2014-03-05 9:42 | 2014-03-05 9:42 | MySQL Server: Partitions | Verified | S3 | 5.6.18, 5.7.5 | Any | Any | reorganize + multirow insert into partition table leads to wrong auto_increment |
75834 | 2015-02-10 7:46 | 2016-02-02 19:35 | MySQL Server: Partitions | Closed (3266 days) | S2 | 5.7.6-m16 | Any | Any | rqg_alter_online_part run into assertion: node->entry == null (row0ins.cc) |
78638 | 2015-09-30 8:03 | 2016-06-18 21:28 | MySQL Server: Partitions | Closed (3071 days) | S3 | 8.0.0-m17 | Any | Any | parts.partition_alter2_1_1_innodb run into assertion |
84362 | 2016-12-28 17:11 | 2016-12-28 17:52 | MySQL Server: Partitions | Verified (2670 days) | S3 | 5.6, 5.7,8.0 | Any | Any | PARTITION BY LIST COLUMNS allows unsupported data types |
26827 | 2007-03-03 20:37 | 2007-07-07 18:50 | MySQL Server: Partitions | Closed (6132 days) | S2 | 5.1, 5.2 | Any (SUSE 10.0 / 64-bit, suse9.3 x86) | Any | table->read_set is set incorrectly, causing update of a different column |
32115 | 2007-11-05 14:59 | 2011-02-16 23:43 | MySQL Server: Partitions | Closed (5158 days) | S2 | 5.5.0 | Any | Any | Bad use of Name_resolution_context from current LEX in partitioning |
33691 | 2008-01-04 13:41 | 2008-03-05 14:49 | MySQL Server: Partitions | Closed (5890 days) | S3 | 6.0.4-p2 | Any | Any | Falcon crash on partition manipulations |
34366 | 2008-02-07 0:02 | 2015-08-23 20:45 | MySQL Server: Partitions | Duplicate (5913 days) | S3 | 5.1.22 | Any | Any | Insert into a partitioned MyISAM table gives ER_AUTOINC_READ_FAILED error |
30648 | 2007-08-27 17:47 | 2007-08-31 13:48 | MySQL Server: Partitions | Closed (6077 days) | S3 | 5.1 | Any | Any | Partition handler may not initialize variable used w/ autoincrement |
33479 | 2007-12-22 12:51 | 2008-05-24 17:05 | MySQL Server: Partitions | Closed (5810 days) | S3 | 5.1+ | Any | Any | Insert on a partitioned auto_increment table gives ER_AUTOINC_READ_FAILED |
34267 | 2008-02-04 3:26 | 2020-11-22 20:45 | MySQL Server: Partitions | Duplicate (5917 days) | S2 | 5.1.23 | Any | Any | Server crash when droping a partition on a table with a trigger |
43477 | 2009-03-07 20:09 | 2015-08-23 20:45 | MySQL Server: Partitions | Duplicate (4946 days) | S2 | 5.1.29, 5.1.32, 5.1.33 | Any | Any | Server hangs with table general log, statement binlog format and partitions |
45840 | 2009-06-30 6:18 | 2011-02-16 23:44 | MySQL Server: Partitions | Closed (5236 days) | S3 | 5.1.30, 5.1.37 | Any | Any | read_buffer_size allocated for each partition when "insert into.. select * from" |
32566 | 2007-11-21 11:32 | 2012-05-18 20:19 | MySQL Server: Partitions | Duplicate (5987 days) | S3 | 5.1 | Any | Any | Range partitioning: Insert of maximum value should fail LESS THAN (numeric max) |
47253 | 2009-09-10 14:30 | 2011-02-16 23:44 | MySQL Server: Partitions | Duplicate (5332 days) | S3 | Any | Any | Assert in ha_partition::end_bulk_insert | |
50392 | 2010-01-17 0:28 | 2011-02-16 23:44 | MySQL Server: Partitions | Closed (5052 days) | S3 | 5.1+ | Any | Any | insert_id is not reset for partitioned tables auto_increment on duplicate entry |
52815 | 2010-04-14 10:29 | 2011-02-16 23:44 | MySQL Server: Partitions | Closed (4884 days) | S3 | 5.5+ | Any | Any | LIST COLUMNS doesn't insert rows in correct partition if muliple columns used |
53806 | 2010-05-19 14:00 | 2011-02-16 23:44 | MySQL Server: Partitions | Closed (4945 days) | S3 | 5.1.46, mysql-next-mr | Any | Any | Wrong estimates for range query in partitioned MyISAM table |
67982 | 2012-12-27 23:45 | 2013-11-01 9:47 | MySQL Server: Partitions | Closed (3823 days) | S3 | 5.5.28, 5.6.9 | Any | Any | Got error 124 from storage engine on DELETE from a partitioned table |
48166 | 2009-10-19 18:28 | 2011-02-16 23:44 | MySQL Server: Partitions | Won't fix (5210 days) | S3 | 5.1+ | Any | Any | Partitions: error message refers to value after function completion |
50393 | 2010-01-17 0:46 | 2011-02-16 23:44 | MySQL Server: Partitions | Verified (5207 days) | S3 | 5.1+ | Any | Any | insert DELAYED disabled for partitioned myisam |
52455 | 2010-03-30 1:54 | 2011-02-16 23:44 | MySQL Server: Partitions | Closed (4937 days) | S3 | 5.1 | Any | Any | Subpar INSERT ON DUPLICATE KEY UPDATE performance with many partitions |
75400 | 2015-01-03 15:06 | 2015-01-03 15:06 | MySQL Server: Partitions | Open | S4 | Any | Any | Add support in partitions of mix InnoDB and Memory engines | |
79372 | 2015-11-21 11:40 | 2015-11-21 13:33 | MySQL Server: Partitions | Verified (3073 days) | S2 | 5.5, 5.5.48 | Any | Any | INSERT ... SELECT does not preserve rows order in InnoDB partitioned tables |
46639 | 2009-08-10 22:51 | 2011-02-16 23:44 | MySQL Server: Partitions | Closed (5330 days) | S1 | 5.1.36 | Any | Any | 1030 (HY000): Got error 124 from storage engine on INSERT ... SELECT ... |
46911 | 2009-08-25 6:56 | 2011-02-16 23:44 | MySQL Server: Partitions | Duplicate (5338 days) | S2 | 5.1.37 | Any | Any | Inconsistent SHOW CREATE TABLE result before/after FLUSH STATUS w/ partitioning |
20340 | 2006-06-08 12:58 | 2006-07-26 0:44 | MySQL Server: Partitions | Closed (6478 days) | S3 | 5.1.12-BK, 5.1.11 | Any (all) | Any | Paritioning does not obey to column type |
104576 | 2021-08-10 4:18 | 2023-12-20 6:36 | MySQL Server: Partitions | Closed (925 days) | S5 | 8.0.26, 5.7.35 | Any | Any | partition table access second index lead to cpu high load |
47753 | 2009-09-30 20:24 | 2022-12-04 20:45 | MySQL Server: Partitions | Duplicate (5295 days) | S3 | 5.5 WL#3352 | Any | Any | Partition by LIST COLUMN_LIST appears to require an order for value list items |
38120 | 2008-07-15 7:28 | 2008-10-09 18:57 | MySQL Server: Partitions | Closed (5672 days) | S3 | 6.0-BK, 5.1 | Any | Any | main.partition fails sporadically |
47752 | 2009-09-30 17:56 | 2011-02-16 23:44 | MySQL Server: Partitions | Closed (5273 days) | S3 | 5.5 WL#3352 | Any | Any | Partition by LIST COLUMN_LIST only recognizing last defined partition |
71947 | 2014-03-05 18:55 | 2014-03-06 5:18 | MySQL Server: Partitions | Verified (3698 days) | S3 | 5.6, 5.7 | Any | Any | Unexpected change in error code on INSERT .. PARTITION causes replication abort |
113614 | 2024-01-11 8:20 | 2024-01-11 9:24 | MySQL Server: Partitions | Won't fix (100 days) | S3 | mysql-5.6.51,mysql-5.7.44 | Any | Any | The partiton table's AUTOINC back to older after change partitions ddl executed. |
37252 | 2008-06-06 19:56 | 2015-02-06 19:01 | MySQL Server: Partitions | Closed (4329 days) | S3 | 5.1, 6.0 | Any | Any | Partitioning performance drops drastically with hundreds of partitions |
38797 | 2008-08-14 13:30 | 2015-08-23 20:45 | MySQL Server: Partitions | Duplicate (5721 days) | S1 | 5.1-bzr | Any (Linux) | Any | Assertion (inited==RND) failed in handler::ha_rnd_end |
40176 | 2008-10-20 13:43 | 2008-11-10 15:40 | MySQL Server: Partitions | Closed (5640 days) | S3 | 5.1.29/5.1.30 | Any | Any | Combination of event, trigger and partitioning breaks auto increment |
40972 | 2008-11-24 10:54 | 2011-02-16 23:43 | MySQL Server: Partitions | Closed (5569 days) | S1 | 5.1+ | Any | Any | Partition pruning can lead to crash for bad dates |
46483 | 2009-07-30 18:53 | 2011-02-16 23:44 | MySQL Server: Partitions | Closed (5236 days) | S2 | 5.1.36 | Any | Any | drop table of partitioned table may leave extraneous file |
46936 | 2009-08-26 10:08 | 2015-08-23 20:45 | MySQL Server: Partitions | Duplicate (5342 days) | S3 | 5.1, next bzr | Any | Any | Duplicate entry for key 'PRIMARY' if used partition and innodb |
47310 | 2009-09-14 12:53 | 2011-02-16 23:44 | MySQL Server: Partitions | Duplicate (5332 days) | S4 | 5.1.37 | Any | Any | Feature request: allow partitioning for any function which returns an integer. |
42877 | 2009-02-16 12:08 | 2011-02-16 23:43 | MySQL Server: Parser | No Feedback (5514 days) | S1 | 5 | Any | Any | Back slash inserting in Last in data |
57821 | 2010-10-28 18:12 | 2018-09-09 20:45 | MySQL Server: Parser | Duplicate (3897 days) | S3 | 5.1+ | Any | Any | select columnname,* from tablename failes |
58131 | 2010-11-11 3:06 | 2010-11-17 0:46 | MySQL Server: Parser | Not a Bug (4903 days) | S3 | 5.1.51 | Any | Any | Inconsistent handling of out of range values |
65497 | 2012-06-02 21:51 | 2012-06-03 7:45 | MySQL Server: Parser | Not a Bug (4339 days) | S3 | 5.5 | Any | Any | sql_no_cache processed as field name in dependent subquery on mysql 5.5 |
76058 | 2015-02-26 9:45 | 2015-04-07 22:08 | MySQL Server: Parser | Closed (3312 days) | S2 | 5.7.6 | Any | Any | refactored parser code may ignore OOM errors and dereference NULL pointers |
78404 | 2015-09-11 9:11 | 2015-09-11 9:41 | MySQL Server: Parser | Verified (3144 days) | S3 | 5.6.22, 5.6.26 | Any | Any | subquery + "select * from...order by 2" (2 cols) fails with unknown column '2' |
8017 | 2005-01-19 18:27 | 2011-02-16 23:43 | MySQL Server: Parser | Closed (5554 days) | S4 | Any | Any | test [sql statment] - will predict if i'll do this will i get an any error | |
95095 | 2019-04-24 1:07 | 2019-04-24 5:54 | MySQL Server: Parser | Not a Bug (1823 days) | S3 | Any | Any | Issue with SQL parser | |
99343 | 2020-04-24 6:03 | 2021-05-31 8:36 | MySQL Server: Parser | Verified (1457 days) | S2 | 8.0.19, 5.7.29, 8.0.25 | Any | Any | Selecting with generated column gets the wrong result |
104211 | 2021-07-05 20:54 | 2021-07-08 11:35 | MySQL Server: Parser | Not a Bug (1018 days) | S3 | 8.0.x | Any | Any | ON DUPLICATE KEY UPDATE and table alias for new VALUES function replacement |
45361 | 2009-06-07 21:58 | 2009-06-11 19:19 | MySQL Server: Parser | Not a Bug (5427 days) | S3 | any | Any | Any | parser behaves too primitive here! |
80559 | 2016-02-29 14:32 | 2016-02-29 15:17 | MySQL Server: Parser | Verified (2973 days) | S3 | 5.7.11 | Any | Any | EXPLAIN CREATE TABLE .. AS SELECT .. does not work |
50755 | 2010-01-30 12:21 | 2011-02-16 23:44 | MySQL Server: Parser | Closed (4937 days) | S3 | 5.1+ | Any | Any | Crash if stored routine def contains version comments |
56935 | 2010-09-22 14:50 | 2010-09-23 5:24 | MySQL Server: Parser | Not a Bug (4958 days) | S3 | 5.021 | Any | Any | insert ... on duplicate key update .. update content may not contain ";" |
71039 | 2013-11-29 14:20 | 2016-08-11 12:25 | MySQL Server: Parser | Verified | S3 | 5.7, 5.7.14 | Any | Any | non-standard usage of table alias allowed in SELECT but not in CREATE VIEW |
38857 | 2008-08-18 13:45 | 2011-02-16 23:43 | MySQL Server: Parser | Duplicate (5723 days) | S4 | Any | Any | SQL addition - ORLIMIT | |
38858 | 2008-08-18 13:56 | 2022-12-04 20:45 | MySQL Server: Parser | Verified (5723 days) | S4 | Any | Any | ORDERGROUP BY construct | |
38859 | 2008-08-18 14:17 | 2022-12-04 20:45 | MySQL Server: Parser | Verified (5723 days) | S4 | 6.0 | Any | Any | limiting a group - LIMITGROUP |
62696 | 2011-10-12 9:36 | 2011-11-09 15:38 | MySQL Server: Parser | Verified (4574 days) | S3 | 5.5.17, 5.6.4-m5 | Any | Any | Using a numeric operator on a TIME column should return an error or warning |
69515 | 2013-06-19 14:55 | 2013-06-19 15:11 | MySQL Server: Options | Verified (3958 days) | S3 | 5.1, 5.5, 5.6, 5.7 | Any | Any | group_concat_max_len >= 4Gb does not work |
43835 | 2009-03-24 15:27 | 2011-02-16 23:43 | MySQL Server: Options | Closed (5454 days) | S3 | 5.1.30 | Any | Any | SHOW VARIABLES does not include 0 for slave_skip_errors |
55180 | 2010-07-12 16:27 | 2011-02-16 23:44 | MySQL Server: Options | Verified | S4 | any | Any | Any | make the Threads_running server status variable more meaningful |
85017 | 2017-02-16 10:22 | 2017-02-16 12:14 | MySQL Server: Options | Verified (2620 days) | S3 | 5.7 | Any | Any | Shouldn't'delayed_insert_timeout' variable be removed? |
40693 | 2008-11-13 10:15 | 2008-11-13 15:39 | MySQL Server: Options | Not a Bug (5637 days) | S5 | 5 | Any | Any | some status variables being reset |
74228 | 2014-10-05 13:22 | 2014-10-07 11:13 | MySQL Server: Options | Verified (3484 days) | S3 | 5.5, 5.6 | Any | Any | Description of autoincrement behavior if offset > increment needs clarification |
76425 | 2015-03-21 6:56 | 2015-05-31 11:13 | MySQL Server: Options | Closed (3266 days) | S1 | 5.7.5-m16, 5.7.6 | Any | Any | bool Ha_trx_info::is_trx_read_write() const: Assertion `is_started()' failed. |
43930 | 2009-03-28 10:18 | 2011-02-16 23:43 | MySQL Server: Options | Verified | S4 | 5.0.x | Any | Any | Add sql_mode that throws warnings when rounding non-integer numbers to integers |
66188 | 2012-08-03 20:02 | 2012-10-06 1:00 | MySQL Server: Options | No Feedback (4215 days) | S3 | 5.5.23, 5.5.27 | Any | Any | Cannot use CREATE TEMPORARY...INSERT with InnoDB when read_only is set |
49349 | 2009-12-02 13:29 | 2018-11-04 20:45 | MySQL Server: Optimizer | Duplicate (4135 days) | S3 | 6.0 | Any | Any | Wrong cost calculation for duplicate weed-out |
50996 | 2010-02-08 14:32 | 2011-02-16 23:44 | MySQL Server: Optimizer | Closed (4985 days) | S3 | Any | Any | Wrong result for second call of prepared statement with view in subselect | |
51016 | 2010-02-09 8:57 | 2020-05-03 20:45 | MySQL Server: Optimizer | Duplicate (5182 days) | S3 | 6.0-codebase-bugfixing | Any | Any | Batched key access gives wrong results for T0 semijoin (T1 join T2) |
84587 | 2017-01-20 13:43 | 2017-06-01 16:21 | MySQL Server: Optimizer | Closed (2524 days) | S2 | 8.0 | Any | Any | WL#9236: including or excluding columns from SELECT list makes results wrong |
102291 | 2021-01-19 9:17 | 2021-01-19 9:58 | MySQL Server: Optimizer | Verified (1187 days) | S1 | 8.0, 8.0.22, 8.0.23 | Any | Any | Subquery produces wrong result when set big_tables = 1 |
106312 | 2022-01-27 18:14 | 2022-02-09 13:20 | MySQL Server: Optimizer | Verified (813 days) | S3 | 5.7 | Any (Ubuntu 20.04.3 LTS) | Any (Intel(R) Core(TM) i7-10700 CPU @ 2.90GHz) | Huge value in GROUP BY clause cause unexpected output |
110882 | 2023-05-02 7:26 | 2023-05-03 12:51 | MySQL Server: Optimizer | Not a Bug (353 days) | S3 | 8.0 | Any | Any (x86_64) | BETWEEN query with index wrong result |
112251 | 2023-09-04 13:19 | 2023-09-05 12:11 | MySQL Server: Optimizer | Can't repeat (228 days) | S3 | 8.1.0 | Any | Any | Uncertain Result |
113211 | 2023-11-24 12:14 | 2023-11-24 12:34 | MySQL Server: Optimizer | Verified (148 days) | S2 | 8.0.35, 8.1.0, 8.2.0 | Any | Any | The latest version 8.0 returns abnormal results for complex queries |
113783 | 2024-01-28 12:50 | 2024-01-30 10:58 | MySQL Server: Optimizer | Not a Bug (81 days) | S4 | 8.0 | Any | Any | only_full_group_by option does not take effect |
6164 | 2004-10-19 20:10 | 2011-02-16 23:43 | MySQL Server: Optimizer | Verified (7122 days) | S4 | 4.0.22 4.1.7 | Any | Any | INSERT ... SELECT ... LIMIT creating too-large temporary tables |
8893 | 2005-03-02 14:51 | 2005-03-09 3:41 | MySQL Server: Optimizer | Closed (6982 days) | S2 | 4.1.10 | Any (all) | Any | Using "SELECT MAX(ID)" with Multiple-Column Indexes |
9689 | 2005-04-06 17:37 | 2005-04-22 21:10 | MySQL Server: Optimizer | Not a Bug (6938 days) | S3 | 4.1.11 | Any (*) | Any | wrong result for subselect in on duplicate key update (query cache) |
85933 | 2017-04-13 13:25 | 2023-11-02 6:30 | MySQL Server: Optimizer | Closed (2397 days) | S5 | 8.0.1-dmr | Any | Any | Performance regression with Prepared Statements |
86574 | 2017-06-03 16:16 | 2017-06-03 19:36 | MySQL Server: Optimizer | Verified (2513 days) | S3 | 5.6 | Any | Any | Confusing EXPLAIN output for INSERT Queries |
86860 | 2017-06-29 5:31 | 2017-06-29 5:45 | MySQL Server: Optimizer | Duplicate (2487 days) | S3 | 5.7.18 | Any | Any | EXPLAIN of non-SELECT statement fails on SLAVE |
89389 | 2018-01-24 19:10 | 2018-01-26 7:26 | MySQL Server: Optimizer | Not a Bug (2276 days) | S2 | 5.5/5.6/5.7/8.0 | Any | Any | wrong result: select (select aggregate(t1.c) from t2) from t1 |
94721 | 2019-03-20 14:55 | 2019-05-20 16:03 | MySQL Server: Optimizer | Closed (1827 days) | S3 | 8.0.17 | Any | Any | Wrong result with correlated LATERAL JOIN |
95876 | 2019-06-19 11:38 | 2023-03-08 20:56 | MySQL Server: Optimizer | Closed (1766 days) | S2 | 8.0.16, 5.7.26, 5.6.44 | Any | Any | Wrong result for query with outer join and IS NOT TRUE predicate in where clause |
100393 | 2020-07-31 4:10 | 2020-07-31 8:29 | MySQL Server: Optimizer | Verified (1359 days) | S7 | 8.0.19, 5.7.31, 8.0.21 | Any | Any | The division precision is inconsistent |
100777 | 2020-09-09 8:21 | 2020-09-09 9:51 | MySQL Server: Optimizer | Verified (1319 days) | S3 | 8.0.21, 5.7.31 | Any | Any | Small negative float equals to 0 when index is used |
100806 | 2020-09-11 5:36 | 2020-09-11 7:44 | MySQL Server: Optimizer | Verified (1317 days) | S3 | 8.0.21, 5.7.31 | Any | Any | Index changes behavior of BETWEEN |
102025 | 2020-12-18 7:33 | 2021-10-25 23:38 | MySQL Server: Optimizer | Closed (908 days) | S2 | 8.0.22, 5.7.32 | Any | Any | Wrong result when use "select all" |
102584 | 2021-02-12 15:19 | 2021-02-16 12:46 | MySQL Server: Optimizer | Not a Bug (1160 days) | S3 | 5.7.31 | Any (CentOS Linux release 7.6.1810 (Core)) | Any | join on result of function |
102903 | 2021-03-10 13:50 | 2021-08-07 18:12 | MySQL Server: Optimizer | Verified (987 days) | S4 | MySQL 8.0.22 | Any | Any | CTAS or ITAS - max_execution_time |
104387 | 2021-07-22 21:24 | 2021-08-20 11:14 | MySQL Server: Optimizer | Closed (976 days) | S2 | 8.0.22, 8.0.23, 8.0.24, 8.0.25, 8.0.26 | Any | Any | CHARACTER_SET_MISMATCH issue with regex comparisons |
105692 | 2021-11-24 10:20 | 2022-01-06 14:13 | MySQL Server: Optimizer | Closed (878 days) | S3 | 8.0.29 | Any | Any | Incorrect result with aggregation by temporary table |
106208 | 2022-01-19 7:37 | 2022-01-21 9:27 | MySQL Server: Optimizer | Verified (822 days) | S3 | 8.0.27, 8.0.28, 5.7.37 | Any | Any | IF function with DECIMAL get different precision result |
106328 | 2022-01-29 0:40 | 2022-02-09 1:33 | MySQL Server: Optimizer | Duplicate (801 days) | S3 | 8.0.28, 5.7.37 | Any | Any | Huge value in ORDER BY clause cause unexpected output |
107661 | 2022-06-26 5:08 | 2022-06-26 15:39 | MySQL Server: Optimizer | Verified (664 days) | S6 | 8.0.29 | Any | Any | Assertion `!sl->order_list.first' failed in MySQL 8.0.29 |
107663 | 2022-06-26 14:56 | 2023-06-27 12:28 | MySQL Server: Optimizer | Verified (664 days) | S6 | 8.0.29 | Any | Any | Assertion `keyparts > 0' failed in MySQL 8.0.29 |
109311 | 2022-12-08 3:40 | 2022-12-09 3:36 | MySQL Server: Optimizer | Verified (498 days) | S1 | 8.0.22 8.0.30, 8.0.31 | Any | Any | Wrong result |
109601 | 2023-01-12 9:00 | 2023-01-12 9:38 | MySQL Server: Optimizer | Verified (464 days) | S3 | 8.0 | Any | Any | Apply partition pruning if all insert rows have non-null values on autoinc field |
109897 | 2023-02-02 10:08 | 2023-02-02 11:32 | MySQL Server: Optimizer | Verified (443 days) | S3 | 8.0.31 | Any | Any | Field_double::val_str causes string truncation |
110244 | 2023-03-01 3:46 | 2023-03-01 6:30 | MySQL Server: Optimizer | Verified (416 days) | S2 | 8.0.32 | Any | Any | Nesting queries in a projection results in different output |
111699 | 2023-07-09 3:46 | 2023-07-10 5:51 | MySQL Server: Optimizer | Verified (285 days) | S3 | 8.0.28, 8.0.33 | Any | Any | Incorrect results |
112264 | 2023-09-05 11:47 | 2023-09-05 12:15 | MySQL Server: Optimizer | Verified (228 days) | S2 | 8.1.0 | Any | Any | Unexpected Result by block_nested_loop |
112269 | 2023-09-06 2:51 | 2023-09-06 4:52 | MySQL Server: Optimizer | Verified (227 days) | S2 | 8.1.0, 8.0.34 | Any | Any | Unexpected Results by the hint JOIN_ORDER |
112306 | 2023-09-11 1:49 | 2023-09-12 11:26 | MySQL Server: Optimizer | Duplicate (221 days) | S3 | 8.1.0, 8.0.34 | Any | Any | Unexpected Result by JOIN_SUFFIX |
112354 | 2023-09-15 7:52 | 2023-10-20 1:00 | MySQL Server: Optimizer | No Feedback (184 days) | S3 | 8.0.28 | Any | Any | Incorrect result |
113647 | 2024-01-16 8:55 | 2024-03-07 20:37 | MySQL Server: Optimizer | Closed (44 days) | S5 | 8.0.35,8.2.0 | Any | Any | identical tables are checked in HashJoin because of no STOP_AT_MATERIALIZATION |
9728 | 2005-04-07 16:52 | 2005-06-27 9:54 | MySQL Server: Optimizer | Closed (6872 days) | S3 | 4.1.11 | Any (*) | Any | decreased functionality in "on duplicate key update" |
70684 | 2013-10-22 8:13 | 2013-10-22 11:35 | MySQL Server: Optimizer | Verified (3833 days) | S3 | 5.5.33, 5.6.14 | Any | Any | HAVING referring to subquery results in WARNING 1292 |
72512 | 2014-05-02 8:57 | 2014-06-04 16:45 | MySQL Server: Optimizer | Closed (3608 days) | S3 | 5.5, 5.6 | Any | Any | Non-aggregated query with set function in ORDER BY should be rejected |
72690 | 2014-05-20 9:13 | 2014-07-15 8:59 | MySQL Server: Optimizer | Not a Bug (3609 days) | S2 | 5.6.17 | Any | Any | A 5.6's optimizer bug which is releated to 'or' operator's number |
72858 | 2014-06-03 22:18 | 2016-02-26 13:49 | MySQL Server: Optimizer | Closed (2976 days) | S2 | 5.6.17, 5.6.20, 5.7.5 | Any | Any | EXPLAIN .. SELECT .. FOR UPDATE takes locks |
73927 | 2014-09-16 10:12 | 2015-03-24 21:34 | MySQL Server: Optimizer | Closed (3358 days) | S3 | 5.7 | Any | Any | SELECT DISTINCT SUM() RETURNS DUPLICATE ROWS |
73932 | 2014-09-16 12:49 | 2015-03-24 21:55 | MySQL Server: Optimizer | Closed (3358 days) | S3 | 5.7 | Any | Any | multi-update crash with long primary key |
74806 | 2014-11-12 4:23 | 2014-11-12 15:34 | MySQL Server: Optimizer | Closed (3447 days) | S2 | 5.6.12 | Any | Any | COUNT(DISTINCT ... ) wrong with "Using index" |
74962 | 2014-11-21 13:24 | 2014-11-21 14:20 | MySQL Server: Optimizer | Verified (3438 days) | S3 | 5.5/5.6 | Any | Any | Matching in char field type is not correct |
75424 | 2015-01-06 14:23 | 2015-04-07 13:44 | MySQL Server: Optimizer | Closed (3301 days) | S3 | 5.7 | Any | Any | EXPLAIN for insert into a view shows wrong table for insertion |
75447 | 2015-01-08 12:59 | 2015-01-08 13:27 | MySQL Server: Optimizer | Verified (3390 days) | S2 | 5.6, 5.6.24, 5.7.6 | Any | Any | INSERT into a view sometimes ignores default values |
76002 | 2015-02-23 8:14 | 2015-02-25 1:35 | MySQL Server: Optimizer | Not a Bug (3342 days) | S3 | 5.6 | Any | Any | different plan when executing query using procedure |
76501 | 2015-03-27 6:50 | 2015-03-27 15:11 | MySQL Server: Optimizer | Verified (3312 days) | S3 | 5.6.22 | Any | Any | "select + distinct + group by " works incorrectly |
77116 | 2015-05-21 11:43 | 2015-05-22 5:40 | MySQL Server: Optimizer | Closed (3256 days) | S3 | 5.6.*, 5.6.24 | Any | Any | Invalid query result |
77782 | 2015-07-20 6:32 | 2015-08-27 4:19 | MySQL Server: Optimizer | Closed (3190 days) | S2 | 5.7.8 | Any | Any | valgrind error (conditional jump) when insert rows into a partitioned table |
77947 | 2015-08-05 12:30 | 2016-02-19 16:37 | MySQL Server: Optimizer | Closed (2983 days) | S2 | 5.7.6 | Any | Any | internal_tmp_disk_storage_engine=innodb breaks SQL optimizer compatibility |
78025 | 2015-08-11 17:43 | 2015-08-11 21:31 | MySQL Server: Optimizer | Verified (3175 days) | S3 | 5.5, 5.6, 5.7 | Any | Any | Special IS NULL logic for 0000-00-00 does not work with merge views and SQ |
78665 | 2015-10-01 12:08 | 2015-10-13 13:58 | MySQL Server: Optimizer | Closed (3112 days) | S2 | 5.7.8 | Any | Any | GCOLS: GCOL VALUE CHANGES WHEN SESSION CHANGES SQL_MODE |
80148 | 2016-01-26 7:41 | 2016-05-31 15:59 | MySQL Server: Optimizer | Closed (2881 days) | S3 | 5.7.8 | Any | Any | found_rows() is not working as expected without sql_calc_found_rows |
81235 | 2016-04-29 11:43 | 2016-05-05 14:05 | MySQL Server: Optimizer | Duplicate (2907 days) | S3 | 5.6 | Any | Any | Incorrect sorting temporary results after Where |
83148 | 2016-09-26 8:57 | 2023-04-16 19:29 | MySQL Server: Optimizer | Closed (2685 days) | S3 | 5.5 | Any | Any | IF and friends gives wrong type for signed and unsigned integer |
84537 | 2017-01-17 14:11 | 2017-10-24 14:31 | MySQL Server: Optimizer | Closed (2419 days) | S3 | 8.0.1 | Any | Any | GROUP BY DESC gives wrong result when groups on DECIMAL and sees a NULL |
85945 | 2017-04-14 8:01 | 2017-04-17 8:08 | MySQL Server: Optimizer | Verified (2560 days) | S3 | 5.7.13, 5.7.18 | Any | Any | SQL optimizer fail to check IS NULL condition |
86215 | 2017-05-08 13:35 | 2017-07-11 22:44 | MySQL Server: Optimizer | Analyzing (2475 days) | S5 | 8.0.1 | Any | Any | MySQL is much slower in 5.7 vs 5.6 |
96647 | 2019-08-26 6:21 | 2019-08-26 7:38 | MySQL Server: Optimizer | Verified (1699 days) | S3 | 5.7.22, 5.7.27, 8.0.17 | Any | Any | Query Rewrite plugin database_pattern column length is too shot |
98592 | 2020-02-14 3:37 | 2020-04-03 12:46 | MySQL Server: Optimizer | Closed (1478 days) | S2 | 5.7,8.0, 5.6.47, 5.7.29, 8.0.19 | Any | Any | distinct(hex(weight_string(ch))) cut result off |
99933 | 2020-06-19 1:30 | 2020-11-11 8:38 | MySQL Server: Optimizer | Closed (1256 days) | S3 | 8.0 | Any | Any | In-memory hash join will only use two-thirds of join buffer |
99934 | 2020-06-19 2:32 | 2020-09-21 14:39 | MySQL Server: Optimizer | Verified (1401 days) | S5 | 8.0.20 | Any | Any | Hash join adds columns to the hash table that is not needed. |
100807 | 2020-09-11 5:39 | 2020-09-11 7:50 | MySQL Server: Optimizer | Verified (1317 days) | S3 | 8.0.21, 5.7.31 | Any | Any | Explicit IS TRUE changes the result for BETWEEN when index is used |
101059 | 2020-10-06 2:47 | 2020-10-06 5:26 | MySQL Server: Optimizer | Verified (1292 days) | S3 | 8.0.19, 8.0.21, 5.7.31, 5.6.49 | Any | x86 | Query result inconsistent for the year type in NOT IN expression |
101687 | 2020-11-20 0:16 | 2020-11-20 5:10 | MySQL Server: Optimizer | Verified (1247 days) | S4 | 8.0.22 | Any | Any | Inverse unix_timestamp(TIMESTAMP_col) function needed |
102251 | 2021-01-15 4:42 | 2022-12-12 22:27 | MySQL Server: Optimizer | Closed (495 days) | S2 | 8.0, 8.0.22, 8.0.23 | Any | Any | CTE produces wrong result |
102656 | 2021-02-19 3:52 | 2021-02-19 6:59 | MySQL Server: Optimizer | Verified (1156 days) | S3 | 8.0.22, 8.0.23 | Any | Any | SELECT results containing the special character " ︠e " is different |
103378 | 2021-04-20 3:34 | 2021-04-20 9:08 | MySQL Server: Optimizer | Not a Bug (1096 days) | S3 | 8.0.23 | Any | Any | sql_mode=only_full_group_by error 1055 is not appear for DELETE and UPDATE |
103836 | 2021-05-28 8:54 | 2022-04-13 8:00 | MySQL Server: Optimizer | Closed (1055 days) | S3 | 8.0.24, 8.0.25 | Any | Any | select cannot get right result with a COLLATE clause |
104966 | 2021-09-17 9:25 | 2021-09-17 12:25 | MySQL Server: Optimizer | Verified (946 days) | S3 | 8.0.23, 5.7.35, 8.0.26 | Any | Any | different result of in expression when table has index |
105437 | 2021-11-03 7:53 | 2021-11-03 9:05 | MySQL Server: Optimizer | Can't repeat (899 days) | S3 | 8.0.23 | Any | Any | Wrong answer when got multiple count(distinct) |
107629 | 2022-06-22 8:41 | 2022-06-22 10:06 | MySQL Server: Optimizer | Verified (668 days) | S3 | 8.0.29 | Any | Any | Incorrect result when using index and materialization-lookup |
107638 | 2022-06-23 4:53 | 2022-08-16 23:25 | MySQL Server: Optimizer | Closed (613 days) | S6 | 8.0.29 | Any | Any | Assertion in val_real() failed in MySQL 8.0.29 |
107647 | 2022-06-24 7:58 | 2022-12-20 13:50 | MySQL Server: Optimizer | Closed (487 days) | S6 | 8.0.29 | Any | Any | Assertion `!table->file->inited' failed in MySQL 8.0.29 |
107660 | 2022-06-26 5:06 | 2022-06-26 15:49 | MySQL Server: Optimizer | Verified (664 days) | S6 | 8.0.29 | Any | Any | Assertion in val_decimal() failed in MySQL 8.0.29 |
110040 | 2023-02-13 8:28 | 2023-02-13 14:00 | MySQL Server: Optimizer | Not a Bug (432 days) | S2 | 8.0.22+ | Any | Any | query bin() function by order by desc return incorrect result set |
110132 | 2023-02-20 9:13 | 2023-02-20 11:01 | MySQL Server: Optimizer | Verified (425 days) | S4 | 8.0 | Any | Any | Allow EXPLAIN for DML to be run with lower/read-only privileges |
111067 | 2023-05-18 8:05 | 2023-05-19 12:55 | MySQL Server: Optimizer | Verified (338 days) | S2 | 8.0.25, 8.0.33 | Any | Any | Query result error |
111318 | 2023-06-07 14:36 | 2023-06-07 14:55 | MySQL Server: Optimizer | Verified (318 days) | S3 | 8.0 | Any | Any | block_nested_loop optimizer wrong result? |
111414 | 2023-06-14 9:26 | 2023-06-16 9:32 | MySQL Server: Optimizer | Can't repeat (309 days) | S3 | 8.0.33 | Any | Any | HASH JOIN results in wrong query results |
111415 | 2023-06-14 9:39 | 2023-06-19 14:12 | MySQL Server: Optimizer | Verified (306 days) | S3 | 8.0 | Any | Any | Correlated group query wrong result |
111418 | 2023-06-14 11:43 | 2023-06-15 14:04 | MySQL Server: Optimizer | Verified (310 days) | S3 | 8.0 | Any | Any | Subquery with ROLLUP gives wrong result |
111435 | 2023-06-15 11:14 | 2023-06-15 13:16 | MySQL Server: Optimizer | Duplicate (310 days) | S3 | 8.0.32 | Any | Any | Hash join results in incorrect query results |
112242 | 2023-09-04 4:40 | 2023-09-04 8:34 | MySQL Server: Optimizer | Verified (229 days) | S2 | 8.1.0, 8.0.34 | Any | Any | Unexpected Results by use_invisible_indexes |
112243 | 2023-09-04 4:54 | 2023-09-21 7:13 | MySQL Server: Optimizer | Verified (229 days) | S3 | 8.0.34 | Any | Any | Unexpected Result by subquery_to_derived |
112296 | 2023-09-08 0:48 | 2024-01-03 16:02 | MySQL Server: Optimizer | Closed (108 days) | S3 | 8.1.0, 8.0.34 | Any | Any | Unexpected Result by NO_BNL |
112768 | 2023-10-19 7:15 | 2023-10-19 10:12 | MySQL Server: Optimizer | Not a Bug (184 days) | S3 | 8.1.0, 8.0.34 | Any | Any | Inconsistent results when tables are JOINed in a different order |
112816 | 2023-10-24 16:15 | 2023-12-13 12:00 | MySQL Server: Optimizer | Verified (169 days) | S2 | 8.0, 8.1 | Any | Any | Inconsistent results when JOINed in different order |
112911 | 2023-11-01 8:21 | 2023-11-01 8:56 | MySQL Server: Optimizer | Verified (171 days) | S2 | 8.1.0, 8.0.35 | Any | Any | Inconsistent results when using PRIMARY and DUPSWEEDOUT |
112912 | 2023-11-01 8:45 | 2023-11-01 14:47 | MySQL Server: Optimizer | Verified (171 days) | S3 | 8.0 | Any | Any | Parsing a string To BIT type got a wrong result |
112914 | 2023-11-01 9:43 | 2023-11-01 15:02 | MySQL Server: Optimizer | Verified (171 days) | S3 | 8.0 | Any | Any | different result related to zerofill and greatest() |
112985 | 2023-11-07 8:33 | 2023-11-08 10:54 | MySQL Server: Optimizer | Verified (165 days) | S3 | 8.0, 8.1, 8.2 | Any | Any | Inconsistent results when switching hash join optimization |
113059 | 2023-11-13 8:29 | 2023-11-13 9:51 | MySQL Server: Optimizer | Verified (159 days) | S2 | 8.2.0 | Any | Any | Inconsistent results when using DUPSWEEDOUT |
113188 | 2023-11-22 17:51 | 2023-12-21 10:18 | MySQL Server: Optimizer | Closed (121 days) | S1 | 8.2.0 | Any | Any | LEFT JOIN returns results that do not exist in table |
113298 | 2023-12-01 4:41 | 2023-12-01 4:55 | MySQL Server: Optimizer | Verified (141 days) | S3 | 8.0.33, 8.1.0, 8.0.35 | Any | Any | Unexpected Results when Using IN for Floating-Point |
113316 | 2023-12-04 3:32 | 2023-12-04 7:21 | MySQL Server: Optimizer | Verified (138 days) | S3 | 8.0.35, 8.1.0, 8.2.0 | Any | Any | When the bit type has an index, the query result is incorrect. |
73136 | 2014-06-27 16:34 | 2015-05-20 15:16 | MySQL Server: Optimizer | Verified (3582 days) | S3 | 5.6.12,5.6.19,5.5, 5.5.38, 5.5.20 | Any | Any | Index scan incorrectly selected over ref+sort leading to x1000 worse performance |
51017 | 2010-02-09 9:07 | 2010-02-13 19:12 | MySQL Server: Optimizer | Not a Bug (5180 days) | S3 | 6.0-codebase-bugfixing | Any | Any | Batched key access gives wrong results for SELECT with LEFT JOIN, GROUP BY |
57024 | 2010-09-26 4:44 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (4952 days) | S2 | 5.1 | Any | Any | Serious performance issue with an outer join |
85821 | 2017-04-06 7:11 | 2020-12-01 11:51 | MySQL Server: Optimizer | Closed (1236 days) | S3 | 8.0.2-DEBUG | Any | Any | partial update on views does not work |
37964 | 2008-07-08 11:17 | 2012-05-18 20:19 | MySQL Server: Optimizer | Duplicate (5758 days) | S2 | 5.1/5.0/6.0 | Any | Any | Wrong result using ORDER BY + LIMIT |
42209 | 2009-01-20 8:30 | 2012-08-31 15:44 | MySQL Server: Optimizer | Closed (4250 days) | S3 | 5.1.30 | Any | Any | Rollback affects the index usage for DELETE statement with FORCE INDEX. |
112451 | 2023-09-25 6:35 | 2023-09-25 7:37 | MySQL Server: Optimizer | Verified (208 days) | S3 | 8.0,8.1 | Any | Any | Incorrect result if there are non-deterministic expressions in in-subquery |
13392 | 2005-09-21 22:47 | 2005-10-31 20:13 | MySQL Server: Optimizer | Closed (6746 days) | S2 | 5.0.12-beta-nt-log | Any (All) | Any | values() fails with 'ambiguous' or returns NULL with ON DUPLICATE and SELECT |
47052 | 2009-09-01 19:22 | 2020-05-03 20:45 | MySQL Server: Optimizer | Duplicate (5248 days) | S3 | 6.0 | Any | Any | wrong result, Subquery with VIEW containing BETWEEN |
77639 | 2015-07-07 12:40 | 2019-12-11 1:09 | MySQL Server: Optimizer | Closed (1653 days) | S4 | 5.7 | Any | Any | Implement VALUES equivalent to a query specification |
82805 | 2016-08-31 2:20 | 2016-08-31 9:47 | MySQL Server: Optimizer | Verified (2789 days) | S2 | 5.7.10, 5.7.14 | Any | Any | Having clause condition fails on join table with TEXT field |
113462 | 2023-12-19 16:05 | 2023-12-20 15:06 | MySQL Server: Optimizer | Verified (122 days) | S3 | 8.0 | Any | Any | Incorrect result |
114237 | 2024-03-06 6:57 | 2024-03-06 8:30 | MySQL Server: Optimizer | Verified (45 days) | S5 | 8.2.0, 8.3.0 | Any | Any | Unexpected Cardinality by Index |
57623 | 2010-10-21 10:43 | 2011-03-02 3:16 | MySQL Server: Optimizer | Closed (4798 days) | S1 | mysql-next-mr-opt-backporting | Any | Any | subquery within before insert trigger causes crash (semijoin=on) |
70555 | 2013-10-08 17:29 | 2013-10-09 8:03 | MySQL Server: Optimizer | Verified (3846 days) | S3 | 5.6.14 | Any | Any | EXPLAIN for INSERT ... SELECT waits for table lock |
79204 | 2015-11-10 12:38 | 2016-02-04 19:57 | MySQL Server: Optimizer | Closed (3063 days) | S3 | 5.7.10 | Any | Any | INSERT INTO table from SELECT accepts to insert into generated columns |
81491 | 2016-05-18 15:05 | 2016-05-18 18:13 | MySQL Server: Optimizer | Not a Bug (2894 days) | S3 | 5.5.49-c11 | Any | Any | delete then insert multiple values produces data in wrong order. |
101269 | 2020-10-22 3:26 | 2022-04-11 9:06 | MySQL Server: Optimizer | Duplicate (740 days) | S1 | 5.7, 8.0, 8.0.22, 5.7.32 | Any | Any | using different index may produce different results |
48703 | 2009-11-11 21:58 | 2022-09-04 20:45 | MySQL Server: Optimizer | In progress (5066 days) | S3 | 5.0+ | Any | Any | nontrivial ORDER/GROUP BY expressions: ambiguous statements not detected |
51018 | 2010-02-09 9:19 | 2011-02-16 23:44 | MySQL Server: Optimizer | Closed (4897 days) | S3 | 6.0-codebase-bugfixing | Any | Any | Batched key access gives wrong results for SELECT with semijoin and NULL |
51122 | 2010-02-11 21:20 | 2018-09-09 20:45 | MySQL Server: Optimizer | Duplicate (5154 days) | S3 | 6.0-codebase-bugfixing | Any | Any | incremental join buffering + dup weedout semijoin + STRAIGHT_JOIN = wrong result |
51431 | 2010-02-23 17:49 | 2011-02-16 23:44 | MySQL Server: Optimizer | Closed (4937 days) | S3 | 5.1.44 | Any | Any | Wrong sort order after import of dump file |
51946 | 2010-03-11 9:23 | 2011-02-16 23:44 | MySQL Server: Optimizer | Duplicate (5154 days) | S1 | 5.1.41 | Any | Any | 'Range' optimized access returns incorrect result (duplicates of rows) |
52283 | 2010-03-22 19:10 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5142 days) | S3 | 5.1.46 | Any | Any | Innodb reports extra warnings when SELECT/WHERE is performed using invalid value |
52303 | 2010-03-23 13:52 | 2010-04-13 5:29 | MySQL Server: Optimizer | Not a Bug (5121 days) | S3 | 5.1.46, 5.5.1-m2, 5.5.3-m3 | Any | Any | MIN() outputs 0 as the minimum year(4) corresponding to 0000 |
57544 | 2010-10-19 0:06 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified | S4 | 5.0, 5.1 | Any | Any | "Sending data" state split |
58719 | 2010-12-03 19:05 | 2010-12-15 12:13 | MySQL Server: Optimizer | Not a Bug (4875 days) | S3 | mysql-5.5.8 | Any | Any | Server does not report ER_SP_FETCH_NO_DATA warning any more |
59187 | 2010-12-27 15:31 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (4863 days) | S2 | 5.1.55, 5.6.2-m5 | Any | Any | Wrong result with NULL NOT IN subquery |
59203 | 2010-12-29 4:38 | 2015-02-24 16:10 | MySQL Server: Optimizer | Closed (3343 days) | S1 | 5.0.91,5.1.39,5.1.55,5.5.8 | Any | Any | Serious optimizer failure when query is encapsulated in additional SELECT/INSERT |
59405 | 2011-01-10 21:34 | 2011-04-21 1:10 | MySQL Server: Optimizer | Closed (4748 days) | S1 | 5.5.8, 5.5.9-bzr | Any (Linux, Windows XP, Mac OS X) | Any | FIND_IN_SET won't work normaly after upgrade from 5.1 to 5.5 |
62617 | 2011-10-04 15:34 | 2013-01-28 18:48 | MySQL Server: Optimizer | Closed (4100 days) | S3 | 5.6.3, 5.6.4 | Any | Any | EXPLAIN EXTENDED wiht DELETE, UPDATE etc. |
68299 | 2013-02-07 5:40 | 2013-05-30 2:07 | MySQL Server: Optimizer | Closed (3978 days) | S3 | 5.6 | Any | Any | unexcepted "Using where" in "explain update/delete" |
68818 | 2013-03-30 5:29 | 2013-04-01 14:37 | MySQL Server: Optimizer | Duplicate (4037 days) | S3 | 5.6.10 | Any | Any | Large Value List in WHERE Clause Spends Too Much Time in 'statistics' State |
13311 | 2005-09-19 0:13 | 2006-09-20 15:28 | MySQL Server: Optimizer | Closed (6422 days) | S3 | 5.0 | Any (All) | Any | IN + binary lead to incorrect SELECT results |
13569 | 2005-09-28 14:09 | 2005-09-28 15:00 | MySQL Server: Optimizer | Not a Bug (6779 days) | S3 | all | Any (all) | Any | User friendly |
15131 | 2005-11-22 11:44 | 2011-02-16 23:43 | MySQL Server: Optimizer | Verified (5499 days) | S4 | 4.1,5.0 | Any | Any | On-disk temporary tables created for GROUP BY should use indexes |
29956 | 2007-07-22 11:48 | 2007-07-22 15:40 | MySQL Server: Optimizer | Won't fix (6117 days) | S4 | All | Any | Any | Explain should optionally execute the query and return the execution path |
30324 | 2007-08-08 23:31 | 2007-10-23 16:34 | MySQL Server: Optimizer | Closed (6024 days) | S2 | 5.0-bk, 5.1-bk | Any | Any | Grouping queries with COUNT(DISTINCT bit column) return wrong results |
35334 | 2008-03-17 12:48 | 2022-09-04 20:45 | MySQL Server: Optimizer | Verified (5842 days) | S4 | 5.0 all | Any | Any | For MyISAM select * from table order by key_field does not use index |
35803 | 2008-04-03 14:36 | 2012-05-18 20:19 | MySQL Server: Optimizer | Duplicate (5825 days) | S1 | 6.0 | Any | Any | subselect_notembedded crashes the server |
35952 | 2008-04-10 1:20 | 2008-04-25 20:24 | MySQL Server: Optimizer | Closed (5839 days) | S2 | 5.1.24 | Any | Any | Regression: 5.1.24 Results not returned for users with select privs as expected |
37742 | 2008-06-30 14:33 | 2011-02-16 23:43 | MySQL Server: Optimizer | Closed (5560 days) | S3 | 5.1.23-rc | Any | Any | HA_EXTRA_KEYREAD flag is set when key contains only prefix of requested column |
39786 | 2008-10-01 17:56 | 2012-10-12 10:59 | MySQL Server: Optimizer | Closed (4208 days) | S3 | 5.1.26 | Any | Any | Explain doesn't show key with order by in derived table. |
39943 | 2008-10-09 1:31 | 2008-10-09 6:59 | MySQL Server: Optimizer | Can't repeat (5672 days) | S2 | 5.1.24 | Any | Any | Wrong index chosen by innoDB |
40992 | 2008-11-24 19:14 | 2018-09-09 20:45 | MySQL Server: Optimizer | Duplicate (5167 days) | S3 | 6.0 bzr | Any | Any | InnoDB: Crash when index_condition_pushdown is on |
41153 | 2008-12-01 15:45 | 2020-05-03 20:45 | MySQL Server: Optimizer | Duplicate (5272 days) | S3 | 5.0.72, 5.1.30, 6.0.7 | Any | Any | DETERMINISTIC SF is evaluated too many times: comparison with not indexed column |
47123 | 2009-09-04 7:13 | 2011-02-16 23:44 | MySQL Server: Optimizer | Closed (5153 days) | S2 | 5.0, 5.1, 5.4 | Any | Any | Endless 100% CPU loop with STRAIGHT_JOIN |
47762 | 2009-10-01 14:29 | 2011-02-16 23:44 | MySQL Server: Optimizer | Closed (5053 days) | S3 | 5.0.87, 5.1, 6.0,5.4 | Any | Any | Incorrect result from MIN() when WHERE tests NOT NULL column for NULL |
47963 | 2009-10-09 23:07 | 2016-02-25 12:24 | MySQL Server: Optimizer | Closed (5153 days) | S1 | 5.1.39, 5.1.41 | Any | Any | Wrong results when index is used |
48046 | 2009-10-14 16:27 | 2024-02-04 20:45 | MySQL Server: Optimizer | Duplicate (4870 days) | S3 | 5.1 | Any | Any | Server incorrectly processing JOINs on NULL values |
48258 | 2009-10-23 7:40 | 2011-02-16 23:44 | MySQL Server: Optimizer | Closed (5053 days) | S3 | 5.0 | Any | Any | Assertion failed when using a spatial index |
33037 | 2007-12-06 12:49 | 2007-12-07 8:43 | MySQL Server: Optimizer | Can't repeat (5979 days) | S5 | 5.0.22-pro-nt-log | Any | Any | Different and much slower access plan used for select when used with insert into |
34660 | 2008-02-19 11:49 | 2011-10-08 16:07 | MySQL Server: Optimizer | Closed (4578 days) | S1 | 5.1.56, 5.0.56, 5.5.10 | Any | Any | crash when federated table loses connection during insert ... select |
35767 | 2008-04-02 10:55 | 2011-02-16 23:43 | MySQL Server: Optimizer | Closed (4900 days) | S1 | 6.0.5pre | Any | Any | Processing of uncorrelated subquery with semi-join cause wrong result and crash |
37348 | 2008-06-11 15:30 | 2011-02-16 23:43 | MySQL Server: Optimizer | Closed (5664 days) | S1 | 5.1/6.0-falcon | Any | Any | Crash in or immediately after JOIN::make_sum_func_list |
47217 | 2009-09-09 11:16 | 2011-02-16 23:44 | MySQL Server: Optimizer | Closed (4898 days) | S2 | 6.0 | Any | Any | Simple Inner join gives wrong result when order by is used |
9676 | 2005-04-06 11:57 | 2006-07-06 19:02 | MySQL Server: Optimizer | Closed (6498 days) | S3 | 4.1 | Any (any) | Any | INSERT INTO x SELECT .. FROM x LIMIT 1; slows down with big tables |
29297 | 2007-06-22 9:06 | 2012-05-18 20:19 | MySQL Server: Optimizer | Duplicate (6143 days) | S3 | 5.0.37, 5.0 BK, 5.1 BK | Any | Any | Wrong result with aggregation and a subquery |
53298 | 2010-04-29 21:15 | 2011-02-16 23:44 | MySQL Server: Optimizer | Closed (4897 days) | S3 | 6.0-codebase-bugfixing | Any | Any | wrong result with semijoin (no semijoin strategy chosen) |
74542 | 2014-10-24 10:05 | 2014-10-24 10:51 | MySQL Server: Optimizer | Verified (3466 days) | S3 | 5.6/5.7 | Any | Any | FLUSH TABLES WITH READ LOCK blocks EXPLAIN UPDATE/DELETE/INSERT |
74543 | 2014-10-24 10:11 | 2017-06-29 5:47 | MySQL Server: Optimizer | Verified (3466 days) | S3 | 5.6/5.7, 5.7.18 | Any | Any | read_only=1 prevents EXPLAIN UPDATE/DELETE/INSERT |
87598 | 2017-08-30 7:44 | 2017-08-30 12:22 | MySQL Server: Optimizer | Duplicate (2425 days) | S3 | 5.7.19 | Any | Any | SELECT DISTINCT doesn't return result with "Using index for group-by" |
100398 | 2020-07-31 8:33 | 2020-07-31 9:50 | MySQL Server: Optimizer | Verified (1359 days) | S3 | 8.0.19, 5.7.31, 8.0.21 | Any | Any | The results of aggregation operations are inconsistent in different partitions |
100764 | 2020-09-08 8:50 | 2020-10-16 1:00 | MySQL Server: Optimizer | No Feedback (1283 days) | S1 | 8.0 | Any | Any | Rename Table causes other SQL execution plans to change. |
102481 | 2021-02-04 15:37 | 2021-02-05 14:40 | MySQL Server: Optimizer | Verified (1170 days) | S3 | 8.0.23 | Any | Any | EXPLAIN FOR CONNECTION not good |
102655 | 2021-02-19 3:07 | 2021-12-02 11:19 | MySQL Server: Optimizer | Duplicate (870 days) | S3 | 8.0, 8.0.23 | Any | Any | results from SELECT are different when use WHERE or not |
102912 | 2021-03-11 2:07 | 2021-03-11 13:02 | MySQL Server: Optimizer | Verified (1136 days) | S3 | 8.0, 8.0.23, 5.7.33 | Any | Any | filter result different on a index bit column with no-index bit column |
110245 | 2023-03-01 3:56 | 2023-03-02 9:59 | MySQL Server: Optimizer | Not a Bug (415 days) | S3 | 8.0.32 | Any | Any | Issue with NOT IN |
112802 | 2023-10-23 8:23 | 2023-10-27 9:46 | MySQL Server: Optimizer | Verified (180 days) | S3 | 8.1.0, 8.0.34 | Any | Any | Inconsistent results when using INDEX |
113464 | 2023-12-19 17:40 | 2024-03-12 11:05 | MySQL Server: Optimizer | Verified (122 days) | S2 | 8.0.27 | Any | Any | >= 8.0.27 Error 1048 when updating row with empty_sql mode |
11745 | 2005-07-05 20:16 | 2005-08-03 20:56 | MySQL Server: Optimizer | Closed (6835 days) | S2 | 4.1.12a | Any (All) | Any | insert where not exists failing |
36559 | 2008-05-07 11:15 | 2010-05-10 18:37 | MySQL Server: Optimizer | Not a Bug (5094 days) | S1 | 5.0.46-5.0.60 | Any | Any | INSERT .. SELECT takes more time to complete on versions 5.0.46 and newer |
36802 | 2008-05-19 15:42 | 2022-01-05 15:50 | MySQL Server: Optimizer | Closed (836 days) | S3 | 5.0, 5.1, 6.0 BK | Any | Any | MySQL only use covered index when selecting from a view (or subquery) with union |
114058 | 2024-02-20 7:28 | 2024-02-20 11:06 | MySQL Server: Optimizer | Not a Bug (60 days) | S3 | 8.0.35 | Any | Any | The return value of the CAST(... AS UNSIGNED) expression is out of range. |
47338 | 2009-09-15 20:29 | 2011-02-16 23:44 | MySQL Server: Optimizer | Closed (4897 days) | S3 | 6.0 | Any | Any | assertion in handler::ha_external_lock |
48472 | 2009-11-02 13:39 | 2011-02-16 23:44 | MySQL Server: Optimizer | Closed (5153 days) | S3 | 5.0.88, 5.1.41 | Any | Any | Loose index scan inappropriately chosen for some WHERE conditions |
48475 | 2009-11-02 14:06 | 2011-02-16 23:44 | MySQL Server: Optimizer | Closed (5153 days) | S3 | 5.0.88, 5.1.41 | Any | Any | DISTINCT is ignored with GROUP BY WITH ROLLUP and only const tables |
49097 | 2009-11-25 12:14 | 2011-02-16 23:44 | MySQL Server: Optimizer | Closed (4897 days) | S3 | 6.0.14 | Any | Any | subquery with view generates wrong result with non-prepared statement |
49453 | 2009-12-04 10:31 | 2011-02-16 23:44 | MySQL Server: Optimizer | Closed (4897 days) | S3 | 6.0 | Any | Any | re-execution of prepared statement with view and semijoin crashes |
50190 | 2010-01-08 16:39 | 2018-09-09 20:45 | MySQL Server: Optimizer | Duplicate (5185 days) | S3 | 6.0-codebase,pe,next-mr | Any | Any | MAX() and MIN() failing for time values with Innodb |
50358 | 2010-01-15 10:01 | 2011-02-16 23:44 | MySQL Server: Optimizer | Closed (4897 days) | S3 | 6.0-codebase | Any | Any | semijoin execution of subquery with outerjoin yields wrong result |
54312 | 2010-06-07 22:19 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5065 days) | S3 | 5.1.47, 5.1.48-bzr | Any | Any | insert ... select .. order by rand(): difference depending on indexes. |
55648 | 2010-07-30 12:21 | 2011-02-16 23:44 | MySQL Server: Optimizer | Closed (4897 days) | S3 | 5.5.6-m3-debug | Any | Any | Server crashes when subjected to max/min on a table containing max allowed TIME |
55986 | 2010-08-15 2:51 | 2018-09-09 20:45 | MySQL Server: Optimizer | Duplicate (4702 days) | S1 | 5.6.99-m5-debug, 5.6.2-debug | Any | Any | Assertion `inited==INDEX' in handler::ha_index_end() on INSERT..SELECT..(SELECT) |
58134 | 2010-11-11 11:01 | 2011-02-16 23:44 | MySQL Server: Optimizer | Closed (4830 days) | S2 | 5.1.51-ndb-7.1.9 | Any | Any | Incorrectly condition pushdown inside subquery to NDB engine |
59186 | 2010-12-27 15:09 | 2011-03-03 1:32 | MySQL Server: Optimizer | Closed (4797 days) | S2 | 5.6.2-m5 | Any | Any | Wrong results of join when ICP is enabled |
67637 | 2012-11-19 16:44 | 2013-01-22 13:50 | MySQL Server: Optimizer | Closed (4106 days) | S3 | 5.6.7, 5.6.8 | Any | Any | EXPLAIN UPDATE output doesn't match query execution |
71097 | 2013-12-05 18:26 | 2014-08-01 15:55 | MySQL Server: Optimizer | Closed (3606 days) | S2 | 5.1.70, 5.5.33, 5.5.35, 5.6.14, 5.6.15 | Any | Any | Wrong results for a simple query with GROUP BY |
71576 | 2014-02-04 6:14 | 2014-02-04 18:08 | MySQL Server: Optimizer | Duplicate (3728 days) | S3 | 5.5.36 | Any | Any | InnoDB Table Statistics Is Not Updated on Bulk INSERT |
72031 | 2014-03-13 8:22 | 2014-03-13 11:14 | MySQL Server: Optimizer | Verified (3691 days) | S3 | 5.6.16 | Any | Any | Strange explain behaviour |
72294 | 2014-04-09 17:28 | 2014-04-10 6:24 | MySQL Server: Optimizer | Verified (3663 days) | S3 | 5.5-debug, 5.6-debug | Any | Any | Assertion `0' fails on killing INSERT .. SELECT into a FEDERATED table |
72734 | 2014-05-24 4:39 | 2016-05-05 13:55 | MySQL Server: Optimizer | Closed (2907 days) | S2 | 5.6.17, 5.7.5 | Any | Any | Wrong sort order when using view with order by |
74813 | 2014-11-12 9:41 | 2015-04-06 18:49 | MySQL Server: Optimizer | Closed (3382 days) | S3 | 5.7.6 | Any | Any | QUERY REWRITE: NULL IS NOT RECOGNIZED BY THE PLUGIN AS A LITERAL |
76679 | 2015-04-13 15:48 | 2017-02-01 14:28 | MySQL Server: Optimizer | Verified (3294 days) | S3 | 5.6, 5.6.24, 5.6.25, 5.7.8 | Any | Any | EXPLAIN incorrectly shows Distinct for tables using join buffer |
80556 | 2016-02-29 12:05 | 2016-06-13 16:39 | MySQL Server: Optimizer | Closed (2868 days) | S2 | 5.7.12 | Any | Any | inserting large json data takes an inordinate amount of time |
28724 | 2007-05-28 13:24 | 2007-06-19 13:33 | MySQL Cluster: NDB API | Closed (6150 days) | S2 | Any | Any | blob code sets error code on transaction object | |
53629 | 2010-05-13 20:32 | 2010-05-17 7:00 | MySQL Cluster: NDB API | Not a Bug (5088 days) | S1 | NDB 7.1.3 | Any | Any | Inserting records using NDB API adds empty padding to make value take max space |
56488 | 2010-09-02 9:46 | 2016-12-18 20:32 | MySQL Cluster: NDB API | Verified (2680 days) | S3 | mysql-5.1-telco-6.2 | Any | Any | NdbApi : Improve Blob/internal operation management |
42047 | 2009-01-12 11:29 | 2021-05-02 20:45 | MySQL Cluster: NDB API | Verified (5571 days) | S3 | mysql-5.1-telco-6.2 | Any | Any | NDBAPI : Too large BIT column causes node failure on insert |
42238 | 2009-01-21 11:54 | 2011-02-16 23:43 | MySQL Cluster: NDB API | Closed (5513 days) | S3 | 6.2+ | Any | Any | NDBAPI : NdbRecord insert permits key column value ambiguity |
36851 | 2008-05-21 12:17 | 2008-05-30 14:12 | MySQL Cluster: NDB API | Closed (5804 days) | S3 | All | Any | Any | NDBAPI : IgnoreError with Insert operation and Blobs |
14400 | 2005-10-27 16:15 | 2006-09-22 15:27 | MySQL Server: MyISAM storage engine | Closed (6420 days) | S2 | 3.23, 4.0, 4.1, 5.0 | Any (any) | Any | Query joins wrong rows from table which is subject of "concurrent insert" |
28478 | 2007-05-16 17:05 | 2007-06-20 0:51 | MySQL Server: MyISAM storage engine | Closed (6149 days) | S2 | 5.0.42, * | Any | Any | Improper key_cache_block_size corrupts MyISAM tables |
29335 | 2007-06-25 12:29 | 2007-06-27 10:14 | MySQL Server: MyISAM storage engine | Not a Bug (6142 days) | S3 | 5.0.38 | Any | Any | INSERT DELAYED checks table space incorrectly on MyISAM |
7963 | 2005-01-17 17:12 | 2005-03-07 22:20 | MySQL Server: MyISAM storage engine | Can't repeat (6984 days) | S2 | 4.1.8 | Any (*) | Any | Zero records not possible |
28837 | 2007-06-01 13:57 | 2008-01-15 16:26 | MySQL Server: MyISAM storage engine | Closed (5940 days) | S3 | 4.1BK/5.0BK/5.1BK | Any | Any | MyISAM storage engine error (134) doing delete with self-join |
17332 | 2006-02-12 21:38 | 2011-02-16 23:43 | MySQL Server: MyISAM storage engine | Closed (5237 days) | S2 | 4.1BK,5.0.18, 5.0.19-bk,5.0.21-bk | Any (Linux,Windows) | Any | changing key_buffer_size on a running server can crash under load |
69585 | 2013-06-26 11:23 | 2014-07-22 18:41 | MySQL Server: MyISAM storage engine | Verified (3560 days) | S1 | 5.5.30 x64, 5.5.39, 5.6.21, 5.7.5 | Any (MS Windows W2K8 64bit, Linux) | Any | low-priority-updates not working on replication slave |
88003 | 2017-10-05 22:08 | 2019-01-22 17:29 | MySQL Server: MyISAM storage engine | Closed (2236 days) | S2 | 5.7.19 | Any | Any | REPAIR TABLE for MyISAM table repeatedly causes index corruption |
40499 | 2008-11-04 13:26 | 2008-11-19 20:10 | MySQL Server: MyISAM storage engine | Not a Bug (5631 days) | S1 | 5.1 | Any | Any | INSERT INTO t SELECT * FROM t does not work with myisam if binlogging is on |
51307 | 2010-02-19 7:06 | 2011-02-16 23:44 | MySQL Server: MyISAM storage engine | Closed (5055 days) | S1 | 5.1.34, 5.1.44, 5.1.45-bzr,5.5.1-m2 | Any | Any | widespread corruption with partitions and insert...select |
6196 | 2004-10-21 12:44 | 2014-07-23 1:52 | MySQL Server: MyISAM storage engine | Closed (3559 days) | S4 | 5.1 | Any | Any | INSERT IGNORE should return warnings |
7714 | 2005-01-06 20:13 | 2005-01-06 20:39 | MySQL Server: MyISAM storage engine | Closed (7044 days) | S3 | 4.0.23 | Any (all) | Any | if disk full, sometimes MyISAM doesn't wait for free space, corrupts table |
7727 | 2005-01-07 7:47 | 2011-02-16 23:43 | MySQL Server: MyISAM storage engine | Verified (6048 days) | S4 | Any | Any | BASE_TABLE function for use w/ MERGE tables | |
37 | 2003-01-25 16:06 | 2003-02-15 23:40 | MySQL Server: MyISAM storage engine | Closed (7735 days) | S1 | 4.1 | Any (any) | Any | RTREE UNIQUE index allows non-unique values |
6284 | 2004-10-27 14:09 | 2004-12-03 14:00 | MySQL Server: MyISAM storage engine | Closed (7078 days) | S3 | 4.0.18-standard and 4.1.2-alpha- | Any (any) | Any | Warnings on SELECT ... INSERT with join on partial index |
8093 | 2005-01-22 20:08 | 2005-01-24 17:19 | MySQL Server: MyISAM storage engine | Closed (7026 days) | S3 | 4.1.8 | Any (*) | Any | GROUP BY can alter some values of a grouped by column |
10184 | 2005-04-26 16:32 | 2005-05-13 12:29 | MySQL Server: MyISAM storage engine | Not a Bug (6917 days) | S3 | 4.0 and higher | Any (any) | Any | auto-increment key not checked for value if in composite key |
12385 | 2005-08-04 14:27 | 2005-08-16 3:53 | MySQL Server: MyISAM storage engine | Closed (6822 days) | S2 | 4.0 | Any (*) | Any | Query Cache and READ LOCAL locks can cause bad results from query |
57323 | 2010-10-07 17:50 | 2011-06-21 18:51 | MySQL Server: MyISAM storage engine | Closed (4687 days) | S1 | 5.1.53, 5.5.7 | Any | Any | myisam corruption with insert ignore and invalid spatial data |
65614 | 2012-06-14 10:33 | 2012-07-15 1:00 | MySQL Server: MyISAM storage engine | No Feedback (4298 days) | S3 | 5.5.19 | Any | Any | Concurrent SELECT with INSERT return error about key file |
55659 | 2010-07-31 11:39 | 2013-03-03 20:45 | MySQL Server: MyISAM storage engine | Verified | S3 | 5.1 bzr | Any | Any | Negative count(*) |
64888 | 2012-04-06 14:43 | 2012-04-09 11:03 | MySQL Server: MyISAM storage engine | Verified (4397 days) | S3 | 5.1, 5.5, 5.6 | Any | Any | Inconsistent behavior of dynamic concurrent_insert values |
22820 | 2006-09-29 11:49 | 2022-03-06 20:45 | MySQL Server: MyISAM storage engine | No Feedback (5827 days) | S3 | 5.1.12 | Any (*) | Any | INSERT DELAYED does not behave like normal insert |
31305 | 2007-09-30 16:08 | 2007-11-26 19:00 | MySQL Server: MyISAM storage engine | Closed (5990 days) | S1 | 4.0.26, 4.1.21, 5.1.23, 5.0.48, 6.0.4 | Any | Any | myisam tables crash when they are near capacity |
34488 | 2008-02-12 12:50 | 2008-10-31 19:24 | MySQL Server: MyISAM storage engine | Not a Bug (5650 days) | S3 | 5.0.54 | Any | Any | Cardinality stats wrong after first analyze against MyISAM table |
36708 | 2008-05-14 6:45 | 2008-05-20 17:55 | MySQL Server: MyISAM storage engine | Not a Bug (5814 days) | S3 | 5.0.60,5.1.24 | Any | Any | extreme fragmentation of a table with blob records |
30284 | 2007-08-07 19:53 | 2008-01-15 16:30 | MySQL Server: MyISAM storage engine | Closed (5940 days) | S2 | 5.0.45,5.1.22BK | Any | Any | spatial key corruption |
30286 | 2007-08-07 21:32 | 2007-11-05 2:52 | MySQL Server: MyISAM storage engine | Closed (6011 days) | S1 | 5.0.45, 5.0.48BK, 5.1.21 | Any | Any | spatial index cause corruption and server crash! |
32705 | 2007-11-26 5:57 | 2008-04-15 2:13 | MySQL Server: MyISAM storage engine | Closed (5849 days) | S1 | 5.1.23, 5.0.50, 6.0.3 | Any | Any | myisam corruption: Key in wrong position at page 1024 with ucs2_bin |
36065 | 2008-04-14 17:08 | 2012-05-18 20:19 | MySQL Server: MyISAM storage engine | Duplicate (5833 days) | S3 | 6.0-falcon-team | Any | Any | MyISAM: duplicate key error on unique values |
40827 | 2008-11-18 16:18 | 2011-02-16 23:43 | MySQL Server: MyISAM storage engine | Closed (5456 days) | S2 | 5.0+ | Any | Any | Killing insert-select to MyISAM can cause table corruption |
26379 | 2007-02-14 19:59 | 2007-12-03 9:33 | MySQL Server: Merge storage engine | Closed (5983 days) | S1 | 4.0 4.1 5.0 5.1 | Any | Any | Combination of FLUSH TABLE and REPAIR TABLE corrupts a MERGE table |
26464 | 2007-02-17 18:25 | 2007-03-15 2:54 | MySQL Server: Merge storage engine | Closed (6246 days) | S2 | 4.1.21, 5.0.36BK, 5.1.16BK, 5.2.4BK | Any (*) | Any | insert delayed + update + merge = corruption |
27809 | 2007-04-13 13:03 | 2008-02-22 18:42 | MySQL Server: Merge storage engine | Closed (5902 days) | S3 | 5.0.40BK | Any | Any | documentation says REPLACE not working with MERGE, but it does |
47648 | 2009-09-25 13:23 | 2011-02-16 23:44 | MySQL Server: Merge storage engine | Closed (5157 days) | S3 | 6.0, mysql-next-4284 | Any | Any | main.merge fails sporadically |
27234 | 2007-03-17 4:48 | 2022-12-04 20:45 | MySQL Server: Merge storage engine | Verified (6240 days) | S4 | Any | Any | INSERT into Merge Table implicitly locks all underlying tables | |
34781 | 2008-02-24 6:36 | 2013-03-03 20:45 | MySQL Server: Merge storage engine | Verified (5900 days) | S4 | 5.0.46, 5.0.54 | Any | Any | create table ... engine=merge should warn user when non-MyISAM tables are used |
8092 | 2005-01-22 18:38 | 2013-07-03 5:38 | MySQL Server: Merge storage engine | Open | S4 | Any | Any | INSERT_METHOD feature request | |
10952 | 2005-05-30 7:53 | 2006-07-10 19:27 | MySQL Server: Merge storage engine | Won't fix (6494 days) | S3 | 5.0, 5.1 | Any | Any | alter table from MyISAM to MERGE lost data without errors and warnings |
30590 | 2007-08-23 10:26 | 2010-05-12 10:44 | MySQL Server: Memory storage engine | Closed (6025 days) | S1 | 5.0.48,5.1.22 | Any | Any | delete from memory table with composite btree primary key |
67978 | 2012-12-27 6:13 | 2012-12-29 16:21 | MySQL Server: Memory storage engine | Verified (4130 days) | S3 | 5.1, 5.5, 5.6 | Any | Any | Signed zero is handled incorrectly by HASH indexes and GROUP BY |
69075 | 2013-04-26 3:07 | 2014-02-19 10:39 | MySQL Server: Memory storage engine | Duplicate (3713 days) | S3 | 5.6.11, 5.6.15 | Any | Any | Memory leak slave_parallel_workers |
80716 | 2016-03-13 9:53 | 2017-09-21 20:40 | MySQL Server: Memcached | Not a Bug (2942 days) | S3 | 5.7.10, 5.7.11 | Any | Any | JSON data not validated if inserted via InnoDB memcache plugin |
95093 | 2019-04-23 22:59 | 2019-04-24 10:00 | MySQL Server: Memcached | Verified (1823 days) | S4 | 8.0.12 | Any | Any | Feature request: change defaults in innodb_memcache.containers |
34393 | 2008-02-07 19:50 | 2008-02-08 7:36 | MySQL Server: Maria storage engine | Not a Bug (5916 days) | S2 | 5.1.23 maria preview | Any | Any | all table engines treated like transactional |
35273 | 2008-03-13 16:02 | 2008-03-17 22:11 | MySQL Server: Maria storage engine | Closed (5878 days) | S3 | 5.1-maria | Any | Any | Corrupted table if using GIS index |
42509 | 2009-02-01 9:20 | 2010-05-26 18:00 | MySQL Server: Maria storage engine | Unsupported (5078 days) | S2 | 6.0-maria | Any | Any | Maria write_block_record: Assertion `data_length < ((block_size) * 3 / 4)' |
39420 | 2008-09-12 11:58 | 2008-11-06 18:05 | MySQL Server: Maria storage engine | Can't repeat (5644 days) | S3 | 6.0.7 | Any | Any | maria deadlock when doing a large insert |
36258 | 2008-04-22 13:58 | 2008-05-19 12:16 | MySQL Server: Maria storage engine | Closed (5815 days) | S2 | 5.1-maria | Any | Any | Maria: INSERT SELECT sends ok to client before committing |
37007 | 2008-05-27 14:36 | 2008-09-05 16:31 | MySQL Server: Maria storage engine | Closed (5706 days) | S3 | 5.1-maria | Any | Any | Maria: different checksum for MyISAM table depending on CHECKSUM=0|1 |
37873 | 2008-07-04 14:00 | 2008-07-11 8:58 | MySQL Server: Maria storage engine | Closed (5762 days) | S3 | 5.1-maria | Any | Any | Client gets ok from INSERT VALUES before commit record is on disk |
40425 | 2008-10-30 11:50 | 2008-12-17 10:30 | MySQL Server: Maria storage engine | Can't repeat (5603 days) | S1 | 6.0 | Any | Any | Maria: ha_maria::enable_indexes(uint): Assertion `0' failed. |
43620 | 2009-03-13 6:34 | 2009-05-07 8:32 | MySQL Server: Maria storage engine | Closed (5462 days) | S3 | 6.0.11-bzr | Any | Any | Maria throws 'Got error 176 from storage engine' on a range query |
43002 | 2009-02-19 7:39 | 2013-07-04 13:10 | MySQL Server: Maria storage engine | Won't fix (3943 days) | S3 | 6.0-TRUNK | Any | Any | maria.maria_notembedded fails sporadically |
42519 | 2009-02-01 15:36 | 2010-01-04 15:47 | MySQL Server: Maria storage engine | Closed (5462 days) | S2 | 6.0-maria | Any | Any | Maria: RESTORE leads to corrupted table and assertion |
40892 | 2008-11-20 16:10 | 2009-01-08 10:38 | MySQL Server: Maria storage engine | Closed (5581 days) | S1 | 6.0.8-release | Any | Any | maria: Livelock in sysbench OLTP_RW test |
40025 | 2008-10-14 16:06 | 2008-11-05 21:11 | MySQL Server: Maria storage engine | Can't repeat (5645 days) | S1 | 6.0-bzr | Any | Any | Maria deadlock in translog_buffer_lock, _ma_unlock_key_del, wait_for_update_bin |
37005 | 2008-05-27 13:54 | 2008-06-11 20:51 | MySQL Server: Maria storage engine | Closed (5792 days) | S3 | 5.1-maria | Any | Any | Maria: ALTER TABLE TRANSACTIONAL=0 leaves table transactional inside Maria |
38368 | 2008-07-25 9:34 | 2008-08-16 10:26 | MySQL Server: Maria storage engine | Can't repeat (5726 days) | S1 | 6.0-bzr | Any | Any | Maria deadlock on INSERT/UPDATE/DELETE |
39210 | 2008-09-03 11:19 | 2009-01-09 14:58 | MySQL Server: Maria storage engine | Closed (5580 days) | S1 | 5.1-maria, 6.0-maria | Any | Any | Maria deadlock in _ma_bitmap_wait_or_flush |
39446 | 2008-09-15 8:49 | 2020-09-13 20:45 | MySQL Server: Maria storage engine | Duplicate (5653 days) | S1 | 6.0-bzr | Any | Any | Maria deadlock in pagecache_read |
40579 | 2008-11-07 15:20 | 2009-03-10 14:39 | MySQL Server: Maria storage engine | Closed (5520 days) | S3 | 5.1-maria | Any | Any | Maria: assertion in page cache in check_and_set_lsn() |
41159 | 2008-12-01 21:01 | 2009-01-09 15:00 | MySQL Server: Maria storage engine | Closed (5580 days) | S3 | 5.1-maria | Any | Any | Maria: deadlock between checkpoint and maria_write() when extending data file |
41962 | 2009-01-08 14:05 | 2009-03-10 20:54 | MySQL Server: Maria storage engine | Closed (5520 days) | S3 | 5.1-maria | Any | Any | Maria: view-related test failures (insert, view, maria, trigger tests) |
43694 | 2009-03-17 9:36 | 2010-05-26 18:00 | MySQL Server: Maria storage engine | Unsupported (5078 days) | S3 | 6.0-maria | Any | Any | Maria: assertion on "table->file->stats.records > 0 || error" in INSERT SELECT |
37545 | 2008-06-20 13:02 | 2022-12-04 20:45 | MySQL Server: Logging | Verified | S4 | 5.0, 5.1, 6.0 | Any | Any | Reduce size of the blob field logged in slow query log |
46679 | 2009-08-12 18:08 | 2011-05-19 4:30 | MySQL Server: Logging | Not a Bug (4720 days) | S3 | 5.0.27, 5.0, 5.1, azalea bzr | Any | Any | setting @@global.log_queries_not_using_indexes=1 does not log queries |
37132 | 2008-06-02 3:48 | 2019-06-19 1:23 | MySQL Server: Logging | Closed (1767 days) | S3 | 5.1.25 | Any | Any | Logging to slow_log table fails with very slow queries |
95181 | 2019-04-29 10:02 | 2020-05-20 13:40 | MySQL Server: Logging | Closed (1431 days) | S3 | 5.7, 8.0 | Any | Any | The bugfix for Bug#28511326 seems incorrect |
109034 | 2022-11-09 4:15 | 2022-11-14 14:45 | MySQL Server: Logging | Verified (523 days) | S4 | 8.0 | Any | Any | Slow log Rows_examined value is inaccurate |
49756 | 2009-12-17 4:39 | 2011-02-16 23:44 | MySQL Server: Logging | Closed (4937 days) | S3 | 5.0.44, 5.1.43 | Any | Any | Rows_examined is always 0 in the slow query log for update statements |
68932 | 2013-04-11 11:19 | 2013-06-06 15:52 | MySQL Server: Logging | Closed (3971 days) | S1 | 5.6.10, 5.6.12 | Any | Any | A regression in 5.6 crash recovery atomicity |
96722 | 2019-09-03 3:19 | 2019-12-10 6:37 | MySQL Server: Logging | Verified (1593 days) | S3 | 5.6.28, 5.6.45, 5.7.27 | Any | Any | Event does't record slow insert in slow log |
103837 | 2021-05-28 9:32 | 2021-05-28 9:54 | MySQL Server: Logging | Verified (1058 days) | S4 | All, 8.0 | Any | Any | Suggest to add materialized view log for innodb tables |
43685 | 2009-03-17 2:41 | 2011-02-16 23:43 | MySQL Server: Locking | Closed (5158 days) | S3 | 5.0.78,5.1.32 | Any | Any | Lock table affects other non-related tables |
47682 | 2009-09-28 16:12 | 2011-02-16 23:44 | MySQL Server: Locking | Closed (5153 days) | S3 | 5.1,6.0.14 | Any | Any | strange behaviour of INSERT DELAYED |
82774 | 2016-08-29 3:13 | 2017-04-13 22:01 | MySQL Server: Locking | Not a Bug (2564 days) | S3 | 5.7.13 | Any | Any | Reasonably easy to generate mysqld semi-hang. Input file is 1K lines. |
64892 | 2012-04-06 17:53 | 2012-08-13 16:22 | MySQL Server: Locking | Closed (4268 days) | S3 | 5.1, 5.5, 5.6 | Any | Any | Session-level low_priority_updates does not work for INSERT |
39358 | 2008-09-10 5:38 | 2008-10-04 6:53 | MySQL Server: Locking | Not a Bug (5677 days) | S3 | 5.0.51-log | Any | Any | Concurrency locks causes deadlocks |
46654 | 2009-08-11 15:15 | 2011-02-16 23:44 | MySQL Server: Locking | Closed (5158 days) | S3 | 5.4.4-alpha | Any | Any | False deadlock on concurrent DML/DDL with partitions, inconsistent behavior |
61502 | 2011-06-13 14:02 | 2011-08-04 21:32 | MySQL Server: Locking | Not a Bug (4643 days) | S2 | 5.5.10 | Any | Any | deadlock on insertion - insert holds and waits on same lock |
86790 | 2017-06-22 9:18 | 2017-06-22 10:34 | MySQL Server: Locking | Verified (2494 days) | S2 | 5.7.18 | Any | Any | FTWRL continues to freeze the server even if it times out ... |
93464 | 2018-12-04 8:28 | 2018-12-06 17:15 | MySQL Server: Locking | Not a Bug (1964 days) | S3 | 8.0.13 | Any | Any | select xxx for update statement conflict insert statement |
96317 | 2019-07-24 13:52 | 2019-08-02 17:55 | MySQL Server: Locking | Not a Bug (1724 days) | S3 | 5.7.18 | Any | Any | Lock wait time out is not occuring for INSERT query |
104431 | 2021-07-27 22:13 | 2021-07-29 13:49 | MySQL Server: Locking | Not a Bug (996 days) | S3 | 8.0.26 | Any | Any | Incorrect data locks listed for INSERT |
989 | 2003-08-04 1:16 | 2011-02-16 23:40 | MySQL Server: Locking | Closed (5008 days) | S1 | 4.0 and higher | Any (all) | Any | If DROP TABLE while there's an active transaction, wrong binlog order |
37998 | 2008-07-09 17:38 | 2008-07-09 17:44 | MySQL Server: Locking | Duplicate (5764 days) | S3 | 5.1.25 | Any | Any | Lock doesn't allow to copy data from general_log to another table |
40113 | 2008-10-17 15:51 | 2011-02-16 23:43 | MySQL Server: Locking | Closed (5370 days) | S2 | 5.0, 5.1, 6.0 bzr | Any (Linux, Win XP SP2 32bit) | Any | Embedded SELECT inside UPDATE or DELETE can timeout without error |
40188 | 2008-10-20 19:51 | 2011-02-16 23:43 | MySQL Server: Locking | Closed (5448 days) | S2 | 6.0 | Any | Any | Replication failure on RBR + Innodb + implicit commit + truncate/drop table |
42147 | 2009-01-16 6:06 | 2014-06-19 22:23 | MySQL Server: Locking | Closed (3593 days) | S3 | 5.0.77-bzr, 5.1, 6.0 | Any | Any | Concurrent DML and LOCK TABLE ... READ for InnoDB table cause warnings in errlog |
46272 | 2009-07-17 17:54 | 2011-02-16 23:44 | MySQL Server: Locking | Closed (5158 days) | S3 | 6.0-codebase | Any | Any | New MDL: unnecessary deadlock |
48652 | 2009-11-09 21:13 | 2022-12-04 20:45 | MySQL Server: Locking | Verified (3694 days) | S4 | 5.1.39, 5.1.42 | Any (XP, Linux) | Any | Deadlock due to Foreign Key constraint |
72072 | 2014-03-19 7:31 | 2014-04-14 13:18 | MySQL Server: Locking | Not a Bug (3659 days) | S3 | 5.5 | Any | Any | 5.5 Lock |
79274 | 2015-11-13 15:03 | 2019-07-25 12:42 | MySQL Server: Locking | Can't repeat (1731 days) | S2 | 5.6, 5.7, 8.0 | Any | Any | CREATE TRIGGER etc is not able to get a SHARED_NO_WRITE metadata lock |
48747 | 2009-11-13 1:10 | 2012-05-18 20:19 | MySQL Server: Locking | Duplicate (5158 days) | S2 | 5.1-rep+3 | Any | Any | Segmentation fault due to MDL in 5.1-rep+3 |
50787 | 2010-02-01 10:37 | 2011-02-16 23:44 | MySQL Server: Locking | Closed (5192 days) | S1 | mysql-next-4284-stage | Any | Any | Crash in MDL_ticket::is_incompatible_when_granted() |
50908 | 2010-02-04 10:45 | 2011-02-16 23:44 | MySQL Server: Locking | Closed (5158 days) | S2 | mysql-next-4284 | Any | Any | Assertion `handler_tables_hash.records == 0' failed in enter_locked_tables_mode |
52377 | 2010-03-25 20:15 | 2022-12-04 20:45 | MySQL Server: Locking | Verified (5049 days) | S4 | 5.5.4-m3,5.6.99-m4 | Any | Any | MDL locks taken by failing statements not automatically removed |
53625 | 2010-05-13 17:46 | 2011-02-16 23:44 | MySQL Server: Locking | Won't fix (4824 days) | S2 | 5.1.49, 5.5.3-m3, 5.6.99 | Any | Any | Deadlock with log_output=TABLE, partitioned table, trigger and auto-inc |
54811 | 2010-06-25 14:35 | 2011-02-16 23:44 | MySQL Server: Locking | Closed (5000 days) | S3 | 5.5.5-m3 | Any | Any | assert in mysql_lock_have_duplicate |
56250 | 2010-08-25 13:07 | 2014-03-10 13:01 | MySQL Server: Locking | Can't repeat (3694 days) | S3 | 5.1, 5.5 | Any | Any | Deadlock between INSERT DELAYED and FLUSH TABLES |
58689 | 2010-12-03 6:02 | 2012-07-31 1:44 | MySQL Server: Locking | Closed (4281 days) | S3 | 5.0, 5.1, 5.6.1 | Any | Any | MyISAM Selects locks inserts inside procedure only |
60114 | 2011-02-11 12:39 | 2012-10-15 14:05 | MySQL Server: Locking | Closed (4205 days) | S3 | mysql-trunk | Any | Any | INSERT DELAYED can call ha_release_auto_increment without having a lock. |
71060 | 2013-12-03 14:08 | 2013-12-05 13:31 | MySQL Server: Locking | Verified (3791 days) | S2 | 5.6.15, 5.6.16, 5.5.35, 5.1.74 | Any | Any | INSERT-SELECT statement takes shared locks in trigger and causes deadlock |
73816 | 2014-09-05 12:56 | 2016-04-18 3:18 | MySQL Server: Locking | Closed (2979 days) | S2 | 5.6.20 | Any | Any | MySQL instance stalling “doing SYNC index” |
Showing 1-1000 of 2775 (Edit, Save, CSV, Feed) | Show Next 1000 Entries » |