Amazon Relational Database Service
User Guide (API Version 2014-10-31)

MySQL Bugs Fixed by Amazon Aurora Database Engine Updates

The following table identifies MySQL bugs that have been fixed by Amazon Aurora database engine updates, and which update they were fixed in.

Database engine update Version MySQL bugs fixed
Database Engine Updates 2015-08-24


  • InnoDB databases with names beginning with a digit cause a full-text search (FTS) parser error. (Bug #17607956)

  • InnoDB full-text searches fail in databases whose names began with a digit. (Bug #17161372)

  • For InnoDB databases on Windows, the full-text search (FTS) object ID is not in the expected hexadecimal format. (Bug #16559254)

  • A code regression introduced in MySQL 5.6 negatively impacted DROP TABLE and ALTER TABLE performance. This could cause a performance drop between MySQL Server 5.5.x and 5.6.x. (Bug #16864741)

Database Engine Updates 2015-10-16

1.2, 1.3

  • Killing a query inside innodb causes it to eventually crash with an assertion. (Bug #1608883)

  • For failure to create a new thread for the event scheduler, event execution, or new connection, no message was written to the error log. (Bug #16865959)

  • If one connection changed its default database and simultaneously another connection executed SHOW PROCESSLIST, the second connection could access invalid memory when attempting to display the first connection's default database memory. (Bug #11765252)

  • PURGE BINARY LOGS by design does not remove binary log files that are in use or active, but did not provide any notice when this occurred. (Bug #13727933)

  • For some statements, memory leaks could result when the optimizer removed unneeded subquery clauses. (Bug #15875919)

  • During shutdown, the server could attempt to lock an uninitialized mutex. (Bug #16016493)

  • A prepared statement that used GROUP_CONCAT() and an ORDER BY clause that named multiple columns could cause the server to exit. ( Bug #16075310)

  • Performance Schema instrumentation was missing for slave worker threads. (Bug #16083949)

  • STOP SLAVE could cause a deadlock when issued concurrently with a statement such as SHOW STATUS that retrieved the values for one or more of the status variables Slave_retried_transactions, Slave_heartbeat_period, Slave_received_heartbeats, Slave_last_heartbeat, or Slave_running. (Bug #16088188)

  • A full-text query using Boolean mode could return zero results in some cases where the search term was a quoted phrase. (Bug #16206253)

  • The optimizer's attempt to remove redundant subquery clauses raised an assertion when executing a prepared statement with a subquery in the ON clause of a join in a subquery. (Bug #16318585)

  • GROUP_CONCAT unstable, crash in ITEM_SUM::CLEAN_UP_AFTER_REMOVAL. (Bug #16347450)

  • Attempting to replace the default InnoDB full-text search (FTS) stopword list by creating an InnoDB table with the same structure as INFORMATION_SCHEMA.INNODB_FT_DEFAULT_STOPWORD would result in an error. (Bug #16373868)

  • After the client thread on a slave performed a FLUSH TABLES WITH READ LOCK and was followed by some updates on the master, the slave hung when executing SHOW SLAVE STATUS. (Bug #16387720)

  • When parsing a delimited search string such as "abc-def" in a full-text search, InnoDB now uses the same word delimiters as MyISAM. (Bug #16419661)

  • Crash in FTS_AST_TERM_SET_WILDCARD. (Bug #16429306)

  • SEGFAULT in FTS_AST_VISIT() for FTS RQG test. (Bug # 16435855)

  • For debug builds, when the optimizer removed an Item_ref pointing to a subquery, it caused a server exit. (Bug #16509874)

  • Full-text search on InnoDB tables failed on searches for literal phrases combined with + or - operators. (Bug #16516193)

  • START SLAVE failed when the server was started with the options --master-info-repository=TABLE relay-log-info-repository=TABLE and with autocommit set to 0, together with --skip-slave-start. (Bug #16533802)

  • Very large InnoDB full-text search (FTS) results could consume an excessive amount of memory. (Bug #16625973)

  • In debug builds, an assertion could occur in OPT_CHECK_ORDER_BY when using binary directly in a search string, as binary may include NULL bytes and other non-meaningful characters. (Bug #16766016)

  • For some statements, memory leaks could result when the optimizer removed unneeded subquery clauses. (Bug #16807641)

  • It was possible to cause a deadlock after issuing FLUSH TABLES WITH READ LOCK by issuing STOP SLAVE in a new connection to the slave, then issuing SHOW SLAVE STATUS using the original connection. (Bug #16856735)

  • GROUP_CONCAT() with an invalid separator could cause a server exit. (Bug #16870783)

  • The server did excessive locking on the LOCK_active_mi and active_mi->rli->data_lock mutexes for any SHOW STATUS LIKE 'pattern' statement, even when the pattern did not match status variables that use those mutexes (Slave_heartbeat_period, Slave_last_heartbeat, Slave_received_heartbeats, Slave_retried_transactions, Slave_running). (Bug #16904035)

  • A full-text search using the IN BOOLEAN MODE modifier would result in an assertion failure. (Bug #16927092)

  • Full-text search on InnoDB tables failed on searches that used the + boolean operator. (Bug #17280122)

  • 4-way deadlock: zombies, purging binlogs, show processlist, show binlogs. (Bug #17283409)

  • When an SQL thread which was waiting for a commit lock was killed and restarted it caused a transaction to be skipped on slave. (Bug #17450876)

  • An InnoDB full-text search failure would occur due to an "unended" token. The string and string length should be passed for string comparison. (Bug #17659310)

  • Large numbers of partitioned InnoDB tables could consume much more memory when used in MySQL 5.6 or 5.7 than the memory used by the same tables used in previous releases of the MySQL Server. (Bug #17780517)

  • For full-text queries, a failure to check that num_token is less than max_proximity_item could result in an assertion. (Bug #18233051)

  • Certain queries for the INFORMATION_SCHEMA TABLES and COLUMNS tables could lead to excessive memory use when there were large numbers of empty InnoDB tables. (Bug #18592390)

  • When committing a transaction, a flag is now used to check whether a thread has been created, rather than checking the thread itself, which uses more resources, particularly when running the server with master_info_repository=TABLE. (Bug #18684222)

  • If a client thread on a slave executed FLUSH TABLES WITH READ LOCK while the master executed a DML, executing SHOW SLAVE STATUS in the same client became blocked, causing a deadlock. (Bug #19843808)

  • Ordering by a GROUP_CONCAT() result could cause a server exit. (Bug #19880368)

Database Engine Updates 2015-12-03


  • SEGV in FTSPARSE(). (Bug #16446108)

  • InnoDB data dictionary is not updated while renaming the column. (Bug #19465984)

  • FTS crash after renaming table to different database. (Bug #16834860)

  • Failed preparing of trigger on truncated tables cause error 1054. (Bug #18596756)

  • Metadata changes might cause problems with trigger execution. (Bug #18684393)

  • Materialization is not chosen for long UTF8 VARCHAR field. (Bug #17566396)

  • Poor execution plan when ORDER BY with limit X. (Bug #16697792)

  • Backport bug #11765744 TO 5.1, 5.5 AND 5.6. (Bug #17083851)

  • Mutex issue in SQL/SQL_SHOW.CC resulting in SIG6. Source likely FILL_VARIABLES. (Bug #20788853)

  • Backport bug #18008907 to 5.5+ versions. (Bug #18903155)

  • Adapt fix for a stack overflow error in MySQL 5.7. (Bug #19678930)

Database Engine Updates 2016-01-11


  • Addressed incomplete fix in MySQL full text search affecting tables where the database name begins with a digit. (Port Bug #17607956)

Database Engine Updates 2016-04-06 1.6

  • SEGV IN MEMCPY(), HA_PARTITION::POSITION (Port Bug # 18383840)





Database Engine Updates 2016-06-01 1.6.5

Database Engine Updates 2016-08-30 1.7
  • Improve scalability by partitioning LOCK_grant lock. (Port WL #8355)

  • Opening cursor on SELECT in stored procedure causes segfault. (Port Bug#16499751)

  • MySQL gives the wrong result with some special usage. (Bug #11751794)

  • Crash in GET_SEL_ARG_FOR_KEYPART – caused by patch for bug #11751794. (Bug #16208709)

  • Wrong results for a simple query with GROUP BY. (Bug #17909656)

  • Extra rows on semijoin query with range predicates. (Bug #16221623)

  • Adding an ORDER BY clause following an IN subquery could cause duplicate rows to be returned. (Bug #16308085)

  • Crash with explain for a query with loose scan for GROUP BY, MyISAM. (Bug #16222245)

  • Loose index scan with quoated int predicate returns random data. (Bug #16394084)

  • If the optimizer was using a loose index scan, the server could exit while attempting to create a temporary table. (Bug #16436567)

  • COUNT(DISTINCT) should not count NULL values, but they were counted when the optimizer used loose index scan. (Bug #17222452)

  • If a query had both MIN()/MAX() and aggregate_function(DISTINCT) (for example, SUM(DISTINCT)) and was executed using loose index scan, the result values of MIN()/MAX() were set improperly. (Bug #17217128)

Database Engine Updates 2016-09-20 1.7.1

Database Engine Updates 2016-10-18 1.8
  • When dropping all indexes on a column with multiple indexes, InnoDB failed to block a DROP INDEX operation when a foreign key constraint requires an index. (Bug #16896810)

  • Solve add foreign key constraint crash. (Bug #16413976)

  • Fixed a crash when fetching a cursor in a stored procedure, and analyzing or flushing the table at the same time. (Bug # 18158639)

  • Fixed an auto-increment bug when a user alters a table to change the AUTO_INCREMENT value to less than the maximum auto-increment column value. (Bug # 16310273)

Database Engine Updates 2016-10-26 1.8.1
  • OpenSSL changed the Diffie-Hellman key length parameters due to the LogJam issue. (Bug #18367167)

Database Engine Updates 2016-11-10 1.9.0, 1.9.1

Database Engine Updates 2016-12-14 1.10
  • UNION of derived tables returns wrong results with '1=0/false'-clauses. (Bug #69471)

  • Server crashes in ITEM_FUNC_GROUP_CONCAT::FIX_FIELDS on 2nd execution of stored procedure. (Bug #20755389)

  • Avoid MySQL queries from stalling for too long during FTS cache sync to disk by offloading the cache sync task to a separate thread, as soon as the cache size crosses 10% of the total size. (Bugs #22516559, #73816)

Database Engine Updates 2017-01-12 1.10.1

Database Engine Updates 2017-02-23 1.11
  • Running ALTER table DROP foreign key simultaneously with another DROP operation causes the table to disappear. (Bug #16095573)

  • Some INFORMATION_SCHEMA queries that used ORDER BY did not use a filesort optimization as they did previously. (Bug #16423536)

  • FOUND_ROWS () returns the wrong count of rows on a table. (Bug #68458)

  • The server fails instead of giving an error when too many temp tables are open. (Bug #18948649)