« Show Previous 1000 Entries | Showing 1001-2000 of 7284 (Edit, Save, CSV, Feed) | Show Next 1000 Entries » |
ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
---|---|---|---|---|---|---|---|---|---|
106113 | 2022-01-08 6:52 | 2022-01-08 9:45 | MySQL Server: Replication | Verified (811 days) | S2 | 8.0.27, 5.7.36 | Any | x86 | Contribution by Tencent: insert on duplicate key cause 1032 replication error in |
106317 | 2022-01-27 22:39 | 2022-03-21 23:40 | MySQL Server: Replication | Verified (791 days) | S3 | 5.7, 8.0 | Any | Any | CHANGE REPLICATION FILTER does not persist after restart |
106388 | 2022-02-07 1:07 | 2022-02-07 9:13 | MySQL Server: Replication | Verified (781 days) | S2 | 5.7, 5.7.37 | Any | Any | Using SPATIAL KEY cause replication error 1032 |
106493 | 2022-02-17 14:38 | 2022-04-11 12:28 | MySQL Server: Replication | Verified (770 days) | S3 | 8.0.28, 5.7.37 | Any | Any | Replication crash when updating a table with a stored generated field in the pri |
112002 | 2023-08-09 6:08 | 2023-08-09 6:24 | MySQL Server: Replication | Verified (233 days) | S3 | 8.0.23+ | Any | Any | opt_replication_sender_observe_commit_only is not honored for XA ROLLBACK |
112189 | 2023-08-26 23:41 | 2023-08-28 9:58 | MySQL Server: Replication | Verified (214 days) | S3 | 8.0 | Any | Any | Binlog::EventHeader position overflow |
112256 | 2023-09-05 8:00 | 2023-10-07 13:28 | MySQL Server: Replication | Verified (204 days) | S3 | 8.0.30 and above, 8.0.34 | Any | Any | The event thread_id of source changed after write to local |
112364 | 2023-09-15 21:40 | 2023-09-22 23:44 | MySQL Server: Replication | Verified (191 days) | S3 | 8.0.34 | Any | Any | Create table like doesn't write the charset on binlog if its created from a temp |
112717 | 2023-10-13 15:14 | 2023-10-25 8:12 | MySQL Server: Replication | Verified (156 days) | S3 | 8.0.34 | Any | Any | Undo log truncation does not finalize when super_read_only=1 |
113038 | 2023-11-10 7:26 | 2023-11-10 8:36 | MySQL Server: Replication | Verified (140 days) | S2 | 8.0 | Any | Any | Contribution by Tencent: mi->data_lock not release if heartbeat event mismatch |
113187 | 2023-11-22 16:24 | 2023-11-28 21:06 | MySQL Server: Replication | Verified (124 days) | S5 | 8.0 and above | Any | Any | replica SQL thread purge applied relay logs blocked commit on source node |
113202 | 2023-11-23 17:12 | 2023-11-23 21:29 | MySQL Server: Replication | Verified (127 days) | S3 | 8.0.35 | Any | Any | p_s.processlist table does not contain async replica threads after restart |
113260 | 2023-11-28 14:55 | 2024-01-23 10:35 | MySQL Server: Replication | Verified (66 days) | S3 | 8.0.36, 8.2.0, 8.3.0 | MacOS | Any | Client error in error log: MY-004031 - The client was disconnected ... |
99628 | 2020-05-19 9:16 | 2020-05-28 14:59 | MySQL Server: Replication | Verified (1408 days) | S2 | 8.0.* | Any | Any | semi sync master not handle ack packet correctly when recv packet timeout |
99760 | 2020-06-02 12:33 | 2020-06-26 8:51 | MySQL Server: Replication | Verified (1395 days) | S3 | 8.0.16 | Any | Any | Statements involving temporary tables getting logged |
99806 | 2020-06-08 16:30 | 2022-01-13 23:40 | MySQL Server: Replication | Verified (1390 days) | S3 | Any | Any | replace master/slave terminology with primary/replica | |
100076 | 2020-07-02 8:03 | 2020-07-03 7:02 | MySQL Server: Replication | Verified (1365 days) | S3 | 5.6, 5.7, 5.7.30, 8.0.20 | Any | Any | Missing db name when alter current db -break slave |
100591 | 2020-08-20 17:57 | 2020-08-20 19:45 | MySQL Server: Replication | Verified (1317 days) | S3 | Any | Any | Contribution: Bug #100586 Assertion failure `m_status == DA_ERROR` in `Diag ... | |
100612 | 2020-08-23 11:28 | 2020-08-24 4:49 | MySQL Server: Replication | Verified (1313 days) | S3 | 5.6,5.7,8.0 | Any | Any | SQL thread prints wrong command in the error log |
100643 | 2020-08-26 11:43 | 2020-08-28 6:11 | MySQL Server: Replication | Verified (1309 days) | S3 | 8.0.21 | Ubuntu | Any | Can't connect to MySQL with sync plugin enabled after user creation |
100691 | 2020-08-30 20:16 | 2022-03-25 16:00 | MySQL Server: Replication | Verified (735 days) | S3 | 8.0.20 | CentOS (8) | x86 | Incorrect replication of excluded table via replicate-wild-ignore-table |
100723 | 2020-09-03 7:30 | 2020-09-08 19:33 | MySQL Server: Replication | Verified (1299 days) | S5 | 8.0 | Any | Any | slow MTS recovery in startup |
101262 | 2020-10-21 8:57 | 2023-02-03 7:30 | MySQL Server: Replication | Verified (1255 days) | S3 | 8.0.21, 8.0.32 | Any | Any | performance_schema.binary_log_transaction_compression_stats timestamps |
101275 | 2020-10-22 13:26 | 2020-10-23 10:23 | MySQL Server: Replication | Verified (1253 days) | S3 | 5.7, 5.7.31, 5.7.32, 8.0.22 | Any | Any | rpl_semi_sync_master_enabled=ON without any connected slaves will cause timeout |
101314 | 2020-10-26 7:14 | 2020-10-29 7:37 | MySQL Server: Replication | Verified (1247 days) | S3 | 8.0 | Any | Any | variable assignment unused in sql/rpl_slave.cc: queue_event() |
101339 | 2020-10-27 12:59 | 2020-10-28 8:18 | MySQL Server: Replication | Verified (1248 days) | S3 | 5.7.29,8.018, 8.0.22, 5.7.32 | Linux | x86 | The binlog file was incorrectly purged |
101351 | 2020-10-28 7:28 | 2020-11-10 12:22 | MySQL Server: Replication | Verified (1235 days) | S2 | 5.7, 5.7.32 | Linux | x86 | Replication failure(errno 1399) on dml in XA tr after rollback on timeout |
101567 | 2020-11-11 19:22 | 2020-11-14 1:45 | MySQL Server: Replication | Verified (1232 days) | S2 | 5.7.30/5.7.31 | Any | Any | Generated column as primary key breaks replication |
101717 | 2020-11-23 12:03 | 2020-12-15 12:53 | MySQL Server: Replication | Verified (1204 days) | S2 | 8.0, 8.0.22 | Any | Any | Poor performance on a GTID slave when log_slave_updates is disabled |
101722 | 2020-11-23 15:26 | 2020-11-23 16:58 | MySQL Server: Replication | Verified (1222 days) | S3 | Any | Any | Contribution: Use mmap for binlog | |
101828 | 2020-12-02 2:37 | 2020-12-02 4:32 | MySQL Server: Replication | Verified (1213 days) | S2 | 8.0.22 | CentOS | x86 | Hash scan incorrectly applied the log resulting in HA_ERR_END_OF_FILE |
101948 | 2020-12-10 8:00 | 2020-12-31 12:11 | MySQL Server: Replication | Verified (1184 days) | S3 | 5.7.29, 5.7.32 | Any | Any | heartbeat is not compatible with local info |
101955 | 2020-12-10 13:51 | 2020-12-31 12:11 | MySQL Server: Replication | Verified (1205 days) | S3 | 5.7.32 | Any | Any | "heartbeat is not compatible with local info" error message has garbled text |
101964 | 2020-12-10 19:57 | 2020-12-11 8:24 | MySQL Server: Replication | Verified (1204 days) | S3 | 5.7.32, 8.0.22 | Any | Any | relay_log_space_limit + stopped sql_thread will stop fetching logs silently |
102100 | 2020-12-31 10:58 | 2020-12-31 12:03 | MySQL Server: Replication | Verified (1184 days) | S3 | 5.7.31, 8.0.22, 5.7.32 | Any | Any | DCL commands are not replicated witch certain replication filters |
102175 | 2021-01-07 12:11 | 2023-09-13 9:33 | MySQL Server: Replication | Verified (1155 days) | S2 | 8.0.22 | Any | Any | log_status has wrong binary_log_position of gtid_executed |
110430 | 2023-03-20 7:11 | 2023-03-30 2:49 | MySQL Server: Replication | Verified (367 days) | S3 | 8.0 | Any | Any | XA COMMIT may not persist GTID into undo header |
110533 | 2023-03-28 15:49 | 2023-03-29 12:17 | MySQL Server: Replication | Verified (366 days) | S3 | 8.0.32 | Any | Any | XA COMMIT may not be recovered after a crash |
110566 | 2023-03-30 11:05 | 2023-03-31 8:20 | MySQL Server: Replication | Verified (364 days) | S2 | 5.7.41 | Any | Any | Contribution by Tencent: checkpoint may regression in mts |
110683 | 2023-04-13 13:21 | 2023-04-14 7:59 | MySQL Server: Replication | Verified (350 days) | S3 | 5.7, 8.0 | Any | Any | Multi-threaded slave statistics output is incorrect |
110889 | 2023-05-03 5:41 | 2023-05-03 6:07 | MySQL Server: Replication | Verified (331 days) | S5 | 8.0.32 | Any | Any | binlog rotate optimize |
111075 | 2023-05-18 13:24 | 2023-05-18 14:01 | MySQL Server: Replication | Verified (316 days) | S3 | 8.0 | Any | Any | I_S.PROCESSLIST shows misleading information for replica threads |
111146 | 2023-05-25 8:45 | 2023-05-26 9:28 | MySQL Server: Replication | Verified (308 days) | S3 | 8.0 | Any | Any | Write set conflict two parallel-able transaction on table with foreign key |
111247 | 2023-06-01 15:02 | 2023-06-05 15:39 | MySQL Server: Replication | Verified (301 days) | S3 | MySQL8.0.22, 8.0.23 | Any | Any | Executing a SELECT statement causes to allocate lots of memory for binlog |
111507 | 2023-06-21 5:12 | 2023-06-21 9:56 | MySQL Server: Replication | Verified (282 days) | S3 | 5.7.42 | Any | Any | Huge memory usage by write_set with foreign key info |
111540 | 2023-06-23 3:41 | 2023-06-23 5:15 | MySQL Server: Replication | Verified (280 days) | S5 | 8.0.32 | Any | Any | binlog compress optimize |
111686 | 2023-07-07 1:57 | 2023-07-07 6:34 | MySQL Server: Replication | Verified (266 days) | S5 | 5.7,8.0, 5.7.42 | Any | Any | Contribution by Tencent: shutdown takes at least 8 seconds if have slave |
111914 | 2023-07-28 16:38 | 2023-08-11 10:26 | MySQL Server: Replication | Verified (242 days) | S2 | 8.0.33 | Any | Any | Global replication filters replace channel specific filters |
113634 | 2024-01-12 17:33 | 2024-01-14 9:16 | MySQL Server: Replication | Verified (75 days) | S3 | 8.0 | Any | Any | Contribution: fix plugin semisync find minAck bug |
113707 | 2024-01-22 11:52 | 2024-01-22 12:04 | MySQL Server: Replication | Verified (67 days) | S3 | 8.3.0, 8.0.36 | Any | Any | replication stops after updating geometry column |
113727 | 2024-01-23 14:34 | 2024-01-26 6:39 | MySQL Server: Replication | Verified (63 days) | S1 | 8.0.19+ | Any | Any | GTID Replica stalls completely when log_slave_updates=0 and a local DDL executed |
113813 | 2024-01-31 2:26 | 2024-02-07 8:24 | MySQL Server: Replication | Verified (58 days) | S3 | MySQL8.0,8.0.36 | Any | Any | Semisync will abort due to wrong transaction binlog postion comparison |
113814 | 2024-01-31 2:42 | 2024-01-31 13:16 | MySQL Server: Replication | Verified (58 days) | S3 | MySQL8.0,5.7 | Any | Any | The Rpl_semi_sync_master_yes_tx and Rpl_semi_sync_master_no_tx are inaccurate |
114074 | 2024-02-21 8:35 | 2024-02-27 14:20 | MySQL Server: Replication | Verified (37 days) | S5 | 8.0.32 | Any | Any | optimize for Writeset_trx_dependency_tracker::get_dependency |
114125 | 2024-02-26 15:51 | 2024-02-27 13:37 | MySQL Server: Replication | Verified (32 days) | S3 | 8.0.35,8.0.36 | CentOS (7.9) | x86 | Parameter set by SET PERSIST is not set to replication threads when restart |
114198 | 2024-03-04 4:21 | 2024-03-07 7:23 | MySQL Server: Replication | Verified (23 days) | S3 | 8.0.35, 8.0.36 | Any | Any | Using PERSIST on binlog_transaction_compression partially compresses binary log |
114273 | 2024-03-08 2:04 | 2024-03-08 5:29 | MySQL Server: Replication | Need Feedback (21 days) | S3 | MySQL8.0.22 to 8.0.33 | Any | Any | turn on the binlog compression and load large data to server will cause oom |
114310 | 2024-03-12 4:14 | 2024-03-19 7:24 | MySQL Server: Replication | Verified (17 days) | S3 | 8.0.33 | Any | Any | Master_compression_algorithm output is wrong |
114361 | 2024-03-15 1:53 | 2024-03-19 11:11 | MySQL Server: Replication | Verified (11 days) | S5 | 8.0 | Any | Any | Unaligned Delegate's lock reduces performance |
114472 | 2024-03-25 7:17 | 2024-03-25 7:20 | MySQL Server: Replication | Verified (4 days) | S3 | V8.0 | Any | Any | MySQL replica encounter error when master and replica innodb_strict_mode=OFF |
114511 | 2024-03-29 7:05 | 2024-03-29 7:05 | MySQL Server: Replication | Open | S3 | MySQL8.0.22 | Any | Any | Turn on binlog compression and read binlog generate by big transaction cause oom |
106671 | 2022-03-08 12:12 | 2022-03-11 8:00 | MySQL Server: Replication | Verified (749 days) | S3 | 5.7.35, 5.7.37 | Any | Any | Contribution by Tencent: mark insert select with autoinc column unsafe |
106727 | 2022-03-15 2:22 | 2022-03-15 13:47 | MySQL Server: Replication | Verified (745 days) | S3 | 8.0.28, 5.7.37 | Any | Any | Report ERROR when logging big binlog events |
106818 | 2022-03-24 11:23 | 2022-06-07 2:29 | MySQL Server: Replication | Verified (661 days) | S2 | 5.7,8.0, 5.7.37 | Any | Any | Replication may fail when XA transactions use replace into statements |
106845 | 2022-03-26 13:23 | 2022-04-06 1:46 | MySQL Server: Replication | Verified (723 days) | S2 | 8.0.25 | CentOS (7.6) | ARM | Parallel replication not working with slave_preserve_commit_order=1 |
106875 | 2022-03-30 14:43 | 2022-04-05 14:13 | MySQL Server: Replication | Verified (724 days) | S3 | 8.0.28 | Any | Any | Contribution by Tencent: writeset can not be used when binlog_format is mixed |
106970 | 2022-04-08 16:55 | 2022-04-21 0:16 | MySQL Server: Replication | Verified (714 days) | S3 | 8.0.21 | Linux | x86 | Replicate_Wild_Do_Table don't take effect |
107008 | 2022-04-13 11:44 | 2022-05-05 7:11 | MySQL Server: Replication | Verified (694 days) | S2 | 5.7.37 | Any | Any | Contribution by Tencent:Shutdown hang due to work thread wait for ack |
107113 | 2022-04-24 10:53 | 2022-04-26 4:17 | MySQL Server: Replication | Verified (705 days) | S3 | 5.7,8.0, 8.0.28 | Any | Any | Got fatal error 1236 from master when reading data from binary log |
107293 | 2022-05-15 13:34 | 2022-05-21 20:52 | MySQL Server: Replication | Verified (678 days) | S2 | 5.7.37, 8.0.28 | Any | Any | CURRENT_TIMESTAMP not safe after all? |
107371 | 2022-05-23 11:12 | 2022-05-23 12:29 | MySQL Server: Replication | Verified (676 days) | S3 | Ver 8.0, 5.7 | Any | Any | slave error: Slave I/O for channel '': Unexpected master's heartbeat data |
107438 | 2022-05-31 19:57 | 2023-05-02 16:49 | MySQL Server: Replication | Verified (667 days) | S2 | 5.7.38 | CentOS (8) | Any | JSON STORED generated column values are inserted as NULL on replica |
107677 | 2022-06-28 7:41 | 2022-06-28 8:18 | MySQL Server: Replication | Verified (640 days) | S2 | 8.0.29, 5.7.38 | Any | Any | Contribution by Tencent: create table like temporary table missing charset info |
107928 | 2022-07-20 23:09 | 2022-07-26 2:17 | MySQL Server: Replication | Verified (617 days) | S2 | 8.0 | Any | Any | MySQL 8.0 Replication breaks when tmpdir space is filled |
107991 | 2022-07-27 2:02 | 2023-10-23 8:31 | MySQL Server: Replication | Verified (158 days) | S2 | 8.0.25 | Any | Any | Clone_persist_gtid causes memory leak |
108061 | 2022-08-03 11:33 | 2022-08-04 2:01 | MySQL Server: Replication | Verified (603 days) | S3 | 5.7.39 | Any | Any | Contribution by Tencent: Generated column calculate error without base column |
108405 | 2022-09-06 16:22 | 2022-09-07 4:56 | MySQL Server: Replication | Verified (569 days) | S3 | 8.0 | Any | Any | Contribution: Implement logic to be able to get a consistent GTID |
106918 | 2022-04-05 17:46 | 2022-05-25 10:19 | MySQL Server: Row Based Replication ( RBR ) | Verified (674 days) | S3 | 8.0.25 | Any | Any | master and slave may get serious in-consistence after add auto-increment as pk |
113236 | 2023-11-27 17:22 | 2024-02-03 15:05 | MySQL Server: Row Based Replication ( RBR ) | Verified (122 days) | S3 | 8.0.35-0ubuntu0.22.04.1 | Ubuntu (22.04.3 LTS 5.15.0-88-generic) | x86 (.) | conflicting replica_parallel_workers spec causes parallel_mode misconfig |
113251 | 2023-11-28 11:54 | 2023-11-29 9:24 | MySQL Server: Row Based Replication ( RBR ) | Verified (121 days) | S3 | MySQL8.0 | Any | Any | the slow log in slave is logged ,when binlog_format is row |
102482 | 2021-02-04 17:24 | 2021-02-15 16:57 | MySQL Server: Row Based Replication ( RBR ) | Verified (1146 days) | S3 | 5.7 | Any | Any | Data loss with ALL_NON_LOSSY and replication between latin1->utf8mb4 |
104546 | 2021-08-05 9:50 | 2024-01-30 15:57 | MySQL Server: Row Based Replication ( RBR ) | Verified (59 days) | S5 | 8.0.26 | Ubuntu (18.04.5 LTS) | x86 (Skylake-SP) | MySQL 8.0.26 single thread replication performance is slower than MySQL 5.7.35. |
109401 | 2022-12-16 2:01 | 2023-07-07 12:19 | MySQL Server: Row Based Replication ( RBR ) | Verified (469 days) | S3 | 8.0.31, 5.7.40, 8.0.33 | Any | Any | Rows_query_log_event truncates query due to treating query as C string |
109923 | 2023-02-03 14:18 | 2023-04-03 8:07 | MySQL Server: Row Based Replication ( RBR ) | Verified (416 days) | S2 | 5.7.37, 8.0.30 | Any | Any | Writeset-based Dependency Tracking will cause error HA_ERR_NO_REFERENCED_ROW. |
110071 | 2023-02-15 6:41 | 2023-02-15 8:11 | MySQL Server: Row Based Replication ( RBR ) | Verified (408 days) | S2 | Any, 5.7, 8.0 | Any | Any | Foreign Key should not be added to Writeset-based Dependency Tracking. |
106437 | 2022-02-10 23:42 | 2023-03-07 6:03 | MySQL Server: Row Based Replication ( RBR ) | Verified | S2 | 8.0.28 | Any | Any | need an option to let applier thread ignore virtual columns on replica.. |
77817 | 2015-07-23 19:18 | 2015-07-24 6:46 | MySQL Server: Row Based Replication ( RBR ) | Verified (3171 days) | S3 | 5.6.25, 5.7.7, 5.6.27, 5.7.9 | Any | Any | Bug #60926 was not fixed properly |
78265 | 2015-08-28 20:48 | 2015-08-31 22:37 | MySQL Server: Row Based Replication ( RBR ) | Verified (3133 days) | S3 | 5.6.26, 5.7.8, 5.7.9 | Any | Any | utf8 on master and utf8mb4 on slave leads to "cannot be converted from type" err |
73091 | 2014-06-24 11:12 | 2014-07-15 16:22 | MySQL Server: Row Based Replication ( RBR ) | Verified (3545 days) | S3 | 5.5.39, 5.6.21, 5.1.74 | Any | Any | A character set error may interrupt replication |
73648 | 2014-08-19 22:10 | 2018-07-06 3:09 | MySQL Server: Row Based Replication ( RBR ) | Verified (2240 days) | S2 | Server version: 5.6.16-log MySQL Communi, 5.6.39 | Linux | Any | innodb table replication is very slow with some of the partioned table |
69101 | 2013-04-30 10:14 | 2013-04-30 10:14 | MySQL Server: Row Based Replication ( RBR ) | Verified | S3 | 5.6.11 | Any | Any | Add counter for number of row events skipped due to IDEMPOTENT slave_exec_mode |
79831 | 2016-01-04 10:12 | 2016-01-04 11:28 | MySQL Server: Row Based Replication ( RBR ) | Verified (3007 days) | S3 | 5.6.28 | Any | Any | Unexpected error message on crash-safe slave with max_relay_log_size set |
80821 | 2016-03-22 11:38 | 2023-10-12 16:31 | MySQL Server: Row Based Replication ( RBR ) | Verified (2920 days) | S3 | 5.7, 5.7.11 | Any | Any | Replication breaks if multi-table DELETE is used in conjunction with Foreign Key |
67942 | 2012-12-18 21:34 | 2012-12-20 16:56 | MySQL Server: Row Based Replication ( RBR ) | Verified (4117 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 |
74927 | 2014-11-19 14:10 | 2014-11-19 16:42 | MySQL Server: Row Based Replication ( RBR ) | Verified (3418 days) | S3 | 5.6.19, 5.6.23 | Any | Any | Column number in slave status error doesn't match information_schema |
71035 | 2013-11-28 15:53 | 2014-10-30 8:47 | MySQL Server: Row Based Replication ( RBR ) | Verified (3772 days) | S2 | mysqlbinlog Ver 3.4, 5.1.74, 5.5.35, 5.6.16 | Linux (CentOS release 6.4 2.6.32-358.23.2.el6.x86_64) | Any | mysqlbinlog dumps out improperly-formatted TIMESTAMP values |
33376 | 2007-12-19 17:35 | 2016-10-16 20:45 | MySQL Server: Row Based Replication ( RBR ) | Verified (4459 days) | S2 | 5.1, 6.0 bzr | Any | Any | Write set for table not set correctly when inserting an empty set |
54249 | 2010-06-05 2:32 | 2017-05-21 20:45 | MySQL Server: Row Based Replication ( RBR ) | Verified (5045 days) | S3 | 5.1 | Any | Any | More verbose RBR error logging |
56007 | 2010-08-16 10:54 | 2023-02-12 20:45 | MySQL Server: Row Based Replication ( RBR ) | Verified | S2 | 5.6.99-m5 | Any | Any | Blackhole slave replication: 2nd slave stops with an error for UPDATE statement |
60784 | 2011-04-06 22:13 | 2014-09-25 19:58 | MySQL Server: Row Based Replication ( RBR ) | Verified (4739 days) | S1 | 5.5.8-log MySQL Communit | Linux | Any | Last_SQL_Errno: 1677 |
43468 | 2009-03-06 22:39 | 2017-05-21 20:45 | MySQL Server: Row Based Replication ( RBR ) | In progress | S3 | 5.1+ | Any | Any | modified_non_trans_table is not set in replicated stmt/trans |
49509 | 2009-12-07 13:40 | 2012-05-18 20:19 | MySQL Server: Row Based Replication ( RBR ) | Verified | S3 | next-mr, 6.0-codebase | Any | Any | RBR replication failure on concurrent ALTER TABLE ENGINE |
97027 | 2019-09-26 10:02 | 2021-01-15 16:47 | MySQL Server: Row Based Replication ( RBR ) | Verified (1169 days) | S2 | 5.7.* | Any | x86 | Bulk insert with ON DUPLICATE KEY UPDATE breaks replicaiton |
83030 | 2016-09-17 7:34 | 2016-09-19 7:19 | MySQL Server: Row Based Replication ( RBR ) | Verified (2748 days) | S1 | 5.7.13, 5.7.15 | Any | Any | AUTO_INCREMENT not updated when using REPLACE INTO |
83090 | 2016-09-22 2:13 | 2016-09-22 7:26 | MySQL Server: Row Based Replication ( RBR ) | Verified (2745 days) | S1 | 5.7.13, 5.7.15 | Any | Any | AUTO_INCREMENT not updated when using INSERT ON DUPLICATE KEY UPDATE |
83418 | 2016-10-18 0:46 | 2016-10-18 8:51 | MySQL Server: Row Based Replication ( RBR ) | Verified (2719 days) | S5 | 5.6, 5.6.34 | Any | Any | When binlog_row_image is MINIMAL, some updates queries logs redundant columns |
83431 | 2016-10-18 18:53 | 2016-11-23 10:21 | MySQL Server: Row Based Replication ( RBR ) | Verified (2683 days) | S1 | 5.6.27.75, 5.6.34 | CentOS | Any | RBR slave's "BEGIN" binlog query event doesn't carry a session database name |
85292 | 2017-03-03 14:48 | 2017-03-03 14:49 | MySQL Server: Row Based Replication ( RBR ) | Verified | S2 | 5.6+ | Any | Any | unreachable statement in function process_event with event type QUERY_EVENT |
91822 | 2018-07-28 3:56 | 2018-07-30 10:55 | MySQL Server: Row Based Replication ( RBR ) | Verified (2069 days) | S3 | 5.6, 5.6.41, 5.5.60 | Debian | Any | incorrect datatype in RBR event when column is NULL and not explicit in query |
92635 | 2018-10-02 13:10 | 2021-11-30 9:31 | MySQL Server: Row Based Replication ( RBR ) | Verified (850 days) | S3 | 5.7.17, 5.7.36 | Any | Any | HA_ERR_CORRUPT_EVENT on different slave schema |
92949 | 2018-10-25 15:38 | 2018-11-05 11:52 | MySQL Server: Row Based Replication ( RBR ) | Verified (1981 days) | S3 | 5.6.42, 5.7.24, 8.0.13 | Any | Any | add auto_increment column as PK cause RBR replication inconsistent |
93917 | 2019-01-14 13:47 | 2019-04-23 12:30 | MySQL Server: Row Based Replication ( RBR ) | Verified (1888 days) | S3 | 5.7.24,8.0.12 | Any | Any | Wrong binlog entry for BLOB on a blackhole intermediary master |
96142 | 2019-07-09 13:24 | 2019-07-10 8:48 | MySQL Server: Row Based Replication ( RBR ) | Verified (1724 days) | S3 | 5.6,5.7, 5.6.44, 5.7.26 | Any | Any | Inconsistent error on slave for Update event on table with non-exists partition |
88057 | 2017-10-11 12:42 | 2018-06-13 12:32 | MySQL Server: Row Based Replication ( RBR ) | Verified (2361 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 (1907 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 |
88595 | 2017-11-21 22:12 | 2022-11-24 12:06 | MySQL Server: Row Based Replication ( RBR ) | Verified (2249 days) | S2 | 5.6.37 | Any | Any | Row-based master-master replication broken by add column or drop column |
88791 | 2017-12-06 15:38 | 2017-12-08 13:05 | MySQL Server: Row Based Replication ( RBR ) | Verified (2303 days) | S2 | 5.7.20 | Ubuntu | Any | Binary log for generated columncontains new value as WHERE clause, not old value |
90608 | 2018-04-24 14:43 | 2022-12-18 8:15 | MySQL Server: Row Based Replication ( RBR ) | Verified (2166 days) | S3 | 8.0.11 | Ubuntu (14.04) | x86 | rpl_gtid.rpl_perfschema_applier_status_by_worker_gtid_skipped_transaction fails |
99759 | 2020-06-02 12:23 | 2020-06-04 12:24 | MySQL Server: Query Cache | Verified (1394 days) | S3 | 5.6, 5.7 | Any | Any | Three cases QueryCache hit query result error cause result mismatch. |
99773 | 2020-06-04 3:10 | 2020-06-04 7:41 | MySQL Server: Query Cache | Verified (1394 days) | S3 | 5.6, 5.7, 5.7.30 | Any | Any | QueryCache: session track gitds info error when hit query result cache |
100293 | 2020-07-22 14:45 | 2020-07-27 4:51 | MySQL Server: Query Cache | Verified (1341 days) | S3 | 5.7, 5.7.31, 5.7.30, 5.6.48 | Any | Any | The SERIALIZABLE transactions are not blocked for query cache |
111921 | 2023-07-31 7:57 | 2023-08-11 12:14 | MySQL Server: Prepared statements | Verified (241 days) | S3 | 8.0 | Any | Any | Reusing prepared statement for different data types, different outcomes are obse |
112011 | 2023-08-09 12:06 | 2023-08-17 12:21 | MySQL Server: Prepared statements | Verified (232 days) | S3 | 8.0 | Any | Any | RESOURCE GROUP hint fails when used within a prepared statement |
112105 | 2023-08-18 2:51 | 2023-08-18 9:21 | MySQL Server: Prepared statements | Verified (224 days) | S3 | 8.1.0, 8.0.34 | Ubuntu (22.04) | x86 (x86_64) | Create table from prepared statement issues |
112703 | 2023-10-12 12:13 | 2023-10-12 12:56 | MySQL Server: Prepared statements | Verified (169 days) | S3 | Any | Any | prepare statment has no warning comping to not prepare statment. | |
113301 | 2023-12-01 7:22 | 2023-12-01 8:53 | MySQL Server: Prepared statements | Verified (119 days) | S2 | 8.0.35, 8.0.31 | Any | Any | using preparation statement to query the time type data, some data is not found |
108293 | 2022-08-26 9:30 | 2022-09-05 7:43 | MySQL Server: Prepared statements | Verified (571 days) | S2 | 8.0.29 | Any | Any | Prepared statement does not use generated column index |
108432 | 2022-09-08 15:06 | 2022-09-08 17:56 | MySQL Server: Prepared statements | Verified (568 days) | S3 | 5.7.38/5.7.39 | Any | Any | Using the prepare statement causes an "unknown column in 'order clause'" error |
103765 | 2021-05-21 9:28 | 2021-08-03 10:40 | MySQL Server: Prepared statements | Verified (1043 days) | S3 | Java MySQL Driver 8.0.24, 8.0.25 | Any | Any | Statement prepare hangs |
105257 | 2021-10-19 3:58 | 2021-10-19 7:03 | MySQL Server: Prepared statements | Verified (892 days) | S3 | 8.0, 5.7.35, 8.0.26 | Any | Any | prepare statement return result is different from execute it directly |
113843 | 2024-02-01 2:49 | 2024-02-01 8:09 | MySQL Server: Prepared statements | Verified (57 days) | S3 | 8.0.32, 8.0.36 | Any | Any | prepared json query can not use index |
114056 | 2024-02-19 23:03 | 2024-02-22 10:56 | MySQL Server: Prepared statements | Verified (36 days) | S5 | 8.0.32, 8.0.22+ | Any | Any | Performance degredation using REGEXP in statement with parameters vs query |
114338 | 2024-03-13 16:41 | 2024-03-19 11:10 | MySQL Server: Prepared statements | Verified (15 days) | S3 | 8.0 | Any | Any | Client might receive incorrect data in ps-protocol |
111310 | 2023-06-07 6:51 | 2023-06-08 8:30 | MySQL Server: Prepared statements | Verified (295 days) | S3 | 8.0.33 | Ubuntu (22.04) | x86 (x86_64) | Prepared statement with CTE memory leak |
111560 | 2023-06-26 9:33 | 2023-06-26 13:53 | MySQL Server: Prepared statements | Verified (277 days) | S3 | 8.0 | Any | Any | A Prepare statement with cursor on will hang when executed after cursor closed |
81981 | 2016-06-23 2:22 | 2016-06-23 7:48 | MySQL Server: Prepared statements | Verified (2836 days) | S3 | 5.6, 5.7 | Any | Any | Basic automation functionality missing from prepared statements |
82139 | 2016-07-07 8:41 | 2016-07-07 10:33 | MySQL Server: Prepared statements | Verified (2822 days) | S2 | 5.7.13 | Any | Any | MySQL server sends internal column type over the wire |
96580 | 2019-08-19 2:54 | 2019-08-19 5:09 | MySQL Server: Prepared statements | Verified (1684 days) | S3 | MySQL-5.7.23, 5.7.27 | Any | Any | Using a prepare-stmts with timestampadd function will get an incorrect result |
99359 | 2020-04-26 10:57 | 2020-04-27 12:43 | MySQL Server: Prepared statements | Verified (1432 days) | S3 | 5.6.47, 5.7.29, 8.0.19 | Any | Any | Order by in group_concat with prepare statement returns unexpected results |
94857 | 2019-04-01 20:37 | 2019-04-04 13:05 | MySQL Server: Prepared statements | Verified (1821 days) | S2 | 5.7.23 | Any | Any | execute statement doesn't return correct result |
91221 | 2018-06-12 7:45 | 2018-06-12 10:33 | MySQL Server: Prepared statements | Verified (2117 days) | S2 | innodb_version = 5.7.21, 5.7.22 | Any | Any | REVOKE ALL PRIVILEGES, GRANT OPTION does not work in stored procedure |
69083 | 2013-04-26 18:10 | 2016-02-25 12:24 | MySQL Server: Prepared statements | Verified | S3 | 5.6.11 | Any | Any | Syntax error in preparing statement for SET PASSWORD |
69218 | 2013-05-13 17:57 | 2024-03-26 7:38 | MySQL Server: Prepared statements | Verified | S2 | 5.6.11 | Any | Any | P_S doesn't record SQL or digest for prepared statements |
69383 | 2013-06-02 20:57 | 2017-03-28 0:30 | MySQL Server: Prepared statements | Verified (3952 days) | S3 | 5.1, 5.5, 5.6, 5.7 | Any | Any | PREPARE from a 800 KB string causes ER_PARSE_ERROR "memory exhausted" |
78523 | 2015-09-22 22:54 | 2015-09-23 9:31 | MySQL Server: Prepared statements | Verified (3110 days) | S3 | 5.7.8-rc-log community version, 5.6.26, 5.6.28, 5.7.10 | Debian (8.1) | Any | can't see temporary table in statement with a subquery and a function |
67225 | 2012-10-14 15:02 | 2014-04-29 8:39 | MySQL Server: Prepared statements | Verified (3622 days) | S2 | 5.6.10 | Windows (XP SP3 32bit) | Any | binary data truncated when using UNION in prepared statement |
40038 | 2008-10-15 9:56 | 2022-12-04 20:45 | MySQL Server: Prepared statements | Verified (5644 days) | S3 | any | Any | Any | variables declared inside store procedures should build prepared statements |
42337 | 2009-01-26 8:05 | 2022-12-04 20:45 | MySQL Server: Prepared statements | Verified (5540 days) | S1 | 5.1.25rc | Windows | Any | DROP EVENT:this command is not supported in the prepared statement protocol yet. |
42490 | 2009-01-30 18:55 | 2023-09-15 8:12 | MySQL Server: Prepared statements | Verified (5534 days) | S2 | 5.1.30, 4.1, 5.0, 5.1, 6.0 bzr | Any | Any | mysql_stmt_result_metadata incorrectly returns null for some statements |
1382 | 2003-09-23 9:40 | 2022-12-04 20:45 | MySQL Server: Prepared statements | Verified (6275 days) | S2 | 4.0, 4.1, 5.0, 5.1 | Any (all) | Any | SQLDescribeParam returns the same type information |
2812 | 2004-02-15 12:18 | 2022-12-04 20:45 | MySQL Server: Prepared statements | Verified (6030 days) | S3 | 5.x | Linux (Linux/Windows) | Any | wrong value for stmt->field_count |
22774 | 2006-09-28 10:24 | 2022-12-04 20:45 | MySQL Server: Prepared statements | Verified (3719 days) | S2 | 5.0.24a | Linux (Fedora Core 5 and Windows XP) | Any | Incorrectly reported data truncation with server prepared statements |
24176 | 2006-11-10 10:32 | 2020-05-03 20:45 | MySQL Server: Prepared statements | Verified (5701 days) | S3 | 5.0.30 | Any | Any | bigint.test fails with --cursor-protocol |
26824 | 2007-03-03 14:21 | 2018-09-09 20:45 | MySQL Server: Prepared statements | Verified (3724 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 |
53216 | 2010-04-27 17:39 | 2022-12-04 20:45 | MySQL Server: Prepared statements | Verified | S3 | 5.5.3-m3, 5.5.4-m3 | Any | Any | Unrelated DDL causes repreparation of a prepared statement |
62257 | 2011-08-25 5:27 | 2013-07-17 13:56 | MySQL Server: Prepared statements | Verified (4286 days) | S2 | 5.5.8-enterprise-commercial, 5.1.64 | Any | Any | Application hangs while sending 1GB data using mysql_stmt_send_long_data() |
62256 | 2011-08-24 21:52 | 2011-08-25 16:03 | MySQL Server: Security: Privileges | Verified (4600 days) | S3 | >= 5.1.53 | Linux | Any | mysql_upgrade should convert Host values in mysql.user to lower case |
62390 | 2011-09-08 19:34 | 2011-09-20 19:47 | MySQL Server: Security: Privileges | Verified (4574 days) | S3 | 5.5.15-log, 5.1.60, 5.6.4 | Any | Any | "grant select on <schema>.* to ''" requires "flush privileges" |
37782 | 2008-07-01 17:58 | 2011-02-16 23:43 | MySQL Server: Security: Privileges | Verified (5379 days) | S3 | 5.0.62, 5.1, 4.1, 6.0 bzr | Any | Any | Program defensively in sql_acl.cc |
39762 | 2008-09-30 19:38 | 2022-12-04 20:45 | MySQL Server: Security: Privileges | Verified (5659 days) | S3 | 5.0.67/5.1/6.0 | Any | Any | create/drop user returns wrong rowcount |
41311 | 2008-12-08 21:39 | 2022-12-04 20:45 | MySQL Server: Security: Privileges | Verified (5589 days) | S3 | 5.0.67, 5.0.72, 5.1.30 | Any | Any | set timestamp allows unprivileged users to change per-session clock |
30395 | 2007-08-13 19:10 | 2022-12-04 20:45 | MySQL Server: Security: Privileges | Verified (6073 days) | S3 | 5.1 | Any | Any | SHOW PROCESSLIST strange results after REVOKE PROCESS ON *.* FROM ... |
31501 | 2007-10-10 10:13 | 2015-09-09 13:53 | MySQL Server: Security: Privileges | Verified (3990 days) | S3 | 5.0.45 | Any | Any | Stored Routines: droping stored procedure revokes all assotiated privileges |
33241 | 2007-12-14 12:48 | 2022-12-04 20:45 | MySQL Server: Security: Privileges | Verified (5588 days) | S3 | 5.0.45, 5.1 BK | Any (Linux (x86_64)) | Any | Wrong privileges used if there are different for same user name IP and host |
34104 | 2008-01-28 13:09 | 2022-12-04 20:45 | MySQL Server: Security: Privileges | Verified (5898 days) | S3 | 5.1 | Any | Any | SELECT FROM I_S.STATISTICS have different privilege requirements than SHOW INDEX |
34520 | 2008-02-13 13:30 | 2022-12-04 20:45 | MySQL Server: Security: Privileges | Verified (5884 days) | S3 | 5.0+ | Any | Any | Late decoding of C-style escape sequences and privilege obfuscation |
35363 | 2008-03-18 6:14 | 2022-12-04 20:45 | MySQL Server: Security: Privileges | Verified (5855 days) | S2 | 5.1.22 | Any | Any | Errors during execution of init_script are not reported to client |
35384 | 2008-03-18 9:10 | 2022-12-04 20:45 | MySQL Server: Security: Privileges | Verified (5848 days) | S3 | 5.1.22, 5.1.24-rc | Windows (also Linux) | Any | Revoke grant fails upon automatic privilege assignment to users on procedures |
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 |
54371 | 2010-06-09 15:32 | 2022-12-04 20:45 | MySQL Server: Security: Privileges | Verified (5041 days) | S3 | 5.1.44, 5.1.49-bzr | Linux | Any | Privileges required to use --events option for mysqldump |
55972 | 2010-08-13 15:10 | 2011-02-16 23:44 | MySQL Server: Security: Privileges | Verified (4949 days) | S3 | 5.1.47, 5.0, 5.6.99 | Any | Any | Privilege ordering sorts % before more specific entries like %.foo.com |
43830 | 2009-03-24 12:06 | 2022-12-04 20:45 | MySQL Server: Security: Privileges | Verified (5481 days) | S3 | 5.1.32, 5.0, 5.1, 6.0 bzr | Linux | Any | CREATE PROCEDURE causes ERROR 1410 unless ALTER ROUTINE is granted |
43918 | 2009-03-27 17:45 | 2016-12-05 10:53 | MySQL Server: Security: Privileges | Verified (5443 days) | S3 | 5.1.31sp1 | Any | Any | Generated version string is too long for the binlog |
43938 | 2009-03-29 9:11 | 2022-12-04 20:45 | MySQL Server: Security: Privileges | Verified (5479 days) | S3 | 5.1.32 | Any | Any | Weird error when NO_AUTO_CREATE_USER sql mode is active, creating user w/o pass |
44311 | 2009-04-16 9:41 | 2022-12-04 20:45 | MySQL Server: Security: Privileges | Verified (5357 days) | S2 | 5.1.33 | Windows (Vista 32 bit) | Any | privilege escalation |
7191 | 2004-12-11 9:46 | 2017-11-11 19:28 | MySQL Server: Security: Privileges | Verified (3724 days) | S2 | 4.1.7, 5.6.17 | Any | Any | REVOKE doens't remove permissions from a logged in user |
7861 | 2005-01-13 6:19 | 2022-12-04 20:45 | MySQL Server: Security: Privileges | Verified (6540 days) | S3 | any | Any (any) | Any | Column level security inconsistent with db/table level security |
9034 | 2005-03-08 0:25 | 2022-12-04 20:45 | MySQL Server: Security: Privileges | Verified (6549 days) | S3 | 5.0.3-alpha-debug | Linux (SuSE 9.1) | Any | Views: Can't GRANT CREATE VIEW unless view already exists |
9582 | 2005-04-02 14:24 | 2014-01-17 15:03 | MySQL Server: Security: Privileges | Verified (3724 days) | S2 | 5.0 | Any | Any | incorrect ACL system refresh after its update by GRANT command |
15704 | 2005-12-13 7:22 | 2022-12-04 20:45 | MySQL Server: Security: Privileges | Verified (6448 days) | S3 | 5.0 | Any | Any | NO_AUTO_CREATE_USER and empty password |
19913 | 2006-05-18 17:01 | 2022-12-04 20:45 | MySQL Server: Security: Privileges | Verified (6239 days) | S3 | 5.0.21-community-nt | Windows (win32 - XP SP2) | Any | Misleading error messages when user attempts to GRANT a priv he doesn't have |
20235 | 2006-06-02 18:03 | 2022-12-04 20:45 | MySQL Server: Security: Privileges | Verified (5903 days) | S3 | 5.0.21-community-nt | Windows (win32 - XP SP2, Fedora core 5) | Any | Unable to SHOW CREATE PROCEDURE without SELECT grant |
24455 | 2006-11-21 8:40 | 2022-12-04 20:45 | MySQL Server: Security: Privileges | Verified (6325 days) | S3 | 5.1.12-beta-community-nt, 5.0 BK | Linux (linux, window 2000) | Any | procs_priv shows error user after granting procedure's privilege to special user |
28331 | 2007-05-09 11:37 | 2022-12-04 20:45 | MySQL Server: Security: Privileges | Verified (5959 days) | S3 | 5.0-bk, 5.1-bk | Any | Any | Unclear error message when CREATE USER fails due to duplicate key |
28565 | 2007-05-21 15:39 | 2020-05-03 20:45 | MySQL Server: Security: Privileges | Verified (6139 days) | S3 | 5.1, 5.0 | Any | Any | Information disclosure during SELECT |
29237 | 2007-06-20 13:51 | 2022-12-04 20:45 | MySQL Server: Security: Privileges | Verified (6122 days) | S3 | 5.1.19, 5.0-BK | Any | Any | Privilege system inconsistent |
90824 | 2018-05-10 13:50 | 2019-06-08 12:49 | MySQL Server: Security: Privileges | Verified (1756 days) | S2 | 5.7.22 | FreeBSD (11.1-RELEASE-p8) | x86 | mysql_secure_installation.cc expires all passwords including internal ones |
91981 | 2018-08-11 13:02 | 2023-05-10 11:56 | MySQL Server: Security: Privileges | Verified (2046 days) | S3 | 5.6, 5.7, 8.0 | Any | Any | Inconsistent user@host definitions for definer/grantor/grantee columns |
92000 | 2018-08-13 22:40 | 2018-08-14 6:11 | MySQL Server: Security: Privileges | Verified (2054 days) | S3 | 5.7.22, 5.7.23 | Any | Any | CREATE user doesn't validade password hash lenght |
93426 | 2018-11-30 12:03 | 2018-11-30 12:15 | MySQL Server: Security: Privileges | Verified (1946 days) | S3 | 8.0.13 | Any | Any | 8.0.13 introduced new "volatile" variable |
81404 | 2016-05-12 18:49 | 2016-05-13 8:53 | MySQL Server: Security: Privileges | Verified (2877 days) | S3 | 5.7.12 | Ubuntu | Any | misleading error message of alter user |
81425 | 2016-05-14 8:50 | 2016-05-16 4:14 | MySQL Server: Security: Privileges | Verified (2874 days) | S3 | 5.7.12 | CentOS | Any | Invalid timestamps are inserted into proxies_priv table |
81621 | 2016-05-27 0:50 | 2016-06-02 12:07 | MySQL Server: Security: Privileges | Verified (2857 days) | S3 | 5.7, 5.7.12 | Debian | Any | GRANT privileges on db vs db table - Wildcard characters in db name - Escaping |
82733 | 2016-08-25 21:56 | 2016-08-27 8:10 | MySQL Server: Security: Privileges | Verified (2771 days) | S3 | 5.6, 5.7, 5.6.32 | Any | Any | Login errors after GRANT ON *.* in sql_mode PAD_CHAR_TO_FULL_LENGTH |
83174 | 2016-09-27 13:53 | 2016-09-28 13:14 | MySQL Server: Security: Privileges | Verified (2739 days) | S3 | 5.7.12, 5.7.15 | Linux (na) | Any | set password with hash_string does not work as described |
86061 | 2017-04-24 21:42 | 2017-05-03 9:26 | MySQL Server: Security: Privileges | Verified (2522 days) | S3 | 5.7.18 | Any | Any | REQUIRE CIPHER doesn't work as documented |
86464 | 2017-05-25 18:12 | 2017-05-25 22:08 | MySQL Server: Security: Privileges | Verified (2500 days) | S3 | 5.7/8.0 | Any | Any | INFORMATION_SCHEMA.TABLES missing performance_schema.session&global_variables |
87363 | 2017-08-09 17:24 | 2017-08-10 18:14 | MySQL Server: Security: Privileges | Verified (2423 days) | S3 | 5.6, 5.5.56, 5.6.37 | Any | Any | Document limitations regarding anonymous accounts that use wildcards |
87420 | 2017-08-15 11:42 | 2017-08-25 11:57 | MySQL Server: Security: Privileges | Verified (2417 days) | S3 | 5.6.36, 5.6.37, 5.5.56, 5.7.19 | CentOS (7.3.1611) | Any | GRANTS using general and specific permissions |
87674 | 2017-09-06 4:39 | 2017-09-06 6:02 | MySQL Server: Security: Privileges | Verified (2396 days) | S1 | 5.7.17, 5.6.37, 5.7.19 | Any | Any | Table 'user' was not locked with LOCK TABLES on FLUSH PRIVILEGES |
88694 | 2017-11-29 10:51 | 2017-12-04 7:23 | MySQL Server: Security: Privileges | Verified (2311 days) | S3 | 5.7.20 | Any | Any | MySQL accepts wildcard for database name for table level grant but won't use it |
88835 | 2017-12-08 11:47 | 2017-12-08 12:25 | MySQL Server: Security: Privileges | Verified (2303 days) | S3 | 8.0.3 | Any | Any | SHOW CREATE USER output not backwards compatible |
84244 | 2016-12-17 11:27 | 2017-03-27 12:37 | MySQL Server: Security: Privileges | Verified (2605 days) | S2 | 8 | Any | Any | Distinguish roles and plain users in mysql.user |
97091 | 2019-10-02 20:56 | 2019-11-18 12:54 | MySQL Server: Security: Privileges | Verified (1604 days) | S2 | 5.7+ | Any | Any | COM_RESET_CONNECTION does not respect CLIENT_INTERACTIVE |
97693 | 2019-11-19 15:44 | 2019-11-21 5:00 | MySQL Server: Security: Privileges | Verified (1590 days) | S3 | 8.0.18, 5.7.28 | Any | Any | ALTER USER user IDENTIFIED BY 'password' broken by invalid authentication_string |
110421 | 2023-03-18 4:02 | 2023-03-26 8:13 | MySQL Server: Security: Privileges | Verified (369 days) | S3 | 8.0.32 | Linux | Any | MySQL server not honoring connection_memory_limit for user created temp tables |
106785 | 2022-03-20 22:02 | 2022-03-21 5:31 | MySQL Server: Security: Privileges | Verified (739 days) | S3 | 8.0.28 | Any | Any | Add ALTER USER privilege |
108222 | 2022-08-22 12:05 | 2022-08-23 13:42 | MySQL Server: Security: Privileges | Verified (585 days) | S3 | 8.0 | Any | Any | ACL cache locking not consistent in 'change_password' function |
100003 | 2020-06-26 11:18 | 2020-06-29 8:29 | MySQL Server: Security: Privileges | Verified (1369 days) | S3 | 8.0.20, 5.7.30 | Any | Any | EXPLAIN FOR CONNECTION seems to still require the SUPER privilege |
100743 | 2020-09-04 15:06 | 2021-01-24 10:40 | MySQL Server: Security: Privileges | Verified (1160 days) | S3 | 5.7.31, 8.0.21 | Any | Any | Additional privileges required to access CONNECTION_CONTROL_FAILED_LOGIN_ATTEMPT |
112152 | 2023-08-23 7:17 | 2023-08-23 12:04 | MySQL Server: Security: Privileges | Verified (219 days) | S3 | 8.0.34 | Any | Any | Rename user to ''@'%' cause "Access denied" |
112873 | 2023-10-27 22:49 | 2023-10-30 7:11 | MySQL Server: Security: Privileges | Verified (151 days) | S3 | 8.0.34, 8.0.35 | Any | Any | Locked account is not shown in mysql.user |
102378 | 2021-01-26 14:24 | 2021-01-27 10:26 | MySQL Server: Security: Privileges | Verified (1157 days) | S3 | 8.0.22 Enterprise, 5.7.33, 8.0.23 | Any | x86 | ALTER USER IF EXISTS ... ACCOUNT LOCK throws error with validate_password |
103393 | 2021-04-21 8:02 | 2021-05-31 17:09 | MySQL Server: Security: Privileges | Verified | S5 | 8.0.24 | Any | Any | need efficient way to bulk import grants & privileges for many users/schemas |
104118 | 2021-06-26 2:42 | 2022-08-23 8:45 | MySQL Server: Security: Privileges | Verified (1004 days) | S2 | 8.0.24 | Any | Any | MGR all second node abnormal stop |
104732 | 2021-08-26 7:20 | 2022-02-25 9:53 | MySQL Server: Security: Privileges | Verified (946 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 |
106400 | 2022-02-08 2:52 | 2022-02-08 7:17 | MySQL Server: Security: Privileges | Verified (780 days) | S3 | 5.7, 8.0 | Any (Fails on all 5.7 environments tested) | Any (Only tested amd64/i386) | Table-level REVOKE fails for a re-created user. |
63926 | 2012-01-04 23:22 | 2012-01-11 20:03 | MySQL Server: Security: Privileges | Verified (4461 days) | S2 | 5.1.59, 5.5.21 | Linux (CentOS 5.x 64bit) | Any | Bug 61222 still exists in 5.1.59 (bad handshake due to old passwords change) |
64532 | 2012-03-03 9:42 | 2012-03-06 8:38 | MySQL Server: Security: Privileges | Verified (4409 days) | S2 | 5.5.20 | Any | Any | columns_priv record not clear or modify when table defination changed |
70030 | 2013-08-14 9:27 | 2014-07-22 18:43 | MySQL Server: Security: Privileges | Verified (3539 days) | S3 | 5.6.12 | Any | Any | current_user does not reflect expected value |
70114 | 2013-08-22 1:38 | 2013-08-22 8:20 | MySQL Server: Security: Privileges | Verified (3872 days) | S3 | 5.1.61, 5.1.71, 5.5.33, 5.6.13, 5.7.2-m12 | Any | Any | MySQL Permissions - Renaming a TEMPORARY table requires DROP privilege |
70304 | 2013-09-11 19:33 | 2018-03-27 7:46 | MySQL Server: Security: Privileges | Verified (3405 days) | S3 | 5.5.33, 5.5.42 | Linux | Any | Debug assertion in close_thread_table |
70384 | 2013-09-20 10:53 | 2013-10-03 11:26 | MySQL Server: Security: Privileges | Verified (3830 days) | S2 | 5.6.12, 5.6.14 | Any | Any | SHOW GRANTS may not return privileges of a user in current session |
70431 | 2013-09-26 8:05 | 2015-07-15 7:11 | MySQL Server: Security: Privileges | Verified (3180 days) | S1 | 5.6.13 | Any (CentOS) | Any | 5.6 CRASHES WHEN READING ANCIENT SYSTEM TABLES |
70742 | 2013-10-27 19:22 | 2014-11-18 10:27 | MySQL Server: Security: Privileges | Verified (3419 days) | S3 | 5.6.14 | Any | Any | Use hex encoding for show grants for sha256 plugin |
70928 | 2013-11-16 13:42 | 2013-11-18 10:30 | MySQL Server: Security: Privileges | Verified (3784 days) | S3 | 5.6.14, 5.7.2-m12 | Any | Any | Error message erroneously claims that SELECT from P_S table is denied |
71279 | 2014-01-02 17:29 | 2014-01-08 9:33 | MySQL Server: Security: Privileges | Verified (3739 days) | S3 | 5.6 | Any | Any | Misleading error message for ANALYZE against PERFORMANCE_SCHEMA tables |
73258 | 2014-07-10 11:19 | 2014-07-10 12:27 | MySQL Server: Security: Privileges | Verified (3550 days) | S3 | >= 5.6.3, 5.6.20 | Linux | Any | Unable to analyze ALL queries with EXPLAIN on read-only account |
73622 | 2014-08-18 9:55 | 2014-08-18 15:24 | MySQL Server: Security: Privileges | Verified (3511 days) | S3 | 5.5 5.6 | Any | Any | Existing privileges lost due to the unstable quick sort |
79314 | 2015-11-17 14:08 | 2020-03-24 2:56 | MySQL Server: Security: Privileges | Verified (3054 days) | S3 | 5.7.9, 5.6.29 | Any | Any | HELP not allowed in sandbox |
79774 | 2015-12-25 8:42 | 2015-12-29 11:31 | MySQL Server: Security: Privileges | Verified (3013 days) | S3 | 5.7.10, 5.7.11 | Any | Any | super_read_only as a server option does not also set read_only |
80860 | 2016-03-25 10:35 | 2016-03-26 5:14 | MySQL Server: Security: Privileges | Verified (2925 days) | S3 | 5.7, 5.7.11, 5.6.29 | Linux | Any | Strange behaviour for PASSWORD function in 5.7 |
74713 | 2014-11-06 12:44 | 2014-11-07 8:21 | MySQL Server: Security: Privileges | Verified (3430 days) | S3 | 5.6, 5.7, 5.6.22 | Any | Any | Inconsistent error codes returned on lack of access for EXPLAIN UPDATE with view |
74733 | 2014-11-07 13:02 | 2014-11-07 16:14 | MySQL Server: Security: Privileges | Verified (3430 days) | S3 | 5.5, 5.6, 5.7 | Any | Any | SELECT privilege is not checked for views on UPDATE which references to columns |
74738 | 2014-11-07 15:10 | 2014-11-07 16:52 | MySQL Server: Security: Privileges | Verified (3430 days) | S3 | 5.5, 5.6, 5.7 | Any | Any | Multi-table DELETE rejected due to lack of SELECT privilege for no good reason |
75097 | 2014-12-03 16:14 | 2019-04-08 13:58 | MySQL Server: Security: Privileges | Verified (3403 days) | S3 | 5.6.21 | Any | Any | WITH GRANT OPTION not functioning as expect |
75118 | 2014-12-05 16:28 | 2014-12-09 20:08 | MySQL Server: Security: Privileges | Verified (3398 days) | S3 | 5.6, 5.5.42, 5.6.23, 5.7.6 | Linux (n.a.) | Any | Misleading error message when WITH GRANT OPTION privilege is missing |
75572 | 2015-01-21 9:22 | 2015-01-21 10:09 | MySQL Server: Security: Privileges | Verified (3355 days) | S3 | 5.6.22 enterprise | Linux (SLES12) | Any | MySQL crashes on create user command after forgetting mysql_upgrade |
76390 | 2015-03-19 12:15 | 2016-10-11 8:19 | MySQL Server: Security: Privileges | Verified (3298 days) | S3 | 5.5/5.6/5.7 | Any | Any | wrong privileges in SHOW FULL COLUMNS |
76641 | 2015-04-09 14:34 | 2016-02-25 12:24 | MySQL Server: Security: Privileges | Verified | S3 | 5.7.7 | Any | Any | Inconsistent quoting of @@session.proxy_user |
75004 | 2014-11-26 4:27 | 2014-12-09 20:42 | MySQL Server: Pluggable Authentication | Verified (3398 days) | S1 | 5.6.20 | Any | Any | validatepassword can't prevent upper case password string which included in file |
71465 | 2014-01-24 2:56 | 2014-01-24 17:02 | MySQL Server: Pluggable Authentication | Verified (3717 days) | S3 | 5.5.37 | Any | Any | mysql.user row with plugin and password generates bogus warning |
71475 | 2014-01-24 21:46 | 2014-01-27 8:01 | MySQL Server: Pluggable Authentication | Verified (3714 days) | S3 | 5.7 | Any | Any | Server fails to disable accounts with conflicting password/plugin |
74242 | 2014-10-07 5:04 | 2014-10-07 9:53 | MySQL Server: Pluggable Authentication | Verified (3461 days) | S3 | 5.6 | Any | Any | Wrong value returned by external_user variable |
74377 | 2014-10-14 12:58 | 2015-11-19 17:30 | MySQL Server: Pluggable Authentication | Verified (3053 days) | S3 | 5.6.21 | Any | Any | empty processlist for proxy user |
79269 | 2015-11-13 13:18 | 2022-12-18 8:23 | MySQL Server: Pluggable Authentication | Verified (2256 days) | S3 | 5.6, 5.7, 8.0.0-dmr, 9.0.0-dmr, 5.7.19, 8.0.4-rc | Linux | Any | Failure of auth_socket authentication with sha256_password as default |
98113 | 2020-01-03 0:19 | 2020-01-16 16:26 | MySQL Server: Pluggable Authentication | Verified (1534 days) | S3 | 5.7, 8.0 | Any | Any | Crash possible when load & unload a connection handler |
81523 | 2016-05-20 15:38 | 2016-05-24 8:55 | MySQL Server: Pluggable Authentication | Verified (2866 days) | S3 | 5.7.10, 5.7.12 | Any | Any | Password validation plugin uses wrong logic |
84091 | 2016-12-07 11:59 | 2016-12-13 14:05 | MySQL Server: Pluggable Authentication | Verified (2663 days) | S3 | 5.7.15 | Any | Any | A possible mistake in send_server_handshake_packet(sql_authentication.cc) |
89459 | 2018-01-29 18:31 | 2018-01-29 21:42 | MySQL Server: Pluggable Authentication | Verified (2251 days) | S3 | Any | Any | Contribution: Adding BinaryLogStream folder | |
59662 | 2011-01-21 16:00 | 2011-02-16 23:44 | MySQL Server: Pluggable Authentication | Verified (4804 days) | S3 | 5.5, 5.6.2 | Any | Any | MySQL Server 5.5 wants to change the auth plugin to the same plugin |
60432 | 2011-03-11 14:56 | 2011-03-19 9:58 | MySQL Server: Pluggable Authentication | Verified (4766 days) | S3 | 5.5.9 | Any | Any | Modifying mysql.user table can deny users from logging in |
60745 | 2011-04-03 22:22 | 2015-11-19 17:44 | MySQL Server: Pluggable Authentication | Verified (4657 days) | S3 | 5.5 | Any | Any | dialog client authentication plugin is broken |
100662 | 2020-08-27 13:51 | 2020-08-27 15:20 | MySQL Server: Pluggable Authentication | Verified (1310 days) | S3 | 8.0.21 | Linux (n.a.) | x86 (n.a.) | Require SSL with PAM LDAP on UNIX Socket seems not to work |
100165 | 2020-07-09 2:41 | 2020-07-09 6:32 | MySQL Server: Performance Schema | Verified (1359 days) | S3 | 5.7.29, 5.7.30, 8.0.20 | Any | Any | The table is visible in performance_schema after renaming it |
100336 | 2020-07-27 15:58 | 2020-07-28 13:45 | MySQL Server: Performance Schema | Verified (1340 days) | S3 | 5.7 | Any | Any | performance_schema.status_by_thread table not populating on Linux |
100432 | 2020-08-05 7:55 | 2020-08-05 14:03 | MySQL Server: Performance Schema | Verified (1332 days) | S5 | 8.0.21 | Any | ARM | Optimal memory-barrier for performance-schema counter |
100962 | 2020-09-26 5:17 | 2020-10-26 11:42 | MySQL Server: Performance Schema | Analyzing (1250 days) | S3 | 5.7 | Any | Any | memory_summary_%_by_event_name Have different values |
101391 | 2020-10-30 3:04 | 2020-11-19 16:59 | MySQL Server: Performance Schema | Verified (1226 days) | S5 | 8.0, 8.0.22 | Any | Any | Performance Schema storage engine doesn't use index optimizations on group by |
101716 | 2020-11-23 9:30 | 2020-12-29 14:10 | MySQL Server: Performance Schema | Verified (1186 days) | S3 | 8.0.22,5.7.32 | Any | Any | P_S memory_summary_by_account_by_event_name table showing incorrect memory stats |
110857 | 2023-04-28 5:56 | 2023-05-02 13:01 | MySQL Server: Performance Schema | Verified (336 days) | S3 | 8.0.30, 8.0.33, 5.7.42 | CentOS (CentOS (CentOS Linux 7 (Core))) | Any ((Linux 3.10.0-1160.49.1.el7.x86_64)) | invalid NO_INDEX_USED=1 metric when using UNION in queries. |
108533 | 2022-09-19 12:04 | 2022-09-20 6:56 | MySQL Server: Performance Schema | Verified (556 days) | S3 | 8.0, 8.0.30 | Any | Any | NULL query text in performance schema after thread killed |
109452 | 2022-12-21 10:22 | 2022-12-21 12:12 | MySQL Server: Performance Schema | Verified (464 days) | S3 | 8.0.31 | Any | Any | Misleading error message on storage engine failing to collect its log info |
110045 | 2023-02-13 11:07 | 2023-02-13 11:35 | MySQL Server: Performance Schema | Verified (410 days) | S3 | 8.0.32 | Linux | x86 | Negative numbers on digests |
106985 | 2022-04-12 1:11 | 2022-04-12 7:44 | MySQL Server: Performance Schema | Verified (717 days) | S3 | 8.0,5.7 | Any | Any | performance_schema.global_variables table shows trimmed data. |
104121 | 2021-06-26 15:19 | 2024-03-20 14:37 | MySQL Server: Performance Schema | Verified (955 days) | S3 | >=5.7.28 , >=8.0.18, 8.0.25, 5.7.34 | Any | Any | PSI_THREAD_INFO not updated while executing PREPARED STATEMENTS. |
113659 | 2024-01-17 7:55 | 2024-01-18 11:22 | MySQL Server: Performance Schema | Verified (71 days) | S3 | 8.0 | Any | Any | explain output "Using temporary" but query dosent create temporary table |
113930 | 2024-02-08 11:41 | 2024-02-09 8:37 | MySQL Server: Performance Schema | Verified (49 days) | S3 | 8.0 | Any | Any | performance_schema_show_processlist = ON generates inconsistent output |
114300 | 2024-03-11 13:45 | 2024-03-11 14:41 | MySQL Server: Performance Schema | Verified (18 days) | S3 | 8.0 | Any | Any | The "fake index" of performance_schema.data_lock_waits causes slow sql |
114480 | 2024-03-26 7:36 | 2024-03-26 13:30 | MySQL Server: Performance Schema | Verified (3 days) | S3 | 8.0 | Any | Any | P_S doesn't record SQL or digest for prepared statements for Non-mysql client |
112035 | 2023-08-10 19:33 | 2024-02-21 1:00 | MySQL Server: Performance Schema | Verified (65 days) | S2 | 8.0.34 | Any | Any | Materializing performance_schema.data_locks can lead to excessive mem usage/OOM |
112959 | 2023-11-03 17:53 | 2023-11-07 10:41 | MySQL Server: Performance Schema | Verified (144 days) | S3 | 8.0 | Any | Any | Wrong rows examined in P_S and slow log for Index Merge. |
89379 | 2018-01-24 11:41 | 2022-03-31 8:21 | MySQL Server: Performance Schema | Verified (2256 days) | S5 | 5.7.20, 5.7.21 | Any | Any | summary_by_user tables get extremely slow with many users. |
89607 | 2018-02-09 13:47 | 2018-06-14 5:03 | MySQL Server: Performance Schema | Verified (2237 days) | S2 | 5.7 | Any | Any | MySQL crash in debug, PFS thread not handling singals. |
90631 | 2018-04-25 12:57 | 2018-04-25 15:14 | MySQL Server: Performance Schema | Verified (2165 days) | S3 | 8.0.11 | Ubuntu (14.04) | x86 | perfschema.statement_digest_query_sample test fails sporadically |
98498 | 2020-02-06 9:41 | 2020-02-07 13:01 | MySQL Server: Performance Schema | Verified (1513 days) | S3 | 5.7, 8.0 | Any (n.a.) | Any (n.a.) | P_S view status_by_thread does not reflect correct results |
98734 | 2020-02-25 11:51 | 2020-02-25 14:32 | MySQL Server: Performance Schema | Verified (1494 days) | S3 | 5.7.29,8.0.19 | Any | Any | Same digest for different queries if we use integer value in ORDER BY caluse |
99039 | 2020-03-23 14:29 | 2020-03-27 1:33 | MySQL Server: Performance Schema | Verified (1466 days) | S3 | >= 5.6.46 , >=5.7.28, >=8.0.18, 5.6.47, 5.7.29, 8.0.19 | Any | Any | PSI thread info not getting updated after statement execution |
99121 | 2020-03-31 8:52 | 2020-06-23 2:23 | MySQL Server: Performance Schema | Verified (1459 days) | S3 | 8.0, 8.0.19 | Any | Any | Performance schema does a meaningless summary according to digest |
99204 | 2020-04-07 20:52 | 2020-04-13 15:53 | MySQL Server: Performance Schema | Verified (1451 days) | S3 | 5.7.29, 8.0.19 | Any | Any | performance_schema threads table PROCESSLIST_INFO incorrect behaviour |
91825 | 2018-07-30 6:16 | 2020-06-16 8:44 | MySQL Server: Performance Schema | Verified (2069 days) | S3 | 5.7.23, 8.0.12, 5.7.22 | Any | Any | The user table is renamed as "SYSTEM_USER" in DIGEST_TEXT of history tables |
83472 | 2016-10-20 21:39 | 2017-06-27 7:41 | MySQL Server: Performance Schema | Verified (2716 days) | S3 | 5.6.27, 5.6.34, 5.7.16 | Linux | Any | Connection Attributes were not correctly read after change user command |
83912 | 2016-11-21 15:28 | 2020-03-09 16:52 | MySQL Server: Performance Schema | Verified (2683 days) | S3 | 5.6, 5.7, 5.6.34 | Any | Any | Time spent sleeping before entering InnoDB is not measured/reported separately |
84609 | 2017-01-23 12:21 | 2017-06-27 7:43 | MySQL Server: Performance Schema | Verified (2622 days) | S3 | 5.7, 8.0, 5.7.17 | Any | Any | Lock information in TABLE_HANDLES misplaced |
84655 | 2017-01-24 22:59 | 2017-06-27 7:44 | MySQL Server: Performance Schema | Verified (2620 days) | S3 | 5.7.17 | Any | Any | replication worker thread status not showing on performance_schema.threads |
94925 | 2019-04-06 0:15 | 2019-04-24 13:37 | MySQL Server: Performance Schema | Verified (1801 days) | S3 | 8.0.15 | Any | Any | Wrong Query Sample Text in Performance Query |
96196 | 2019-07-13 7:17 | 2019-07-16 10:28 | MySQL Server: Performance Schema | Verified (1719 days) | S3 | 5.7.26, 8.0.16 | Any | Any | performance_schema_accounts_size and p_s_hosts_size limited by 16384 |
81394 | 2016-05-12 13:40 | 2023-09-18 15:54 | MySQL Server: Performance Schema | Verified (193 days) | S3 | 5.7.12,5.7.15 | Any | Any | Unable to change performance_schema whilst super_read_only is enabled |
82663 | 2016-08-20 5:12 | 2017-06-27 7:40 | MySQL Server: Performance Schema | Verified (2772 days) | S1 | 5.7.13, 5.7.14 | Any | Any | mysqld hangs when accessing Performance Schema tables |
83276 | 2016-10-06 1:03 | 2016-10-06 7:31 | MySQL Server: Performance Schema | Verified (2731 days) | S2 | 5.7,8 | Any | Any | P_S.replication_connection_status contains a zero datetime |
76956 | 2015-05-06 14:34 | 2018-10-31 7:36 | MySQL Server: Performance Schema | Verified (3250 days) | S2 | 5.6, 8.0.13 | Any | Any | Threads table PROCESSLIST_INFO truncate query |
77293 | 2015-06-10 9:42 | 2024-01-25 17:10 | MySQL Server: Performance Schema | Verified (1641 days) | S3 | 5.6.16 | Linux (CentOS6.5) | Any | Wrong processlist_user in threads table for replication threads |
78068 | 2015-08-14 12:21 | 2015-08-18 13:08 | MySQL Server: Performance Schema | Verified (3149 days) | S3 | 5.7.8 | Any | Any | replication_* tables miss information about binary log position and other |
78303 | 2015-09-02 10:02 | 2016-09-22 7:50 | MySQL Server: Performance Schema | Verified (3131 days) | S3 | 5.7 | Any | Any | Add some DNS latency timings to performance_schema (host_cache?) |
79011 | 2015-10-28 21:53 | 2017-06-27 7:23 | MySQL Server: Performance Schema | Verified (3052 days) | S3 | 5.6.24 | Any | Any | truncated digest_text values don't always end with "..." |
68413 | 2013-02-18 2:45 | 2013-09-25 2:58 | MySQL Server: Performance Schema | Verified (3838 days) | S5 | 5.6.10, 5.6.13 | Any | Any | performance_schema overhead is at least 10% |
69755 | 2013-07-16 12:58 | 2015-05-04 8:59 | MySQL Server: Performance Schema | Analyzing (3908 days) | S3 | 5.5.31-0ubuntu0.12.04.2 | Linux (Linux xxx 3.5.0-34-generic #55~precise1-Ubuntu SMP Fri Jun 7 16:25:50 UTC 2013 x86_64 x86_64 ) | Any | file_instances leaks with innodb_file_per_table |
72825 | 2014-06-01 3:47 | 2014-08-10 8:15 | MySQL Server: Performance Schema | Verified | S3 | 5.7.4 | Linux (OL6) | Any | WORKER_ID in replication_execute_status_by_worker is always 1 SQL Not Running |
73112 | 2014-06-25 11:47 | 2016-02-23 15:52 | MySQL Server: Performance Schema | Verified (2957 days) | S3 | 5.6.16, 5.6.17, 5.6.20 | Linux | Any | Performance Schema - Statement Tables - Stored Procedures Counters are 0 |
73967 | 2014-09-18 12:35 | 2015-07-20 8:17 | MySQL Server: Performance Schema | Verified (3363 days) | S3 | 5.6.20 | Any | Any | Incorrect string value for sql_text |
79487 | 2015-12-02 6:21 | 2016-01-15 13:07 | MySQL Server: Performance Schema | Verified (3039 days) | S3 | 5.6, 5.7 | Any | Any | Provide non-Windows implementations for LF_BACKOFF |
80372 | 2016-02-15 12:58 | 2017-06-27 7:25 | MySQL Server: Performance Schema | Verified (2964 days) | S3 | 8.0.0-m17-enterprise-commercial-advanced | Any | Any | Built-in mysql functions are case sensitive when used in query digest hash |
80523 | 2016-02-26 9:23 | 2020-12-30 4:05 | MySQL Server: Performance Schema | Verified (2954 days) | S3 | 8.0.0, 8.0.11 | Windows | Any | current_memory in sys.session can go negative! |
71204 | 2013-12-22 15:42 | 2014-01-06 13:43 | MySQL Server: Performance Schema | Verified (3748 days) | S3 | 5.6.14, 5.6.16 | Any | Any | Timing for stages in P_S is different from what SHOW PROFILE reports |
71293 | 2014-01-04 18:35 | 2021-08-08 20:45 | MySQL Server: Performance Schema | Verified (3735 days) | S3 | 5.6 | Any | Any | Manual page for P_S.FILE_INSTANCES table does not explain EVENT_NAME values |
70823 | 2013-11-05 17:50 | 2013-11-05 20:00 | MySQL Server: Partitions | Verified (3797 days) | S3 | 5.6.14, 5.7.2 | Any | Any | Extended keys doesn't work for partitioned tables |
71630 | 2014-02-07 19:36 | 2014-02-08 20:57 | MySQL Server: Partitions | Verified (3703 days) | S3 | 5.1, 5.5, 5.6, 5.7 | Any | Any | Assertion `! is_set()' fails on UPDATE on a partitioned table with subquery |
71906 | 2014-03-03 9:47 | 2014-03-10 8:06 | MySQL Server: Partitions | Verified (3672 days) | S3 | 5.6.15 | Any | Any | SHOW CREATE TABLE FOR PARTITIONED TABLES: output slightly wrong |
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 |
71947 | 2014-03-05 18:55 | 2014-03-06 5:18 | MySQL Server: Partitions | Verified (3676 days) | S3 | 5.6, 5.7 | Any | Any | Unexpected change in error code on INSERT .. PARTITION causes replication abort |
72222 | 2014-04-03 14:21 | 2014-04-03 16:43 | MySQL Server: Partitions | Verified (3648 days) | S3 | mysql-5.5.35; mysql-5.6.16 | Linux | Any | Strange interaction of SQL_MODE=ANSI and partition by TIMESTAMP |
72274 | 2014-04-08 11:45 | 2014-04-08 14:14 | MySQL Server: Partitions | Verified (3643 days) | S5 | 5.6.17 | Linux | Any | Allow DECIMAL as partitioning key and/or improve pruning for FLOOR(DECIMAL) |
77773 | 2015-07-17 23:50 | 2015-07-20 12:44 | MySQL Server: Partitions | Verified (3175 days) | S3 | 5.6.23, 5.6.25 | CentOS | Any | DATA DIRECTORY and INDEX DIRECTORY ignored for MyISAM partitions on Linux |
78164 | 2015-08-21 10:11 | 2015-11-25 18:23 | MySQL Server: Partitions | Verified (3143 days) | S2 | 5.6.26 , 5.6.27, 5.7.9 | Ubuntu (14.04.2 64bit) | Any | alter table command affect partitioned table data directory |
79372 | 2015-11-21 11:40 | 2015-11-21 13:33 | MySQL Server: Partitions | Verified (3051 days) | S2 | 5.5, 5.5.48 | Any | Any | INSERT ... SELECT does not preserve rows order in InnoDB partitioned tables |
63083 | 2011-11-03 0:47 | 2011-11-29 16:19 | MySQL Server: Partitions | Verified (4504 days) | S2 | 5.x | Any | Any | ERROR 1469 (HY000): The mix of handlers in the partitions is not permitted in th |
65112 | 2012-04-26 10:30 | 2012-05-02 20:27 | MySQL Server: Partitions | Verified (4349 days) | S3 | 5.5.20, 5.6.6 | Linux (Linux vega203 2.6.18-238.el5 #1 SMP Thu Jan 13 15:51:15 EST 2011 x86_64 x86_64 x86_64 GNU/Linux) | Any | About half of partitions are empty on Key partition |
65286 | 2012-05-11 16:28 | 2015-01-15 14:43 | MySQL Server: Partitions | Verified (4339 days) | S5 | mysql 5.1, 5.5 | Any | Any | Avoid copying on REORGANIZE PARTITION where possible |
66187 | 2012-08-03 18:07 | 2012-08-10 16:25 | MySQL Server: Partitions | Verified (4255 days) | S2 | 5.1.63, 5.5.25a, 5.5.28 | Any | Any | Wrong query plan for min/max over an entire partition |
67241 | 2012-10-15 20:03 | 2012-10-17 13:41 | MySQL Server: Partitions | Verified (4181 days) | S3 | 5.5 | Linux | Any | Partition pruning not working utf8 / skip-character-set-client-handshake options |
67351 | 2012-10-24 8:02 | 2017-05-03 16:04 | MySQL Server: Partitions | Verified (4136 days) | S2 | 5.5.27-29.0 | Linux | Any | Cardinality samples of partitioned tables sometimes widely off |
70265 | 2013-09-06 18:10 | 2015-08-23 20:45 | MySQL Server: Partitions | Verified (3854 days) | S5 | 5.6.13 | Any | Any | Optimizer under-estimates rows when there are many unmatched partitions |
70303 | 2013-09-11 19:24 | 2015-11-19 15:57 | MySQL Server: Partitions | Analyzing (3852 days) | S2 | 5.5.32 | MacOS | Any | main.partition sporadically fails when using the embedded server |
72614 | 2014-05-12 0:42 | 2014-05-12 6:41 | MySQL Server: Partitions | Verified (3609 days) | S3 | 5.6.17, 5.6.19 | Any | Any | DATA DIRECTORY for partitioned tables |
72945 | 2014-06-10 21:24 | 2018-11-02 9:41 | MySQL Server: Partitions | Verified (3579 days) | S3 | 5.* | Any | Any | Partitions are opened for information_schema.partitions queries |
81712 | 2016-06-03 13:32 | 2016-06-06 8:09 | MySQL Server: Partitions | Verified (2853 days) | S2 | 5.7.12, 5.6.31, 5.7.13 | Windows (Microsoft Windows 7 Professional 64bit Service Pack 1) | Any | lower_case_table_names=2 ignored on ADD PARTITION on Windows |
96895 | 2019-09-17 5:45 | 2019-09-19 5:10 | MySQL Server: Partitions | Verified (1655 days) | S3 | 5.7.26 | Windows | Any | Test main.partition_rename_longfilename fails on Samba storage |
97041 | 2019-09-26 16:20 | 2019-09-28 14:33 | MySQL Server: Partitions | Verified (1644 days) | S1 | 8.0+, 8.0.17, 5.7.27 | Any | Any | main&sub partition field order different from combined pk, query result lose row |
98231 | 2020-01-15 8:27 | 2020-03-11 13:52 | MySQL Server: Partitions | Verified (1533 days) | S3 | 8.0 | Any | Any | show index from a partition table gets a wrong cardinality value |
88377 | 2017-11-06 21:54 | 2019-03-11 13:33 | MySQL Server: Partitions | Verified (1845 days) | S3 | 5.5, 5.6, 5.7, 8.0, 5.7.20 | Any | Any | Wrong CREATE_TIME and UPDATE_TIME for partitioned table |
88639 | 2017-11-24 7:05 | 2017-11-27 9:48 | MySQL Server: Partitions | Verified (2314 days) | S1 | 5.6.38/5.7/8.0 | Any | Any | ERROR 1030 (HY000): Got error -1 from storage engine on PARTITION CREATE TABLE |
88916 | 2017-12-14 10:59 | 2021-01-11 3:59 | MySQL Server: Partitions | Verified (2297 days) | S3 | 5.6, 5.7, 5.6.38, 5.7.20 | Any | Any | Assertion `table->s->db_create_options == part_table->s->db_create_options' |
87170 | 2017-07-23 11:40 | 2019-02-08 14:12 | MySQL Server: Partitions | Verified | S5 | 5.6.37, 5.7.19 | Any | Any | altering tables with many partitions is slower than expected |
87914 | 2017-09-29 11:33 | 2017-10-04 14:21 | MySQL Server: Partitions | Verified (2368 days) | S3 | 5.7 | Any | Any | Possible unintended usage of a field in file "sql/sql_partition.cc" |
94875 | 2019-04-02 19:21 | 2019-04-03 5:57 | MySQL Server: Partitions | Verified (1822 days) | S3 | 8.0.15 | Any | Any | MySQL is performing Engine substitution with partitions |
96574 | 2019-08-16 17:21 | 2019-08-19 6:48 | MySQL Server: Partitions | Verified (1684 days) | S2 | 5.7.24, 5.7.27 | MacOS | Any | reorganize partition downcases table name on Mac OS X |
91203 | 2018-06-10 16:02 | 2018-06-11 8:17 | MySQL Server: Partitions | Verified (2118 days) | S3 | 5.6.38, 5.6.40, 5.7.22, 8.0.11 | CentOS (6,5) | x86 | For partitions table, deal with NULL with is mismatch with reference guide. |
91855 | 2018-08-01 13:38 | 2019-07-22 9:15 | MySQL Server: Partitions | Verified (1712 days) | S3 | 8.0.12 | Any | Any | Last reference to WITH_PARTITION_STORAGE_ENGINE and --skip-partition |
92661 | 2018-10-03 21:42 | 2018-12-02 22:24 | MySQL Server: Partitions | Verified (2003 days) | S3 | 5.7.23 | Any | Any | SELECT on key partitioned enum reading all partitions instead of 1 |
83435 | 2016-10-19 0:40 | 2020-09-08 22:05 | MySQL Server: Partitions | Verified (2718 days) | S1 | 5.7.15/5.6 | Any | Any | ALTER TABLE is very slow when using PARTITIONED table |
84360 | 2016-12-28 13:36 | 2016-12-28 15:22 | MySQL Server: Partitions | Verified (2648 days) | S2 | 5.7.17 | Ubuntu (16.04) | Any | İt is possible partitoned table to alter to non-existing general tablespace |
84362 | 2016-12-28 17:11 | 2016-12-28 17:52 | MySQL Server: Partitions | Verified (2648 days) | S3 | 5.6, 5.7,8.0 | Any | Any | PARTITION BY LIST COLUMNS allows unsupported data types |
84370 | 2016-12-29 13:42 | 2016-12-30 4:14 | MySQL Server: Partitions | Verified (2646 days) | S2 | 5.7.17 | Any | Any | It is possible to enable compression for partitioned table in general tablespace |
85238 | 2017-03-01 2:58 | 2017-03-01 10:36 | MySQL Server: Partitions | Verified (2585 days) | S3 | 5.6, 5.7, 8.0 | Any | Any | Dropping non-existent partition throws unexpected error under certain conditions |
112181 | 2023-08-25 9:04 | 2023-09-18 8:39 | MySQL Server: Partitions | Verified (214 days) | S3 | 8.0 | Any | Any | TIMESTAMP(N) partitions doesn't prune for inequity |
112738 | 2023-10-16 9:26 | 2023-10-16 9:35 | MySQL Server: Partitions | Verified (165 days) | S1 | 8.0.30, 8.0.34 | Any | Any | can't truncate partition when partition_id exceed INT_MAX |
113338 | 2023-12-05 11:16 | 2023-12-07 8:11 | MySQL Server: Partitions | Verified (113 days) | S3 | 8.0.34, 8.0.35 | Linux | Any | return error result with a qubquery |
113369 | 2023-12-08 3:51 | 2024-01-05 13:06 | MySQL Server: Partitions | Verified (112 days) | S3 | 8.0.34, 8.0.35 | Any | Any | In the hash partition table, the query result is error. |
109939 | 2023-02-05 9:23 | 2023-02-07 9:19 | MySQL Server: Partitions | Verified (416 days) | S3 | 8.0.32, 5.7.41 | Any | Any | Lists partitions can not be reorganized (must be in consecutive order) |
109994 | 2023-02-08 19:44 | 2023-02-09 5:35 | MySQL Server: Partitions | Verified (414 days) | S3 | 5.7, 8.0 | Any | Any | Unexpected 1748 error returns when update stored generated column partition key |
110341 | 2023-03-10 17:18 | 2023-03-16 14:12 | MySQL Server: Partitions | Verified (382 days) | S3 | 8.0.32 | Any | Any | FOUND_ROWS() gives wrong result on prepared query against partitioned table |
100810 | 2020-09-11 8:11 | 2020-09-14 18:46 | MySQL Server: Partitions | Verified (1292 days) | S1 | MySQL8.0.20 | Any (rhel-7.4) | Any (intel x86) | miss to check table definition for partitioned table while importing tablespace |
101310 | 2020-10-26 4:39 | 2020-10-27 22:55 | MySQL Server: Partitions | Verified (1250 days) | S3 | 8.0.21, 8.0.22 | Any | Any | partition by key distribute unbalance for utf8 |
101984 | 2020-12-13 14:28 | 2020-12-14 7:04 | MySQL Server: Partitions | Verified (1201 days) | S3 | 8.0.22, 5.7.32 | CentOS | x86 | partition by key distribute unbalance when PARTITIONS is even and some COLLATE |
102090 | 2020-12-30 7:13 | 2020-12-30 9:35 | MySQL Server: Partitions | Verified (1185 days) | S3 | MySQL8.0.22/5.7 | Red Hat (rhel-7.4) | x86 (intel x86-64) | partitioned-table creation incorrectly checks timezone-dependent expressions |
104819 | 2021-09-03 6:55 | 2021-09-03 12:17 | MySQL Server: Partitions | Verified (938 days) | S3 | 8.0 | Any | Any | partition table maxvalue define error |
104881 | 2021-09-09 8:25 | 2021-09-15 8:46 | MySQL Server: Partitions | Verified (932 days) | S3 | 8.0.26, 5.7.35 | Any | Any | partition_info::set_used_partition not raise error when finding no partition |
104956 | 2021-09-16 8:54 | 2021-09-16 10:27 | MySQL Server: Partitions | Verified (925 days) | S3 | 8.0.26, 5.7.35 | Any | Any | SHOW CREATE TABLE outputs are inconsistent after CREATE TABLE and ALTER TABLE |
104981 | 2021-09-18 7:14 | 2021-09-20 6:44 | MySQL Server: Partitions | Verified (921 days) | S3 | 8.0.26 | Any | Any | Raise error that partition' name to be dropped doesn't exist at an earlier stage |
105014 | 2021-09-23 3:32 | 2021-09-23 15:33 | MySQL Server: Partitions | Verified (918 days) | S1 | 8.0.25, 8.0.26, 8.0.11, 5.7.35 | Any (rhel-7.4) | Any (x86-64) | query gets incorrect resultset from table with subpartitions |
105075 | 2021-09-29 13:00 | 2021-09-29 13:35 | MySQL Server: Partitions | Verified (912 days) | S3 | 5.7 | Any | Any | part field of unsigned bigint type |
105186 | 2021-10-11 9:40 | 2021-10-11 10:41 | MySQL Server: Partitions | Verified (900 days) | S2 | 8.0.26, 5.7.35 | Any | Any | a null value is not treated as zero in hash partition table |
105202 | 2021-10-13 10:02 | 2021-10-13 10:52 | MySQL Server: Partitions | Verified (898 days) | S3 | 8.0.26, 5.7.35 | Any | Any | ha_innopart::store_lock() traverse all partitions starting from index 1 not 0 |
105204 | 2021-10-13 11:22 | 2021-11-01 8:41 | MySQL Server: Partitions | Verified (898 days) | S3 | 8.0.26 | Any | Any | ha_innopart traverse all partitions instead of only used partitions causing loss |
105317 | 2021-10-26 6:12 | 2021-10-26 7:20 | MySQL Server: Partitions | Verified (885 days) | S3 | 8.0.26, 8.0.27 | Any | Any | Behavior of auto-increment value after EXCHANGE PARTITION is inconsistent |
105490 | 2021-11-08 11:28 | 2022-01-26 8:45 | MySQL Server: Partitions | Verified (872 days) | S3 | 8.0.27 | Any | Any | Empty loop brings loss to performance when pruning partitions for INSERT command |
105801 | 2021-12-05 3:35 | 2021-12-08 14:16 | MySQL Server: Partitions | Verified (842 days) | S5 | 5.7 | Any | Any | ha_innopart::records_in_range spend too much cpu cost |
106039 | 2022-01-05 7:08 | 2022-01-11 6:10 | MySQL Server: Partitions | Verified (808 days) | S5 | 8.0.27 | Any | Any | Skip using priority queue and visiting unused partitions when single partition |
111582 | 2023-06-27 12:03 | 2023-06-30 10:33 | MySQL Server: Partitions | Verified (273 days) | S3 | 8.0.33 | Any | Any | Query is incorrect after importing partition table with a different definition |
111685 | 2023-07-07 1:13 | 2023-07-07 8:13 | MySQL Server: Partitions | Verified (266 days) | S3 | 8.0.32, 8.0.33 | Linux | x86 | ADD PARTITION with DATA DIRECTORY forces relocation of other partitions |
113419 | 2023-12-14 12:50 | 2023-12-18 10:47 | MySQL Server: Partitions | Verified (105 days) | S3 | 8.0 | Any | Any | Contribution by Tencent: partition prune ignore subpartition where condition |
113700 | 2024-01-22 4:13 | 2024-01-22 8:45 | MySQL Server: Partitions | Verified (67 days) | S2 | 8.0.22, 8.0.36 | Any | Any | REORGANIZE PARTITION causes losing data |
113750 | 2024-01-25 6:50 | 2024-01-26 10:12 | MySQL Server: Partitions | Verified (63 days) | S2 | 8.0.36 | Any (rhel-7.4) | Any (x86-64) | stats of partitions could be empty after some kind of alter table DDL statements |
114396 | 2024-03-19 2:54 | 2024-03-19 5:53 | MySQL Server: Partitions | Verified (10 days) | S2 | 8.0.22, 8.0.35, 8.0.36 | Any | Any | NULL is not treated as 0 for tables partitioned by key |
114400 | 2024-03-19 9:34 | 2024-03-19 12:16 | MySQL Server: Partitions | Verified (10 days) | S3 | 8.0.32, 8.0.36 | Any | Any | Create partition table with DATA DIRECTORY execution result is incorrect |
106609 | 2022-03-01 8:11 | 2022-03-02 1:55 | MySQL Server: Partitions | Verified (759 days) | S3 | 8.0.27, 5.7 | Any | Any | For EXCHANGE PARTITION, make partition table writable while validation |
106884 | 2022-04-01 8:53 | 2022-05-24 20:59 | MySQL Server: Partitions | Verified (725 days) | S2 | 8.0, 8.0.28 | Any | Any | Data are not repartitioned when the partition key's charset is modified |
107556 | 2022-06-14 1:52 | 2022-06-14 8:20 | MySQL Server: Partitions | Verified (654 days) | S2 | 8.0.29 | Any | Any | restore_object_from_record on partition table consumes too much memory |
107791 | 2022-07-07 7:01 | 2022-07-18 9:11 | MySQL Server: Partitions | Verified (631 days) | S3 | 8.0.29, 5.7.38 | Any | Any | Left join with derived partitioned table returns wrong result |
103029 | 2021-03-18 6:34 | 2021-03-19 13:02 | MySQL Server: Partitions | Verified (1107 days) | S3 | 8.0 | Any | Any | Suboptimal plan due to null partition catch |
59004 | 2010-12-17 18:15 | 2015-08-23 20:45 | MySQL Server: Partitions | Verified (4851 days) | S3 | 5.5.9 | Linux (SUSE 64-bit) | Any | partition with floor(big_decimal_column) fails |
60298 | 2011-03-01 22:33 | 2021-06-02 2:23 | MySQL Server: Partitions | Verified (4775 days) | S3 | 5.1+ | Any | Any | Geometry columns/spatial indexes unsupported in partitioned tables |
60325 | 2011-03-03 21:29 | 2011-03-12 10:39 | MySQL Server: Partitions | Verified (4766 days) | S3 | 5.5, 5.1.57, 5.6.3 | Any | Any | partition optimization |
62568 | 2011-09-28 21:54 | 2011-11-09 16:34 | MySQL Server: Partitions | Verified (4565 days) | S3 | 5.5.12, 5.5.17 | Any | Any | Partition options not supported by storage engine are silently ignored |
36312 | 2008-04-24 7:42 | 2020-11-22 20:45 | MySQL Server: Partitions | Verified (4846 days) | S3 | 5.1.24,5.1.51 | Linux | Any | InnoDB DATA_FREE BUG? |
46300 | 2009-07-20 9:07 | 2011-02-16 23:44 | MySQL Server: Partitions | Verified (4969 days) | S3 | 5.1.36-log, 5.1.46, 5.5.3 | HP/UX (11.23 PA 2.0, LINUX F12) | Any | Partitioned table: LOAD DATA INFILE "stalls" - HPUX 11.23 PA RISC |
50393 | 2010-01-17 0:46 | 2011-02-16 23:44 | MySQL Server: Partitions | Verified (5185 days) | S3 | 5.1+ | Any | Any | insert DELAYED disabled for partitioned myisam |
51470 | 2010-02-24 17:36 | 2011-02-16 23:44 | MySQL Server: Partitions | Verified (5113 days) | S2 | 5.1, 5.5.1, 5.6.99 | Any | Any | subpartition by key need an expression |
53819 | 2010-05-19 17:42 | 2022-12-27 1:25 | MySQL Server: Partitions | Analyzing (5063 days) | S3 | mysql-next-mr-wl3561 | Any | Any | assert in my_seek, concurrent workload |
52844 | 2010-04-15 1:00 | 2022-12-04 20:45 | MySQL Server: Parser | Verified (5097 days) | S3 | 5.0.60-log, 5.0.91, 5.1.47 | Any (Linux, Mac OS X) | Any | semi-colon following MySQL comment fails to parse inside of CREATE PROCEDURE |
53426 | 2010-05-05 8:01 | 2022-12-04 20:45 | MySQL Server: Parser | Verified (5077 days) | S3 | 5.1.44 | Any | Any | Not able to parse a ISO9075 compliant 3-table join |
54491 | 2010-06-14 16:12 | 2022-12-04 20:45 | MySQL Server: Parser | Verified (5037 days) | S3 | 5.5.3 | Any | Any | inconsistent handling of sql_no_cache between 5.1 and 5.5 |
54580 | 2010-06-17 10:54 | 2022-12-04 20:45 | MySQL Server: Parser | Verified (5034 days) | S3 | 5.1.49-bzr | Any | Any | plugin with a name starting like an existing option causes wrong parsing |
55477 | 2010-07-22 11:21 | 2020-02-12 23:32 | MySQL Server: Parser | Verified (4952 days) | S1 | 5.1.44, 5.1.50-bzr, 5.5.20 | Windows (XP) | Any | Bad parsing of SQL operators (!! is different from ! !) |
55840 | 2010-08-09 14:45 | 2022-12-04 20:45 | MySQL Server: Parser | Verified (4607 days) | S3 | 5.1.45, 5.5-bzr | Any | Any | Precedence / Order of Operations = IN strange. |
62696 | 2011-10-12 9:36 | 2011-11-09 15:38 | MySQL Server: Parser | Verified (4552 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 |
1956 | 2003-11-25 16:23 | 2022-12-04 20:45 | MySQL Server: Parser | Verified (5662 days) | S3 | 4.0.12, 4.1.0, 5.1.52 | Any (Any) | Any | Parser allows naming of PRIMARY KEY |
5967 | 2004-10-07 22:31 | 2022-12-04 20:45 | MySQL Server: Parser | Verified (5990 days) | S1 | 5.0.2-alpha-debug | Linux (SuSE 8.2) | Any | Stored procedure declared variable used instead of column |
14347 | 2005-10-26 18:53 | 2022-12-04 20:45 | MySQL Server: Parser | Verified (5539 days) | S2 | 5.0.15, 5.0.74, 5.1.30, 6.0.9 | Linux (Linux Suse 10, Windows) | Any | Can't remove FOREIGN KEY |
24833 | 2006-12-05 18:34 | 2018-09-09 20:45 | MySQL Server: Parser | Verified (6283 days) | S3 | 5.0.26, 5.1 BK | Linux (Linux) | Any | QUICK option to DELETE lost in a multiple-table delete |
28902 | 2007-06-05 18:46 | 2022-12-04 20:45 | MySQL Server: Parser | Verified (5840 days) | S3 | 5.1 | Any | Any | Strange: CREATE TEMPORARY TABLE <not existing database>.t1 is successful |
38583 | 2008-08-05 19:41 | 2022-12-04 20:45 | MySQL Server: Parser | Verified (5643 days) | S3 | 5.0.51b-community-nt MySQL Community Edi | Windows | Any | Parser error messages are meaningless. |
41235 | 2008-12-04 16:41 | 2022-12-04 20:45 | MySQL Server: Parser | Verified (5594 days) | S3 | 5.1.29, 4.1, 5.0, 5.1, 6.0 bzr | Any (Mac OS X, Linux) | Any | Using * and a function in a SELECT can cause a SQL syntax error (ERROR 1064) |
50510 | 2010-01-21 15:23 | 2022-12-04 20:45 | MySQL Server: Parser | Verified (5181 days) | S3 | 5.0+, 5.1+, 6.0-codebase | Any | Any | invalid double LIMIT clause is accepted |
52088 | 2010-03-16 12:14 | 2022-12-04 20:45 | MySQL Server: Parser | Verified (5015 days) | S3 | 5.1.49-bzr | Any (Debian Squeeze 32-bit/Ubuntu 9.10 .deb package, Windows XP) | Any | Comments are sometimes incorrectly parsed as column names in results view |
52421 | 2010-03-28 22:31 | 2022-12-04 20:45 | MySQL Server: Parser | Verified (5114 days) | S3 | 5.1.32, 5.1.43 | Any | Any | DECIMAL type given with decimals doesn't return an error. |
32432 | 2007-11-16 10:55 | 2012-05-18 20:19 | MySQL Server: Parser | Patch pending (5965 days) | S2 | 5.1.23 | Any | Any | ALTER TABLE does not accept the ENGINE and PARTITION clauses together |
34564 | 2008-02-14 19:20 | 2022-12-04 20:45 | MySQL Server: Parser | Verified (5849 days) | S3 | 5.1.22-rc-log | Any | Any | CAST does not accept varchar type |
34629 | 2008-02-17 20:35 | 2022-12-04 20:45 | MySQL Server: Parser | Verified (5884 days) | S3 | 5.0.45 | Any | Any | CHANGE MASTER TO doesn't permit quoted values |
36140 | 2008-04-16 14:00 | 2022-12-04 20:45 | MySQL Server: Parser | Verified (5825 days) | S3 | 5.0.60 and up | Any | Any | Inconsistent synonymy of USING and TYPE for index creation |
36161 | 2008-04-16 22:44 | 2018-09-09 20:45 | MySQL Server: Parser | Verified (5825 days) | S3 | 5.0 and 5.1 | Any | Any | Subquery in FROM clause accepts invalid syntax of LIMIT |
36219 | 2008-04-20 3:16 | 2022-12-04 20:45 | MySQL Server: Parser | Verified (5643 days) | S3 | 5.0.51a.community-nt | Windows (Vista 64) | Any | CREATE TABLE: wrong error message |
36633 | 2008-05-09 17:52 | 2011-02-16 23:43 | MySQL Server: Parser | Verified (5801 days) | S3 | 5.0 and up | Any | Any | MICROSECOND accepted, SQL_TSI_MICROSECOND not accepted |
46641 | 2009-08-11 0:54 | 2022-12-04 20:45 | MySQL Server: Parser | Verified (5338 days) | S3 | 5.1.36/5.4 | Any | Any | Unclear warning message 'Warning: 1292: Truncated incorrect DOUBLE value: ___' |
46833 | 2009-08-20 13:20 | 2022-12-04 20:45 | MySQL Server: Parser | Verified (5317 days) | S3 | 5.4 | Any | Any | SHOW ENGINE ALL exist in code but are not documented |
46968 | 2009-08-28 5:14 | 2022-12-04 20:45 | MySQL Server: Parser | Verified (5327 days) | S3 | 5.1.39, 6.0.12, next bzr | Any | Any | 'Incorrect information in file' with partitioned table created with ANSI_QUOTES |
83475 | 2016-10-21 8:17 | 2016-10-26 9:29 | MySQL Server: Parser | Verified (2711 days) | S2 | 5.6.32 | Linux | Any | filter in select query works incorrectly |
83608 | 2016-10-29 10:51 | 2016-10-29 12:15 | MySQL Server: Parser | Verified (2708 days) | S3 | 5.5, 5.6, 5.7 | Any | Any | Assertion `m_cpp_buf <= pt r && ptr <= m_cpp_buf + m_buf_length' failed |
83921 | 2016-11-22 20:33 | 2017-01-04 7:22 | MySQL Server: Parser | Verified (2641 days) | S3 | 5.7.16 | CentOS (7) | Any | falsely Ambigous Column in On Duplicate Key Update using a subselect |
88337 | 2017-11-02 17:52 | 2017-11-03 10:09 | MySQL Server: Parser | Verified (2338 days) | S3 | 5.5.53-0ubuntu0.14.04.1-log | Ubuntu (14.04.5) | Any | mod result differs between hex and decimal values |
88450 | 2017-11-12 11:09 | 2017-11-12 13:34 | MySQL Server: Parser | Verified (2329 days) | S3 | 5.5/5.6/5.7/8.0 | Any | Any | Multiple DISTINCTs are allowed |
81309 | 2016-05-04 11:58 | 2022-09-04 20:45 | MySQL Server: Parser | In progress (2884 days) | S3 | 5.7.11 | Any | Any | Keywords UTC_DATE, UTC_TIME, UTC_TIMESTAMP should be non-reserved |
82317 | 2016-07-22 7:42 | 2018-07-18 8:55 | MySQL Server: Parser | Verified (2807 days) | S3 | 5.5.49 | Any (v14.04.1) | Any | Unrelevant error message: Unknown column in 'having' clause |
82735 | 2016-08-26 0:32 | 2016-08-26 8:41 | MySQL Server: Parser | Verified (2772 days) | S3 | 5.6.31, 5.6.32 | Any | Any | Fractional seconds ignored in view definitions |
83256 | 2016-10-04 16:17 | 2016-10-04 16:51 | MySQL Server: Parser | Verified (2733 days) | S3 | 5.5/5.6/5.7 | Red Hat (rhel6) | Any | date in multi-column IN clause with multi-values clause is parsed incorrectly |
98521 | 2020-02-08 11:21 | 2020-02-20 6:29 | MySQL Server: Parser | Verified (1501 days) | S3 | 8.0.18, 5.7.29, 8.0.19 | Any | Any | Core client cannot send any query with commentary characters in hints |
99343 | 2020-04-24 6:03 | 2021-05-31 8:36 | MySQL Server: Parser | Verified (1435 days) | S2 | 8.0.19, 5.7.29, 8.0.25 | Any | Any | Selecting with generated column gets the wrong result |
99382 | 2020-04-28 7:34 | 2020-04-29 8:13 | MySQL Server: Parser | Verified (1430 days) | S1 | 5.7, 8.0 | Any | Any | Complex nested views take up a lot of memory |
87726 | 2017-09-11 13:44 | 2017-09-11 22:19 | MySQL Server: Parser | Verified (2391 days) | S3 | 5.7.7/8.0 | Debian | Any | Error 1142 when creating view with subquery without having a default schema |
94344 | 2019-02-15 11:35 | 2019-02-18 16:35 | MySQL Server: Parser | Verified (1866 days) | S3 | 5.7.25 | Any | Any | `SHOW TRIGGERS LIKE` doesn't correctly interpret the underscore symbol (`_`) |
73277 | 2014-07-11 13:23 | 2014-07-15 13:55 | MySQL Server: Parser | Verified (3545 days) | S3 | 5.537-35.1-log, 5.0.97, 5.1.74, 5.5.39, 5.6.21, 5.7.5 | Any | Any | REGEXP escape of - not escaped properly in character group |
73590 | 2014-08-14 17:56 | 2016-04-07 13:54 | MySQL Server: Parser | Verified (3514 days) | S3 | 5.5.26 5.6.19 | Any | Any | MySQL returns "ERROR 1046 (3D000): No database selected" when executing "Update |
77941 | 2015-08-05 3:28 | 2015-08-05 7:21 | MySQL Server: Parser | Verified (3159 days) | S3 | 5.7.8 | Any | Any | HA_CREATE_USED_COMPRESS is defined but not used |
78395 | 2015-09-10 11:46 | 2015-09-14 11:53 | MySQL Server: Parser | Verified (3122 days) | S3 | 5.6.22, 5.1.77, 5.5.46, 5.6.26, 5.7.9 | Any | Any | Get "Unknown column 'c1' in 'having clause' " when c1 is a valid column |
78404 | 2015-09-11 9:11 | 2015-09-11 9:41 | MySQL Server: Parser | Verified (3122 days) | S3 | 5.6.22, 5.6.26 | Any | Any | subquery + "select * from...order by 2" (2 cols) fails with unknown column '2' |
78879 | 2015-10-20 6:23 | 2022-09-04 20:45 | MySQL Server: Parser | Verified (3083 days) | S3 | 5.6.23, 5.6.27, 5.5.47 | Linux | Any | LIKE and '<' should have same precedence according the document. |
79350 | 2015-11-20 7:44 | 2015-11-20 11:47 | MySQL Server: Parser | Verified (3052 days) | S3 | 5.7.9 | Any | Any | Allow SHOW in the Rewriter plugin |
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 |
75700 | 2015-01-30 12:40 | 2015-01-30 17:32 | MySQL Server: Parser | Verified (3346 days) | S3 | mysql Ver 14.14 Distrib 5.1.73 | Linux (Centos 2.6.32-358.el6.x86_64) | Any | Cannot create MySQL database with name '5e370227_db' |
75777 | 2015-02-05 0:47 | 2015-02-06 15:45 | MySQL Server: Parser | Verified (3339 days) | S3 | 5.6, 5.6.22 | Any | Any | SELECT FROM DUAL PROCEDURE ANALYSE() returns syntax error |
68286 | 2013-02-06 5:42 | 2019-04-13 13:10 | MySQL Server: Parser | Verified (4069 days) | S3 | 5.1, 5.5(.29), 2.6.7 | Windows (probably any) | Any | Cannot change FK constraint settings |
68370 | 2013-02-13 18:23 | 2013-02-13 20:07 | MySQL Server: Parser | Verified (4062 days) | S3 | 5.5 | Any | Any | ENUM with NOT NULL, allows NULL / empty string |
68676 | 2013-03-14 21:25 | 2021-08-10 16:42 | MySQL Server: Parser | Verified (4028 days) | S3 | 5.5.30, 5.0.97, 5.1.70, 5.5.32, 5.6.12, 5.7.2 | Linux | Any | Escaping backslash in identifier name |
68699 | 2013-03-18 1:07 | 2013-03-18 5:20 | MySQL Server: Parser | Verified (4029 days) | S3 | 5.5.29 | Any | Any | Unit parsing problem |
68832 | 2013-04-02 11:04 | 2013-04-26 13:59 | MySQL Server: Parser | Verified (3990 days) | S2 | 5.1.70 | Linux (RHEL6) | Any | Daylight Saving time and interval |
68902 | 2013-04-09 12:16 | 2013-04-09 17:02 | MySQL Server: Parser | Verified (4007 days) | S3 | 5.1, 5.5, 5.0.97, 5.1.70, 5.5.32, 5.6.12, 5.7.1 | Any | Any | Duplicate table aliases |
68920 | 2013-04-10 16:09 | 2013-06-03 16:40 | MySQL Server: Parser | Verified (4005 days) | S3 | 5.5.29 | Any | Any | Inconsistent ordering with column alias in expression |
69208 | 2013-05-13 5:22 | 2013-05-20 7:56 | MySQL Server: Parser | Verified (3966 days) | S3 | any | Any | Any | A typo in sql_yacc.yy leads to possibility of creation valid nonsense queries |
69374 | 2013-06-01 6:49 | 2014-08-31 5:24 | MySQL Server: Parser | Verified (3498 days) | S2 | 5.6 | Any | Any | User Variable not updating properly in some cases |
69836 | 2013-07-25 9:30 | 2013-07-25 13:02 | MySQL Server: Parser | Verified (3900 days) | S3 | 5.5 | Any | Any | Query returns a strange column name (with the comments) |
69929 | 2013-08-05 18:19 | 2016-02-25 12:24 | MySQL Server: Parser | Verified | S3 | 5.6.13 | Any | Any | Remove support for COM_PROCESS_INFO |
80559 | 2016-02-29 14:32 | 2016-02-29 15:17 | MySQL Server: Parser | Verified (2951 days) | S3 | 5.7.11 | Any | Any | EXPLAIN CREATE TABLE .. AS SELECT .. does not work |
65360 | 2012-05-18 14:12 | 2014-08-21 19:20 | MySQL Server: Parser | Verified (4333 days) | S3 | 5.1.61, 5.5.23 | Any | Any | Update does not work with double-nested queries without default database |
103665 | 2021-05-12 5:48 | 2021-05-14 6:09 | MySQL Server: Parser | Verified (1052 days) | S3 | 8.0.23, 5.7.34, 8.0.24 | Any | Any | The aliases interferes despite the fact that the database is specified |
105004 | 2021-09-22 10:20 | 2024-02-22 19:27 | MySQL Server: Parser | Verified (918 days) | S2 | 8.0.26 | Any | Any | mysql 8.0 parser consuming more memory than 5.7 for similar query |
105990 | 2021-12-28 8:37 | 2021-12-28 9:45 | MySQL Server: Parser | Verified (822 days) | S2 | 8.0/5.6/5.7 | Any | Any | Contribution by Tencent: parse ending of SP error |
112729 | 2023-10-15 11:20 | 2023-10-16 6:13 | MySQL Server: Parser | Verified (165 days) | S3 | 8.1.0 | Any | Any | Two single quotes escaping inconsistency in index expression |
100375 | 2020-07-30 6:16 | 2023-03-10 13:25 | MySQL Server: Parser | Verified (1337 days) | S3 | 5.7.31, 5.6.48 | Any | Any | Column name cannot be parsed inside COS function |
107109 | 2022-04-24 9:07 | 2023-04-14 13:24 | MySQL Server: Parser | Verified (662 days) | S2 | 8.0.27, 5.7.37, 8.0.32 | Any (rhel-7.4) | Any (x86-64) | Optimizer hints doesn't work if client charset is the same with charset of syste |
110488 | 2023-03-24 7:52 | 2023-03-24 9:17 | MySQL Server: Parser | Verified (371 days) | S3 | all, 8.0 | CentOS (7.x) | x86 (64bit) | pound sign can not included in qb_name hint |
110562 | 2023-03-30 8:05 | 2023-04-18 21:01 | MySQL Server: Parser | Verified (350 days) | S2 | 8.0.32 | Windows (11) | x86 (64bit) | values statement |
111892 | 2023-07-26 6:52 | 2023-11-13 10:14 | MySQL Server: Parser | Verified (246 days) | S3 | 8.1 | Any | Any | Two single quotes escaping inconsistency |
113887 | 2024-02-04 2:12 | 2024-02-05 13:07 | MySQL Server: Parser | Verified (53 days) | S3 | 8.0 | Any | Any | MySQL fails to execute query if a subquery refer to a column of parent table |
113949 | 2024-02-09 19:55 | 2024-02-12 9:16 | MySQL Server: Parser | Verified (46 days) | S3 | 8.3.0, 8.0.36 | Any | Any | Backslash escaping inconsistency in LIKE operator |
113726 | 2024-01-23 14:31 | 2024-01-23 15:16 | MySQL Server: Packaging | Verified (66 days) | S3 | 8.4.0 | Any | Any | Contribution: Add support for specifying a .cnf file and a linux user |
112949 | 2023-11-03 7:25 | 2023-12-15 14:46 | MySQL Server: Packaging | Verified (105 days) | S3 | 8.2.0 | Any | Any (RHEL rpms) | missing mysql-community-libs-compat rpms for 8.2.0 |
101233 | 2020-10-19 19:06 | 2020-10-20 6:33 | MySQL Server: Packaging | Verified (1256 days) | S3 | 8.0 | Debian | ARM | Debian APT repository missing aarch64/arm64 packages |
94154 | 2019-01-31 15:14 | 2019-04-15 11:18 | MySQL Server: Packaging | Verified (1884 days) | S3 | Any | Any | Contribution: Updated mysqld_multi script to be able to pass custom paramet ... | |
96167 | 2019-07-11 2:50 | 2019-07-11 5:39 | MySQL Server: Packaging | Verified (1723 days) | S3 | 8.0 | Any | Any | Many header files now missing from devel package |
85778 | 2017-04-04 11:39 | 2017-04-07 12:07 | MySQL Server: Packaging | Verified (2548 days) | S2 | 5.6+ | Ubuntu (ver 14.04) | Any | Custom apparmor profile not correctly replaced if user agrees to replace cnf |
97768 | 2019-11-25 9:16 | 2021-12-10 9:21 | MySQL Server: Packaging | Verified (1585 days) | S2 | 8.0.18 | Ubuntu (18.04.3) | x86 | Adding 2 apparmor rules for mysql from apt repo for using huge page not failed |
59160 | 2010-12-24 16:29 | 2012-06-10 20:45 | MySQL Server: Packaging | Verified (4844 days) | S3 | Windows | Any | packages - src suffix used in an incoherent way | |
61584 | 2011-06-21 11:54 | 2012-06-10 20:45 | MySQL Server: Packaging | Verified (4665 days) | S3 | 5.5.13 | Windows (XP SP2 JP) | Any | installing server only will still setup shortcut for cmdline client |
70985 | 2013-11-23 8:24 | 2013-12-05 13:35 | MySQL Server: Packaging | Verified (3769 days) | S3 | 5.6.14 | Any | Any | mysql-community-server should not depend on mysql-community-client |
77646 | 2015-07-08 0:27 | 2016-10-14 12:02 | MySQL Server: Packaging | Verified (3187 days) | S3 | Any | Any | SUSE patches we keep against 5.6 (contribution) | |
77703 | 2015-07-13 15:49 | 2015-07-14 4:11 | MySQL Server: Packaging | Verified (3181 days) | S3 | Any | Any | Update README (contribution) | |
79996 | 2016-01-15 1:16 | 2016-01-15 6:03 | MySQL Server: Packaging | Verified (2996 days) | S3 | All | Any | Any | Suggest to add a "--numanode" option to mysqld_safe scripts |
74651 | 2014-10-31 15:19 | 2016-05-20 8:31 | MySQL Server: Packaging | Verified (3432 days) | S3 | 5.6/5.7 | Linux (CentOS 6) | Any | mysql-community rpms uninstall followed by reinstall changes /etc/my.cnf |
76042 | 2015-02-25 8:45 | 2015-02-25 15:46 | MySQL Server: Packaging | Verified (3320 days) | S3 | 5.6.23 | Linux (OL6.4) | Any | mysqld_multi.server was not included in Package mysql-community-server.rpm |
74729 | 2014-11-07 10:19 | 2014-11-07 10:46 | MySQL Server: Options | Verified (3430 days) | S3 | 5.6.20-debug, 5.6.22, 5.7.6 | Linux (CentOS 7) | Any | assertion:mode == BUF_GET_POSSIBLY_FREED || !fix_block->page.file_page_was_freed |
74730 | 2014-11-07 10:23 | 2017-08-13 23:25 | MySQL Server: Options | Verified (3430 days) | S3 | 5.6.20-debug, 5.6.22, 5.7.6 | Linux (CentOS 7) | Any | Assertion failure in fil0fil.cc line 5594 | abort sig 6 in fil/fil0fil.cc:5594 |
74732 | 2014-11-07 12:13 | 2015-04-08 7:17 | MySQL Server: Options | Verified (3430 days) | S3 | 5.6.21 | Windows (W7) | Any | init_file use in windows needs ";" terminator |
74871 | 2014-11-14 18:45 | 2014-11-15 5:50 | MySQL Server: Options | Verified (3422 days) | S3 | 5.5.40, 5.5.42, 5.6.23 | Linux | Any | max_seeks_for_key default value is invalid when used in cnf |
75286 | 2014-12-22 12:23 | 2014-12-22 14:56 | MySQL Server: Options | Verified (3385 days) | S3 | 5.7.5, 5.6.22 | Any | Any | server accepts garbage port |
76270 | 2015-03-11 22:56 | 2016-06-18 21:24 | MySQL Server: Options | Verified (3305 days) | S3 | 5.7.6, 8.0.0 | Any | Any | Consider improving startup mysql startup NO_AUTO_CREATE_USER warning message |
71081 | 2013-12-04 23:50 | 2016-02-25 12:24 | MySQL Server: Options | Verified | S3 | 5.7.3 | Any | Any | Need status variable for COM_RESET_CONNECTION |
71194 | 2013-12-20 20:33 | 2013-12-24 13:53 | MySQL Server: Options | Verified (3752 days) | S3 | 5.5.35, 5.6.16 | Linux | Any | mysqld daemon should check if any process uses the socket file before removing |
71309 | 2014-01-06 22:44 | 2015-01-28 23:04 | MySQL Server: Options | Verified (3734 days) | S3 | 5.6.14-enterprise-commercial-advanced-log, 5.6.15 | Linux (Red Hat Enterprise Linux Server release 5.6 (Tikanga)) | Any | Not able to customize mysql prompt with new line and tab options |
71367 | 2014-01-14 2:01 | 2014-01-14 6:03 | MySQL Server: Options | Verified (3727 days) | S3 | 5.6 | Any | Any | speficied is not a word, though it sounds cool |
71477 | 2014-01-25 12:10 | 2014-01-27 15:11 | MySQL Server: Options | Verified (3714 days) | S3 | 5.6.15 | Any | Any | transaction_allow_batching is available in non-Cluster MySQL Server 5.6 |
71479 | 2014-01-25 15:32 | 2014-01-30 14:23 | MySQL Server: Options | Verified (3714 days) | S3 | 5.6 | Windows (Win64) | Any | sort_buffer_size is limited to 4GB-1 on 64-bit Windows |
71602 | 2014-02-06 9:10 | 2017-08-23 10:47 | MySQL Server: Options | Verified (3703 days) | S3 | 5.6.15 | Any | Any | Unexpected option file read from basedir |
71852 | 2014-02-27 6:34 | 2015-04-18 22:06 | MySQL Server: Options | Verified (3677 days) | S3 | 5.6.16, 5.6.17 | Linux | Any | ULONG_MAX capable sys vars could not set in my.cnf |
71853 | 2014-02-27 6:37 | 2014-03-05 12:01 | MySQL Server: Options | Verified (3677 days) | S3 | 5.6.16, 5.6.17 | Linux | Any | eval_num_suffix return overflowed/underflowed value |
71960 | 2014-03-06 23:57 | 2017-12-23 10:39 | MySQL Server: Options | Verified (3269 days) | S1 | 5.6.16, 5.6.20 | MacOS (10.8) | Any | Mysql 5.6.16 on OSX throws connection errors with innodb_file_per_table option |
72019 | 2014-03-12 12:13 | 2014-03-31 14:21 | MySQL Server: Options | Verified (3651 days) | S3 | any | Any | Any | Is my server 32 bit or 64 bit? |
72429 | 2014-04-23 8:30 | 2014-04-28 6:32 | MySQL Server: Options | Verified (3625 days) | S3 | 5.5 , 5.6 | Any (options ignored, option handling intransparent ) | Any | handling of options, expire logs |
72583 | 2014-05-08 18:32 | 2014-05-08 19:03 | MySQL Server: Options | Verified (3613 days) | S3 | 5.6.17 | Any | Any | SQL Mode shows deprecated settings even when not used |
72587 | 2014-05-09 1:40 | 2014-05-09 11:12 | MySQL Server: Options | Verified (3612 days) | S3 | MySQL 5.6.17 | Any | Any | innodb-buffer-pool-instances gives a warning when set to -1 |
72626 | 2014-05-13 2:34 | 2014-05-13 6:47 | MySQL Server: Options | Verified (3608 days) | S3 | 5.6.17, 5.6.19 | Any | Any | innodb_open_files gives a warning when set to -1 |
73119 | 2014-06-25 20:38 | 2014-06-26 7:14 | MySQL Server: Options | Verified (3564 days) | S3 | 5.5.36, 5.5.38 | Any | Any | create temporary table ... select fails on read-only slave |
73435 | 2014-07-30 12:27 | 2014-07-30 12:33 | MySQL Server: Options | Verified | S3 | 5.6.21 | Any | Any | innodb_api_enable_binlog is not recognized when used on the mysqld command line |
74211 | 2014-10-03 11:29 | 2024-02-06 9:33 | MySQL Server: Options | Verified (52 days) | S3 | 5.6.14, 5.7, 8.0 | Any | Any | No upgrade path for explicit_defaults_for_timestamp = 1 |
74228 | 2014-10-05 13:22 | 2014-10-07 11:13 | MySQL Server: Options | Verified (3462 days) | S3 | 5.5, 5.6 | Any | Any | Description of autoincrement behavior if offset > increment needs clarification |
74246 | 2014-10-07 8:04 | 2014-10-07 9:11 | MySQL Server: Options | Verified (3461 days) | S3 | 5.7, 5.6.22, 5.7.6 | Any | Any | SET: Semantic behavior different for regular execution and function |
74482 | 2014-10-21 12:42 | 2014-10-25 8:44 | MySQL Server: Options | Verified (3447 days) | S3 | 5.5.38 | Linux | Any | A # character cannot be represented in MySQL .ini files |
74551 | 2014-10-24 15:11 | 2014-10-25 17:21 | MySQL Server: Options | Verified (3443 days) | S3 | 5.6.21 | Linux | Any | Dots in file names of configuration files |
63452 | 2011-11-28 5:59 | 2011-12-05 8:19 | MySQL Server: Options | Verified (4505 days) | S3 | 5.5.18 | Any | Any | Show currently used my.ini/mycnf directory location |
63685 | 2011-12-08 21:38 | 2017-01-05 14:54 | MySQL Server: Options | Verified (4494 days) | S3 | 5.5.19 | Any (Mac OS X, Vista 32-bit Home Premium) | Any | MySQL does not recognize timezone offset UTC +14:00 |
63718 | 2011-12-11 18:45 | 2011-12-14 10:30 | MySQL Server: Options | Verified (4491 days) | S3 | 5.1.41, 5.1.61 | Any | Any | Unable to increase ft_max_word_len variable |
63989 | 2012-01-11 8:41 | 2012-01-19 12:06 | MySQL Server: Options | Verified (4461 days) | S3 | 5.5 | Linux | Any | innodb_buffer_pool_size with 128M default is too large |
64243 | 2012-02-06 19:18 | 2012-02-09 12:08 | MySQL Server: Options | Verified (4435 days) | S2 | any | Any | Any | Database where log tables are written should be configurable |
64347 | 2012-02-16 6:01 | 2012-02-16 16:35 | MySQL Server: Options | Verified (4425 days) | S3 | 5.1.52, 5.1.62, 5.5.22 | Any | Any | lower_case_table_names and my_database_names_init |
64666 | 2012-03-15 23:47 | 2012-03-20 7:44 | MySQL Server: Options | Verified (4396 days) | S2 | 5.1,5.5,5.6 | Any | Any | MySQL discards fractional part of the default values of system |
65122 | 2012-04-26 19:08 | 2012-04-26 19:49 | MySQL Server: Options | Verified (4355 days) | S1 | 5.5.24 | Any | Any | Fix for ipv4/ipv6 hostnames is incorrect |
65333 | 2012-05-16 13:03 | 2012-05-21 11:28 | MySQL Server: Options | Verified (4334 days) | S3 | 5.x | Any | Any | option --safe-user-create and sql_mode NO_AUTO_CREATE_USER should be dependent |
65343 | 2012-05-16 20:13 | 2012-05-21 11:31 | MySQL Server: Options | Verified (4334 days) | S3 | any | Any | Any | Please expose --skip-grant-tables as a variable |
65711 | 2012-06-22 13:30 | 2012-06-25 6:24 | MySQL Server: Options | Verified (4298 days) | S3 | 5.5.25, 5.5.26, 5.6.5 | Any | Any | Server crashes in intern_plugin_lock on concurrent install plugin / set variable |
65732 | 2012-06-26 8:43 | 2012-07-05 14:56 | MySQL Server: Options | Verified (4285 days) | S3 | Any | Any | Session variable late value acessment | |
66884 | 2012-09-20 3:16 | 2017-01-09 18:04 | MySQL Server: Options | Verified (4077 days) | S3 | 5.5, 5.0.97, 5.1.69, 5.5.31, 5.7.1 | Linux (I only test it on ubuntu 11.10) | Any | SERVER_STATUS is always inited with SERVER_STATUS_AUTOCOMMIT=1 |
66893 | 2012-09-20 14:34 | 2013-01-31 11:12 | MySQL Server: Options | Verified (4208 days) | S3 | 5.5+ | Windows | Any | Minimum value for table-open-cache |
67422 | 2012-10-30 13:50 | 2015-01-07 19:03 | MySQL Server: Options | Verified | S3 | 5.5.28 | Linux | Any | mysqld fails to switch DNS resolver if thread_cache_size > 0 |
79509 | 2015-12-03 14:33 | 2018-01-03 19:56 | MySQL Server: Options | Verified (3039 days) | S3 | 5.7.10, 5.7.18, 5.7.20 | Any | Any | Bad tls_version values are not rejected |
79558 | 2015-12-08 16:29 | 2018-01-03 13:50 | MySQL Server: Options | Verified (2814 days) | S2 | 5.7.10 | Any | Any | tls_version accepts invalid arguments |
79608 | 2015-12-11 18:36 | 2015-12-13 14:28 | MySQL Server: Options | Verified (3029 days) | S3 | 5.1+, 5.7.10 | Any | Any | mysqld_safe mishandles UMASK |
80312 | 2016-02-09 8:14 | 2016-02-09 8:23 | MySQL Server: Options | Verified (2971 days) | S3 | 5.7.11 | CentOS (6.6) | Any | maximum_query_cache_size cannot be set |
80419 | 2016-02-18 0:38 | 2016-02-18 8:04 | MySQL Server: Options | Verified (2962 days) | S3 | Any | Any | thr_lock: Only set stack size when stack size is < 64k (contribution) | |
80668 | 2016-03-09 7:27 | 2016-03-16 2:56 | MySQL Server: Options | Verified (2936 days) | S3 | 5.7.10, 5.7.11 | CentOS | Any | InnoDB: Failing assertion: !m_fatal in in file ut0ut.cc line 938 |
80690 | 2016-03-10 14:50 | 2016-03-14 8:30 | MySQL Server: Options | Verified | S3 | 5.6.27 | Windows | Any | !include directive is ignored in my.cnf if it is last line in file |
80949 | 2016-04-04 20:41 | 2016-04-05 8:20 | MySQL Server: Options | Verified (2915 days) | S3 | 5.7. 5.7.11, 5.6.29 | Any | Any | When setting a boolean variable values less than 0 are allowed |
81130 | 2016-04-18 15:46 | 2016-04-18 19:48 | MySQL Server: Options | Verified (2902 days) | S3 | 5.7.12 | Any | Any | master_info_file is not listed in 'show global variables'; |
77436 | 2015-06-22 14:55 | 2015-06-23 10:44 | MySQL Server: Options | Verified (3202 days) | S2 | 5.6.23, 5.6.26 | Linux | Any | procs_priv table not restored with sql_mode traditional and only_full_group_by |
77781 | 2015-07-19 20:35 | 2015-07-20 18:47 | MySQL Server: Options | Verified (3175 days) | S3 | 5.6 | Any | Any | No alternative for max_long_data_size in 5.6 |
77976 | 2015-08-07 9:08 | 2017-09-22 14:37 | MySQL Server: Options | Verified (2380 days) | S3 | 5.6.23, 5.6.26, 5.6.37 | CentOS (CentOS 7) | Any | InnoDB: Failing assertion: event in file os0sync.cc line 419 |
78238 | 2015-08-27 5:09 | 2016-11-24 12:11 | MySQL Server: Options | Verified (3128 days) | S1 | 5.6, 5.7.8 (RC2), 5.7.9 | Any | Any | --query-alloc-block-size issues with numerous different crash examples |
68963 | 2013-04-15 17:23 | 2018-12-10 9:50 | MySQL Server: Options | Verified (4000 days) | S3 | 5.6.10 and earlier | Any | Any | SHOW GLOBAL STATUS Threads_running may be misleading |
69226 | 2013-05-14 10:31 | 2018-02-06 13:52 | MySQL Server: Options | Verified (2243 days) | S3 | 5.6.11,5.7.21,8.0.4 | Any | Any | Status variable for SSL/TLS implementation |
69244 | 2013-05-15 13:28 | 2013-05-16 4:50 | MySQL Server: Options | Verified (3970 days) | S3 | 5.6.11 | Any | Any | Documentation and code inconsistent wrt. back_log |
69295 | 2013-05-21 16:22 | 2013-05-22 9:04 | MySQL Server: Options | Verified (3964 days) | S3 | 5.1.44, 5.6.10 | Any | Any | Slow_queries status variable incremented when it should not |
69314 | 2013-05-24 21:33 | 2013-05-25 7:57 | MySQL Server: Options | Verified (3961 days) | S3 | 5.7.1 | Any | Any | ignore-db-dir option doesn't work for databases with an * in the name |
69515 | 2013-06-19 14:55 | 2013-06-19 15:11 | MySQL Server: Options | Verified (3936 days) | S3 | 5.1, 5.5, 5.6, 5.7 | Any | Any | group_concat_max_len >= 4Gb does not work |
69682 | 2013-07-05 22:12 | 2013-07-11 16:59 | MySQL Server: Options | Verified (3914 days) | S3 | 5.6.12 | Any | Any | mysqld crashes after uninstall of plugin with "first" status var |
69704 | 2013-07-09 23:26 | 2013-07-10 5:36 | MySQL Server: Options | Verified (3915 days) | S3 | 5.5.32, 5.6.12 | Any | Any | Strangeness with max_binlog_stmt_cache_size Settings |
69976 | 2013-08-09 19:44 | 2015-06-05 7:07 | MySQL Server: Options | Verified (3363 days) | S3 | 5.6.13 | Any | Any | No deprecation warning on innodb_stats_sample_pages |
69997 | 2013-08-12 15:19 | 2013-08-15 22:49 | MySQL Server: Options | Verified (3879 days) | S3 | any. | Any | Any | Please expose skip-character-set-client-handshake as a variable |
70008 | 2013-08-13 5:35 | 2018-05-23 6:26 | MySQL Server: Options | Verified (3769 days) | S3 | all (up to 5.7.1) | Any (n/a) | Any | use tx_isolation for startup/my.cnf parameter settings for consistency |
70036 | 2013-08-14 17:22 | 2014-06-06 13:29 | MySQL Server: Options | Verified (3584 days) | S3 | 5.6.13 | MacOS (10.6) | Any | character-set-client option ignored in my.cnf |
98332 | 2020-01-23 7:12 | 2021-01-16 0:52 | MySQL Server: Options | Verified (1526 days) | S3 | 8.0.19 | Any | Any | partial_revokes=1 disables wildcard database grants |
99187 | 2020-04-06 7:14 | 2020-04-06 7:28 | MySQL Server: Options | Verified (1453 days) | S3 | 8.0.19 | Any | Any | PLUGIN_VAR_OPCMDARG is more better for innodb_dedicated_server |
81442 | 2016-05-16 22:12 | 2018-01-24 16:08 | MySQL Server: Options | Verified (2256 days) | S3 | 5.7.12,5.7.15,8.0.0,8.0.4-rc | Any | Any | Unable to analyze table whilst super_read_only is enabled |
81649 | 2016-05-30 23:33 | 2016-05-31 11:55 | MySQL Server: Options | Verified (2859 days) | S2 | 5.7.12 | Any | Any | [ERROR] Can't create interrupt-thread (error 11, errno: 12) |
81690 | 2016-06-02 13:55 | 2017-06-12 16:27 | MySQL Server: Options | Verified (2856 days) | S3 | 5.7.12 | Any | Any | executing prepared statements increases com_stmt_execute but also com_select |
82237 | 2016-07-15 3:15 | 2016-07-15 5:54 | MySQL Server: Options | Verified (2814 days) | S1 | 5.7.13, 5.6.31 | Any | Any | OPTIMIZER_SWITCH cannot be modified once a different collation is selected |
82414 | 2016-08-02 16:01 | 2016-08-02 16:21 | MySQL Server: Options | Verified (2796 days) | S3 | 5.7, 5.7.14 | Any | Any | Incorrect charset in INFORMATION_SCHEMA |
82577 | 2016-08-14 11:43 | 2016-08-15 5:58 | MySQL Server: Options | Verified (2783 days) | S3 | Any | Any | let variables in my.cnf specify percent of ram | |
84002 | 2016-11-29 9:33 | 2016-12-02 13:52 | MySQL Server: Options | Verified (2674 days) | S3 | 5.7, 5.6.34, 5.7.16 | Any | Any | Cannot override skip-name-resolve in my.cnf |
84081 | 2016-12-06 18:38 | 2021-11-09 15:27 | MySQL Server: Options | Verified (2667 days) | S3 | 5.7.14, 5.7.16 | Ubuntu | Any | super_read_only and read_only not allowing OPTIMIZE TABLE on 5.7 |
84085 | 2016-12-07 2:30 | 2016-12-09 6:54 | MySQL Server: Options | Verified (2667 days) | S3 | 5.7, 5.7.16 | Linux | Any | inconsistent states for system variables after PL routine finished |
85017 | 2017-02-16 10:22 | 2017-02-16 12:14 | MySQL Server: Options | Verified (2598 days) | S3 | 5.7 | Any | Any | Shouldn't'delayed_insert_timeout' variable be removed? |
85297 | 2017-03-03 17:04 | 2017-03-03 17:05 | MySQL Server: Options | Verified | S3 | 5.7+ | Any | Any | unreachable code in check_track_session_sys_vars |
88070 | 2017-10-12 7:17 | 2017-10-16 12:04 | MySQL Server: Options | Verified (2356 days) | S3 | 8.0.3 | Any | Any | Too limited compatibility options for transaction isolation |
88382 | 2017-11-07 9:13 | 2017-11-07 13:09 | MySQL Server: Options | Verified (2334 days) | S3 | 8.0.3 | Any | Any | Persisted configuration in mysqld-auto.cnf is not reflected in mysqld output |
89673 | 2018-02-14 17:57 | 2018-02-15 6:54 | MySQL Server: Options | Verified (2234 days) | S3 | 5.7, 5.7.9, 5.7.21 | Linux | Any | Default values showed by "--verbose --help" doesn't match with the documentation |
89741 | 2018-02-21 4:55 | 2018-02-21 8:03 | MySQL Server: Options | Verified (2228 days) | S3 | 5.6.39, 5.5.59 | Any | Any | Events log Note level messages even for log_warnings=0 |
90208 | 2018-03-24 14:59 | 2018-03-27 6:19 | MySQL Server: Options | Verified (2194 days) | S2 | 5.7.20, 5.7.21, 5.6.39 | Any | Any | option 'default(_tmp)_storage_engine' does not work as expected |
90394 | 2018-04-11 19:57 | 2018-04-12 12:21 | MySQL Server: Options | Verified (2178 days) | S3 | 5.7.21 | Any | Any | SSL session cache: hits/misses wrong and size hardcoded |
85799 | 2017-04-05 8:32 | 2017-04-05 12:50 | MySQL Server: Options | Verified (2550 days) | S3 | 5.7.1, 5.6.35, 5.7.17 | CentOS | Any | variable --master-info-file |
85940 | 2017-04-13 22:16 | 2017-05-07 1:17 | MySQL Server: Options | Verified (2518 days) | S3 | 5.6.36 | Debian | Any | MySQL 5.6.36 changes default sql_mode |
87657 | 2017-09-04 12:56 | 2017-09-05 14:13 | MySQL Server: Options | Verified (2397 days) | S3 | 5.7 | Any | Any | Trailing # comment on !includedir / !include directive causes error |
90939 | 2018-05-19 3:43 | 2018-05-21 6:07 | MySQL Server: Options | Verified (2139 days) | S3 | 5.6.39, 5.6.40 | Any | Any | ERROR 1238 (HY000): Variable 'explicit_defaults_for_timestamp' is a read only va |
90943 | 2018-05-20 14:42 | 2018-05-20 15:53 | MySQL Server: Options | Verified (2140 days) | S3 | 5.7/8.0 | Any | Any | Buffer pool size adjustment can cause crashes on small instance sizes |
91887 | 2018-08-03 10:29 | 2018-08-03 12:37 | MySQL Server: Options | Verified (2065 days) | S3 | 5.7.22, 8.0.13 | Any | Any | Redundant code around mysql_real_data_home_ptr in rpl_make_log_name() |
92032 | 2018-08-15 23:07 | 2018-10-02 12:03 | MySQL Server: Options | Verified (2051 days) | S3 | Any | Any | Restrict usage of session foreign_key_checks | |
92391 | 2018-09-12 15:55 | 2018-09-13 6:56 | MySQL Server: Options | Verified (2024 days) | S3 | 5.6.40 5.7.6, 5.6.41 | Red Hat | Any | read_only=1, non super user Create temporary as select from temp fails |
92958 | 2018-10-26 9:21 | 2018-11-20 14:30 | MySQL Server: Options | Verified (1960 days) | S3 | 5.7.22 | Debian | x86 | Event Creation not respecting SQL_MODE settings |
93851 | 2019-01-08 12:15 | 2019-01-09 7:57 | MySQL Server: Options | Verified (1906 days) | S3 | 5.7, not 8.0 | Any | Any | Buffer underflow in fix_paths |
94487 | 2019-02-27 8:17 | 2019-02-27 17:19 | MySQL Server: Options | Verified (1857 days) | S3 | 8.0, 5.6, 5.7 | Any | Any | Wrong default value for max_binlog_cache_size |
95261 | 2019-05-06 14:04 | 2019-06-14 12:33 | MySQL Server: Options | Verified (1788 days) | S3 | 8.0.15, 8.0.16 | Any | Any | innodb_undo_log_encrypt and innodb_redo_log_encrypt do not emit client warnings |
95985 | 2019-06-25 21:42 | 2019-06-25 22:31 | MySQL Server: Options | Verified (1739 days) | S3 | 5.7/8.0 | Ubuntu | x86 | SET GLOBAL on rbr_exec_mode fails |
95987 | 2019-06-25 23:21 | 2019-06-26 5:59 | MySQL Server: Options | Verified (1738 days) | S3 | 8.0.16, 5.7.26, 5.6.44 | Ubuntu | x86 | SET key_cache_* and key_buffer_* variables fails nondeterministically |
100283 | 2020-07-22 7:40 | 2020-07-22 10:19 | MySQL Server: Options | Verified (1346 days) | S2 | 5.7, 5.7.31 | Linux | Any | Super_read_only prevents myisam_recover_options from working |
101204 | 2020-10-16 10:12 | 2021-08-04 7:15 | MySQL Server: Options | Verified (1260 days) | S2 | 8.0 | Any | Any | innodb_dedicated_server sets incorrect number of log files if RAM < 2GB |
101238 | 2020-10-20 10:22 | 2020-10-20 11:14 | MySQL Server: Options | Verified (1256 days) | S3 | 8.0.21, 5.7.31 | Any | Any | table_open_cache adjustment doesn't kick in when changed dynamically |
101469 | 2020-11-05 4:53 | 2020-11-05 10:38 | MySQL Server: Options | Verified (1240 days) | S3 | 8.0.21, 8.0.22, 5.7.32 | Any | Any | skip_name_resolve does not take effect |
102005 | 2020-12-16 6:50 | 2020-12-16 7:51 | MySQL Server: Options | Verified (1199 days) | S3 | 8.0.22, 5.7, 5.7.32 | Any | Any | Session tracker not reset itself when error affect next statement |
113978 | 2024-02-13 18:38 | 2024-02-14 9:25 | MySQL Server: Options | Verified (44 days) | S3 | 8.0.35, 8.0.36 | Any | Any | Set admin_port in port being used does not throw error |
102327 | 2021-01-21 7:45 | 2021-01-21 9:34 | MySQL Server: Options | Verified (1163 days) | S3 | 8.0.23 | Any | Any | Possible memory leaks in mysqld |
102328 | 2021-01-21 8:58 | 2021-01-21 9:54 | MySQL Server: Options | Verified (1163 days) | S3 | 5.6, 5.7, 8.0, 5.7.33, 8.0.23 | Any | Any | Range of innodb_ft_sort_pll_degree error |
104066 | 2021-06-21 7:00 | 2023-11-24 13:22 | MySQL Server: Options | Verified (1012 days) | S3 | 8.0.23, 8.0.25 | Linux | Any | Inconsistency of description for default_collation_for_utf8mb4 |
105016 | 2021-09-23 9:03 | 2021-09-23 13:24 | MySQL Server: Options | Verified (918 days) | S3 | 8.0.25, 8.0.26, 5.7.35 | Linux | Any | create user with max_user_connections ,it save as Unexpected data |
105442 | 2021-11-03 13:05 | 2021-11-03 14:19 | MySQL Server: Options | Verified (877 days) | S3 | 5.7 | Any | Any | Contribution: Fix memory leak when host_cache_size is 0. |
105570 | 2021-11-15 8:53 | 2021-11-15 9:01 | MySQL Server: Options | Verified (865 days) | S2 | 8.0.25, 8.0.27, 5.7.36 | Any | Any | Dynamic setting variable innodb_buffer_pool_load_abort cannot take effect |
105933 | 2021-12-19 8:11 | 2021-12-21 8:04 | MySQL Server: Options | Verified (829 days) | S3 | 5.7.35, 8.0.27 | Linux | Any | The table "general_log" not close when config option general_log set into OFF |
105957 | 2021-12-22 7:44 | 2021-12-22 8:01 | MySQL Server: Options | Verified (828 days) | S3 | 5.7.35, 8.0.27 | Linux | Any | The table "slow_log" not close when config option slow_query_log set into OFF |
105964 | 2021-12-23 1:43 | 2021-12-23 5:06 | MySQL Server: Options | Verified (827 days) | S3 | 5.7.35, 8.0.27 | Linux | Any | The table "general_log/slow_log" not close when config log_output set into NONE |
106122 | 2022-01-10 8:25 | 2022-01-12 9:54 | MySQL Server: Options | Verified (809 days) | S3 | 5.7.36 | Any | Any | [Tencent]session track of collation_connection missing character_set_connectioB |
112798 | 2023-10-23 7:02 | 2023-10-23 7:44 | MySQL Server: Options | Verified (158 days) | S2 | 8.1, 8.0.34 | Linux | Any | The configuration value of innodb_buffer_pool_size underflow |
110490 | 2023-03-24 11:08 | 2023-03-27 5:13 | MySQL Server: Options | Verified (371 days) | S3 | Ver 8.0 | Any | Any | add a option to get the malloc lib infomation of MySQL server use |
111062 | 2023-05-17 18:49 | 2023-05-22 12:39 | MySQL Server: Options | Verified (315 days) | S3 | 8.0.33 | MacOS | ARM | Cannot disable TLS in MySQL 8.0.33 |
111143 | 2023-05-24 15:11 | 2023-05-26 7:56 | MySQL Server: Options | Verified (308 days) | S3 | 8.0.33, 5.7.42 | MacOS | ARM | Quoting of ints |
106591 | 2022-02-28 4:10 | 2022-02-28 7:06 | MySQL Server: Options | Verified (760 days) | S5 | 8.0 | Any | Any | net_set_read_timeout、net_set_write_timeout value set |
107115 | 2022-04-25 3:47 | 2023-05-24 10:25 | MySQL Server: Options | Verified (704 days) | S2 | 8.0.27, 8.0.28, 8.0.33 | Any | Any | ??at the end of the error mecessage after setting Chinese characters to variable |
57972 | 2010-11-04 11:21 | 2011-02-16 23:44 | MySQL Server: Options | Verified (4894 days) | S3 | 5.5.8,5.6.1-m4,5.6.99-m5 | Any | Any | mysqld --help --verbose does not always list all optimizer_switch flags |
58106 | 2010-11-10 10:24 | 2011-02-16 23:44 | MySQL Server: Options | Verified (4888 days) | S3 | 5.1-bugteam | Any | Any | Wrong directory info in general_log_file/slow_query_log_file. |
58114 | 2010-11-10 13:55 | 2011-02-16 23:44 | MySQL Server: Options | Verified (4853 days) | S3 | 5.5 | Any | Any | NULL value in a system variable is not displayed as such in SHOW VARIABLES/I_S |
59325 | 2011-01-06 10:06 | 2014-10-10 7:30 | MySQL Server: Options | Verified (4112 days) | S3 | 5.5.8 GA | Windows (WS 2008 Std SP2 x86 32-bit) | Any | OpenSSL generated key/certificate required for SSL/TLS connections |
59441 | 2011-01-12 10:42 | 2012-05-18 20:19 | MySQL Server: Options | Verified (4810 days) | S3 | any | Any | Any | No information in GLOBAL 'character_set_database' variable |
60018 | 2011-02-08 19:13 | 2011-02-16 23:44 | MySQL Server: Options | Verified | S3 | 4.1 and above | Any | Any | Report deprecated options in error log (some old options are missing) |
60113 | 2011-02-11 11:53 | 2011-03-02 18:27 | MySQL Server: Options | Verified (4780 days) | S3 | 5.6.2 | Any | Any | plugin names are conflicting with system variable names |
60538 | 2011-03-18 20:29 | 2011-03-19 8:50 | MySQL Server: Options | Verified (4759 days) | S3 | 5.1.55, 5.1.57 | Any | Any | MySQL fails to start when max_connect_errors is set to 18446744073709547520 |
60703 | 2011-03-31 7:26 | 2015-11-19 16:59 | MySQL Server: Options | Verified (4658 days) | S2 | MySQL Community 5.5.9 | Windows (Windows Server 2003 Standard Edition) | Any | " --verbose --help" seems don't read the options in service name based group |
61130 | 2011-05-11 4:32 | 2012-01-17 20:01 | MySQL Server: Options | Verified (4455 days) | S3 | 5.0.77, 5.0.95, 5.1.62, 5.5.21, 5.6.5 | Linux (CenOS 5.5) | Any | Key_blocks_not_flushed values is not correct! |
62224 | 2011-08-22 8:00 | 2015-08-06 19:12 | MySQL Server: Options | Verified (4602 days) | S3 | 5.5.13, 5.6.3, 5.1.60 | Any | Any | Setting open-files-limit above the hard limit won't be logged in errorlog |
62545 | 2011-09-26 22:44 | 2011-09-27 11:49 | MySQL Server: Options | Verified (4567 days) | S3 | 5.5 | Any | Any | my_atof and getopt_double callers pass bogus end of string offsets |
62752 | 2011-10-15 17:32 | 2014-07-31 13:29 | MySQL Server: Options | Verified (4520 days) | S3 | 5.5.16, 5.1.60 | Linux (CentOS 5.7 x86_64) | Any | mysqld --verbose --help ends with error |
43398 | 2009-03-05 4:45 | 2016-10-16 20:45 | MySQL Server: Options | Verified (5502 days) | S3 | 4.1, 5.0, 5,1, 6.0 bzr | Any | Any | mysqld in --bootstrap mode still initialises its binlog |
43523 | 2009-03-10 2:01 | 2011-02-16 23:43 | MySQL Server: Options | Verified (5498 days) | S3 | 5.0.51, 5.1.32 | Linux (Possibly more) | Any | Open_files status variable does not report all opened file descriptors by the OS |
44509 | 2009-04-28 9:15 | 2011-10-28 3:21 | MySQL Server: Options | Verified (5448 days) | S3 | >= 5.0 | Any | Any | Inconsistent use of ON/OFF variable values in my.cnf vs SHOW GLOBAL VARIABLES |
53494 | 2010-05-07 15:32 | 2011-02-16 23:44 | MySQL Server: Options | Verified (5056 days) | S3 | 5.1 | Any | Any | Update docs for Queries and Questions in SHOW STATUS |
55288 | 2010-07-15 14:35 | 2011-02-16 23:44 | MySQL Server: Options | Verified (5001 days) | S3 | 5.1+ | Any | Any | Use of the underscore or hyphen for variables and options is confusing |
55893 | 2010-08-10 20:08 | 2018-09-09 20:45 | MySQL Server: Options | Verified (4980 days) | S3 | mysql-next-mr-opt-backporting | Any | Any | optimizer_switch should report which variable it can not process |
56264 | 2010-08-25 17:41 | 2011-02-16 23:44 | MySQL Server: Options | Verified (4964 days) | S3 | 5.1.47, 5.1.51-bzr | Linux | Any | Command-line options are case-sensitive but don't throw errors |
57112 | 2010-09-29 18:16 | 2011-02-16 23:44 | MySQL Server: Options | Verified (4929 days) | S3 | 5.1.49, 5.6.99 | Any | Any | Incorrect option parsing code in my_getopt.c |
57220 | 2010-10-04 15:00 | 2011-02-16 23:44 | MySQL Server: Options | Verified (4924 days) | S2 | 5.1.48 | Any | Any | SET SESSION @sql_log_off should not require SUPER privilege |
20040 | 2006-05-24 10:46 | 2017-01-12 15:32 | MySQL Server: Options | Verified (6239 days) | S3 | 5.1-bk, 5.0.38 | Any (*) | Any | SSL connections do not affect SSL statistics in STATUS output |
20263 | 2006-06-05 2:35 | 2011-02-16 23:43 | MySQL Server: Options | Verified (5930 days) | S3 | 5.0.22 | Any | Any | mysql.cnf line break incompatibility |
21978 | 2006-09-01 22:13 | 2011-02-16 23:43 | MySQL Server: Options | Verified (5959 days) | S3 | 4.0.18, 5.0, 6.0.10, 5.5 | Windows (Windows 2000) | Any | 'flush_time' value set for 1800 sec. on Non Win9x/Me installs by default |
24758 | 2006-12-01 18:08 | 2012-05-18 20:19 | MySQL Server: Options | Verified (5959 days) | S3 | 5.0.27, 4.1 BK, 5.1 BK | Linux (Fedora Core6) | Any | max_user_connections=0 doesn't work had to set a value to make it work |
25153 | 2006-12-18 17:35 | 2013-03-03 20:45 | MySQL Server: Options | Verified (6310 days) | S3 | 5.0,5.1 | Linux (SUSE 10.0 / 64-bit) | Any | mysqld --skip-engine option |
25748 | 2007-01-22 11:14 | 2018-09-09 20:45 | MySQL Server: Options | Verified (5959 days) | S3 | 5.0.32-33/5.1.14/5.2.0 | Windows (windows) | Any | my.ini (Windows) file demands Unix file syntax for SSL parameters |
29854 | 2007-07-17 19:05 | 2018-09-09 20:45 | MySQL Server: Options | Verified (5959 days) | S3 | 5.1.19, 5.1 BK | Any | Any | mysqld --help --verbose retuns [ERROR] instead of printing help |
31106 | 2007-09-20 11:17 | 2022-12-04 20:45 | MySQL Server: Options | Verified (6035 days) | S3 | 5.1.20 | Any | Any | errors whenn running "mysqld --help" before "mysql_install_db" |
41584 | 2008-12-18 10:20 | 2018-09-09 20:45 | MySQL Server: Options | Verified (5580 days) | S3 | Ver 5.1.31-debug | Linux (suse-linux on x86_64) | Any | Inconsistent behaviour when comparing system variable "timestamp". |
42305 | 2009-01-23 14:53 | 2011-02-16 23:43 | MySQL Server: Options | Verified (5544 days) | S3 | 5.1/6.0 | Any | Any | It is not possible to list existing key caches |
47513 | 2009-09-22 10:16 | 2011-02-16 23:44 | MySQL Server: Options | Verified (5302 days) | S3 | 6.0.14 | Any | Any | Test main.merge_recover fails |
49171 | 2009-11-27 20:02 | 2022-12-04 20:45 | MySQL Server: Options | Verified (5233 days) | S3 | 5.1 | Any | Any | read_buffer_size is only partially dynamic variable |
49778 | 2009-12-17 19:02 | 2011-02-16 23:44 | MySQL Server: Options | Verified | S3 | 5.1 | Windows | Any | Mix of forward (/) and backward (\) slashes in show variables paths |
50130 | 2010-01-07 9:24 | 2019-05-16 7:48 | MySQL Server: Options | Verified (5195 days) | S3 | 5.0+ | Any | Any | --sysdate-is-now sets no system variable |
50330 | 2010-01-14 13:47 | 2022-12-04 20:45 | MySQL Server: Options | Verified (5187 days) | S3 | 5.5.99-m3 (Celosia) | Any (32 bit) | Any | sys_vars.sql_select_limit_basic fails on 32 bit OS without big tables support |
50378 | 2010-01-15 17:34 | 2022-12-04 20:45 | MySQL Server: Options | Verified (5184 days) | S2 | 5.0.77, 5.0, 5.1 bzr | Linux (RHEL 5.4) | Any | Uptime_since_flush_status has an abnormally large value |
50425 | 2010-01-18 17:42 | 2011-02-16 23:44 | MySQL Server: Options | Verified (5184 days) | S3 | 5.5.1-m2-community | Any | Any | Better defaults (key buffer, thread_cache_size) |
50641 | 2010-01-26 21:07 | 2013-03-03 20:45 | MySQL Server: Options | Verified (5176 days) | S3 | 5.1.41 | Any | Any | setting innodb_adaptive_hash_index = ON actually disables it |
51820 | 2010-03-08 9:12 | 2011-02-16 23:44 | MySQL Server: Options | Verified (5135 days) | S3 | 5.0, 5.1, 5.5-m3, 6.0-codebase | Any | Any | Error log is automatically named after the PID file's name |
51834 | 2010-03-08 15:56 | 2022-12-04 20:45 | MySQL Server: Options | Verified (5134 days) | S3 | 5.1.44, 5.0, 5.1, 5.5.99 | Any (MS Windos XP Pro SP3 32bit, Mac OS X) | Any | Case Sensitivity table name problem with Windows |
47884 | 2009-10-07 3:24 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5173 days) | S2 | 5.1.39, 5.1.44, 5.5.99 | Linux (Linux web2 2.6.18-92.1.18.el5.028stab060.8 #1 SMP Mon Feb 9 21:44:50 MSK 2009 x86_64) | Any | MySQL 5.1.39 failed to use index |
48049 | 2009-10-14 16:46 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified | S3 | 5.1.37, 5.5.7 | Any | Any | SELECT MIN(1) reports differently for MERGE tables in 5.0 and 5.1 |
48103 | 2009-10-16 0:32 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified | S3 | 5.1, 6.0 | Any | Any | Using STRAIGHT_JOIN with Innodb tables can produce duplicate results |
48190 | 2009-10-20 14:59 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified | S3 | 5.1,6.0 | Any | Any | Error processing ALL subqueries on empty sets - different than JavaDB/Postgres |
48245 | 2009-10-22 20:25 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5271 days) | S3 | 5.1,mysql-6.0-codebase-bugfixing | Any | Any | crash in Bitmap<64u>::merge called by add_key_field |
48703 | 2009-11-11 21:58 | 2022-09-04 20:45 | MySQL Server: Optimizer | In progress (5044 days) | S3 | 5.0+ | Any | Any | nontrivial ORDER/GROUP BY expressions: ambiguous statements not detected |
48886 | 2009-11-19 0:38 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5244 days) | S5 | 5.1+ | Any | Any | MySQL doesn't seem to optimize "less than empty string" |
49200 | 2009-11-30 10:19 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5233 days) | S3 | 6.0 | Any | Any | Select_type in explain output incorrect for semijoin queries |
49276 | 2009-12-01 17:03 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5232 days) | S5 | 5.0.85-community-log, 5.0.89, 5.1.42 | Linux | Any | Optimization for IN (on InnoDB tables) depends on number of set elements |
49504 | 2009-12-07 12:54 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5226 days) | S3 | 5.1+ | Any | Any | Inconsistency in handling range predicates with NULL constants |
49590 | 2009-12-10 16:03 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified | S3 | 5.0+ | Any | Any | Server reporting different result sets for a query depending on use of indexes |
50168 | 2010-01-08 2:16 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5189 days) | S3 | 5.0,5.1 | Any | Any | The value of 'rows' in EXPLAIN output is not accurate for LIMIT |
50388 | 2010-01-16 4:13 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified | S5 | 5.1.41,5.1.42, 5.1.43-bzr | Any | Any | partition pruning not working with some right joins |
50953 | 2010-02-05 18:40 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5165 days) | S2 | 5.1.41, 5.1.44, 5.5.99 | Any | Any | Locked rows change in number, strangely. |
51521 | 2010-02-25 18:03 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5145 days) | S2 | 5.1.42, 5.1.45-bzr | Any | Any | MERGE Algorithm in LEFT JOIN retuns 0000-00-00 instead of NULL |
52029 | 2010-03-13 12:26 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5121 days) | S5 | 5.1.44 | Any | Any | GROUP BY results in much slower query |
52030 | 2010-03-13 12:35 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5127 days) | S2 | 5.1.44 | Any | Any | WHERE clause with != primary key check slows a query from 0.06 sec to 4 min |
52170 | 2010-03-18 9:57 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5121 days) | S5 | 5.1.44, mysql-next-mt | Linux (fc12) | Any | innodb query optimizer fails (null possible_keys) with multicolumn key |
52174 | 2010-03-18 10:59 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5106 days) | S3 | 4.1, 5.0, 5.1 | Any | Any | Sometimes wrong plan when reading a MAX value from non-NULL index |
52283 | 2010-03-22 19:10 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5120 days) | S3 | 5.1.46 | Any | Any | Innodb reports extra warnings when SELECT/WHERE is performed using invalid value |
52762 | 2010-04-12 10:49 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5099 days) | S5 | 5.3 | Any | Any | like should be index optimised if starts with _ rather than % |
52784 | 2010-04-13 14:02 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5099 days) | S3 | 5.1.43, 5.6.99-m4 | Any | Any | Non optimal execution plan when using "NULL-safe not equal" on partitioned table |
53648 | 2010-05-14 14:00 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5064 days) | S3 | 5.1.48-bzr | Any | Any | Where clause with IS TRUE generates different plan |
53793 | 2010-05-19 9:52 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5063 days) | S3 | 6.0-codebase-bugfixing | Any | Any | "early NULL filtering" not done for outer join converted to inner join |
54056 | 2010-05-28 6:43 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5054 days) | S3 | 5.1.47, 5.1.48, 5.6.99 | Any | Any | Incorrect number format in output from SELECT |
54179 | 2010-06-02 11:37 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified | S3 | 5.1.37 , 5.1.47 , 5.5.4 | Any | Any | Index is not used for range scan on SET field |
54207 | 2010-06-03 15:05 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5042 days) | S2 | 5.1.40, 5.1.48, all | Linux (5u4) | Any | why mysql cann't using index to filter column after range condition ; |
54312 | 2010-06-07 22:19 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5043 days) | S3 | 5.1.47, 5.1.48-bzr | Any | Any | insert ... select .. order by rand(): difference depending on indexes. |
54921 | 2010-06-30 16:41 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5021 days) | S3 | 5.0-bzr, 5.1-bzr | Any | Any | ORDER BY doesn't use index if ref lookup on VARBINARY column used |
55248 | 2010-07-14 9:22 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5007 days) | S5 | 5.1.43, 5.1.48 | Windows | Any | constant WHERE inefficient |
55979 | 2010-08-13 22:05 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (4974 days) | S5 | 5.1.39 | Linux | Any | Key not used if IN() list contains mix of strings and integers |
56165 | 2010-08-21 8:12 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (4967 days) | S3 | 5.0.not_sure, 5.0, 5.1, 5.6.99 bzr | Any | Any | Bad Optimization |
56925 | 2010-09-22 11:27 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (4804 days) | S3 | 5.5 | Any | Any | Wrong execution of UPDATE … WHERE sec_key=… ORDER BY pk DESC |
57024 | 2010-09-26 4:44 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (4930 days) | S2 | 5.1 | Any | Any | Serious performance issue with an outer join |
57216 | 2010-10-04 12:59 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (4921 days) | S3 | 5.1, 5.6.99 bzr | Any | Any | InnoDB column prefix index not treated as a covering one |
58008 | 2010-11-05 9:38 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (4893 days) | S3 | 5.1, 5.0 | Any | Any | wrong datatype (blob) in the resultset if the string is larger than 512 bytes |
58101 | 2010-11-10 0:21 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (4887 days) | S5 | 5.1.38-community-log, 5.1.54-bzr | Linux | Any | Optimizer picks wrong order of queries |
58604 | 2010-11-30 21:28 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (4866 days) | S1 | 5.5.7, 5.5.9, 5.6.1 | Any | Any | crash in cleanup code of explain partitions after killing connection |
58737 | 2010-12-05 7:59 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (4862 days) | S3 | 5.1.53, 5.1.54 | Windows (7) | Any | nested query fails to execute |
58924 | 2010-12-14 18:38 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (4853 days) | S3 | 5.1.44, 5.0, 5.1, 5.6.1 | Linux | Any | a LIMIT after a UNION doesn't propogate to all queries |
58928 | 2010-12-14 20:58 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (4854 days) | S3 | 5.1-bugteam | Any | Any | "not exists" optimization not applied if relevant table is not single inner one |
59119 | 2010-12-23 0:01 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (4845 days) | S2 | 5.1.50 | Any | Any | Incorrect table order chosen for three table join with an ORDER BY |
59187 | 2010-12-27 15:31 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (4841 days) | S2 | 5.1.55, 5.6.2-m5 | Any | Any | Wrong result with NULL NOT IN subquery |
59557 | 2011-01-17 15:26 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (4820 days) | S2 | 5.1, 5.5 | Any | Any | MySQL uses order of fields in GROUP BY when ORDER BY NULL is specified |
59650 | 2011-01-21 9:32 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (4816 days) | S3 | mysql-trunk | Any | Any | SELECT Does Not Return Result For "equal / Null safe equal" Operator On BIT |
59952 | 2011-02-04 17:20 | 2014-03-16 11:44 | MySQL Server: Optimizer | Verified (4767 days) | S3 | 5.1.55-community, 5.6.3 | Any | Any | distinct ,distinct_key,group_key |
60023 | 2011-02-08 21:45 | 2014-05-22 12:13 | MySQL Server: Optimizer | Verified | S5 | 5.5.8 , 5.1.51 | Any | Any | No Loose Index Scan for GROUP BY / DISTINCT on InnoDB partitioned table |
60185 | 2011-02-20 15:58 | 2011-03-03 8:35 | MySQL Server: Optimizer | Verified (4786 days) | S3 | 5.0.51, 5.5.11 | Linux | Any | index DEPENDENT SUBQUERY |
60494 | 2011-03-16 17:26 | 2011-03-19 9:43 | MySQL Server: Optimizer | Verified (4761 days) | S3 | 5.1.36-community, 5.1.57 | Any | Any | Order By produces wrong order |
60702 | 2011-03-30 23:25 | 2011-04-05 14:55 | MySQL Server: Optimizer | Verified (4747 days) | S5 | 5.1.57 | Any | Any | GROUP BY orders when used inside a UNION query, though it should not |
61551 | 2011-06-17 12:26 | 2011-06-18 8:34 | MySQL Server: Optimizer | Verified (4669 days) | S3 | 5.1.56 | Any | Any | Loose index scan is not used for select COUNT(distinct a) |
61936 | 2011-07-21 6:27 | 2011-07-31 15:28 | MySQL Server: Optimizer | Verified (4634 days) | S2 | 5.1.48, 5.5.13, 5.5.16 | Linux (x86_64) | Any | STRAIGHT_JOIN has no effect on query with subquery in FROM clause |
62307 | 2011-08-31 1:54 | 2011-09-01 21:29 | MySQL Server: Optimizer | Verified (4593 days) | S3 | 5.5.15 | Any | Any | Condition "TIME = '19:20'" does not use index in sjis |
43341 | 2009-03-03 21:39 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5505 days) | S2 | 5.1 | Any | Any | FORCE INDEX FOR ORDER BY does not affect join queries |
43342 | 2009-03-03 21:54 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5505 days) | S2 | 5.1, 6.0 | Any | Any | FORCE INDEX hint does not differentiate between ORDER BY and GROUP BY |
43531 | 2009-03-10 11:24 | 2020-05-03 20:45 | MySQL Server: Optimizer | Verified (5316 days) | S3 | 5.1, 6.0.11-bzr | Linux | Any | Crash if Falcon or MyISAM, subqueries, 4 clients |
43720 | 2009-03-18 6:00 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5490 days) | S3 | 6.0.11, 5.0, 5.1 bzr | Any | Any | MyISAM & Maria gives wrong results with range access on bit type |
44201 | 2009-04-10 3:04 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5036 days) | S3 | 5.1.32, 5.1.35-bzr, 6.0.11-bzr, 5.0, 5.6.99 | Any | Any | Performance problem with View |
44445 | 2009-04-23 19:24 | 2020-05-03 20:45 | MySQL Server: Optimizer | Verified (5336 days) | S3 | 5.1.31-log, 5.0, 5.1, azalea bzr | Linux | Any | Problem using index when selecting all columns |
44549 | 2009-04-29 17:47 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified | S3 | 5.0.80, 5.1.34 | Any | Any | optimizer incorrectly chooses table scan and filesort over index |
44593 | 2009-05-01 3:31 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5446 days) | S3 | 5.0.56, 5.0.72 | Any | Any | MyISAM tables showing odd "rows" value with EXPLAIN of a JOIN query |
45001 | 2009-05-21 6:22 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5380 days) | S3 | 5.1.33, 4.1, 5.0, 5.1, 6.0 bzr | Any | Any | EXPLAIN says "Using index; Using filesort", however table scan is used |
45314 | 2009-06-03 22:46 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5412 days) | S3 | 5.1.28-rc-community, 4.1, 5.0, 5.1, 6.0 bzr | Any (MS Windows, Linux) | Any | Index is not used for joining on a nullable columns with no additional condition |
45373 | 2009-06-08 13:14 | 2022-09-04 20:45 | MySQL Server: Optimizer | Verified (5397 days) | S3 | 5.1.35-community, 5.1.36-bzr | Any | Any | INDEX FOR GROUP BY is not used if there is a LIMIT clause in the query |
45424 | 2009-06-10 6:58 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5406 days) | S2 | 5.0.51a, 5.0.77 and 5.1.34, 5.1, 6.0 bzr | Linux | Any | UPDATE statement cause full table scan ? |
45680 | 2009-06-23 14:15 | 2020-04-01 13:16 | MySQL Server: Optimizer | Verified | S3 | 5.0.54, 5.0.82, 5.1.35, 6.0.12 | Any | Any | wrong results when using index for lookup with implicitly casted values |
45741 | 2009-06-25 10:46 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5387 days) | S1 | 5.0.83, 5.0, 5.1, 5.5.8 | Linux | Any | Memory of server increases abnormally for sql with mass <> condition |
45776 | 2009-06-26 7:17 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5390 days) | S5 | mysql-5.1.35 | Linux | Any | "OR" condition on SPATIAL index not optimized |
45880 | 2009-07-01 14:21 | 2022-09-04 20:45 | MySQL Server: Optimizer | Verified | S3 | 5.0, 5.1 | Any | Any | OUTER JOINed tables with no condition in WHERE must be at the end of explain |
46011 | 2009-07-07 14:05 | 2020-05-03 20:45 | MySQL Server: Optimizer | Verified (4917 days) | S3 | 5.1-bugteam | Any | Any | Regression after applying fix for bug #45828 |
46056 | 2009-07-08 20:24 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified | S3 | 5.0,5.1,5.4 | Any | Any | Duplicate rows returned on MAX + ORDER BY |
46135 | 2009-07-12 19:03 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (4997 days) | S2 | 5.0, 5.1, next, 6.0.0, 6.0.2, 5.1.36 | Any | Any | LIMIT + JOIN problem |
46217 | 2009-07-16 11:16 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified | S3 | 5.0,5.1,5.4 | Any | Any | Wrong result on aggregate + JOIN + ORDER BY + LIMIT |
46227 | 2009-07-16 14:43 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5370 days) | S3 | 5.0,5.1,5.4 | Any | Any | Wrong result on DISTINCT + aggregate + JOIN + InnoDB |
46277 | 2009-07-17 21:33 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified | S3 | 5.0, 5.1, 5.4, 6.0 | Any | Any | differing results for equivalent queries using VAR_POP() & AVG() with DISTINCT |
46283 | 2009-07-18 15:22 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified | S3 | 5.0, 5.1, 5.4, 6.0 | Any | Any | COUNT() returning bad values when LIMIT 1 clause added to query |
46288 | 2009-07-18 19:12 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5368 days) | S3 | 5.1.35-community, 5.1.36 | Windows | Any | Index is not used for equality condition on single-row, multiple column subquery |
46376 | 2009-07-24 17:05 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5357 days) | S5 | 5.0.85, 5.1.36, 5.1.38, 5.1.39 | Windows (XP) | Any | Optimizer choose wrong index even when where clause and order-by are covered |
46475 | 2009-07-30 11:24 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5355 days) | S3 | 5.1,5.4 | Any | Any | Different optimizations chosen for exactly equivalent queries |
46517 | 2009-08-02 21:54 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified | S3 | 5.4,5.6.99 | Any | Any | Queries with constant / null only WHERE clause interpreted differently in azalea |
46648 | 2009-08-11 11:41 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5338 days) | S3 | 5.1.32, 4.1, 5.0, 5.1, azalea bzr | Linux (2.6.28.7) | Any | SQL_CALC_FOUND_ROWS kills performance with ORDER BY and LIMIT |
46717 | 2009-08-14 11:14 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5331 days) | S5 | 5.1.32 | Any | Any | Unnecessary joins are not optimized away |
46853 | 2009-08-21 11:07 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5238 days) | S3 | Any | Any | valgrind warnings in mysql-pe branch with the testcase for the BUG#45816 | |
46989 | 2009-08-29 5:52 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5326 days) | S3 | 5.1,5.4 | Any | Any | NULL attribute gets lost when "CREATE TABLE AS SELECT ... GROUP BY WITH ROLLUP" |
47330 | 2009-09-15 15:39 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5301 days) | S5 | 5.0.77, 5.1.34, 5.1.37 | Linux (Debian x64) | Any | Slow query with left join and having. |
47454 | 2009-09-19 19:33 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5304 days) | S3 | 5.1.35 | Any | Any | Not exists optimization method is not used for NULL columns in the right table |
37264 | 2008-06-07 22:35 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5643 days) | S5 | 5.1.24-rc 5.1.29-rc 5.1.30 | Any | Any | MySQL wrongly uses filesort |
37305 | 2008-06-10 9:53 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5706 days) | S3 | 5.0/5.1/6.0, 5.7.18 | Any | Any | select count(*); returns value |
37902 | 2008-07-06 15:14 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5724 days) | S3 | 5.0.45, 5.0.68 | MacOS | Any | Bug (2) in the query optimizer (explain) |
38251 | 2008-07-21 0:29 | 2020-05-03 20:45 | MySQL Server: Optimizer | Verified (5730 days) | S5 | 5.0.51 | Any | Any | Useless external queries should be ignored |
38397 | 2008-07-27 20:13 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5723 days) | S3 | 5.1.26, 5.0.62 | Any | Any | select distinct + order by desc is executed inefficiently |
38550 | 2008-08-04 21:47 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5643 days) | S5 | 5.0.60, 5.1 | Any | Any | multiple optimizer bugs for queries with references from preceding table |
39298 | 2008-09-08 6:42 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5506 days) | S3 | 4.0, 4.1, 5.0, 5.1, 6.0 | Any | Any | Prefix key search returns wrong result for multi-level collations |
39944 | 2008-10-09 2:10 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5650 days) | S3 | 4.1, 5.0, 5,1, 6.0 bzr | Any | Any | With join buffer executor ignores index scan |
40151 | 2008-10-19 18:12 | 2020-05-03 20:45 | MySQL Server: Optimizer | Verified (3984 days) | S3 | 6.0/5.6 | Any | Any | EXPLAIN doesn't show DISTINCT+join optimization |
41064 | 2008-11-27 2:25 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5601 days) | S3 | MySQL 5.0.27-standard, 5.0.70, 6.0.7 | Linux | Any | enum query never use index and it should |
41109 | 2008-11-28 17:13 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5476 days) | S2 | 5.1.30, 5.0, 5.1, 6.0 bzr | Any | Any | Query takes >5 hrs and locks db, when optimised manually takes <1s |
41220 | 2008-12-04 9:59 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5337 days) | S5 | 5.1.30, 5.0, 5.1, azalea bzr | Any | Any | LEFT JOIN with compound clause uses table scan, while INNER JOIN uses indexes |
41350 | 2008-12-10 8:00 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5588 days) | S3 | 5.0.46-log | Linux | Any | String expression collation determined only by the first equality operand |
41873 | 2009-01-05 15:52 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5555 days) | S3 | 5.1.30-community, 5.0, 5.1, 6.0 bzr | Any (MS Windows, Linux) | Any | MySQL doesn't use indexes when joining large table to small one |
42808 | 2009-02-12 22:17 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5523 days) | S5 | 4.1, 5.0, 5.1 | Any | Any | Execution Plan Cache |
42948 | 2009-02-17 23:02 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5505 days) | S5 | 5.0.67-0ubuntu6, 6.0.11 | Linux (Ubuntu 8.10) | Any | MySQL Optimizer does not properly use Indexes on Views with "Group By" |
43011 | 2009-02-19 10:01 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5309 days) | S2 | 5.0.75, 5.0.*, 5.1.* | Any | Any | inconsistent content for 'rows' column in EXPLAIN for index_merge |
43052 | 2009-02-20 9:49 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5516 days) | S3 | 5.1.30-community, 4.1, 5.0, 5.1, 6.0 bzr | Any (MS Windows XP, Linux) | Any | not optimalised (sub)query, = versus IN |
43219 | 2009-02-26 9:49 | 2020-12-23 7:46 | MySQL Server: Optimizer | Verified (5510 days) | S3 | 5.0.70, 4.1, 5.0, 5.1, 6.0 bzr | Linux (Gentoo) | Any | delete does not use index when using OR in where clause |
7080 | 2004-12-07 15:23 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (6999 days) | S3 | 4.0 | Linux (Linux) | Any | Optimizer choose incorrect index |
7604 | 2004-12-31 20:13 | 2020-05-03 20:45 | MySQL Server: Optimizer | Verified (5219 days) | S3 | 5.0.21-BK, 6.0.14 | Linux (Linux) | Any | Row subqueries don't work with ALL |
8036 | 2005-01-20 10:12 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (6999 days) | S3 | 4.0.18, 4.1.10, 5.1.52 | FreeBSD (Free BSD 4.5, Linux) | Any | Bad optimization of ORDER BY ... LIMIT 1 if one table is MyISAM, another InnoDB |
8113 | 2005-01-24 15:43 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5337 days) | S5 | 5.0, 5.1, azalea bzr | Any | Any | Select with between optimization |
8662 | 2005-02-21 21:31 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5233 days) | S5 | 6.0.14, 5.1.12-BK, 4.1.10 | Any | Any | optimizer, query takes 3 to 10 times as long when using index |
8749 | 2005-02-23 21:08 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5294 days) | S3 | 4.1.10, 5.0.67 | Any (*) | Any | EXPLAIN report different "type" w and w/o USE INDEX(...) for the same used key |
11948 | 2005-07-14 18:00 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (6813 days) | S3 | 5.0 | Any | Any | MyISAM only, nested JOIN Views, dramatic performance loss |
12113 | 2005-07-22 14:23 | 2014-01-24 12:43 | MySQL Server: Optimizer | Verified (3717 days) | S1 | 5.0.28-BK, 4.0,5.0 | Any | Any | Composite index chosen partially for ORDER BY ... LIMIT query. |
12799 | 2005-08-25 9:46 | 2020-05-03 20:45 | MySQL Server: Optimizer | Verified (5294 days) | S3 | 5.0.10-log, 4.1.13a-log on win, 4.1 on RHES3.0 | Windows (windows xp) | Any | one result returned when change from summer time causes dup unique key recs |
14084 | 2005-10-17 20:09 | 2014-01-23 9:50 | MySQL Server: Optimizer | Verified (3718 days) | S3 | 5.0-bk | Any | Any | index_merge access method not used for federated engine |
14253 | 2005-10-24 9:26 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5202 days) | S3 | 5.0, 4.1, 6.0.14-bzr | Linux (Linux) | Any | Optimizer uses partial indexes for subqueries, where it should not |
15907 | 2005-12-21 15:23 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5218 days) | S5 | 5.0.19-BK, 5.0.13, 6.0.14-bzr | Linux (Linux) | Any | Binary comparison ignores indexes |
17259 | 2006-02-09 2:23 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5625 days) | S5 | 5.0.15, 6.0.7 | Linux (Linux) | Any | Query optimizer chooses wrong index |
17299 | 2006-02-10 12:35 | 2014-01-23 9:53 | MySQL Server: Optimizer | Verified (3718 days) | S3 | 5.0.18 | Any (All) | Any | Inefficient optimizer for fulltext queries. |
18465 | 2006-03-23 17:43 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5299 days) | S2 | 5.0.20-BK, 5.0.19, 5.0.85 | Any (any) | Any | Optimizer/execution plan bug with dependent subqueries in ON clauses of JOINs |
18688 | 2006-03-31 14:07 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (6048 days) | S3 | 4.0, 4.1, 5.0 | Linux (linux) | Any | non-optimal plan for SELECT |
19195 | 2006-04-19 12:09 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5299 days) | S3 | 5.0.27-BK, 5.0.21-BK, 5.0.19 | Linux (Linux) | Any | Optimizer does not use proper index for join |
20111 | 2006-05-28 10:57 | 2014-01-24 13:26 | MySQL Server: Optimizer | Verified (3717 days) | S5 | 4.1.19-log | Linux (Linux) | Any | named columns used in subqueries hinder optimisation of LIKE, BETWEEN, range |
24251 | 2006-11-13 10:58 | 2018-09-09 20:45 | MySQL Server: Optimizer | In progress (5240 days) | S5 | 5.0.30-BK, 5.1.12 | Linux (Linux, Win XP SP2) | Any | Non-optimal choice of indexes for queries |
24697 | 2006-11-29 15:13 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (4836 days) | S3 | 5.0.24a-community-nt-log/4.1BK/5.0BK/5.1BK | Windows (Windows 2000 and Linux) | Any | insert .. select ....ON DUPLICATE KEY UPDATE fails with ambiguous column name |
24754 | 2006-12-01 13:34 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5223 days) | S3 | 5.1.14, 5.1.43-bzr | Linux (Linux) | Any | Index is not used when joining two tables |
24770 | 2006-12-02 0:37 | 2018-09-09 20:45 | MySQL Server: Optimizer | In progress (4757 days) | S5 | 5.1 | Any (all) | Any | update with subquery slow |
25068 | 2006-12-14 11:56 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5643 days) | S3 | 4.0.27, 5.0.19, 5.0.36-BK | Linux (Linux) | Any | MyISAM-Optimizer prefers full table scan than index for IN with >15 elements |
25764 | 2007-01-22 20:59 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5542 days) | S3 | 5.0.36-BK, 6.0.8-bzr | Linux (Linux, Mac OS X) | Any | Query Cost Estimate seems to only cover a part of subqueries, not full query. |
26232 | 2007-02-09 17:28 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (6252 days) | S3 | 4.1.22, 5.0.34, 5.0.36-BK | Linux (Linux) | Any | review of bug #20944 / proof of concept attached |
26284 | 2007-02-12 12:32 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5983 days) | S3 | 5.0.bk | Linux (Linux) | Any | bug #26273 / optimize, not executed for index, if datafile is gap-free |
26832 | 2007-03-04 18:17 | 2011-04-05 14:46 | MySQL Server: Optimizer | Verified (4742 days) | S5 | 5.5 | Any | Any | ENUM types not optimized |
27452 | 2007-03-26 17:35 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5611 days) | S3 | 5.0.40-BK, 5.0.24a-debian-log, 5.1.31-bzr, 6.0.7-alpha, 6.0.9-bzr | Linux | Any | Correlated subquery produces inefficient optimizer plan for INFORMATION_SCHEMA |
28404 | 2007-05-13 18:33 | 2018-11-11 14:44 | MySQL Server: Optimizer | Verified (1965 days) | S2 | 4.0.31, 4.1.25, 4.1.26, 5.0.42-BK, 5.0.46, 5.1.33 | Linux | Any | Optimizer does not consider index that can be used for ORDER BY |
28554 | 2007-05-21 9:32 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5425 days) | S3 | 4.1.22, 5.0.42-BK | Any | Any | Optimizer wrongly prefers index for (col = value) over (PK <= value) |
29421 | 2007-06-28 13:43 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (6119 days) | S2 | 5.1.14-beta/5.0 | Any | Any | MySQL allows mixing of GROUP columns with no GROUP columns in complex terms |
29433 | 2007-06-29 0:03 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5233 days) | S3 | 5.0.27, 5.0, 5.1, 4.1, 5.2 BK, 6.0.14-bzr | Any | Any | composite index not used |
29443 | 2007-06-29 13:28 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (4915 days) | S3 | 5.1.19 | Any | Any | cost calculations are off |
30302 | 2007-08-08 12:41 | 2022-09-04 20:45 | MySQL Server: Optimizer | Verified (5065 days) | S3 | 5.0.40, 5.1, 5.2, 5.0 BK | Any | Any | Query from EXPLAIN EXTENDED .. SHOW WARNINGS returns different result |
30342 | 2007-08-09 18:52 | 2015-10-07 14:54 | MySQL Server: Optimizer | Verified (3096 days) | S5 | 5.0.37, 5.6.17 | Any | Any | Equality propagation can make optimization much slower |
31446 | 2007-10-08 12:14 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5643 days) | S5 | 5.0.44, 5.0.37, 6.0.2 Alpha | Any | Any | Inefficient index use with order by and joins |
31901 | 2007-10-29 2:51 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5889 days) | S5 | 5.0.45 | Any | Any | read_rnd_buffer_size doesn't seem to be used as written in Reference Manual |
32341 | 2007-11-13 19:29 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5643 days) | S3 | 5.0.41, 5.0.52 | Linux | Any | Subquery does not use index with session variable, works with string literal |
34078 | 2008-01-26 14:19 | 2020-05-03 20:45 | MySQL Server: Optimizer | Verified (5880 days) | S3 | 4.1,5.0,5.1,6.0-BK | Any (Linux) | Any | ref access is not used for varchar column |
34080 | 2008-01-26 17:25 | 2020-05-03 20:45 | MySQL Server: Optimizer | Verified (5907 days) | S3 | 5.0.54, 5.0.45 | Linux (Ubuntu) | Any | EXPLAIN EXTENDED converts NULL to empty string |
34310 | 2008-02-05 14:51 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (3754 days) | S5 | 5.0.51a-log, 5.0.54, 5.6.14 | Linux | Any | Optimizer is inefficient by using ORDER BY function() and LIMIT |
34666 | 2008-02-19 14:11 | 2020-05-03 20:45 | MySQL Server: Optimizer | Verified (5814 days) | S3 | 5.0/5.1/6.0.4 | Any | Any | Incomplete metadata returned to client on view + group by + Innodb/Falcon |
35633 | 2008-03-28 8:19 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5845 days) | S1 | 5.0.54, 5.0.56 | Linux (2.6.25-rc4) | Any | Column cant be NULL error on SELECT...FROM (SELECT not_null_column, agg_func...) |
35724 | 2008-03-31 22:24 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5504 days) | S2 | MySQL 5.0.51a-community-nt, 5.1, 6.0 BK | Any | Any | Non-found left join data passed as a parameter to a function in WHERE |
36195 | 2008-04-18 2:29 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5814 days) | S3 | 5.1-bk | Any | Any | mysqld calls handler->cond_push twice |
36300 | 2008-04-23 17:49 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5190 days) | S3 | 4.1.26, 5.0.32, 5.0+, 5.1.43-bzr, 6.0.14-bzr | Linux | Any | min() and max() functions returns NULL when using NOT + BETWEEN in where |
36422 | 2008-04-30 2:19 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5812 days) | S3 | 6.0.x | Any | Any | EXPLAIN EXTENDED; SHOW WARNINGS doesn't have ON expression for semi-joins |
36725 | 2008-05-14 20:19 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5603 days) | S2 | 5.1.22/5.0BK/5.1BK | Linux (Ubuntu 7.04) | Any | UPDATE takes too long to execute |
36817 | 2008-05-20 13:19 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5381 days) | S5 | 5.0.54a,5.1.19, 5.1.25, 5.0.60, 5.5 | Any | Any | Non optimal index choice, depending on index creation order |
37053 | 2008-05-29 4:11 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5673 days) | S3 | 4.1, 5.0, 5.1,6.0.5 | Any (Linux, Solaris) | Any | Optimizer unnecessarily uses temporary and filesort with ORDER BY |
93845 | 2019-01-07 21:55 | 2021-08-23 12:23 | MySQL Server: Optimizer | Verified (1906 days) | S2 | 5.7,8.0.11,8.0.13 | Any | Any | Optimizer choose wrong index, sorting index instead of filtering index |
94224 | 2019-02-06 16:45 | 2019-11-17 10:39 | MySQL Server: Optimizer | Verified (1877 days) | S3 | 5.6, 5.6.43 | Any (any) | Any (any) | [5.6] Optimizer reconsiders index based on index definition order, not value |
94548 | 2019-03-04 15:31 | 2019-03-05 10:03 | MySQL Server: Optimizer | Verified (1851 days) | S3 | 5.7, 5.7.25, 8.0.15 | CentOS (7) | Any | Optimizer error evaluating JSON_Extract |
94611 | 2019-03-10 2:14 | 2019-03-10 5:32 | MySQL Server: Optimizer | Verified (1846 days) | S2 | 8.0.15-rds-dev, 8.0.15, 5.7.25,5.6.43 | CentOS | Any | Wrong results returned with "group by" |
94612 | 2019-03-10 2:18 | 2020-12-13 18:00 | MySQL Server: Optimizer | Verified (1846 days) | S2 | 8.0.15-rds-dev, 8.0.15, 5.7.25,5.6.43 | CentOS | Any | Wrong results are returned with "group by" |
94731 | 2019-03-21 6:08 | 2019-03-21 12:38 | MySQL Server: Optimizer | Verified (1835 days) | S3 | 5.7.25 | Any | Any | Optimizer hints removed from views definition |
94795 | 2019-03-27 7:07 | 2019-03-27 9:19 | MySQL Server: Optimizer | Verified (1829 days) | S2 | 5.7.22, 5.7.25 | Oracle Linux (6.8) | x86 | wrong results with GROUP_CONCAT |
94800 | 2019-03-27 14:11 | 2023-06-27 12:31 | MySQL Server: Optimizer | Verified (1829 days) | S2 | 5.7.23-4 | CentOS | Any | Lost connection (for Debug version) or wrong result (for release version) |
94903 | 2019-04-04 8:39 | 2020-08-26 12:32 | MySQL Server: Optimizer | Verified (1817 days) | S3 | 8.0.15 | Any | Any | optimazer chooses inefficient plan for order by + limit in subquery |
94973 | 2019-04-10 16:12 | 2019-04-25 23:04 | MySQL Server: Optimizer | Verified (1800 days) | S2 | 5.7.25 | Linux (Ubuntu 4.15.0-47-generic) | x86 (64 bit) | Wrong result with subquery in where clause and order by |
95020 | 2019-04-15 10:11 | 2019-04-24 13:02 | MySQL Server: Optimizer | Verified (1802 days) | S5 | 5.7.25 | CentOS | Any | select no rows return but check profile process Creating sort index |
95041 | 2019-04-17 3:12 | 2019-06-03 13:52 | MySQL Server: Optimizer | Verified (1763 days) | S3 | 5.6.41 | Any | Any | select with union cause ERROR1169(23000)Can't write,because of unique constraint |
95058 | 2019-04-18 18:12 | 2019-04-25 2:29 | MySQL Server: Optimizer | Verified (1800 days) | S3 | 5.7.21 | Any | Any | Index not used for column with IS TRUE or IS FALSE operators |
95303 | 2019-05-08 16:17 | 2019-05-09 14:53 | MySQL Server: Optimizer | Verified (1786 days) | S2 | 8.0.15, 5.6.36, 5.6.44, 5.7.26 | Linux | x86 | RIGHT ... IN evaluating to 1 within user function, 0 outside of user function |
95416 | 2019-05-20 0:33 | 2019-05-22 21:45 | MySQL Server: Optimizer | Verified (1775 days) | S2 | 5.7.25,8.0.15, 5.6.44, 5.7.26, 8.0.16 | Any | Any | ZERO Date is both NULL and NOT NULL |
95543 | 2019-05-27 12:37 | 2019-05-29 12:34 | MySQL Server: Optimizer | Verified | S2 | 5.7.26 | Any | Any | optimizer prefers index for order by rather than filtering - (70x slower) |
95776 | 2019-06-13 2:34 | 2019-06-13 5:38 | MySQL Server: Optimizer | Verified (1751 days) | S3 | 5.7.15-log MySQL Community Server (GPL), 5.6.44, 5.7.26, 8.0.16 | CentOS | Any | About FUNCTION STDDEV_SAMP:Data only in different order |
95823 | 2019-06-15 10:54 | 2019-06-16 5:57 | MySQL Server: Optimizer | Verified (1748 days) | S3 | 8.0, 5.7.26, 8.0.16 | Any | Any | EXPLAIN FORMAT=JSON shows incorrect information in used_key_parts |
95824 | 2019-06-15 11:07 | 2019-06-16 5:58 | MySQL Server: Optimizer | Verified (1748 days) | S3 | 5.7.26,8.0.16 | Any | Any | Optimizer trace prints ranges incorrectly for multi-part keys |
95936 | 2019-06-23 20:54 | 2019-10-18 15:41 | MySQL Server: Optimizer | Verified (1737 days) | S3 | 5.7.25 | CentOS | x86 | insert into ... select does not work with repeatable read |
95938 | 2019-06-24 6:51 | 2019-07-23 11:46 | MySQL Server: Optimizer | Verified (1711 days) | S3 | 8.0.16, 5.7.26, 5.6.44 | Ubuntu | x86 | Function return value with newline yields wrong result when used as a boolean |
95957 | 2019-06-24 16:26 | 2019-06-25 5:15 | MySQL Server: Optimizer | Verified (1739 days) | S3 | 8.0.16, 5.7.26, 5.6.44 | Ubuntu | x86 | IN operator issue when comparing signed column and the column cast to unsigned |
95960 | 2019-06-24 18:55 | 2019-09-26 12:36 | MySQL Server: Optimizer | Verified (1712 days) | S3 | 8.0.16, 5.7.26, 5.6.44 | Ubuntu | x86 | The logical operators &, |, and ^ do not ignore newlines in TEXT |
96087 | 2019-07-04 3:06 | 2019-07-24 5:26 | MySQL Server: Optimizer | Verified (1730 days) | S2 | 8.0.16, 5.7.26, 5.6.44 | Any | Any | DIV + const expression return wrong data |
96090 | 2019-07-04 8:01 | 2019-07-10 14:19 | MySQL Server: Optimizer | Verified (1725 days) | S3 | 5.7.26 MySQL Community Server | Linux | Any | select exists return wrong result while subquery contains limit offset. |
96137 | 2019-07-09 9:20 | 2019-07-09 16:25 | MySQL Server: Optimizer | Verified (1725 days) | S2 | 5.7.17 MySQL Community Server | Linux | Any | NOT(NOT( FIELD > ALL (SUBQUERY) )) 'S RESULT NOT EQUAL FIELD > ALL (SUBQUERY) |
96379 | 2019-07-31 5:55 | 2019-08-02 7:03 | MySQL Server: Optimizer | Verified (1702 days) | S3 | 8.0.16, 8.0.17, 5.7.27 | Windows | x86 | First query successfull, second - ERROR 1270 (HY000): Illegal mix of collations |
96503 | 2019-08-12 3:31 | 2019-08-12 5:20 | MySQL Server: Optimizer | Verified (1691 days) | S3 | 8.0.17, 5.6.45, 5.7.27 | Any | Any | last_day does not return null with invalid argument "2011-01-00" |
83627 | 2016-11-01 8:16 | 2016-11-01 9:36 | MySQL Server: Optimizer | Verified (2705 days) | S3 | 5.7/8.0 | Linux | Any | inconsistent results with generated column when meets char and padding |
83722 | 2016-11-07 13:28 | 2020-06-24 9:10 | MySQL Server: Optimizer | Verified (2699 days) | S3 | 5.7/8.0 | Ubuntu (16.04) | Any | UNION with outer LIMIT can return wrong number of rows |
83856 | 2016-11-17 4:19 | 2019-11-15 17:31 | MySQL Server: Optimizer | Verified (2658 days) | S3 | 5.7.13,5.7.16 | CentOS | Any | Index ref not used for multi-column IN - type or collation conversion warning |
84024 | 2016-12-01 2:40 | 2016-12-02 9:07 | MySQL Server: Optimizer | Verified (2674 days) | S3 | 5.7.16, 5.6.34 | Any | Any | Optimizer thinks clustered primary key is not covering |
84416 | 2017-01-04 23:11 | 2017-01-05 11:26 | MySQL Server: Optimizer | Verified (2640 days) | S3 | 5.6 and 5.7 | Any | Any | MySQL updates 0000-00-00 00:00:00 for datetime type |
84638 | 2017-01-24 12:40 | 2017-01-30 6:47 | MySQL Server: Optimizer | Verified (2619 days) | S3 | 5.6, 5.7 | Any | Any | Missing FROM clause returns error when using INTO at the end of the statement |
84720 | 2017-01-30 12:09 | 2017-01-30 13:19 | MySQL Server: Optimizer | Verified (2615 days) | S3 | 5.6.27,5.7, 5.7.17 | Any | Any | WITH ROLLUP not providing expected NULL values |
84858 | 2017-02-07 13:09 | 2017-02-09 6:34 | MySQL Server: Optimizer | Verified (2605 days) | S3 | 5.6, 5.7, 5.6.35 | Any | Any | Time is spent at "statistics" stage for primary key lookups |
85126 | 2017-02-22 10:42 | 2017-02-28 7:19 | MySQL Server: Optimizer | Verified (2586 days) | S1 | 5.6.35 | Any | Any | Delete by range in presence of partitioning and no PK always picks wrong index |
85188 | 2017-02-27 2:33 | 2017-02-27 7:30 | MySQL Server: Optimizer | Verified (2587 days) | S3 | 5.6.34,5.6.35, 5.7.17 | Any | Any | warnings of explain extended does not convert charset |
96647 | 2019-08-26 6:21 | 2019-08-26 7:38 | MySQL Server: Optimizer | Verified (1677 days) | S3 | 5.7.22, 5.7.27, 8.0.17 | Any | Any | Query Rewrite plugin database_pattern column length is too shot |
96688 | 2019-08-29 4:14 | 2019-08-29 11:31 | MySQL Server: Optimizer | Verified (1674 days) | S3 | 8.0.16, 8.0.17 | Any | Any | sql query 'where' condition |
96958 | 2019-09-20 21:42 | 2019-09-22 14:28 | MySQL Server: Optimizer | Verified (1650 days) | S3 | 8.0 | Any | Any | MySQL optimizer wrongly chooses to use a bigger and inefficient index for query |
97339 | 2019-10-23 8:06 | 2021-07-23 13:05 | MySQL Server: Optimizer | Verified (1613 days) | S2 | 5.7.18, 5.7.28, 5.6.46 | Any | Any | bin() function return Incorrect result set |
97648 | 2019-11-14 20:25 | 2019-11-19 14:48 | MySQL Server: Optimizer | Verified (1593 days) | S3 | 5.7, 8.0 | Any | Any | Bug in order by clause in union clause |
98055 | 2019-12-23 11:37 | 2020-01-24 13:03 | MySQL Server: Optimizer | Verified (1527 days) | S3 | 5.7 | Red Hat (amezon RDS) | Any | MySQL Optimizer Bug not picking right index |
98520 | 2020-02-08 9:37 | 2020-05-05 14:51 | MySQL Server: Optimizer | Verified (1424 days) | S5 | 8.0 | Any | ARM | Suboptimal implementations for some load/store functions for little-endian arch |
98647 | 2020-02-18 13:06 | 2020-02-18 14:03 | MySQL Server: Optimizer | Verified (1501 days) | S3 | 5.7.29 | Windows | x86 | Bad SUM result with GROUP BY |
98770 | 2020-02-28 4:02 | 2020-03-03 15:05 | MySQL Server: Optimizer | Verified (1487 days) | S5 | 8.0.19 | Any | Any | Non-covering full index scan is always preferred over table scan for GROUP BY |
98771 | 2020-02-28 6:29 | 2020-03-02 18:39 | MySQL Server: Optimizer | Verified (1491 days) | S2 | 5.7, 5.7.29 | Any | Any | Performance impact while selecting data from a JSON type column |
98838 | 2020-03-05 6:11 | 2020-03-05 6:22 | MySQL Server: Optimizer | Verified (1485 days) | S2 | mysql5.7.22 mysql5.7.29 | Any | Any | select distinct will return wrong result in one case |
99130 | 2020-03-31 12:18 | 2020-04-01 13:10 | MySQL Server: Optimizer | Verified (1459 days) | S3 | 8.0.19,5.6.47, 5.7.29 | Any | Any | BETWEEN malfunctions when comparing a string containing a newline |
99135 | 2020-03-31 16:54 | 2020-04-01 5:11 | MySQL Server: Optimizer | Verified (1458 days) | S3 | 8.0.19, 5.6.47, 5.7.29 | Any | Any | BETWEEN malfunctions when comparing large numbers |
99142 | 2020-04-01 7:39 | 2020-04-01 8:27 | MySQL Server: Optimizer | Verified (1458 days) | S2 | 8.0.16, 8.0.19, 5.7.29 | Any | Any | The result mismatches when DISTINCT syntax exists |
99146 | 2020-04-01 9:49 | 2020-04-01 10:42 | MySQL Server: Optimizer | Verified (1458 days) | S3 | 8.0.19, 5.7.29 | Any | Any | Comparison on FLOAT column and large value malfunctions |
99149 | 2020-04-01 11:07 | 2020-04-01 11:46 | MySQL Server: Optimizer | Verified (1458 days) | S3 | 8.0.19 | Any | Any | BETWEEN query malfunctions for special character and TEXT index |
99244 | 2020-04-14 3:22 | 2020-04-22 12:45 | MySQL Server: Optimizer | Verified (1438 days) | S1 | 8.0.19 | Any | Any | bad performance in hash join because join with no join condition between tables |
99245 | 2020-04-14 3:55 | 2021-05-31 8:40 | MySQL Server: Optimizer | Verified (1445 days) | S3 | 8.0.19, 5.6.47, 5.7.29 | CentOS | Any | Wrong result is returned with DISTINCT syntax |
99273 | 2020-04-16 6:02 | 2020-04-16 7:53 | MySQL Server: Optimizer | Verified (1443 days) | S2 | 8.0.19, 5.7.29 | Any | Any | Item_ref in Having Clause points to invalid outer table field |
99340 | 2020-04-23 20:36 | 2020-04-24 6:48 | MySQL Server: Optimizer | Verified (1435 days) | S2 | 8.0.19, 5.6.47, 5.7.29 | Any | Any | RAND not always returning the same value for equal argument N |
99354 | 2020-04-25 13:34 | 2020-04-25 18:21 | MySQL Server: Optimizer | Verified (1434 days) | S3 | 5.7.26, 8.0.19 | Any | Any | Nondeterministic stored function returns incorrect results |
99381 | 2020-04-28 7:26 | 2020-04-29 7:07 | MySQL Server: Optimizer | Verified (1430 days) | S2 | 8.0.20 | Any | Any | ORDER_BY Index-level optimizer hint implies NO_JOIN_INDEX for second table |
99414 | 2020-04-30 17:48 | 2020-05-20 12:20 | MySQL Server: Optimizer | Verified (1425 days) | S3 | 8.0.20 | Any | Any | Where exists performance 8.0.16 onwards |
99459 | 2020-05-06 8:17 | 2020-05-08 13:41 | MySQL Server: Optimizer | Verified (1421 days) | S3 | 5.6,5.7,8.0 | Any | Any | SQL run with GROUP_MIN_MAX may infinite loop and never return |
99499 | 2020-05-09 22:13 | 2020-05-25 11:25 | MySQL Server: Optimizer | Verified (1417 days) | S3 | 5.7.29 | Any | Any | Incorrect result when constant equailty expression is used in LEF JOIN condition |
81469 | 2016-05-17 21:51 | 2016-05-18 6:54 | MySQL Server: Optimizer | Verified (2872 days) | S3 | 5.6.30, 5.7.12 | Any | Any | Slow performance for IN subquery and UNION |
81803 | 2016-06-10 12:35 | 2016-06-15 16:58 | MySQL Server: Optimizer | Verified (2844 days) | S5 | >=5.1 | Any | Any | Mysql 5.1 and later Update performance regression |
82021 | 2016-06-27 17:46 | 2016-06-28 6:11 | MySQL Server: Optimizer | Verified (2831 days) | S3 | 5.6.31, 5.7.13 | Any | Any | Difference in range behaviour between range analyzer and query execution engine |
82074 | 2016-06-30 21:50 | 2016-07-01 5:04 | MySQL Server: Optimizer | Verified (2828 days) | S3 | 5.5.49, 5.6.30, 5.7.13 | Any | Any | Select_scan set even if table scan was not used |
82334 | 2016-07-25 10:58 | 2016-12-16 14:00 | MySQL Server: Optimizer | Verified (2660 days) | S2 | 5.7.13 | CentOS | Any | unexpected order for grouped query |
82338 | 2016-07-25 21:05 | 2021-12-29 17:53 | MySQL Server: Optimizer | Verified (821 days) | S3 | any, 5.6.31, 5.7.13 | Any | Any | Please support ASC/DESC index traversal on ASC/ASC indexing. |
82363 | 2016-07-27 19:28 | 2016-07-28 8:11 | MySQL Server: Optimizer | Verified (2801 days) | S3 | 5.7 and every other | Any | Any | impossible const condition still followed in a JOIN |
82565 | 2016-08-12 12:31 | 2016-08-13 5:09 | MySQL Server: Optimizer | Verified (2785 days) | S3 | 8.0.0-dmr | Any | Any | Conditions are only constant propagated within an AND condition |
82725 | 2016-08-25 15:55 | 2016-09-14 6:28 | MySQL Server: Optimizer | Verified (2753 days) | S5 | 5.7.14, 5.7.15 | CentOS (Linux rda-db-rep.ucar.edu 3.10.0-327.28.2.el7.x86_64 #1 SMP Wed Aug 3 11:11:39 UTC 2016 x86_64 x86_6) | Any | Extremely slow query when optimizer_switch='derived_merge=ON' |
82751 | 2016-08-27 9:31 | 2017-06-13 4:51 | MySQL Server: Optimizer | Verified (2771 days) | S3 | 5.6 | Any (https://aws.amazon.com/amazon-linux-ami/2016.03-release-notes/) | Any | Create View appears to corrupt geospatial function names in version 5.6 |
82805 | 2016-08-31 2:20 | 2016-08-31 9:47 | MySQL Server: Optimizer | Verified (2767 days) | S2 | 5.7.10, 5.7.14 | Any | Any | Having clause condition fails on join table with TEXT field |
83006 | 2016-09-15 7:51 | 2016-09-15 8:36 | MySQL Server: Optimizer | Verified (2752 days) | S2 | 5.6.24 | Any | Any | Incorrect processing of WHERE condition with ELT |
83062 | 2016-09-20 13:18 | 2018-04-24 20:15 | MySQL Server: Optimizer | Verified (2746 days) | S3 | 5.6.32, 5.7.14, 5.6.33, 5.7.15 | Any | Any | it's no longer possible to determine used key parts by looking at key_length |
83071 | 2016-09-21 8:02 | 2016-09-21 8:34 | MySQL Server: Optimizer | Verified (2746 days) | S3 | 5.7.14, 5.6.*, 5.7.15 | Any | Any | MySQL prefers first declared index over more useful other indexes |
83248 | 2016-10-03 15:57 | 2023-02-22 1:40 | MySQL Server: Optimizer | Verified (2734 days) | S3 | 8.0.0, 5.7.15 | Any | Any | Partition pruning is not working with LEFT JOIN |
83323 | 2016-10-10 18:02 | 2018-04-13 12:41 | MySQL Server: Optimizer | Verified (2531 days) | S3 | 5.7, 5.6, 8.0.1 | Any | Any | Optimizer chooses wrong plan when joining 2 tables |
90847 | 2018-05-12 16:57 | 2018-08-18 11:52 | MySQL Server: Optimizer | Verified (2146 days) | S1 | 5.7.22, 8.0.11 | Windows (W10 64bit) | x86 | Query returns wrong data if order by is present |
91139 | 2018-06-04 20:37 | 2021-01-13 11:59 | MySQL Server: Optimizer | Verified (1172 days) | S5 | 8.0.11 | Any | Any | use index dives less often |
91362 | 2018-06-21 15:18 | 2019-02-13 14:05 | MySQL Server: Optimizer | Verified (2107 days) | S1 | 5.6.36 - 5.6.40 and 5.7.18 - 5.7.22, 5.6.40, 5.7.22 | Any | Any | Incorrect query results under certain conditions. |
91418 | 2018-06-26 7:08 | 2018-09-07 13:32 | MySQL Server: Optimizer | Verified (2103 days) | S3 | 5.7,8.0.11, 5.7.22 | Any | Any | derived_merge causing inccorect results with distinct subquery and uuid() |
91780 | 2018-07-24 20:10 | 2018-07-25 14:45 | MySQL Server: Optimizer | Verified (2074 days) | S3 | 8.0.11, 5.7.22 | Any | Any | Inconsistent printing of EXPLAIN queries. |
91878 | 2018-08-02 23:09 | 2019-09-03 5:29 | MySQL Server: Optimizer | Verified (2053 days) | S3 | 5.7.23, 8.0.12, 5.7.22, 8.0.11 | Any | Any | Wrong results with optimizer_switch='derived_merge=ON'; |
91898 | 2018-08-03 23:15 | 2018-09-03 4:42 | MySQL Server: Optimizer | Verified (2062 days) | S3 | 8.0.11,5.5.60, 5.6.41, 5.7.23,8.0.12 | Any | Any | Lost of precision in Item_func_mod::real_op |
92020 | 2018-08-15 11:25 | 2019-02-18 16:46 | MySQL Server: Optimizer | Verified (2053 days) | S3 | 5.7.23, 8.0.12 | Any | Any | Introduce new SQL mode rejecting queries with results depending on query plan |
92092 | 2018-08-20 19:21 | 2022-03-23 11:15 | MySQL Server: Optimizer | Verified (2047 days) | S3 | 8.0.11, 5.7.17 | Any | Any | getTableName gives inconsistent results |
92297 | 2018-09-05 16:29 | 2018-11-12 21:51 | MySQL Server: Optimizer | Verified (2031 days) | S3 | 8.0.12, 5.7.23, 5.6.41, 5.5.61 | Any | Any | GROUP_CONCAT doesn't work properly with FLOAT(M,D) fields with value of M digits |
92421 | 2018-09-14 9:57 | 2021-06-08 6:49 | MySQL Server: Optimizer | Verified (2011 days) | S5 | 5.7 | Any | Any | Queries with views and operations over local variables don't use indexes |
92466 | 2018-09-17 16:05 | 2018-09-18 9:14 | MySQL Server: Optimizer | Verified (2019 days) | S3 | 5.7.22, 5.7.23, 8.0.12 | Any | Any | Case function error on randomly generated values |
92538 | 2018-09-24 3:42 | 2018-10-01 8:51 | MySQL Server: Optimizer | Verified (2006 days) | S3 | 5.7.23, 5.7.17 | Windows (windows10) | x86 | when I use CachedRowSet. error:Table doesn't exist |
92654 | 2018-10-03 11:16 | 2018-10-03 14:05 | MySQL Server: Optimizer | Verified (2004 days) | S3 | 8.0.12, 5.7.23 | Windows | x86 | GROUP BY fails for queries when a temporary table is involved |
92850 | 2018-10-19 0:46 | 2018-10-22 5:31 | MySQL Server: Optimizer | Verified (1985 days) | S3 | 5.7.23 | Any | Any | Bad select+order by+limit performance in 5.7 |
93049 | 2018-11-01 23:03 | 2018-11-02 7:06 | MySQL Server: Optimizer | Verified (1974 days) | S3 | 8.0.13, 5.7.24, 5.6.42 | Any | Any | ORDER BY pk, otherdata should just use PK |
93188 | 2018-11-14 11:16 | 2020-07-15 12:53 | MySQL Server: Optimizer | Verified (1960 days) | S5 | 5.7 | Any | Any | Optimiser chose incorrect join order inside of derived table |
93360 | 2018-11-27 9:41 | 2018-12-12 14:48 | MySQL Server: Optimizer | Verified (1934 days) | S5 | 5.6.16,5.7.23 | Linux | x86 | mysterious optimizer behavior |
93418 | 2018-11-30 1:07 | 2018-11-30 5:01 | MySQL Server: Optimizer | Verified (1946 days) | S3 | 5.7, 5.7.24 | Any | Any | SELECT with IN clause get wrong result set |
93455 | 2018-12-03 16:46 | 2018-12-06 14:04 | MySQL Server: Optimizer | Verified (1941 days) | S3 | 5.7.24 | Any | Any | max_execution_time optimizer hint has no effect on boolean full-text search |
93491 | 2018-12-05 17:40 | 2018-12-06 5:39 | MySQL Server: Optimizer | Verified (1940 days) | S3 | 8.0.13, 5.7.24, 5.6.42 | Any | Any | Optimizer does not correctly consider attached conditions in planning |
93606 | 2018-12-14 7:53 | 2021-11-23 15:30 | MySQL Server: Optimizer | Verified (1905 days) | S2 | 5.6.40,5.7.24 | CentOS (6.9) | x86 | when use Connector/J preparestatement mysql returns the wrong result |
88014 | 2017-10-06 17:33 | 2017-10-23 9:13 | MySQL Server: Optimizer | Verified (2349 days) | S3 | 5.7.19 | Linux | Any | Rewrite plugin fails to accept pattern with multiple values IN() |
88127 | 2017-10-17 21:45 | 2021-11-23 7:22 | MySQL Server: Optimizer | Verified (2353 days) | S3 | 5.7.19, 5.7.20 | Any | Any | Index not used for 'order by' query with utf8mb4 character set |
88181 | 2017-10-23 5:30 | 2018-06-11 19:55 | MySQL Server: Optimizer | Verified (2349 days) | S3 | 5.7.20 | Any | Any | Another example of optimizer choosing ref over range when range is faster |
88252 | 2017-10-27 14:38 | 2017-10-30 10:41 | MySQL Server: Optimizer | Verified (2345 days) | S3 | 5.7 | Any | Any | Incorrect result when using IS NULL expression |
88671 | 2017-11-28 0:16 | 2017-12-04 15:41 | MySQL Server: Optimizer | Verified (2307 days) | S5 | 5.7.19 | Any | Any | ALL + BNL chosen over REF in query plan with a simple SELECT + JOIN |
88896 | 2017-12-13 12:12 | 2017-12-14 5:34 | MySQL Server: Optimizer | Verified (2297 days) | S3 | 5.6, 5.7.20, 8.0.3, 5.6.38 | Any | Any | Different query result, depending from data load pattern |
89051 | 2017-12-25 19:06 | 2018-01-02 9:54 | MySQL Server: Optimizer | Verified (2285 days) | S3 | 5.7.20 | Any | Any | EXPLAIN output is different for same content depending when index was added |
89149 | 2018-01-08 23:41 | 2018-01-16 17:07 | MySQL Server: Optimizer | Verified (2264 days) | S5 | 5.7.20 | Red Hat (7.4) | Any | SELECT DISTINCT on multiple TEXT columns is slow |
89182 | 2018-01-11 9:51 | 2018-01-11 13:10 | MySQL Server: Optimizer | Verified (2269 days) | S3 | 5.6.38, 5.7.20, 8.0.3 | Any | Any | Optimizer unable to ignore index part entering less optimal query plan |
89367 | 2018-01-24 2:52 | 2018-01-24 9:04 | MySQL Server: Optimizer | Verified (2256 days) | S3 | 5.7.20, 5.7.21 | Any | Any | Storing result in a variable(UDV) causes query on a view to use derived tables |
89473 | 2018-01-30 16:56 | 2018-01-30 18:16 | MySQL Server: Optimizer | Verified (2250 days) | S3 | 5.7.21 | Any | Any | Inconsistent metadata from derived tables usage. |
89481 | 2018-01-31 6:57 | 2018-02-06 11:38 | MySQL Server: Optimizer | Verified (2247 days) | S5 | 5.6.25.5.7.18 | Red Hat | Any | mysql does't optimize range query when using where |
89621 | 2018-02-12 1:10 | 2018-02-13 17:33 | MySQL Server: Optimizer | Verified (2236 days) | S3 | 5.6.17 | MacOS (10.13.3) | Any | ORDER BY BINARY on alias throws Error:1247 |
89650 | 2018-02-13 13:55 | 2018-02-14 6:56 | MySQL Server: Optimizer | Verified (2235 days) | S3 | 5.7, 8.0, 5.6.39, 5.7.21 | Any | Any | Incorrect ordering with memory tables and long keys |
90043 | 2018-03-13 8:53 | 2019-02-18 16:43 | MySQL Server: Optimizer | Verified (2207 days) | S3 | 5.6, 5.7 | Linux | Any | convert_tz doesn't handle offset more than 13 hours |
85945 | 2017-04-14 8:01 | 2017-04-17 8:08 | MySQL Server: Optimizer | Verified (2538 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 (2453 days) | S5 | 8.0.1 | Any | Any | MySQL is much slower in 5.7 vs 5.6 |
86220 | 2017-05-08 16:35 | 2018-11-06 12:50 | MySQL Server: Optimizer | Verified (1971 days) | S3 | 5.7.18 | Any | Any | Query returns wrong results when using UDF in view |
86574 | 2017-06-03 16:16 | 2017-06-03 19:36 | MySQL Server: Optimizer | Verified (2491 days) | S3 | 5.6 | Any | Any | Confusing EXPLAIN output for INSERT Queries |
86610 | 2017-06-07 14:36 | 2017-06-16 6:47 | MySQL Server: Optimizer | Verified (2480 days) | S3 | 5.7 | Linux (centos7) | Any | Mysql 5.6 and 5.7.17 enterprise "semi join" results are different |
86973 | 2017-07-06 13:26 | 2017-07-07 7:19 | MySQL Server: Optimizer | Verified (2457 days) | S1 | 5.6, 5.5.56, 5.6.36, 5.7.18 | Any | Any | BIN() function error |
87264 | 2017-07-31 21:49 | 2017-08-31 9:04 | MySQL Server: Optimizer | Verified (2431 days) | S2 | 5.6.36, 5.6.37, 5.7.19 | CentOS (release 6.9) | Any | Query not returning expected results |
87339 | 2017-08-07 12:36 | 2018-10-30 8:39 | MySQL Server: Optimizer | Verified (1977 days) | S2 | 5.7 and 8.0, 8.0.13 | Any | Any | Duplicating the condition gives a different result set |
87644 | 2017-09-01 22:19 | 2022-09-06 8:01 | MySQL Server: Optimizer | Verified (2165 days) | S2 | 5.7.18 | CentOS (6 (x86_64)) | Any | Order by on 'datetime' column not working with LIMIT <row_count> |
87670 | 2017-09-05 9:32 | 2017-09-06 7:54 | MySQL Server: Optimizer | Verified (2396 days) | S3 | 5.7.18, 5.6.37, 5.7.19 | Any | Any | Force index for group by is not always honored |
87915 | 2017-09-29 13:47 | 2018-04-27 14:20 | MySQL Server: Optimizer | Verified (2163 days) | S3 | 5.7.18/trunk | Any | Any | Constant in multi-byte character fails to propagate to dependent subquery |
87947 | 2017-10-03 4:00 | 2018-06-11 19:57 | MySQL Server: Optimizer | Verified (2363 days) | S5 | 5.7.19 | Any | Any | Optimizer chooses ref over range when access when range access is faster |
68072 | 2013-01-12 18:02 | 2013-01-13 15:08 | MySQL Server: Optimizer | Verified (4093 days) | S2 | 5.1, 5.5 | Any (Win64, CentOS Linux) | Any | MySQL 5.1 issue with timediff, group by on multiple columns, join, primary key |
68154 | 2013-01-23 13:07 | 2016-10-09 20:45 | MySQL Server: Optimizer | Verified (4082 days) | S3 | 5.6.* | Any | Any | explain output 'Using index condition' not proper |
68554 | 2013-03-03 16:16 | 2022-03-14 16:43 | MySQL Server: Optimizer | Verified (4029 days) | S5 | 5.6.10 | Any | Any | Optimizer wrongly choses covering index over ICP |
68564 | 2013-03-04 21:17 | 2016-02-10 16:45 | MySQL Server: Optimizer | Verified (4041 days) | S2 | 5.5.8-log | Any | Any | ROLLUP-NULL sometimes becomes other than NULL |
68825 | 2013-04-01 16:28 | 2018-07-11 15:09 | MySQL Server: Optimizer | Verified (3132 days) | S5 | 5.6.10 | Any | Any | performance regressions for single-threaded workloads |
68852 | 2013-04-03 9:27 | 2013-04-03 9:41 | MySQL Server: Optimizer | Verified (4013 days) | S3 | 5.5.28 | Any | Any | Wrong behavior with aggregate functions, dates and between |
68899 | 2013-04-09 9:38 | 2013-04-10 11:00 | MySQL Server: Optimizer | Verified (4006 days) | S3 | 5.5.30, 5.6.10 | Linux | Any | High join_buffer_size prevents use of spatial index on joined tables |
68919 | 2013-04-10 14:25 | 2013-04-10 14:33 | MySQL Server: Optimizer | Verified (4006 days) | S5 | 5.6.10 | Any | Any | Performance regression when DS-MRR is used for query with small limit |
68979 | 2013-04-17 3:47 | 2018-07-11 15:11 | MySQL Server: Optimizer | Verified (3964 days) | S5 | 5.6.10 | Linux | Any | performance regression of MySQL 5.6.10? |
69203 | 2013-05-11 17:35 | 2020-12-06 20:45 | MySQL Server: Optimizer | Verified (3794 days) | S3 | 5.7 | Linux (Ubuntu 12.04 64-bit) | Any | Valgrind warnings and crash on select from an InnoDB table |
69219 | 2013-05-13 20:14 | 2013-05-13 20:32 | MySQL Server: Optimizer | Verified (3973 days) | S5 | 5.6.12 | Any | Any | CREATE TEMPORARY TABLE ... SELECT is slower on 5.6 than on 5.1 |
69285 | 2013-05-20 3:48 | 2013-06-10 10:28 | MySQL Server: Optimizer | Verified (3945 days) | S3 | 5.5+ | Any | Any | count upon not null field can not treated as count(*) |
69350 | 2013-05-30 5:44 | 2014-02-20 5:48 | MySQL Server: Optimizer | Verified | S5 | 5.6 | Any | Any | performance regression between 5.5 and 5.6 for simple statement in routine loop |
69567 | 2013-06-25 8:44 | 2016-06-16 20:30 | MySQL Server: Optimizer | Verified (2843 days) | S3 | 5.6.12 | Any | Any | EXPLAIN FORMAT=JSON lists subquery in optimized_away_subqueries, but it is run |
69729 | 2013-07-12 2:18 | 2018-07-12 12:54 | MySQL Server: Optimizer | Verified (3913 days) | S2 | 5.5.31, 5.5.32 | Any | Any | Bad interaction between MIN/MAX and "NOT BETWEEN" leads to wrong results |
69795 | 2013-07-19 17:54 | 2016-06-16 20:32 | MySQL Server: Optimizer | Verified (2843 days) | S3 | 5.6.12 | Any | Any | EXPLAIN FORMAT=JSON doesn't show Using filesort for UNIONs |
69891 | 2013-08-01 6:33 | 2014-09-18 21:25 | MySQL Server: Optimizer | Verified | S3 | 5.1.31 | Any | Any | since 5.1.31 REPLACE() function concats it's results under certain conditions |
70314 | 2013-09-12 12:28 | 2013-09-12 14:07 | MySQL Server: Optimizer | Verified (3851 days) | S3 | 5.6 | Any | Any | Ambiguous column updated with UPDATE ... JOIN ... USING |
70357 | 2013-09-16 17:35 | 2013-11-21 14:09 | MySQL Server: Optimizer | Verified (3781 days) | S2 | 5.6.13 | Any | Any | Use of group_concat causes having conditions to be ignored |
70359 | 2013-09-16 23:02 | 2013-09-17 7:10 | MySQL Server: Optimizer | Verified (3846 days) | S3 | 5.1, 5.5, 5.6, 5.7 | Any | Any | Wrong result (missing rows) with group by, multi-part key, equality conditions |
70466 | 2013-09-30 7:24 | 2013-09-30 8:45 | MySQL Server: Optimizer | Verified (3833 days) | S2 | 5.5,5.6 | Any | Any | No results when filesorting with a correlation in subquery's HAVING clause |
70491 | 2013-10-02 19:04 | 2013-10-02 20:35 | MySQL Server: Optimizer | Verified (3831 days) | S2 | 5.6.13 | Any | Any | SELECT DISTINCT may return a wrong result if a join buffer is involved |
70555 | 2013-10-08 17:29 | 2013-10-09 8:03 | MySQL Server: Optimizer | Verified (3824 days) | S3 | 5.6.14 | Any | Any | EXPLAIN for INSERT ... SELECT waits for table lock |
70598 | 2013-10-10 22:19 | 2013-10-13 11:23 | MySQL Server: Optimizer | Verified (3820 days) | S3 | 5.5.32,5.5.34, 5.6.14, 5.7.2 | Linux (.6.18-348.16.1.el5) | Any | Premature expression evaluation prevents short-circuited conditionals |
70626 | 2013-10-15 22:08 | 2017-07-17 13:18 | MySQL Server: Optimizer | Verified (3817 days) | S3 | 5.1+ | Linux (Ubuntu 12.04) | Any | select * from t where exists (select * from t limit 0); returns rows |
72501 | 2014-05-01 17:31 | 2014-05-01 18:12 | MySQL Server: Optimizer | Verified | S3 | 5.6.17 | Any | Any | joining NULLs + different collation is not efficient |
72532 | 2014-05-04 19:26 | 2014-05-05 8:42 | MySQL Server: Optimizer | Verified (3616 days) | S3 | 5.6.12, 5.6.19 | Any | Any | DESCRIBE with FULLTEXT does Key=MUL incorrectly |
72646 | 2014-05-14 9:40 | 2014-05-14 12:17 | MySQL Server: Optimizer | Verified (3607 days) | S3 | 5.5 5.6, 5.6.19 | Any | Any | A strange result from explain query |
72711 | 2014-05-21 18:33 | 2014-05-22 8:33 | MySQL Server: Optimizer | Verified (3599 days) | S2 | 5.5.31, 5.5.38 | Any | Any | HOUR() of a DATETIME with date zero occasionally (unpredictably) returns NULL |
72745 | 2014-05-26 4:28 | 2014-05-26 5:48 | MySQL Server: Optimizer | Verified (3595 days) | S2 | 5.5.37, 5.5.38 | Any | Any | Wrong Results When Using Intersect |
72814 | 2014-05-30 9:31 | 2014-07-18 18:56 | MySQL Server: Optimizer | Verified (3588 days) | S3 | 5.6.17 | Any | Any | Assertion `!(ordered_index_usage == ordered_index_void && ... fails |
72815 | 2014-05-30 11:06 | 2014-05-31 14:24 | MySQL Server: Optimizer | Verified (3591 days) | S5 | 5.1, 5.5, 5.6, 5.7 | Any | Any | UPDATE ... WHERE ... ORDER BY... always does a filesort even if not required |
72892 | 2014-06-05 16:27 | 2014-06-09 9:39 | MySQL Server: Optimizer | Verified (3581 days) | S3 | Any | Any | Please allow multiple ranges in the LIMIT clause | |
72996 | 2014-06-13 6:08 | 2015-04-10 7:07 | MySQL Server: Optimizer | Verified (3276 days) | S3 | 5.6.16, 5.6.19, 5.6.18,5.6.23 | Any | Any | desc error on convert |
73046 | 2014-06-19 2:42 | 2016-02-17 11:23 | MySQL Server: Optimizer | Verified (3571 days) | S3 | 5.6.19 | Any | Any | Optimizer chooses wrong plan with (const, range) order by range ASC |
73094 | 2014-06-24 12:24 | 2014-06-25 8:26 | MySQL Server: Optimizer | Verified (3565 days) | S2 | 5.5, 5.6, 5.6.19, 5.7.5 | Linux | Any | MySQL uses all partitions instead necessary ones when using CASE THEN ELSE END |
73136 | 2014-06-27 16:34 | 2015-05-20 15:16 | MySQL Server: Optimizer | Verified (3560 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 |
73284 | 2014-07-13 19:12 | 2014-07-14 8:47 | MySQL Server: Optimizer | Verified (3546 days) | S1 | 5.5.35, 5.5.38 | Any | Any | Wrong query result when search from 2 related views |
73357 | 2014-07-22 14:42 | 2014-07-22 19:10 | MySQL Server: Optimizer | Verified (3538 days) | S3 | 5.6, 5.7 | Any | Any | Wrong result on query involving information_schema |
73603 | 2014-08-15 14:28 | 2015-05-04 13:17 | MySQL Server: Optimizer | Verified (3362 days) | S5 | 5.6.20, 5.6.24 | Windows (Server 2012 R2) | Any | MySQL 5.6.20 Not Using Index |
73825 | 2014-09-06 16:45 | 2014-11-06 11:39 | MySQL Server: Optimizer | Verified (3492 days) | S3 | 5.1, 5.5, 5.6, 5.7 | Any | Any | Wrong result (extra row) with group by, multi-part key |
73907 | 2014-09-12 18:27 | 2014-09-14 3:51 | MySQL Server: Optimizer | Verified (3484 days) | S2 | 5.5/5.6/5.7 | Windows (Server 2008) | Any | REGRESSION: Indexes miss on quoted large numeric bigints |
74049 | 2014-09-24 8:01 | 2014-09-24 10:01 | MySQL Server: Optimizer | Verified (3474 days) | S3 | 5.6.19-67.0, 5.6.22 | Any | Any | Update query use filesort instead of index |
74078 | 2014-09-25 16:15 | 2014-10-16 19:49 | MySQL Server: Optimizer | Verified (3452 days) | S5 | 5.6.19/5.5/5.7 | Linux (Ubuntu 14) | Any | join of large table to small table is slow if small table has less than 7 rows |
74083 | 2014-09-25 18:11 | 2014-10-09 12:58 | MySQL Server: Optimizer | Verified (3459 days) | S5 | 5.6.20, 5.6.22 | Linux (CentOS 6.5) | Any | ENUM index scan is slower than INT index scan |
74105 | 2014-09-26 12:16 | 2014-09-26 12:55 | MySQL Server: Optimizer | Verified (3472 days) | S3 | 5.5.38-0ubuntu0.14.04.1, 5.5.41, 5.1.74 | Linux | Any | Qualified comparisons return true when subquery contains nulls |
74251 | 2014-10-07 14:54 | 2014-10-07 15:55 | MySQL Server: Optimizer | Verified (3461 days) | S3 | 5.1/5.5/5.6 | Any | Any | Syntax error when using DUAL dummy table in UNION subselect with ORDER BY |
74256 | 2014-10-07 22:43 | 2015-11-02 6:19 | MySQL Server: Optimizer | Verified (3362 days) | S2 | 5.6.19, 5.6.22 | Any | Any | index_extensions used incorrectly in select cause performance regression |
74462 | 2014-10-20 19:26 | 2014-11-01 0:57 | MySQL Server: Optimizer | Verified (3436 days) | S3 | 5.6.21 | Any | Any | EXPLAIN FORMAT=JSON produces ordering_operation when no ordering takes place. |
74490 | 2014-10-22 2:08 | 2014-10-22 6:57 | MySQL Server: Optimizer | Verified (3446 days) | S3 | 5.6.20-debug, 5.6.22 | Linux (CentOS 7) | Any | Assertion `table->key_read == 0' failed | sig 6 in close_open_tables |
74542 | 2014-10-24 10:05 | 2014-10-24 10:51 | MySQL Server: Optimizer | Verified (3444 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 (3444 days) | S3 | 5.6/5.7, 5.7.18 | Any | Any | read_only=1 prevents EXPLAIN UPDATE/DELETE/INSERT |
74661 | 2014-11-02 20:20 | 2016-06-16 20:44 | MySQL Server: Optimizer | Verified (2843 days) | S3 | 5.6.21, 5.6.22, 5.7.6 | Any | Any | EXPLAIN FORMAT=JSON says two temptables are used, execution shows just one |
74744 | 2014-11-07 22:45 | 2016-06-16 20:45 | MySQL Server: Optimizer | Verified (2843 days) | S3 | 5.6.21, 5.6.22, 5.7.6 | Any | Any | EXPLAIN FORMAT=JSON produces duplicates_removal where there is none |
74962 | 2014-11-21 13:24 | 2014-11-21 14:20 | MySQL Server: Optimizer | Verified (3416 days) | S3 | 5.5/5.6 | Any | Any | Matching in char field type is not correct |
75121 | 2014-12-05 18:25 | 2014-12-08 8:26 | MySQL Server: Optimizer | Verified (3402 days) | S2 | 5.6.21 | Linux (CentOS 5.11) | Any | IN clause subquery optimization |
75266 | 2014-12-18 16:36 | 2014-12-18 18:19 | MySQL Server: Optimizer | Verified (3389 days) | S2 | 5.6.19 | Any | Any | Setting sum of decimal field on user defined variable is not working as expected |
75447 | 2015-01-08 12:59 | 2015-01-08 13:27 | MySQL Server: Optimizer | Verified (3368 days) | S2 | 5.6, 5.6.24, 5.7.6 | Any | Any | INSERT into a view sometimes ignores default values |
75510 | 2015-01-15 0:36 | 2015-01-16 9:59 | MySQL Server: Optimizer | Verified (3360 days) | S3 | 5.6.21 | Any | Any | MySQL chooses index scan over full table scan |
75668 | 2015-01-28 16:21 | 2015-01-28 20:10 | MySQL Server: Optimizer | Verified (3348 days) | S2 | 5.6.22/5.7 | FreeBSD (FreeBSD 8.4) | Any | Use of Distinct, Group_concat, and Group by together produces 1 NULL row result. |
75967 | 2015-02-19 12:45 | 2015-02-20 8:06 | MySQL Server: Optimizer | Verified (3325 days) | S3 | 5.6, 5.7, 5.6.24 | Any | Any | Wrong result (extra rows) with SQ and comparison to NULL, materialization=off |
75991 | 2015-02-21 18:12 | 2015-02-23 9:59 | MySQL Server: Optimizer | Verified (3322 days) | S3 | 5.6.14-log, 5.6.24 | Windows (Vista) | Any | writ of ALLOW_INVALID_DATES |
75992 | 2015-02-21 18:29 | 2015-02-23 9:45 | MySQL Server: Optimizer | Verified (3322 days) | S3 | 5.6.14-log, 5.6.24 | Windows (Vista) | Any | no warning when, under "ALLOW_INVALID_DATES", an invalid date is discarded |
76029 | 2015-02-24 14:26 | 2015-02-24 15:52 | MySQL Server: Optimizer | Verified (3321 days) | S3 | 5.6.23 | Linux | Any | IN / NOT IN doesn't return correct result when on-disk temporary table is used |
76501 | 2015-03-27 6:50 | 2015-03-27 15:11 | MySQL Server: Optimizer | Verified (3290 days) | S3 | 5.6.22 | Any | Any | "select + distinct + group by " works incorrectly |
76604 | 2015-04-07 4:29 | 2015-04-07 6:15 | MySQL Server: Optimizer | Verified (3279 days) | S3 | 5.6.23, 5.6.24, 5.6.25, 5.7.8 | Linux (CentOS 7) | Any | Assertion `length > 0 && keyparts != 0' failed in create_ref_for_key |
76679 | 2015-04-13 15:48 | 2017-02-01 14:28 | MySQL Server: Optimizer | Verified (3272 days) | S3 | 5.6, 5.6.24, 5.6.25, 5.7.8 | Any | Any | EXPLAIN incorrectly shows Distinct for tables using join buffer |
76755 | 2015-04-20 12:35 | 2015-04-25 13:23 | MySQL Server: Optimizer | Verified (3261 days) | S2 | 5.6.24 | Any | Any | Query execution plan / indexes problem |
70684 | 2013-10-22 8:13 | 2013-10-22 11:35 | MySQL Server: Optimizer | Verified (3811 days) | S3 | 5.5.33, 5.6.14 | Any | Any | HAVING referring to subquery results in WARNING 1292 |
70886 | 2013-11-12 10:42 | 2013-11-12 11:02 | MySQL Server: Optimizer | Verified (3790 days) | S3 | 5.5.32, 5.6 | Any | Any | MIN/MAX optimizer doesn't take into account type conversions |
70901 | 2013-11-13 20:18 | 2013-11-14 18:02 | MySQL Server: Optimizer | Verified (3788 days) | S3 | 5.5.31, 5.5.35, 5.1.71, 5.0.97, 5.6.15 | Any | Any | ORDER BY of a TEXT column doesn't use the same ordering as the < > = operators |
71027 | 2013-11-27 19:50 | 2013-11-28 13:31 | MySQL Server: Optimizer | Verified (3774 days) | S3 | 5.6.11, 5.6.14 | Any | Any | Full-scan UPDATE is EXPLAINED confusingly |
71140 | 2013-12-13 9:16 | 2015-07-31 8:59 | MySQL Server: Optimizer | Verified (3164 days) | S2 | 5.1, 5.5, 5.6.15, 5.7.7 | Any | Any | Optimizer does NOT use range checks in typical self-join for InnoDB tables |
« Show Previous 1000 Entries | Showing 1001-2000 of 7284 (Edit, Save, CSV, Feed) | Show Next 1000 Entries » |