MySQL Server now includes Performance Schema, a feature for monitoring server execution at a low level. It is implemented via the PERFORMANCE_SCHEMA storage engine and the performance_schema database. Performance Schema focuses primarily on performance data. This differs from INFORMATION_SCHEMA, which serves for inspection of metadata. For more information, see Chapter 20, MySQL Performance Schema.

Performance Schema support is included in binary MySQL distributions. It is disabled by default. To enable it, start the server with the --performance_schema option.

To create the performance_schema database if you are upgrading from an earlier release, run mysql_upgrade and restart the server. See Section 4.4.8, “mysql_upgrade — Check Tables for MySQL Upgrade”.

Incompatible Change: Several changes were made to processing of server system variables and command-line options to make their treatment more consistent.

General changes:

Variable-specific changes:

See also Bug#34437, Bug#34635.

Incompatible Change: Several changes have been made regarding the language and character set of error messages:

For more information, see Section 9.2, “Setting the Error Message Language”, and Section 9.1.6, “Character Set for Error Messages”.

See also Bug#46218, Bug#46236.

Incompatible Change: FLUSH TABLES has a new variant, FLUSH TABLES tbl_list WITH READ LOCK. This variant enables tables to be flushed and locked in a single operation. It provides a workaround for the restriction (due to work done for Bug#989) that FLUSH TABLES is disallowed when there is an active LOCK TABLES ... READ.

See also Bug#42465.

Partitioning: The UNIX_TIMESTAMP() function is now supported in partitioning expressions using TIMESTAMP columns. For example, it now possible to create a partitioned table such as this one:

CREATE TABLE t (c TIMESTAMP) 
PARTITION BY RANGE ( UNIX_TIMESTAMP(c) ) (
    PARTITION p0 VALUES LESS THAN (631148400),
    PARTITION p1 VALUES LESS THAN (946681200),
    PARTITION p2 VALUES LESS THAN (MAXVALUE)
);

All other expressions involving TIMESTAMP values are now rejected with an error when attempting to create a new partitioned table or to alter an existing partitioned table.

When accessing an existing partitioned table having a timezone-dependent partitioning function (where the table was using a previous version of MySQL), a warning rather than an error is issued. In such cases, you should fix the table. One way of doing this is to alter the table's partitioning expression so that it uses UNIX_TIMESTAMP(). (Bug#42849)

Cluster Replication: Replication: MySQL Replication now supports attribute promotion and demotion for row-based replication between columns of different but similar types on the master and the slave. For example, it is possible to promote an INT column on the master to a BIGINT column on the slave, and to demote a TEXT column to a VARCHAR column.

The implementation of type demotion distinguishes between lossy and non-lossy type conversions, and their use on the slave can be controlled by setting the slave_type_conversions global server system variable.

For more information, see Row-based replication: attribute promotion and demotion. (Bug#47163, Bug#46584)

Replication: The SHOW SLAVE STATUS statement now has a Master_Info_File field indicating the location of the master.info file. (Bug#50316)

Replication: Introduced the binlog_direct_non_transactional_updates system variable. Enabling this variable causes updates using the statement-based logging format to tables using nontransactional engines to be written directly to the binary log, rather than to the transaction cache.

Before enabling this variable, be certain that you have no dependencies between transactional and nontransactional tables. A statement that both selects from an InnoDB table and inserts into a MyISAM table is an example of such a dependency. For more information, see Section 16.1.3.4, “Binary Log Options and Variables”. (Bug#46364)

See also Bug#28976, Bug#40116.

Replication: Because SHOW BINLOG EVENTS cannot be used to read events from relay log files, a new SHOW RELAYLOG EVENTS statement has been added for this purpose. (Bug#28777)

Replication: For replication based on row-based and mix-format binary logging, it is now safe to mix transactional and nontransactional statements within a transaction. The nontransactional statements are logged immediately rather than waiting until the transaction ends, ensuring that their results are logged and replicated correctly regardless of the result of the transaction.

InnoDB stores redo log records in a hash table during recovery. On 64-bit systems, this hash table was 1/8 of the buffer pool size. To reduce memory usage, the dimension of the hash table was reduced to 1/64 of the buffer pool size (or 1/128 on 32-bit systems). (Bug#53122)

mysqltest has a new --max-connections option to set a higher number of maximum allowed server connections than the default 128. This option can also be passed via mysql-test-run.pl. (Bug#51135)

mysql-test-run.pl has a new --portbase option and a corresponding MTR_PORT_BASE environment variable for setting the port range, as an alternative to the existing --build-thread option. (Bug#50182)

SHOW PROFILE CPU has been ported to Windows. Thanks to Alex Budovski for the patch. (Bug#50057)

The Rows_examined value in slow query log rows now is nonzero for UPDATE and DELETE statements that modify rows. (Bug#49756)

mysql-test-run.pl has a new --gprof option that runs the server through the gprof profiler, much the same way the currently supported --gcov option runs it through gcov. (Bug#49345)

mysqltest has a new lowercase_result command that converts the output of the next statement to lowercase. This is useful for test cases where the lettercase may vary between platforms. (Bug#48863)

mysqladmin now has purge-backup-logs, purge-backup-logs-id, and purge-backup-logs-date commands to purge the backup logs. These are equivalent to the various forms of the PURGE BACKUP LOGS statement. (Bug#48353)

On Linux (and perhaps other systems), the performance of MySQL Server can be improved by using a different malloc() implementation, developed by Google and called tcmalloc. The gain is noticeable with a higher number of simultaneous users. To support use of this library, the following changes have been made:

The --malloc-lib option works by modifying the LD_PRELOAD environment value to affect dynamic linking to enable the loader to find the memory-allocation library when mysqld runs:

As a result of the preceding changes, Linux users can use the libtcmalloc_minimal.so now included in binary packages by adding these lines to the my.cnf file:

[mysqld_safe]
malloc-lib=tcmalloc

Those lines also suffice for users on any platform who have installed a tcmalloc package in /usr/lib. To use a specific tcmalloc library, specify its full path name. Example:

[mysqld_safe]
malloc-lib=/opt/lib/libtcmalloc_minimal.so

(Bug#47549)

mysqladmin now has a flush-backup-logs command to flush the backup logs. This is equivalent to using the FLUSH BACKUP LOGS statement. (Bug#47493)

With semisynchronous replication, for each transaction, the master waits until timeout for acknowledgement of receipt from some semisynchronous slave. If no response occurs during this period, the master reverts to normal replication. A new system variable, rpl_semi_sync_master_wait_no_slave, controls whether the master waits for the timeout to expire before reverting to normal replication even if the slave count drops to zero during the timeout period.

If the value is ON (the default), it is allowable for the slave count to drop to zero during the timeout period (for example, if slaves disconnect). The master still waits for the timeout, so as long as some slave reconnects and acknowledges the transaction within the timeout interval, semisynchronous replication continues.

If the value is OFF, the master reverts to normal replication if the slave count drops to zero during the timeout period. (Bug#47298)

A new option, --mysql-backup, determines whether MySQL Backup is enabled or disabled. By default, MySQL Backup is disabled. (Bug#46541)

mysqltest has a new remove_files_wildcard command that removes files matching a pattern from a directory. (Bug#39774)

MySQL Backup now has a restore_disables_events system variable that controls whether RESTORE disables Event Scheduler events that are restored from the backup image. By default, this variable is enabled, which disables restored events. If the variable is disabled, restored events retain their state as recorded in the image. (Bug#37445)

There is a new system variable, skip_name_resolve, that is set from the value of the --skip-name-resolve server option. This provides a way to determine at runtime whether the server uses name resolution for client connections. (Bug#37168)

BACKUP DATABASE new treats a nonexistent database as a nonfatal condition and issues a warning rather than an error. (Bug#36635)

BACKUP DATABASE now has an OVERWRITE option that enables you to overwrite an existing backup image file. Without this option, the behavior is the same as before: If the named image file already exists, the statement fails with an error. (Bug#36402)

Previously, mysqldump would not dump the INFORMATION_SCHEMA database and ignored it if it was named on the command line. Now, mysqldump will dump INFORMATION_SCHEMA if it is named on the command line. Currently, this requires that the --skip-lock-tables (or --skip-opt) option be given. (Bug#33762)

Previously, SELECT ... INTO OUTFILE dumped column values without character set conversion, which could produce data files that cannot be imported without error if different columns used different character sets. A consequence of this is that mysqldump ignored the --default-character-set option if the --tab option was given (which causes SELECT ... INTO OUTFILE to be used to dump data.)

INTO OUTFILE now can be followed by a CHARACTER SET clause indicating the character set to which dumped values should be converted. Also, mysqldump adds a CHARACTER SET clause to the SELECT ... INTO OUTFILE statement used to dump data, so that --default-character-set is no longer ignored if --tab is given.

Other changes are that SELECT ... INTO OUTFILE enforces that ENCLOSED BY and ESCAPED BY arguments must be a single character, and SELECT ... INTO OUTFILE and LOAD DATA INFILE produce warnings if non-ASCII field or line separators are specified. (Bug#30946)

The TRADITIONAL SQL mode now includes NO_ENGINE_SUBSTITUTION. (Bug#21099)

FLUSH LOGS now takes an optional log_type value so that FLUSH log_type LOGS can be used to flush only a specified log type. These log_type options are allowed:

Thanks to Eric Bergen for the patch to implement this feature. (Bug#14104)

All numeric operators and functions on integer, floating point and DECIMAL values now throw an “out of range” error (ER_DATA_OUT_OF_RANGE) rather than returning an incorrect value or NULL, when the result is out of the supported range for the corresponding data type. (Bug#8433)

mysqladmin now allows the password value to be omitted following the password command. In this case, mysqladmin prompts for the password value, which enables you to avoid specifying the password on the command line. Omitting the password value should be done only if password is the final command on the mysqladmin command line. Otherwise, the next argument is taken as the password. (Bug#5724)

Some conversions between Japanese character sets are more efficient.

Previously, in the absence of other information, the MySQL client programs mysql, mysqladmin, mysqlcheck, mysqlimport, and mysqlshow used the compiled-in default character set, usually latin1.

Now these clients can autodetect which character set to use based on the operating system setting, such as the value of the LANG or LC_ALL locale environment language on Unix system or the code page setting on Windows systems. For systems on which the locale is available from the OS, the client uses it to set the default character set rather than using the compiled-in default. Thus, users can configure the locale in their environment for use by MySQL clients. For example, setting LANG to ru_RU.KOI8-R causes the koi8r character set to be used. The OS character set is mapped to the closest MySQL character set if there is no exact match. If the client does not support the matching character set, it uses the compiled-in default. (For example, ucs2 is not supported as a connection character set.)

Third-party applications that wish to use character set autodetection based on the OS setting can use the following mysql_options() call before connecting to the server:

mysql_options(mysql,
              MYSQL_SET_CHARSET_NAME,
              MYSQL_AUTODETECT_CHARSET_NAME);

See Section 9.1.4, “Connection Character Sets and Collations”.

Performance: Partitioning: When used on partitioned tables, the records_in_range handler call checked more partitions than necessary. The fix for this issue reduces the number of unpruned partitions checked for statistics in partition range checking, which has resulted in some partition operations being performed up to 2-10 times faster than before this change was made, when testing with tables having 1024 partitions. (Bug#48846)

See also Bug#37252, Bug#47261.

Performance: Replication: When writing events to the binary log, transactional events (that is, events that operate on transactional tables) are written to a thread-specific transaction cache, which is then written to the binary log on commit. In order to handle nontransactional events, there was a lock taken on the binary log (when entering the function MYSQL_BIN_LOG::write()), even when the event was written to the transaction cache instead of the binary log, causing a major bottleneck in replication performance. (Bug#42757)

Performance: The method for comparing INFORMATION_SCHEMA names and database names was nonoptimal and an improvement was made: When the database name length is already known, a length check is made first and content comparison skipped if the lengths are unequal. (Bug#49501)

Performance: The MD5() and SHA1() functions had excessive overhead for short strings. (Bug#49491)

Performance: While looking for the shortest index for a covering index scan, the optimizer did not consider the full row length for a clustered primary key, as in InnoDB. Secondary covering indexes will now be preferred, making full table scans less likely. (Bug#39653)

Performance: When the query cache is fragmented, the size of the free block lists in the memory bins grows, which causes query cache invalidation to become slow. There is now a 50ms timeout for a SELECT statement waiting for the query cache lock. If the timeout expires, the statement executes without using the query cache. (Bug#39253)

See also Bug#21074.

Important Change: Security Fix: Additional corrections were made for the symlink-related privilege problem originally addressed in MySQL 6.0.5. The original fix did not correctly handle the data directory path name if it contained symlinked directories in its path, and the check was made only at table-creation time, not at table-opening time later. (Bug#32167, CVE-2008-2079)

See also Bug#39277.

Security Fix: The server failed to check the table name argument of a COM_FIELD_LIST command packet for validity and compliance to acceptable table name standards. This could be exploited to bypass almost all forms of checks for privileges and table-level grants by providing a specially crafted table name argument to COM_FIELD_LIST.

In MySQL 5.0 and above, this allowed an authenticated user with SELECT privileges on one table to obtain the field definitions of any table in all other databases and potentially of other MySQL instances accessible from the server's file system.

Additionally, for MySQL version 5.1 and above, an authenticated user with DELETE or SELECT privileges on one table could delete or read content from any other table in all databases on this server, and potentially of other MySQL instances accessible from the server's file system. (Bug#53371, CVE-2010-1848)

Security Fix: The server was susceptible to a buffer-overflow attack due to a failure to perform bounds checking on the table name argument of a COM_FIELD_LIST command packet. By sending long data for the table name, a buffer is overflown, which could be exploited by an authenticated user to inject malicious code. (Bug#53237, CVE-2010-1850)

Security Fix: Privilege checking for UNINSTALL PLUGIN was incorrect. (Bug#51770, CVE-2010-1621)

Security Fix: The server could be tricked into reading packets indefinitely if it received a packet larger than the maximum size of one packet. (Bug#50974, CVE-2010-1849)

Security Fix: For servers built with yaSSL, a preauthorization buffer overflow could cause memory corruption or a server crash. We thank Evgeny Legerov from Intevydis for providing us with a proof-of-concept script that allowed us to reproduce this bug. (Bug#50227, CVE-2009-4484)

Security Fix: MySQL clients linked against OpenSSL can be tricked not to check server certificates. (Bug#47320, CVE-2009-4028)

Incompatible Change: Replication: The --binlog_format system variable can no longer be set inside a transaction. In other words, the binary logging format can no longer be changed while a transaction is in progress. (Bug#47863)

Incompatible Change: Replication: The file names for the semisynchronous plugins were prefixed with lib, unlike file names for other plugins. The file names no longer have a lib prefix.

This change introduces an incompatibility if the plugins had been installed using the previous names. To handle this, uninstall the older version before installing the newer version. For example, use these statements for the master side plugins on Unix:

mysql> UNINSTALL PLUGIN rpl_semi_sync_master;
mysql> INSTALL PLUGIN rpl_semi_sync_master SONAME 'semisync_master.so';

If you do not uninstall the older version first, attempting to install the newer version results in an error:

mysql> INSTALL PLUGIN rpl_semi_sync_master SONAME 'semisync_master.so';
ERROR 1125 (HY000): Function 'rpl_semi_sync_master' already exists

For the slave side, similar statements apply:

mysql> UNINSTALL PLUGIN rpl_semi_sync_slave;
mysql> INSTALL PLUGIN rpl_semi_sync_slave SONAME 'semisync_slave.so';

Incompatible Change: For debug builds, wttempts to execute RESET statements within a transaction that had acquired metadata locks led to an assertion failure.

As a result of this bug fix, RESET statements now cause an implicit commit. (Bug#51336)

Incompatible Change: A deadlock occurred for this sequence of events: Session 1 locked a table using LOCK TABLES; Session 2 dropped the database containing the table; Session 1 created any database.

A consequence of this bug fix is that CREATE DATABASE is disallowed within a session that has an active LOCK TABLES statement. (Bug#49988)

Incompatible Change: Time zone calculation for backups was not correct on the powermac platform because the timezone variable was not set correctly.

This fix involves a change to the internal format of times in backup image files, so backups made prior to this release cannot be restored using the current backup code. (Bug#43221)

Incompatible Change: For application compatibility reasons, when sql_auto_is_null is 1, MySQL converts auto_inc_col IS NULL to auto_inc_col = LAST_INSERT_ID(). However, this was being done regardless of whether the predicate was alone or at the top level. Now it occurs only when it is a single top-level predicate.

In conjunction with this bug fix, the default value of the sql_auto_is_null system variable has been changed from 1 to 0, which may cause incompatibilities with existing applications. (Bug#41371)

Incompatible Change: In binary installations of MySQL, the supplied binary-configure script would start and configure MySQL, even when command help was requested with the --help command-line option. The --help, if provided, will no longer start and install the server. (Bug#30954)

Incompatible Change: The Locked thread state was equivalent to the Table lock state and has been removed. It no longer appears in SHOW PROCESSLIST output. (Bug#28870)

Important Change: Replication: When changing binlog_format or binlog_direct_non_transactional_updates, permissions were not checked prior to checking the scope and context of the variable being changed.

As a result of this fix, an error is no longer reported when—in the context of a transaction or a stored function—you try to set a value for a session variable that is the same as its previous value, or for a variable whose scope is global only. (Bug#51277)

Important Change: Replication: The RAND() function is now marked as unsafe for statement-based replication. Using this function now generates a warning when binlog_format=STATEMENT and causes the format to switch to row-based logging when binlog_format=MIXED.

This change is being introduced because, when RAND() was logged in statement mode, the seed was also written to the binary log, so the replication slave generated the same sequence of random numbers as was generated on the master. While this could make replication work in some cases, the order of affected rows was still not guaranteed when this function was used in statements that could update multiple rows, such as UPDATE or INSERT ... SELECT; if the master and the slave retrieved rows in different order, they began to diverge. (Bug#49222)

Important Change: Replication: The following functions have been marked unsafe for statement-based replication:

None of the functions just listed are guaranteed to replicate correctly when using the statement-based format, because they can produce different results on the master and the slave. The use of any of these functions while binlog_format is set to STATEMENT is logged with the warning, Statement is not safe to log in statement format. When binlog_format is set to MIXED, the binary logging format is automatically switched to the row-based format whenever one of these functions is used. (Bug#47995)

Important Change: Replication: When invoked, CHANGE MASTER TO and SET GLOBAL sql_slave_skip_counter now cause information to be written to the error log about the slave's state prior to execution of the statement. For CHANGE MASTER TO, this information includes the previous values for MASTER_HOST, MASTER_PORT, MASTER_LOG_FILE, and MASTER_LOG_POS. For SET GLOBAL sql_slave_skip_counter, this information includes the previous values of sql_slave_skip_counter, the group relay log name, and the group relay log position. (Bug#43406, Bug#43407)

Important Change: Replication: For an engine that supported only row-based replication, replication stopped with an error when executing row events.

For information about changes in how the binary logging format is determined in relation to statement type and storage engine logging capabilities, see Section 5.2.4.3, “Mixed Binary Logging Format”.

As part of the fix for this issue, the EXAMPLE storage engine is now changed so that it supports statement-based logging only. Previously, it supported row-based logging only. (Bug#39934)

Important Change: The IPv6 loopback address ::1 was interpeted as a hostname rather than a numeric IP address.

In addition, the IPv6-enabled server on Windows interpeted the hostname localhost as ::1 only, which failed to match the default 'root'@'127.0.0.1' account in the mysql.user privilege table.

(Bug#43006)

See also Bug#38247, Bug#45283, Bug#45584, Bug#45606.

Partitioning: Partition pruning on RANGE partitioned tables did not always work correctly; the last partition was not excluded if the range was beyond it (when not using MAXVALUE). Now the last partition is not included if the partitioning function value is not within the range. (Bug#51830)

Partitioning: Attempting to partition a table using a DECIMAL column caused the server to crash; this not supported and is now specifically disallowed. (Bug#51347)

Partitioning: ALTER TABLE statements that cause table partitions to be renamed or dropped (such as ALTER TABLE ... ADD PARTITION, ALTER TABLE ... DROP PARTITION, and ALTER TABLE ... REORGANIZE PARTITION) — when run concurrently with queries against the INFORMATION_SCHEMA.PARTITIONS table — could fail, cause the affected partitioned tables to become unusable, or both. This was due to the fact that the INFORMATION_SCHEMA database ignored the name lock imposed by the ALTER TABLE statement on the partitions affected. In particular, this led to problems with InnoDB tables, because InnoDB would accept the rename operation, but put it in a background queue, so that subsequent rename operations failed when InnoDB was unable to find the correct partition. Now, INFORMATION_SCHEMA honors name locks imposed by ongoing ALTER TABLE statements that cause partitions to be renamed or dropped. (Bug#50561)

See also Bug#47343, Bug#45808.

Partitioning: The insert_id server system variable was not reset following an insert that failed on a partitioned MyISAM table having an AUTO_INCREMENT column. (Bug#50392)

Partitioning: Foreign keys are not supported on partitioned tables. However, it was possible via an ALTER TABLE statement to set a foreign key on a partitioned table; it was also possible to partition a table with a single foreign key. (Bug#50104)

Partitioning: When SHOW CREATE TABLE was invoked for a table that had been created using the TO_SECONDS() function, the output contained the wrong MySQL version number in the conditional comments. (Bug#49591)

Partitioning: It was possible to execute a CREATE TEMPORARY TABLE tmp LIKE pt statement, where pt is a partitioned table, even though partitioned temporary tables are not permitted, which caused the server to crash. Now a check is performed to prevent such statements from being executed. (Bug#49477)

Partitioning: A query that searched on a ucs2 column failed if the table was partitioned. (Bug#48737)

Partitioning: In some cases, it was not possible to add a new column to a table that had subpartitions. (Bug#48276)

Partitioning: GROUP BY queries performed poorly for some partitioned tables. This was due to the block size not being set for partitioned tables, thus the keys per block was not correct, which could cause such queries to be optimized incorrectly. (Bug#48229)

See also Bug#37252.

Partitioning: When an ALTER TABLE ... REORGANIZE PARTITION statement on an InnoDB table failed due to innodb_lock_wait_timeout expiring while waiting for a lock, InnoDB did not clean up any temporary files or tables which it had created. Attempting to reissue the ALTER TABLE statement following the timeout could lead to storage engine errors, or possibly a crash of the server. (Bug#47343)

Partitioning: SELECT COUNT(*) from a partitioned table failed when using the ONLY_FULL_GROUP_BY SQL mode. (Bug#46923)

This regression was introduced by Bug#45807.

Partitioning: An ALTER TABLE ... ADD PARTITION statement that caused open_files_limit to be exceeded led to a crash of the MySQL server. (Bug#46922)

See also Bug#47343.

Partitioning: REPAIR TABLE failed for partitioned ARCHIVE tables. (Bug#46565)

Partitioning: SUBPARTITION BY KEY failed with DEFAULT CHARSET=utf8. (Bug#45904)

Partitioning: When performing an INSERT ... SELECT into a partitioned table, read_buffer_size bytes of memory were allocated for every partition in the target table, resulting in consumption of large amounts of memory when the table had many partitions (more than 100).

This fix changes the method used to estimate the buffer size required for each partition and limits the total buffer size to a maximum of approximately 10 times read_buffer_size. (Bug#45840)

Partitioning: The first time that a query against the INFORMATION_SCHEMA.TABLES table for partitioned tables using the ARCHIVE engine was run, it returned invalid data. If the server had been restarted since such a table had been created, or if the table had never actually been opened, its DATA_LENGTH was reported as 0 bytes. (The second and subsequent attempts to issue the same query returned the expected result.) (Bug#44622)

Partitioning: The cardinality of indexes on partitioned tables was calculated using the first partition in the table, which could result in suboptimal query execution plans being chosen. Now the partition having the most records is used instead, which should result in better use of indexes and thus improved performance of queries against partitioned tables in many if not most cases. (Bug#44059)

Partitioning: ALTER TABLE on a partitioned table caused unnecessary deadlocks. (Bug#43867)

See also Bug#46654.

Partitioning: Attempting to drop a partitioned table from one connection while waiting for the completion of an ALTER TABLE that had been issued from a different connection, and that changed the storage engine used by the table, could cause the server to crash. (Bug#42438)

Partitioning: After attempting to create a duplicate index on a partitioned table (and having the attempt fail as expected), a subsequent attempt to create a new index on the table caused the server to hang. (Bug#40181)

Partitioning: When used on a partitioned table, ALTER TABLE produced the wrong error message when the name of a nonexistent storage engine was used in the ENGINE clause. (Bug#35765)

Partitioning: Truncating a partitioned MyISAM table did not reset the AUTO_INCREMENT value. (Bug#35111)

Partitioning: Portions of the partitioning code were refactored in response to potential regression issues uncovered while working on the fix for Bug#31210. (Bug#32115)

See also Bug#40281.

Replication: When using the statement-based logging format, statements that used CONNECTION_ID() were always kept in the transaction cache; consequently, nontransactional changes that should have been flushed before the transaction were kept in the transaction cache. (Bug#53075)

This regression was introduced by Bug#51894.

Replication: In some cases, attempting to update a column with a value of an incompatible type resulted in a mismatch between master and slave because the column value was set to its implicit default value on the master (as expected), but the same column on the slave was set to NULL. (Bug#52868)

Replication: When temporary tables were in use, switching the binary logging format from STATEMENT to ROW did not take effect until all temporary tables were dropped. (The existence of temporary tables should prevent switching the format only from ROW to STATEMENT from taking effect, not the reverse.) (Bug#52616)

Replication: A buffer overrun in the handling of DATE column values could cause mysqlbinlog to fail when reading back logs containing certain combinations of DML on a table having a DATE column followed by dropping the table. (Bug#52202)

Replication: The failure of a REVOKE statement was logged with the wrong error code, causing replication slaves to stop even when the failure was expected on the master. (Bug#51987)

Replication: Issuing any DML on a temporary table temp followed by DROP TEMPORARY TABLE temp, both within the same transaction, caused replication to fail.

The fix introduces a change to statement-based binary logging with respect to temporary tables. Within a transaction, changes to temporary tables are saved to the transaction cache and written to the binary log when the transaction commits. Otherwise, out-of-order logging of events could occur. This means that temporary tables are treated similar to transactional tables for purposes of caching and logging. This affects assessment of statements as safe or unsafe and the associated error message was changed from:

Unsafe statement written to the binary log using statement format
since BINLOG_FORMAT = STATEMENT. Statements that read from both
transactional and non-transactional tables and write to any of them
are unsafe.

To:

Unsafe statement written to the binary log using statement format
since BINLOG_FORMAT = STATEMENT. Statements that read from both
transactional (or a temporary table of any engine type) and
non-transactional tables and write to any of them are unsafe.

(Bug#51894)

See also Bug#51291, Bug#53075.

This regression was introduced by Bug#46364.

Replication: When using the row-based or mixed replication format with a debug build of the MySQL server, inserts into columns using the UTF32 character set on the master caused the slave to crash. (Bug#51787)

See also Bug#51716.

Replication: When using the row-based or mixed replication format, column values using the UTF16 character set on the master were padded incorrectly on the slave. (Bug#51716)

See also Bug#51787.

Replication: The flag stating whether a user value was signed or unsigned (unsigned_flag) could sometimes change between the time that the user value was recorded for logging purposes and the time that the value was actually written to the binary log, which could lead to inconsistency. Now unsigned_flag is copied when the user variable value is copied, and the copy of unsigned_flag is then used for logging. (Bug#51426)

See also Bug#49562.

Replication: Enabling binlog_direct_non_transactional_updates causes nontransactional changes to be written to the binary log upon committing the statement. However, even when not enabled, the addition of this variable introduced a number of undesired changes in behavior:

These problems have been handled as follows:

(Bug#51291)

This regression was introduced by Bug#46364.

Replication: TRUNCATE TABLE performed on a temporary table using the InnoDB storage engine was logged even when using row-based mode. (Bug#51251)

Replication: When using temporary tables the binary log needs to insert a pseudo-thread ID for threads that are using temporary tables, each time a switch happens between two threads, both of which are using temporary tables. However, if a thread issued a failing statement before exit, its ID was not recorded in the binary log, and this in turn caused the ID for the next thread that tried to do something with a temporary table not to be logged as well. Subsequent replays of the binary log failed with the error Table ... doesn't exist. (Bug#51226)

Replication: If the master was using sql_mode='TRADITIONAL', duplicate key errors were not sent to the slave, which received 0 rather than the expected error code. This caused replication to fail even when such an error was expected. (Bug#51055)

Replication: An issue internal to the code, first seen in Bug#49132 but not completely resolved in the fix for that bug, was removed. This should prevent similar issues to those in the previous bug with binlog_format changes following DDL statements.

For developers working with the MySQL Server code: the public class variable THD::current_stmt_binlog_row_based was supposed to have been removed as part of the fix for Bug#39934, but was still present in the code. If a developer later tried to use this variable, it could cause the previous issues to re-occur, and possibly new ones to arise. The variable has now been removed; the previously added class functions THD::is_current_stmt_binlog_format_row(), THD::set_current_stmt_binlog_format_row(), and THD::clear_current_stmt_binlog_format_row() should be used instead. (Bug#51021)

Replication: Adding an index to a table on the master caused the slave to stop logging slow queries to the slow query log. (Bug#50620)

Replication: When run with the --database option, mysqlbinlog printed ROLLBACK statements but did not print any corresponding SAVEPOINT statements. (Bug#50407)

Replication: FLUSH LOGS could in some circumstances crash the server. This occurred because the I/O thread could concurrently access the relay log I/O cache while another thread was performing the FLUSH LOGS, which closes and reopens the relay log and, while doing so, initializes (or re-initializes) its I/O cache. This could cause problems if some other thread (in this case, the I/O thread) is accessing it at the same time.

Now the thread performing the FLUSH LOGS takes a lock on the relay log before actually flushing it. (Bug#50364)

Replication: On a replication slave, a race condition between the I/O thread and FLUSH LOGS could crash the server. (Bug#50364)

Replication: If a CHANGE MASTER TO statement set MASTER_HEARTBEAT_PERIOD to 30 or higher, Slave_received_heartbeats did not increase on the slave. This caused the slave to reconnect before the time indicated by slave_net_timeout had elapsed.

This issue affected big-endian 64-bit platforms such as Solaris/SPARC. (Bug#50296)

Replication: The error message given when trying to replicate (using statement-based mode) insertions into an AUTO_INCREMENT column by a stored function or a trigger was improved. (Bug#50192)

Replication: With semisynchronous replication, memory allocated for handling transactions could be freed while still in use, resulting in a server crash. (Bug#50157)

Replication: When a CREATE EVENT statement was followed by an additional statement and the statements were executed together as a single statement, the CREATE EVENT statement was padded with “garbage” characters when written to the binary log, which led to a syntax error when trying to read back from the log. (Bug#50095)

Replication: The server could deadlock when FLUSH LOGS was executed concurrently with DML statements. To fix this problem, nontransactional changes are now always flushed before transactional changes. (Bug#50038)

Replication: In some cases, inserting into a table with many columns could cause the binary log to become corrupted. (Bug#50018)

See also Bug#42749.

Replication: Metadata for GEOMETRY fields was not properly stored by the slave in its definitions of tables. (Bug#49836)

See also Bug#48776.

Replication: Column length information generated by InnoDB did not match that generated by MyISAM, which caused invalid metadata to be written to the binary log when trying to replicate BIT columns. (Bug#49618)

Replication: Statement-based replication of user variables having numeric data types did not always work correctly. (Bug#49562)

Replication: When using the semi-synchronous replication plugin on Windows, the wait time calculated when the master was waiting for reply from the slave was incorrect. In addition, when the wait time was less than the current time, the master did not wait for a reply at all.

This issue was caused by the fact that a different internal function was used to get current time by the plugin on Windows as opposed to other platforms, and this function was not correctly implemented. Now the Windows version of the plugin uses the same function as other platforms for this purpose. (Bug#49557)

Replication: When using a non-transactional table on the master with autocommit disabled, no COMMIT was recorded in the binary log following a statement affecting this table. If the slave's copy of the table used a transactional storage engine, the result on the slave was as though a transaction had been started, but never completed. (Bug#49522)

See also Bug#29288.

Replication: When using row-based replication, setting a BIT or CHAR column of a MyISAM table to NULL, then trying to delete from the table, caused the slave to fail with the error Can't find record in table. (Bug#49481, Bug#49482)

Replication: A LOAD DATA INFILE statement that loaded data into a table having a column name that had to be escaped (such as `key` INT) caused replication to fail when logging in mixed or statement mode. In such cases, the master wrote the LOAD DATA event into the binary log without escaping the column names. (Bug#49479)

See also Bug#47927.

Replication: Due to a change in the format of the information used by the slave to connect to the master, which could cause to reject connection attempts to older masters by newer slaves. (Bug#49259)

This regression was introduced by Bug#13963.

Replication: When logging in row-based mode, DDL statements are actually logged as statements; however, statements that affected temporary tables and followed DDL statements failed to reset the binary log format to ROW, with the result that these statements were logged using the statement-based format. Now the state of binlog_format is restored after a DDL statement has been written to the binary log. (Bug#49132)

Replication: Reading from a table that used a self-logging storage engine and updating a table that used a transactional engine (such as InnoDB) generated changes that were written to the binary log using statement format which could make slaves diverge. However, when using mixed logging format, such changes should be written to the binary log using row format. (This issue did not occur when reading from tables using a self-logging engine and updating MyISAM tables, as this was already handled by checking for combinations of non-transactional and transactional engines.) Now such statements are classified as unsafe, and in mixed mode, cause a switch to row-based logging. (Bug#49019)

Replication: Spatial data types caused row-based replication to crash. (Bug#48776)

Replication: When using row-based logging, TRUNCATE TABLE was written to the binary log even if the affected table was temporary, causing replication to fail. (Bug#48350)

Replication: When using statement-based or mixed-format replication, the database name was not written to the binary log when executing a LOAD DATA statement. This caused problems when the table being loaded belonged to a database other than the current database; data could be loaded into the wrong table (if a table having the same name existed in the current database) or replication could fail (if no table having that name existed in the current database). Now a table referenced in a LOAD DATA statement is always logged using its fully qualified name when the database to which it belongs is not the current database. (Bug#48297)

Replication: When a session was closed on the master, temporary tables belonging to that session were logged with the wrong database names when either of the following conditions was true:

(Bug#48216)

See also Bug#46861, Bug#48297.

Replication: When using row-based replication, changes to nontransactional tables that occurred early in a transaction were not immediately flushed upon committing a statement. This behavior could break consistency since changes made to nontransactional tables become immediately visible to other connections. (Bug#47678)

See also Bug#47287, Bug#46864, Bug#43929, Bug#46129.

Replication: When using row-based logging, the statement CREATE TABLE t IF NOT EXIST ... SELECT was logged as CREATE TEMPORARY TABLE t IF NOT EXIST ... SELECT when t already existed as a temporary table. This was caused by the fact that the temporary table was opened and the results of the SELECT were inserted into it when a temporary table existed and had the same name.

Now, when this statement is executed, t is created as a base table, the results of the SELECT are inserted into it—even if there already exists a temporary table having the same name—and the statement is logged correctly. (Bug#47418)

See also Bug#47442.

Replication: When mysqlbinlog --verbose was used to read a binary log that had been recorded using the row-based format, the output for events that updated some but not all columns of tables was not correct. (Bug#47323)

Replication: Performing ALTER TABLE ... DISABLE KEYS on a slave table caused row-based replication to fail. (Bug#47312)

Replication: When using the row-based format to replicate a transaction involving both transactional and nontransactional engines, which contained a DML statement affecting multiple rows, the statement failed; if this transaction was followed by a COMMIT, the master and the slave could diverge, because the statement was correctly rolled back on the master, but was applied on the slave. (Bug#47287)

See also Bug#46864.

Replication: When using row-based logging, a failing INSERT...SELECT statement on a nontransactional table was not flagged correctly, such that, if a rollback was requested and no other nontransactional table had been updated, nothing was written to the binary log. (Bug#47175)

See also Bug#40278.

Replication: Due to a change in the size of event representations in the binary log, when replicating from a MySQL 4.1 master to a slave running MySQL 5.0.60 or later, the START SLAVE UNTIL statement did not function correctly, stopping at the wrong position in the log. Now the slave detects that the master is using the older version of the binary log format, and corrects for the difference in event size, so that the slave stops in the correct position. (Bug#47142)

Replication: BEGIN statements were not included in the output of mysqlbinlog. (Bug#46998)

Replication: A problem with the BINLOG statement in the output of mysqlbinlog could break replication; statements could be logged with the server ID stored within events by the BINLOG statement rather than the ID of the running server. With this fix, the server ID of the server executing the statements can no longer be overridden by the server ID stored in the binary log's format description statement. (Bug#46640)

This regression was introduced by Bug#32407.

Replication: When using row-based replication, DROP TEMPORARY TABLE IF EXISTS was written to the binary log if the table named in the statement did not exist, even though a DROP TEMPORARY TABLE statement should never be logged in row-based logging mode, whether the table exists or not. (Bug#46572)

Replication: There were two related issues concerning handling of unsafe statements and setting of the binary logging format when there were open temporary tables on the master, and the existing replication format was row-based or mixed:

(Bug#45855, Bug#45856)

Replication: When using semisynchronous replication, an error raised on the slave while sending a response to the master caused the slave I/O thread to stop. (Bug#45852)

Replication: Semisynchronous replication used an extra connection from slave to master to send replies. This was a regular client connection, and used a normal SET statement to set the reply information on master. This was visible to users and had the potential to add undesired extra output to the query log, the output of SHOW PROCESSLIST, or both.

We have rectified this issue by reverting to the previous method of sending replies to the master via the same connection that is used to send binary logging information.

This patch also removes the rpl_semi_sync_master_reply_log_file_pos system variable. (Bug#45848)

Replication: Statements that updated AUTO_INCREMENT columns in multiple tables were logged using the row-based format when --binlog_format was set to MIXED, but did not cause an Unsafe statement warning to be generated when --binlog_format was set to STATEMENT. (Bug#45827)

See also Bug#39934.

Replication: Even though INSERT DELAYED statements are unsafe for statement-based replication, they caused the statement only to be logged in row format when the binary logging format was MIXED, but did not cause a warning to be generated when the binary logging format was STATEMENT. (Bug#45825)

Replication: When using MIXED binary logging format, statements containing a LIMIT clause and occurring in stored routines were not written to the log as row events. (Bug#45785)

Replication: Concurrent transactions that inserted rows into a table with an AUTO_INCREMENT column could break statement-based or mixed-format replication error 1062 Duplicate entry '...' for key 'PRIMARY' on the slave. This was especially likely to happen when one of the transactions activated a trigger that inserted rows into the table with the AUTO_INCREMENT column, although other conditions could also cause the issue to manifest. (Bug#45677)

Replication: FLUSH STATUS failed to reset the status variables Rpl_semi_sync_master_yes_tx and Rpl_semi_sync_master_no_tx. (Bug#45674)

Replication: When using statement-based replication, database-level character sets were not always honored by the replication SQL thread. This could cause data inserted on the master using LOAD DATA to be replicated using the wrong character set.

(Bug#45516)

Replication: A flaw in the implementation of the purging of binary logs could result in orphaned files being left behind in the following circumstances:

In addition, if the slave was not connected during the purge operation, it was possible for a log file that was in use to be removed; this could lead data loss and possible inconsistencies between the master and slave. (Bug#45292)

Replication: The server failed to start when using the --log-slave-updates option without also using the --log-bin option. Now in such cases, only a warning message is generated. (Bug#44663)

Replication: STOP SLAVE did not flush the relay log or the master.info or relay-log.info files, which could lead to corruption if the server crashed. (Bug#44188)

Replication: Large transactions and statements could corrupt the binary log if the size of the cache (as set by max_binlog_cache_size) was not large enough to store the changes.

Now, for transactions that do not fit into the cache, the statement is not logged, and the statement generates an error instead.

For nontransactional changes that do not fit into the cache, the statement is also not logged—an incident event is logged after committing or rolling back any pending transaction, and the statement then raises an error.

(Bug#43929)

See also Bug#37148.

Replication: When the logging format was set without binary logging being enabled, the server failed to start. Now in such cases, the server starts successfully, binlog_format is set, and a warning is logged instead of an error. (Bug#42928)

Replication: On the master, if a binary log event is larger than max_allowed_packet, the error message ER_MASTER_FATAL_ERROR_READING_BINLOG is sent to a slave when it requests a dump from the master, thus leading the I/O thread to stop. On a slave, the I/O thread stops when receiving a packet larger than max_allowed_packet.

In both cases, however, there was no Last_IO_Error reported, which made it difficult to determine why the slave had stopped in such cases. Now, Last_IO_Error is reported when max_allowed_packet is exceeded, and provides the reason for which the slave I/O thread stopped. (Bug#42914)

See also Bug#14068, Bug#47200, Bug#47303.

Replication: When using statement-based replication and the transaction isolation level was set to READ COMMITTED or a less strict level, InnoDB returned an error even if the statement in question was filtered out according to the --binlog-do-db or --binlog-ignore-db rules in effect at the time. (Bug#42829)

Replication: Using row-based replication, executing a transactional workload containing MyISAM tables and SAVEPOINT statements caused replication to fail. (Bug#40278)

Replication: When using the STATEMENT or MIXED logging format, the statements LOAD DATA CONCURRENT LOCAL INFILE and LOAD DATA CONCURRENT INFILE were logged as LOAD DATA LOCAL INFILE and LOAD DATA LOCAL INFILE, respectively (in other words, the CONCURRENT keyword was omitted). As a result, when using replication with either of these logging modes, queries on the slaves were blocked by the replication SQL thread while trying to execute the affected statements. (Bug#34628)

Replication: FLUSH LOGS did not actually close and reopen the binary log index file. (Bug#34582)

See also Bug#5.0.90.

Replication: An error message relating to permissions required for SHOW SLAVE STATUS was confusing. (Bug#34227)

Replication: Manually removing entries from the binary log index file on a replication master could cause the server to repeatedly send the same binary log file to slaves. (Bug#28421)

Replication: Valgrind revealed an issue with mysqld that as corrected: memory corruption in replication slaves when switching databases. (Bug#19022)

Replication: Formerly, only slaves that had been started with the --report-hosts option were visible in the output of SHOW SLAVE HOSTS. Now, all slaves that are registered with the master appear in SHOW SLAVE HOSTS output.

As part of the fix for this issue, the Rpl_recovery_rank column, which had appeared in the output of SHOW SLAVE HOSTS in some MySQL releases, was removed because the corresponding variable (also removed by this fix) was never actually used. (Bug#13963)

See also Bug#21132, Bug#21869.

Cluster Replication: When expire_logs_days was set, the thread performing the purge of the log files could deadlock, causing all binary log operations to stop. (Bug#49536)

API: The fix for Bug#24507 could lead in some cases to client application failures due to a race condition. Now the server waits for the “dummy” thread to return before exiting, thus making sure that only one thread can initialize the POSIX threads library. (Bug#42850)

Missing Performance Schema tables were not reported in the error log at server startup. (Bug#53617)

SHOW ENGINE PERFORMANCE_SCHEMA STATUS underreported the amount of memory allocated by Performance Schema. (Bug#53566)

Certain path names passed to LOAD_FILE() could cause a server crash. (Bug#53417)

Performance Schema code was subject to a buffer overflow. (Bug#53363)

Incorrect results could be returned for LEFT JOIN of InnoDB tables with an impossible WHERE condition. (Bug#53334)

For some queries having subqueries in the WHERE clause (semijoin), the semijoin was wrongly transformed into an inner join leading to excess rows in the result. (Bug#53298)

Internal Performance Schema header files were unnecessarily installed publicly. (Bug#53281)

Performance Schema header files were not installed in the correct directory. (Bug#53255)

The server could crash when processing subqueries with empty results. (Bug#53236)

When reporting a foreign key constraint violation during INSERT, InnoDB could display uninitialized data for the DB_TRX_ID and DB_ROLL_PTR system columns. (Bug#53202)

mysqldump and SELECT ... INTO OUTFILE truncated long BLOB and TEXT values to 766 bytes. (Bug#53088)

DBUG code could in some cirsumstances call FreeState() twice, leading to a server crash or failure. (Bug#52884)

With a non-latin1 ASCII-based current character set, the server inappropriately converted DATETIME values to strings. This resulted in the optimizer not using indexes on such columns. (Bug#52849)

An overly strict assertion could fail during the purge of delete-marked records in DYNAMIC or COMPRESSED InnoDB tables that contain column prefix indexes. (Bug#52746)

InnoDB attempted to choose off-page storage without ensuring that there was an “off-page storage” flag in the record header. To correct this, in DYNAMIC and COMPRESSED formats, InnoDB stores locally any non-BLOB columns having a maximum length not exceeding 256 bytes. This is because there is no room for the “external storage” flag when the maximum length is 255 bytes or less. This restriction trivially holds in REDUNDANT and COMPACT formats, because there InnoDB always stores locally columns having a length up to local_len = 788 bytes. (Bug#52745)

mysqld_safe set plugin_dir using a default path name rather than a path depending on basedir. (Bug#52737)

The large_pages system variable was tied to the --large-files command-line option, not the --large-pages option. (Bug#52716)

Semi-consistent read was implemented for InnoDB to address Bug#3300. Semi-consistent reads do not block when a nonmatching record is already locked by some other transaction. If the record is not locked, a lock is acquired, but is released if the record does not match the WHERE condition. However, semi-consistent read was attempted even for UPDATE statements having a WHERE condition of the form pk_col1=constant1, ..., pk_colN=constantN. Some code that was designed with the assumption that semi-consistent read would be only attempted on table scans, failed. (Bug#52663)

Setting @@GLOBAL.debug to an empty string failed to clear the current debug settings. (Bug#52629)

SHOW CREATE TABLE was blocked if the table was write locked by another session. (Bug#52593)

Attempts to access a nonexistent table in the performance_schema database resulted in a misleading error message. (Bug#52586)

For values of optimizer_join_cache_level less than or equal to 4, the server could crash in queries with outer joins and indexed columns. (Bug#52540)

Performance Schema could enter an infinite loop if required to create a large number of mutex instances. (Bug#52502)

mysql_upgrade attempted to work with stored routines before they were available. (Bug#52444)

EXPLAIN EXTENDED crashed trying to resolve references to freed temporary table columns for GROUP_CONCAT() ORDER BY arguments. (Bug#52397)

The server tried to read too many records from the join cache, resulting in a crash. (Bug#52394)

On Windows, an IPv6 connection to the server could not be made using an IPv4 address or host name. (Bug#52381)

Two sessions trying to set the global event_scheduler system variable to OFF resulted in one of them hanging waiting for the event scheduler to stop. (Bug#52367)

There was a race condition between flags used for signaling that a query was killed, which led to error-reporting and lock-acquisition problems. (Bug#52356)

The optimizer could attempt to evaluate the WHERE clause before any rows had been read, resulting in a server crash. (Bug#52177)

An assertion was raised as a result of a NULL string being passed to the dtoa code. (Bug#52165)

A memory leak occurred due to missing deallocation of the comparators array (a member of the Arg_comparator class). (Bug#52124)

For debug builds, creating a view containing a subquery that might require collation adjustment caused an assertion to be raised. For example, this could occur if some items had different collations but the result collation could be adjusted to the one of them. (Bug#52120)

Aggregate functions could incorrectly return NULL in outer join queries. (Bug#52051)

A COUNT(DISTINCT) query on a view could cause a server crash. (Bug#51980)

For LDML-defined collations, some data structures were not initialized properly to enable UPPER() and LOWER() to work correctly. (Bug#51976)

Running the make test-bt target would fail in the event of a single test run failure, instead of running all the tests in the suite. (Bug#51896)

On Windows, LOAD_FILE() could cause a crash for some pathnames. (Bug#51893)

Invalid memory reads occurred for HANDLER ... READ NEXT after a failed HANDLER ... READ FIRST. (Bug#51877)

After TRUNCATE TABLE of a MyISAM table, subsequent queries could crash the server if myisam_use_mmap was enabled. (Bug#51868)

If myisam_sort_buffer_size was set to a small value, table repair for MyISAM tables with FULLTEXT indexes could crash the server. (Bug#51866)

On Windows, the my_rename() function failed to check whether the source file existed. (Bug#51861)

In LOAD DATA INFILE, using a SET clause to set a column equal to itself caused a server crash. (Bug#51850)

Stored routine DDL statements were written to the binary log using statement-based format regardless of the current logging format. (Bug#51839)

A problem with equality propagation optimization for prepared statements and stored procedures caused a server crash upon re-execution of the prepared statement or stored procedure. (Bug#51650)

See also Bug#8115, Bug#8849.

The server attempted to deallocate already freed memory for the slave_load_tmpdir system variable. (Bug#51635)

The optimizer performed an incorrect join type when COALESCE() appeared within an IN() operation. (Bug#51598)

Locking involving the LOCK_plugin, LOCK_global_system_variables, and LOCK_status mutexes could deadlock. (Bug#51591)

Executing a LOAD XML INFILE statement could sometimes lead to a crash of the MySQL Server. (Bug#51571)

The server crashed when the optimizer attempted to determine constant tables but a table storage engine did not support exact record count. (Bug#51494)

For debug builds, semijoin flattening for a subquery in a HAVING clause could raise an assertion. (Bug#51487)

mysqld_multi failed due to a syntax error in the script. (Bug#51468)

In the embedded server with innodb_file_per_table enabled, InnoDB rejected full path names to tables. (Bug#51384)

The server could crash populating the INFORMATION_SCHEMA.PROCESSLIST table due to lack of mutex protection. (Bug#51377)

Use of HANDLER statements with tables that had spatial indexes caused a server crash. (Bug#51357)

With an XA transaction active, SET autocommit = 1 could cause side effects such as memory corruption or a server crash. (Bug#51342)

Corrupt MyISAM tables were automatically repaired even when myisam_recover_options was set to OFF. (Bug#51327)

Following a bulk insert into a MyISAM table, if MyISAM failed to build indexes using repair by sort, data file corruption could occur. (Bug#51307)

CHECKSUM TABLE could compute the checksum for BIT columns incorrectly. (Bug#51304)

A HAVING clause on a joined table in some cases failed to eliminate rows which should have been excluded from the result set. (Bug#51242)

ALTER TABLE on a MERGE table that has been locked using LOCK TABLES ... WRITE incorrectly produced an ER_TABLE_NOT_LOCKED_FOR_WRITE error. (Bug#51240)

The find_files() function used by SHOW statements performed redundant and unnecessary memory allocation. (Bug#51208)

Two sessions trying to set the global event_scheduler system variable to different values could deadlock. (Bug#51160)

With the duplicate weedout semijoin strategy, if a memory temporary table was converted to a disk table, the row count reported for the query result was one too low. (Bug#51100)

Use of incremental join buffering could produce incorrect query results. (Bug#51092)

The optimizer failed to properly remove join caches that it determined were unneeded, resulting in a server crash. (Bug#51084)

On some Unix/Linux platforms, an error during build from source could be produced, referring to a missing LT_INIT program. This is due to versions of libtool 2.1 and earlier. (Bug#51009)

Referring to a subquery result in a HAVING clause could produce incorrect results. (Bug#50995)

InnoDB fast index creation could incorrectly use a table copy in some cases. (Bug#50946)

The Loose Index Scan optimization method assumed that it could on the storage engine to maintain interval endpoint information, which was not true for the partitioning engine. (Bug#50939)

The type inference used for view columns caused some columns in views to be handled as the wrong type, as compared to the same columns in base tables. DATE columns in base tables were treated as TIME columns in views, and base table TIME columns as view DATETIME columns. (Bug#50918)

Use of filesort plus the join cache normally is preferred to a full index scan. But it was used even if the index is clustered, in which case, the clustered index scan can be faster. (Bug#50843)

For debug builds, SHOW BINARY LOGS caused an assertion to be raised if binary logging was not enabled. (Bug#50780)

When a storage engine supports both consistent snapshot and has a native driver, the BACKUP DATABASE code incorrectly attempted to use the native driver for a table that has partitions defined. (Bug#50697)

The SSL certificates in the test suite were about to expire. They have been updated with expiration dates in the year 2015. (Bug#50642)

The server did not recognize that the stored procedure cache became invalid if a view was created or modified within a procedure, resulting in a crash. (Bug#50624)

For debug builds on Windows, incorrect error handling for the backup logs caused an assertion to be raised. (Bug#50615)

For some queries with many tables, the optimizer spent too much time seeking the execution plan. (Bug#50595)

Incorrect handling of BIT columns in temporary tables could lead to spurious duplicate-key errors. (Bug#50591)

SPATIAL indexes were allowed on columns with non-spatial data types, resulting in a server crash for subsequent table inserts. (Bug#50574)

Index prefixes could be specified with a length greater than the associated column, resulting in a server crash for subsequent table inserts. (Bug#50542)

Use of loose index scan optimization for an aggregate function with DISTINCT (for example, COUNT(DISTINCT)) could produce incorrect results. (Bug#50539)

Global read lock handling was incorrect, which could lead to mysqldump timeouts. (Bug#50517)

User-defined variables of type REAL that contained NULL were handled improperly when assigned to a column of another type. (Bug#50511)

An incorrect string access caused part of an error message to be output as garbage. (Bug#50496)

The stop time for RESTORE operations was logged incorrectly. (Bug#50458)

The second or subsequent invocation of a stored procedure containing DROP TRIGGER could cause a server crash. (Bug#50423)

The return value for calls to put information into the stored routine cache were not consistently checked, causing an assertion to be raised. (Bug#50412)

The printstack function does not exist on Solaris 8 or earlier, which would lead to a compilation failure. (Bug#50409)

The optimizer raised an assertion due to a divide-by-zero error during I/O cost estimation. (Bug#50381)

Setting --secure-file-priv to the empty string left the value unaffected. (Bug#50373)

Double-nested, noncorrelated IN subqueries failed when using the FirstMatch optimization strategy with join_cache_level set to 1. (Bug#50361)

Full-text queries that used the truncation operator (*) could enter an infinite loop. (Bug#50351)

For debug builds, an assertion was incorrectly raised in the optimizer when matching ORDER BY expressions. (Bug#50335)

A NULL pointer was dereferenced in a special debug mode used by a FEDERATED test case. (Bug#50308)

A user could see tables in INFORMATION_SCHEMA.TABLES without appropriate privileges for them. (Bug#50276)

Debug output for join structures was garbled. (Bug#50271)

Cost calculation for semijoins could be incorrect, leading to an incorrect execution plan or a server crash. (Bug#50237)

The server crashed when an InnoDB background thread attempted to write a message containing a partitioned table name to the error log. (Bug#50201)

Passwords for CREATE USER statements were written to the binary log in plaintext rather than in ciphertext. (Bug#50172)

Within a stored routine, selecting the result of CONCAT_WS() with a routine parameter argument into a user variable could return incorrect results. (Bug#50096)

With semijoin optimization enabled, references to views within a subquery could cause a server crash. (Bug#50089)

Calculation of intervals for Event Scheduler events was not portable. (Bug#50087)

If an error occurred when a prepared statement was reprepared, OUT parameters incorrectly could be sent to the client, leading to a crash. (Bug#49972)

If a subquery that had been converted to a semijoin contained an outer join, constant table optimization was not always done. (Bug#49952)

The YEAR values 2000 and 0000 could be treated as equal. (Bug#49910)

With engine condition pushdown enabled, filesort could raise an assertion due to improper data setup. (Bug#49906)

Queries optimized with GROUP_MIN_MAX did not clean up KEYREAD optimizations properly, causing subsequent queries to return incomplete rows. (Bug#49902)

The filesort sorting method applied to a CHAR(0) column could lead to a server crash. (Bug#49897)

For some queries, QUICK_ROR_INTERSELECT_SELECT was asked to provide sorted output. This raised an assertion because it does not support sorting. (Bug#49867)

The LooseScan semijoin strategy could return incorrect results with Multi-Range Read (MRR) enabled because MRR did not return rows in key order as required for LooseScan. (Bug#49845)

Performing a single in-place ALTER TABLE containing ADD INDEX and DROP INDEX options that used the same index name could result in a corrupt table definition file. Now such ALTER TABLE statements are no longer performed in place. (Bug#49838)

mysql_upgrade did not detect when CSV log tables incorrectly contained columns that could be NULL. Now these columns are altered to be NOT NULL. (Bug#49823)

For debug builds on Windows, SAFEMALLOC was defined inconsistently, leading to mismatches when using my_malloc() and my_free(). (Bug#49811)

The mysql.server script had incorrect shutdown logic. (Bug#49772)

EXPLAIN EXTENDED UNION ... ORDER BY caused a crash when the ORDER BY referred to a nonconstant or full-text function or a subquery. (Bug#49734)

MySQL Backup code could fail due to improper thread handling. (Bug#49680)

The push_warning_printf() function was being called with an invalid error level MYSQL_ERROR::WARN_LEVEL_ERROR, causing an assertion failure. To fix the problem, MYSQL_ERROR::WARN_LEVEL_ERROR has been replaced by MYSQL_ERROR::WARN_LEVEL_WARN. (Bug#49638)

EXPLAIN for queries with subqueries evaluated using materialization (with the result stored in a temporary table) caused a server crash. (Bug#49630)

For dynamic format MyISAM tables containing LONGTEXT columns, a bulk INSERT ... ON DUPLICATE KEY UPDATE or bulk REPLACE could cause corruption. (Bug#49628)

For debug builds, a missing DEBUG_VOID_RETURN caused RESTORE to raise an assertion. (Bug#49614)

The backup metadata lock put in place by one BACKUP DATABASE or RESTORE operation could incorrectly be deactivated by another such operation issued concurrently. (Bug#49603)

Some prepared statements could raise an assertion when re-executed. (Bug#49570)

sql_buffer_result had an effect on non-SELECT statements, contrary to the documentation. (Bug#49552)

For debug builds, with sql_safe_updates enabled, a multiple-table UPDATE with the IGNORE modifier could raise an assertion. (Bug#49534)

The result of comparison between nullable BIGINT and INT columns was inconsistent. (Bug#49517)

In some cases a subquery need not be evaluated because it returns only aggregate values that can be calculated from table metadata. This sometimes was not handled by the enclosing subquery, resulting in a server crash. (Bug#49512)

A Valgrind error in make_cond_for_table_from_pred() was corrected. Thanks to Sergey Petrunya for the patch to fix this bug. (Bug#49506)

When compiling on Windows, an error in the CMake definitions for InnoDB would cause the engine to be built incorrectly. (Bug#49502)

Incorrect cache initialization prevented storage of converted constant values and could produce incorrect comparison results. (Bug#49489)

EXPLAIN EXTENDED crashed trying to print column names for a subquery in the FROM clause when the table had gone out of scope. (Bug#49487)

Comparisons involving YEAR values could produce incorrect results. (Bug#49480)

See also Bug#43668.

Valgrind warnings for CHECKSUM TABLE were corrected. (Bug#49465)

Mixing full-text searches and row expressions caused a crash. (Bug#49445)

For an InnoDB table with BLOB and TEXT columns containing NULL values, those values became empty strings after BACKUP DATABASE and RESTORE. (Bug#49414)

If a LOCK TABLES statement was in effect, BACKUP DATABASE was unable to open the backup log tables. (Bug#49398)

Some MySQL Backup log messages were improperly formatted. (Bug#49358)

If a MEMORY table in a backup image exeeded the maximum size allowed by the server for that storage engine, a RESTORE of the image resulted in a general “Error when sending data” message from the default restore driver. Now the driver additionally reports a more specific “table full” message that better reflects the cause of the error. (Bug#49353)

The MyISAM backup driver did not protect acquire a mutex for a structure that it was destroying, causing a crash if another thread attempted to access the structure. (Bug#49343)

mysqltest no longer lets you execute an SQL statement on a connection after doing a send command, unless you do a reap first. This was previously accepted but could produce unpredictable results. (Bug#49269)

BACKUP DATABASE performance was degraded for backups that included many triggers. (Bug#49264)

Specifying an index algorithm (such as BTREE) for SPATIAL or FULLTEXT indexes caused a server crash. These index types do not support algorithm specification, and it is now disallowed to do so. (Bug#49250)

Creating or dropping a table with 1023 transactions active caused an assertion failure. (Bug#49238)

mysql-test-run.pl now recognizes the MTR_TESTCASE_TIMEOUT, MTR_SUITE_TIMEOUT, MTR_SHUTDOWN_TIMEOUT, and MTR_START_TIMEOUT environment variables. If they are set, their values are used to set the --testcase-timeout, --suite-timeout, --shutdown-timeout, and --start-timeout options, respectively. (Bug#49210)

The optimizer sometimes incorrectly handled conditions of the form WHERE col_name='const1' AND col_name='const2'. (Bug#49199)

With semijoin optimization enabled, the second execution of a prepared statement that referenced a view in a subquery could produce incorrect results. (Bug#49198)

RESTORE crashed if a native backup driver required a storage engine that was not loaded. (Bug#49146)

Execution of DECODE() and ENCODE() could be inefficient because multiple executions within a single statement reinitialized the random generator multiple times even with constant parameters. (Bug#49141)

Valgrind warnings for several logging messages were corrected. (Bug#49130)

With binary logging enabled, REVOKE ... ON {PROCEDURE|FUNCTION} FROM ... could cause a crash. (Bug#49119)

The LIKE operator did not work correctly when using an index for a ucs2 column. (Bug#49028)

For debug builds on Windows, warnings about incorrect use of debugging directives were written to the error log. The directives were rewritten to eliminate these messages. (Bug#49025)

Semisynchronous replication could run out of nodes to execute simultaneous transactions if the Event Scheduler was executing events. (Bug#49020)

check_key_in_view() was missing a DBUG_RETURN in one code branch, causing a crash in debug builds. (Bug#48995)

If a query involving a table was terminated with KILL, a subsequent SHOW CREATE TABLE for that table caused a server crash. (Bug#48985)

Several strmake() calls had an incorrect length argument (too large by one). (Bug#48983)

For BACKUP DATABASE, there was a race condition between the backup thread and the locking thread for the default backup driver. (Bug#48930)

On POSIX systems, calls to select() with a file descriptor set larger than FD_SETSIZE resulted in unpredictable I/O errors; for example, when a large number of tables required repair. (Bug#48929)

A BACKUP DATABASE and RESTORE cycle could fail to handle database and table lettercase on systems with lower_case_table_names set to 2. (Bug#48923)

A dependent subquery containing COUNT(DISTINCT col_name)) could be evaluated incorrectly. (Bug#48920)

Privileges for stored routines were ignored for mixed-case routine names. (Bug#48872)

See also Bug#41049.

On Fedora 12, strmov() did not guarantee correct operation for overlapping source and destination buffer. Calls were fixed to use an overlap-safe version instead. (Bug#48866)

Building MySQL on Fedora Core 12 64-bit failed, due to errors in comp_err. (Bug#48864)

With semijoin optimization enabled, a stored procedure that selected from a view in a subquery crashed when invoked the second time. (Bug#48834)

Concurrent ALTER TABLE operations on an InnoDB table could raise an assertion. (Bug#48782)

If a stored function contained a RETURN statement with an ENUM value in the ucs2 character set, SHOW CREATE FUNCTION and SELECT DTD_IDENTIFIER FROM INFORMATION_SCHEMA.ROUTINES returned incorrect values. (Bug#48766)

An ARZ file missing from the database directory caused the server to crash. (Bug#48757)

Certain INTERVAL expressions could cause a crash on 64-bit systems. (Bug#48739)

Selecting from INFORMATION_SCHEMA.ROUTINES or INFORMATION_SCHEMA.PARAMETERS resulted in a memory leak. (Bug#48729)

Incomplete reset of internal TABLE structures could cause a crash with eq_ref table access in subqueries. (Bug#48709)

During query execution, ranges could be merged incorrectly for OR operations and return an incorrect result. (Bug#48665)

With semijoin optimization enabled, incorrect processing of semijoin nests resulted in incorrect query results. (Bug#48623)

In MySQL 5.1, READ COMMITTED was changed to use less locking due to the availability of row based binary logging (see the Note under READ COMMITTED at Section 12.3.6, “SET TRANSACTION Syntax”). However, READ UNCOMMITTED did not have the same change, so it was using more locks than the higher isolation level, which is unexpected. This was changed so that READ UNCOMMITTED now also uses the lesser amount of locking and has the same restrictions for binary logging. (Bug#48607)

The InnoDB Table Monitor reported the FLOAT and DOUBLE data types incorrectly. (Bug#48526)

A trigger could change the behavior of assigning NULL to a NOT NULL column. (Bug#48525)

Re-execution of a prepared statement could cause a server crash. (Bug#48508)

With row-based binary logging, the server crashed for statements of the form CREATE TABLE IF NOT EXISTS existing_view LIKE temporary_table. This occurred because the server handled the existing view as a table when logging the statement. (Bug#48506)

The error message for ER_UPDATE_INFO was subject to buffer overflow or truncation. (Bug#48500)

The server crashed when it could not determine the best execution plan for queries involving outer joins with nondeterministic ON clauses such as the ones containing the RAND() function, a user-defined function, or a NOT DETERMINISTIC stored function. (Bug#48483)

DISTINCT was ignored for queries with GROUP BY WITH ROLLUP and only const tables. (Bug#48475)

Loose index scan was inappropriately chosen for some WHERE conditions. (Bug#48472)

The server could crash and corrupt the tablespace if the InnoDB tablespace was configured with too small a value, or if many CREATE TEMPORARY TABLE statements were executed and the temporary file directory filled up with innodb_file_per_table enabled. (Bug#48469)

Parts of the range optimizer could be initialized incorrectly, resulting in Valgrind errors. (Bug#48459)

A bad typecast could cause query execution to allocate large amounts of memory. (Bug#48458)

Running SHOW CREATE TABLE on a view v1 that contained a function which accessed another view v2 could trigger a infinite loop if the view (v2) referenced within the function caused a warning to be raised while being opened. (Bug#48449)

Following a literal, the COLLATE clause was mishandled such that different results can be produced depending whether an index is used. (Bug#48447)

Invalid memory reads could occur following a query that referenced a MyISAM tale multiple times with a write lock. (Bug#48438)

EXPLAIN could cause a server crash for some queries with subqueries. (Bug#48419)

SUM() artificially increased the precision of a DECIMAL argument, which was truncated when a temporary table was created to hold the results. (Bug#48370)

See also Bug#45261.

SHOW BINLOG EVENTS could fail with a error: Wrong offset or I/O error. (Bug#48357)

Valgrind warnings related to binary logging of LOAD DATA INFILE statements were corrected. (Bug#48340)

GRANT and REVOKE crashed if a user name was specified as CURRENT_USER(). (Bug#48319)

On Windows, InnoDB could not be built as a statically linked library. (Bug#48317)

If a prepared statement using a merged view referencing an INFORMATION_SCHEMA table was executed, no metadata lock of the view was taken. Consequently, it was possible for concurrent DDL statements on the view to execute and cause statements to be written in the wrong order to the binary log. (Bug#48315)

If an outer query was invalid, a subquery might not even be set up. EXPLAIN EXTENDED did not expect this and caused a crash by trying to dereference improperly set up information. (Bug#48295)

For debug builds, creating a view containing a row constructor caused an assertion to be raised. (Bug#48294)

A query containing a view using temporary tables and multiple tables in the FROM clause and PROCEDURE ANALYSE() caused a server crash.

As a result of this bug fix, PROCEDURE ANALYSE() is legal only in a top-level SELECT. (Bug#48293)

See also Bug#46184.

Error handling was missing for SELECT statements containing subqueries in the WHERE clause and that assigned a SELECT result to a user variable. The server could crash as a result. (Bug#48291)

The MERGE engine failed to open a child table from a different database if the child table or database name contained characters that were the subject of table name to filename encoding.

Further, the MERGE engine did not properly open a child table from the same database if the child table name contained characters such as '/', '#'. (Bug#48265)

An assertion could fail if the optimizer used a SPATIAL index. (Bug#48258, Bug#47019)

If REPAIR TABLE was used on a table already read-locked by LOCK TABLES, the repair mistakenly tried to upgrade the read lock to an exclusive lock, triggering an assertion. (Bug#48248)

Memory-allocation failures were handled incorrectly in the InnoDB os_mem_alloc_large() function. (Bug#48237)

FLUSH TABLES WITH READ LOCK could deadlock when executed against concurrent DDL statements for stored routines or account-management statements. (Bug#48210)

WHERE clauses with outer_value_list NOT IN subquery were handled incorrectly if the outer value list contained multiple items at least one of which could be NULL. (Bug#48177)

Searches using a non-default collation could return different results for a table when partitioning was and was not used. (Bug#48161)

With one thread waiting for a lock on a table, if another thread dropped the table and created a new table with the same name and structure, the first thread would not notice that the table had been re-created and would try to used cached metadata that belonged to the old table but had been freed. (Bug#48157)

A combination of GROUP BY WITH ROLLUP, DISTINCT and the const join type in a query caused a server crash when the optimizer chose to employ a temporary table to resolve DISTINCT. (Bug#48131)

Some IN() clauses were processed differently for InnoDB than for other storage engines. (Bug#48093)

mysql_secure_installation did not work on Solaris. (Bug#48086)

Use of a view that selects from character columns in a subquery could crash the server. (Bug#48073)

A subquery that selected from a view could return incorrect results when used in a non-prepared statement. (Bug#48073)

The subquery optimizer had a memory leak. (Bug#48060)

The backup logging to the FILE destination enabled, the server did not check whether the log files were missing and create them as necessary. (Bug#48059)

Server shutdown failed on Windows. (Bug#48047)

On Windows, the server failed to find a description for Event ID 100. (Bug#48042)

When running mysql_secure_installation, the command would fail if the root password contained multiple spaces, \, # or quote characters. (Bug#48031)

Interruption of BACKUP DATABASE resulted in spurious duplicate error messages. (Bug#47994)

In some cases, using a null microsecond part in a WHERE condition (for example, WHERE date_time_field <= 'YYYY-MM-DD HH:MM:SS.0000') could lead to incorrect results due to improper DATETIME comparison. (Bug#47963)

A build configured using the --without-server option did not compile the yaSSL code, so if --with-ssl was also used, the build failed. (Bug#47957)

MySQL Backup logged information differently to the table and file backup log destinations. (Bug#47956)

The backup driver waited too long in unlock(). (Bug#47939)

MATCH IN BOOLEAN MODE searches could return too many results inside a subquery. (Bug#47930)

When a query used a DATE or DATETIME value formatted using any separator characters other than hyphen ('-') and a >= condition matching only the greatest value in an indexed column, the result was empty if an index range scan was employed. (Bug#47925)

mysys/mf_keycache.c requires threading, but no test was made for thread support. (Bug#47923)

For debug builds, an assertion could fail during the next statement executed for a temporary table after a multiple-table UPDATE involving that table and modified an AUTO_INCREMENT column with a user-supplied value. (Bug#47919)

Slow CALL statements were not always logged to the slow query log because execution time for multiple-statement stored procedures was assessed incorrectly. (Bug#47905)

A query that read from a derived table (of the form SELECT ... FROM (SELECT ...)) produced incorrect results when the following conditions were present:

(Bug#47904)

Attempts to use BACKUP DATABASE for partitioned tables with subpartitions caused a server crash. (Bug#47879)

The mysys/mf_strip.c file, which defines the strip_sp() function, has been removed from the MySQL source. The function was no longer used within the main build, and the supplied function was causing symbol errors on Windows builds. (Bug#47857)

The backup catalog did not contain sufficient information to perform privilege checking for triggers. (Bug#47804)

When building storage engines on Windows it was not possible to specify additional libraries within the CMake file required for the build. An ${engine}_LIBS macro has been included in the files to support these additional storage-engine specific libraries. (Bug#47797)

When building a pluggable storage engine on Windows, the engine name could be based on the directory name where the engine was located, rather than the configured storage engine name. (Bug#47795)

During cleanup of a stored procedure's internal structures, the flag to ignore the errors for INSERT IGNORE or UPDATE IGNORE was not cleaned up, which could result in a server crash. (Bug#47788)

If the first argument to GeomFromWKB() function was a geometry value, the function just returned its value. However, it failed to preserve the argument's null_value flag, which caused an unexpected NULL value to be returned to the caller, resulting in a server crash. (Bug#47780)

InnoDB could crash when updating spatial values. (Bug#47777)

The pthread_cond_wait() implementations for Windows could deadlock in some rare circumstances. (Bug#47768)

The optimization to read MIN() or MAX() values from an index did not properly handle comparisons with NULL values. This could produce incorrect results for MIN() or MAX()when the WHERE clause tested a NOT NULL column for NULL. (Bug#47762)

Killing a query during the optimization phase of a subquery could cause a server crash. (Bug#47761)

User-defined collations with an ID less then 256 were not initialized correctly when loaded and caused a server crash. (Bug#47756)

The BLACKHOLE storage engine failed to load on Solaris and OpenSolaris if DTrace probes had been enabled. (Bug#47748)

For debug builds, killing a SELECT retrieving from a view that was processing a function caused an assertion to be raised. (Bug#47736)

Failure to open a view with a nonexistent DEFINER was improperly handled and the server would crash later attempting to lock the view. (Bug#47734)

Using REPLACE to update a previously inserted negative value in an AUTO_INCREMENT coumn in an InnoDB table caused the table auto-increment value to be updated to 2147483647. (Bug#47720)

If a session held a global read lock acquired with FLUSH TABLES WITH READ LOCK, a lock for one table acquired with LOCK TABLES, and issued an INSERT DELAYED statement for another table, deadlock could occur. (Bug#47682)

The mysql client status command displayed an incorrect value for the server character set. (Bug#47671)

The query shown by EXPLAIN EXTENDED plus SHOW WARNINGS could produce results different from the original query. (Bug#47669)

Connecting to a 4.1.x server from a 5.1.x or higher mysql client resulted in a memory-free error when disconnecting. (Bug#47655)

Queries containing GROUP BY ... WITH ROLLUP that did not use indexes could return incorrect results. (Bug#47650)

If an invocation of a stored procedure failed in the table-open stage, subsequent invocations that did not fail in that stage could cause a crash. (Bug#47649)

If a prepared statement used both a MERGE table and a stored function or trigger, execution sometimes failed with a No such table error. (Bug#47648)

CREATE VIEW raised an assertion if a temporary table existed with the same name as the view. (Bug#47635)

An assertion occurred in ha_myisammrg.cc line 1137:

  DBUG_ASSERT(this->file->children_attached);

The problem was found while running RQG tests and the assertion occurred during REPAIR, OPTIMIZE, and ANALYZE operations. (Bug#47633)

Assignment of a system variable sharing the same base name as a declared stored program variable in the same context could lead to a crash. (Bug#47627)

Renaming a column of an InnoDB table caused the server to go out of sync with the InnoDB data dictionary. (Bug#47621)

MyISAM could write uninitialized data to new index pages. Now zeros are written to unused bytes in the pages. (Bug#47598)

On WIndows, when an idle named pipe connection was forcibly closed with a KILL statement or because the server was being shut down, the thread that was closing the connection would hang infinitely. (Bug#47571, Bug#31621)

On Mac OS X or Windows, sending a SIGHUP signal to the server or an asynchronous flush (triggered by flush_time) caused the server to crash. (Bug#47525)

RESTORE did not restore table AUTO_INCREMENT values properly. (Bug#47484)

Debug builds could not be compiled with the Sun Studio compiler. (Bug#47474)

OPTIMIZE TABLE for an InnoDB table could raise an assertion if another session issued a concurrent DROP TABLE. (Bug#47459)

For updates to InnoDB tables, TIMESTAMP columns could be updated even when no values actually changed. (Bug#47453)

Setting myisam_repair_threads larger than 1 could result in the cardinality for all indexes of a MyISAM table being set to 1 after parallel index repair. (Bug#47444)

Queries of the form SELECT SUM(DISTINCT varchar_key) FROM tbl_name caused a server crash. (Bug#47421)

my_static.o was included twice into libmysqld, resulting in duplicate-symbol errors on Mac OS X 10.6. (Bug#47414)

A function call could end without throwing an error or setting the return value. For example, this could happen when an error occurred while calculating the return value. This is fixed by setting the value to NULL when an error occurs during evaluation of an expression. (Bug#47412)

On Solaris, no stack trace was printed to the error log after a crash. (Bug#47391)

Previously, BACKUP DATABASE failed if there were two databases whose names differed in lettercase only and when one database contained an object that was missing in the other. Now BACKUP DATABASE correctly determines which objects are in which database even when database names differ only in lettercase. (Bug#47386)

mysqladmin debug could crash on 64-bit systems. (Bug#47382)

A crash occurred when a user variable that was assigned to a subquery result was used as a result field in a SELECT statement with aggregate functions. (Bug#47371)

With semijoin optimization enabled, transformation of a subquery to a semijoin could crash the server if a name resolution error occurred. (Bug#47367)

The assert could be raised if ALTER VIEW was used to alter a view (existing or nonexisting) and a temporary table with the same name already existed. (Bug#47335)

If a temporary table was created with the same name as a view referenced in a stored routine, routine execution could raise an assertion. (Bug#47313)

Selecting from the process list in the embedded server caused a crash. (Bug#47304)

See also Bug#43733.

ANALYZE TABLE and CHECK TABLE are now included in the set of statements blocked by the backup metadata lock because under some conditions these statements can modify tables. (Bug#47281)

A simple SELECT with implicit grouping could return many rows rather than a single row if the query was ordered by the aggregated column in the select list. (Bug#47280)

An assertion could be raised for CREATE TABLE if there was a pending INSERT DELAYED or REPLACE DELAYED for the same table. (Bug#47274)

Using LOCK TABLES to lock a table and a view with the same name could raise an assertion. (Bug#47249)

InnoDB raised errors in some cases in a manner not compatible with SIGNAL and RESIGNAL. (Bug#47233)

In some cases, an impossible WHERE expression was not detected, allowing the optimizer to choose an incorrect execution plan and leading to a wrong result. Also, the absence of early NULL-filtering allowed the server to do useless scans with NULL values in a NULL-rejecting predicate, thus slowing query execution. (Bug#47217)

Programs did not exit if the option file specfied by --defaults-file was not found. (Bug#47216)

The first execution of STOP SLAVE UNTIL stopped too early. (Bug#47210)

A multiple-table UPDATE involving a natural join and a mergeable view raised an assertion. (Bug#47150)

When the mysql client was invoked with the --vertical option, it ignored the --skip-column-names option. (Bug#47147)

On FreeBSD, memory mapping for MERGE tables could fail if underlying tables were empty. (Bug#47139)

Solaris binary packages now are compiled with -g0 rather than -g. (Bug#47137)

Corrected a potential problem of unintended overwriting of files when the MY_DONT_OVERWRITE_FILE flag was used. (Bug#47126)

If an InnoDB table was created with the AUTO_INCREMENT table option to specify an initial auto-increment value, and an index was added in a separate operation later, the auto-increment value was lost (subsequent inserts began at 1 rather than the specified value). (Bug#47125)

Incorrect handling of predicates involving NULL by the range optimizer could lead to an infinite loop during query execution. (Bug#47123)

A CREATE TABLE attempt for a table that had been opened with HANDLER caused an assertion failure because CREATE TABLE did not close any open handlers for the table. (Bug#47107)

EXPLAIN caused a server crash for certain valid queries. (Bug#47106)

When HANDLER OPEN was attempted on a MERGE table, an error occurred because this is an unsupported operation, but locks could remain unreleased. (Bug#47098)

mysqld_safe did not always pass --open-files-limit through to mysqld. mysqld_safe did not treat dashes and underscores as equivalent in option names. (Bug#47095)

Repair by sort or parallel repair of MyISAM tables could fail to fail over to repair with key cache. (Bug#47073)

For events of MYSQL_AUDIT_GENERAL_CLASS, the event subclass was not passed to audit plugins even though the server passed the subclass to the plugin handler. The subclass is now available through the following changes:

The example plugin in the plugin/audit_null directory has been modified to count events of each subclass, based on the event_subclass value. See Section 22.2.5.2, “Writing Audit Plugins”. (Bug#47059)

InnoDB Plugin did not compile on some Solaris systems. (Bug#47058)

On WIndows, when a failed I/O operation occurred with return code of ERROR_WORKING_SET_QUOTA, InnoDB intentionally crashed the server. Now InnoDB sleeps for 100ms and retries the failed operation. (Bug#47055)

After a binary upgrade to MySQL 5.1 from a MySQL 5.0 installation that contains ARCHIVE tables, accessing those tables caused the server to crash, even if you had run mysql_upgrade or CHECK TABLE ... FOR UPGRADE.

To work around this problem, use mysqldump to dump all ARCHIVE tables before upgrading, and reload them into MySQL 5.1 after upgrading. The same problem occurs for binary downgrades from MySQL 5.1 to 5.0. (Bug#47012)

The mysql_config script contained a reference to @innodb_system_libs@ that was not replaced with the corresponding library flags during the build process and ended up in the output of mysql_config --libs. (Bug#47007)

The configure option --without-server did not work. (Bug#46980)

Failed multiple-table DELETE statements could raise an assertion. (Bug#46958)

When MySQL crashed (or a snapshot was taken that simulates a crash), it was possible that internal XA transactions (used to synchronize the binary log and InnoDB) could be left in a PREPARED state, whereas they should be rolled back. This occurred when the server_id value changed before the restart, because that value was used to construct XID values.

Now the restriction is relaxed that the server_id value be consistent for XID values to be considered valid. The rollback phase should then be able to clean up all pending XA transactions. (Bug#46944)

When creating a new instance on Windows using mysqld-nt and the --install parameter, the value of the service would be set incorrectly, resulting in a failure to start the configured service. (Bug#46917)

A malformed query caused EXPLAIN EXTENDED to crash during the attempt to display the optimizer-transformed query. Now if the query is malformed, EXPLAIN EXTENDED does not try to show the optimizer-transformed query. (Bug#46860)

The test suite was missing from RPM packages. (Bug#46834)

Some error messages included a literal mysql database name rather than a parameter for the database name. (Bug#46792)

For InnoDB tables, an unnecessary table rebuild for ALTER TABLE could sometimes occur for metadata-only changes. (Bug#46760)

The server could crash for queries with the following elements: 1. An “impossible where” in the outermost SELECT; 2. An aggregate in the outermost SELECT; 3. A correlated subquery with a WHERE clause that includes an outer field reference as a top-level WHERE sargable predicate; (Bug#46749)

The server crashed for attempts to drop a trigger for which the subject table was shadowed by a temporary table with the same name. (Bug#46747)

In a subquery, a condition of the form subquery_column = x (where x came from an outer table) matched even when x contained NULL. The result was that extra rows were incorrectly returned. (Bug#46743)

The optimizer failed to return NULL for an aggregate applied to an empty result when semijoin optimization was used. (Bug#46733)

InnoDB Plugin did not compile using gcc 4.1 on PPC systems. (Bug#46718)

Queries with nested subqueries in the FROM clause using materialization could cause a server crash. (Bug#46692)

The optimizer exited prematurely in some cases when it became clear that zero rows would satisfy the query. In these cases, subqueries for which the optimizer had decided to use a materialization strategy were not set up properly. (Bug#46680)

Transactional locks acquired with LOCK TABLES did not protect InnoDB tables from DDL operations initiated from other sessions. (Bug#46678)

Deadlock could occur when executing transactions containing data-modifying statements at the same time as FLUSH TABLES WITH READ LOCK or SET read_only=1 statements. (Bug#46673)

InnoDB does not currently support transactional locking with the NOWAIT modifier, but the error message indicated a lock wait timeout. Now it indicates that this operation is unsupported. (Bug#46664)

Deadlock occurred if one session was running a multiple-statement transaction that involved a single partitioned table and another session attempted to alter the table. (Bug#46654)

Concurrent INSERT INTO ... SELECT statements for an InnoDB table could cause an AUTO_INCREMENT assertion failure. (Bug#46650)

The Serbian locale name 'sr_YU' is obsolete. It is still recognized for backward compatibility, but 'sr_RS' now should be used instead. (Bug#46633)

On Solaris and HP-UX systems with the environment set to the default C locale, MySQL client programs issued an Unknown OS character set error. (Bug#46619)

SHOW CREATE TRIGGER for a MERGE table trigger caused an assertion failure. (Bug#46614)

Selecting from a MERGE table with a corrupted child MyISAM table could cause a server crash when the server attempted to automatically repair the child table. (Bug#46610)

DIV operations that are out of range generate an error Error (Code 1264): Out of range value (correct), but also an error: Error (Code 1041): Out of memory (incorrect). (Bug#46606)

If a context object creation failed, BACKUP DATABASE crashed rather than handling the error. (Bug#46588)

If the binary log was open and unreadable, BACKUP DATABASE crashed rather than handling the error. (Bug#46574)

With semijoin optimization enabled, some queries using IN subqueries incorrectly returned empty results. (Bug#46556)

With semijoin optimization enabled, the optimizer sometimes chose an illegal execution plan for the FirstMatch strategy, resulting in duplicate values from IN subqueries. (Bug#46550)

With materialization enabled, certain subqueries with a WHERE clause that should return rows returned no rows. (Bug#46548)

If a transaction was rolled back inside InnoDB due to a deadlock or lock wait timeout, and a statement in the transaction had an IGNORE clause, the server could crash at the end of the statement or on shutdown. (Bug#46539)

The server could crash attempting to flush privileges after receipt of a SIGHUP signal. (Bug#46495)

TRUNCATE TABLE for a table that was opened with HANDLER did not close the handler and left it in an inconsistent state that could lead to a server crash. Now TRUNCATE TABLE for a table closes all open handlers for the table. (Bug#46456)

HANDLER OPEN followed by TRUNCATE TABLE could cause a server crash. (Bug#46452)

See also Bug#20667.

Trailing spaces were not ignored for user-defined collations that mapped spaces to a character other than 0x20. (Bug#46448)

See also Bug#29468.

The IGNORE clause on a DELETE statement masked an SQL statement error that occurred during trigger processing. (Bug#46425)

If INSERT INTO tbl_name invoked a stored function that modified tbl_name, the server crashed. (Bug#46374)

Use of an aggregate function without a GROUP BY clause could return several rows rather than a single row. (Bug#46328)

The server crashed if a shutdown occurred while a connection was idle. This happened because of a NULL pointer dereference while logging to the error log. (Bug#46267)

If the server is started with --skip-grant-tables, plugin loading and unloading should be disallowed, but the server failed to reject INSTALL PLUGIN and UNINSTALL PLUGIN statements. (Bug#46261)

Dropping an InnoDB table that used an unknown collation (created on a different server, for example) caused a server crash. (Bug#46256)

HANDLER statements within a transaction that already holds metadata locks could lead to deadlocks. (Bug#46224)

If innodb_force_recovery was set to 4 or higher, the server could crash when opening an InnoDB table containing an auto-increment column. MySQL versions 5.1.31 and later were affected. (Bug#46193)

A query containing a subquery in the FROM clause and PROCEDURE ANALYSE() caused a server crash. (Bug#46184)

See also Bug#48293.

The optimizer could continue to execute a query after a storage engine reported an error, leading to a server crash. (Bug#46175)

Deadlock could occur for INFORMATION_SCHEMA queries when execution attempted to open a table or its .frm file. (Bug#46044)

On 64-bit systems, --skip-innodb did not skip InnoDB startup. (Bug#46043)

For queries that used GROUP_CONCAT(DISTINCT ...), the value of max_heap_table_size was used for memory allocation, which could be excessive. Now the minimum of max_heap_table_size and tmp_table_size is used. (Bug#46018)

InnoDB did not disallow creation of an index with the name GEN_CLUST_INDEX, which is used internally. (Bug#46000)

CREATE TABLE ... SELECT could cause a server crash if no default database was selected. (Bug#45998)

Valgrind errors for InnoDB Plugin were corrected. (Bug#45992, Bug#46656)

If EXPLAIN encountered an error in the query, a memory leak occurred. (Bug#45989)

Valgrind warnings in semisynchronous replication code were corrected. (Bug#45973)

Improperly closing tables when INSERT DELAYED needed to reopen tables could cause an assertion failure. (Bug#45949)

See also Bug#18484.

Specifying an unknown column name together with an invalid number of expressions on the left-hand side of an IN subquery caused a core dump in Item_field::fix_fields(). (Bug#45863)

The default value of rpl_semi_sync_master_timeout was changed from 10ms to 10000ms (10 seconds) to reduce the incidence of timeouts. In addition, the master now logs when semisynchronous replication switches on or off. (Bug#45819)

Configuring MySQL for DTrace support resulted in a build failure on Solaris if the directory for the dtrace executable was not in PATH. (Bug#45810)

An infinite hang and 100% CPU usage occurred after handler tried to open a merge table.

If the command mysqladmin shutdown was executed during the hang, the debug server generated the following assert:

mysqld: table.cc:407: void free_table_share(TABLE_SHARE*): Assertion `share->ref_count ==
0' failed.
090610 14:54:04 - mysqld got signal 6 ;

(Bug#45781)

During the build of the Red Hat IA64 MySQL server RPM, the system library link order was incorrect. This made the resulting Red Hat IA64 RPM depend on "libc.so.6.1(GLIBC_PRIVATE)(64bit)", thus preventing installation of the package. (Bug#45706)

With semisynchronous replication enabled, the master considered semisynchronous status to be on even with no slaves connected. (Bug#45672, Bug#45673)

The caseinfo member of the CHARSET_INFO structure was not initialized for user-defined Unicode collations, leading to a server crash. (Bug#45645)

Grouping by a subquery in a query with a DISTINCT aggregate function led to incorrect and unordered grouping values. (Bug#45640)

The return value was not checked for some my_hash_insert() calls. (Bug#45613)

For an IPv6-enabled MySQL server, privileges specified using standard IPv4 addresses for hosts were not matched (only IPv4-mapped addresses were handled correctly).

As part of the fix for this bug, a new build option --disable-ipv6 has been introduced. Compiling MySQL with this option causes all IPv6-specific code in the server to be ignored.

(Bug#45606)

See also Bug#38247, Bug#43006, Bug#45283, Bug#45584.

BACKUP DATABASE failed to produce an error if a table to be backed up required a storage engine that was not loaded. (Bug#45587)

The hostname cache failed to work correctly. (Bug#45584)

See also Bug#38247, Bug#43006, Bug#45283, Bug#45606.

Appending values to an ENUM or SET definition is a metadata change for which ALTER TABLE need not rebuild the table, but it was being rebuilt anyway. (Bug#45567)

The socket system variable was unavailable on Windows. (Bug#45498)

Propagation of a large unsigned numeric constant in WHERE expressions could lead to incorrect results. This also affected EXPLAIN EXTENDED, which printed incorrect numeric constants in such transformed WHERE expressions. (Bug#45360)

In the ER_TABLEACCESS_DENIED_ERROR error message, the command name parameter could be truncated. (Bug#45355)

Truncation of DECIMAL values could lead to assertion failures; for example, when deducing the type of a table column from a literal DECIMAL value. (Bug#45261)

See also Bug#48370.

BACKUP DATABASE failed if a database contained a stored function with the same name as a built-in function. (Bug#45249)

A HAVING clause could be lost if an index for ORDER BY was available, incorrectly allowing additional rows to be returned. (Bug#45227)

There was no timeout for attempts to acquire metadata locks (for example, a DROP TABLE attempt for a table that was open in another transaction would not time out).

To handle such situations, there is now a lock_wait_timeout system variable that specifies the timeout in seconds for attempts to acquire metadata locks. The allowed values range from 1 to 3153600 (1 year). The default is 3153600.

This timeout applies to all statements that use metadata locks. These include DML and DDL operations on tables, views, stored procedures, and stored functions, as well as LOCK TABLES, FLUSH TABLES WITH READ LOCK, and HANDLER statements.

The timeout value applies separately for each metadata lock attempt. A given statement can require more than one lock, so it is possible for the statement to block for longer than the lock_wait_timeout value before reporting a timeout error. When lock timeout occurs, ER_LOCK_WAIT_TIMEOUT is reported.

lock_wait_timeout does not apply to delayed inserts, which always execute with a timeout of 1 year. This is done to avoid unnecessary timeouts because a session that issues a delayed insert receives no notification of delayed insert timeouts.

In addition, the unused table_lock_wait_timeout system variable was removed. (Bug#45225)

The XOR logical operator did not work correctly with Index Condition Pushdown. XOR conditions could be incorrectly pushed to an index that could not handle it, something that lead to missing records in the query result set. (Bug#45221)

Valgrind warnings about uninitialized variables in optimizer code were corrected. (Bug#45195)

With semijoin optimization enabled, incorrect FirstMatch initialization allowed join cache usage and led to incorrect results. (Bug#45191)

Client flags were incorrectly initialized for the embedded server, causing several tests in the jp test suite to fail. (Bug#45159)

Concurrent execution of statements requiring a table-level lock and statements requiring a non-table-level write lock for a table could deadlock. (Bug#45143)

Joins involving BLOB columns caused crashes when using the Batched Key Access method. (Bug#45092)

Killing a delayed-insert thread could cause a server crash. (Bug#45067)

Execution of FLUSH TABLES or FLUSH TABLES WITH READ LOCK concurrently with LOCK TABLES resulted in deadlock. (Bug#45066)

It was possible for init_available_charsets() not to initialize correctly. (Bug#45058)

If a session had a table locked with LOCK TABLES for both READ and WRITE, ALTER TABLE could fail. (Bug#45035)

GROUP BY on a constant (single-row) InnoDB table joined to other tables caused a server crash. (Bug#44886)

The BACKUP DATABASE statement could fail even if the user had all privileges for backed-up objects. The RESTORE statement could fail in the middle if the user did not have sufficient privileges to access all objects in the backup image. To deal with such problems, the privileges required for backup and restore operations are established to be as follows:

To deal with such problems, the privileges required for backup and restore operations are established to be as follows: For BACKUP DATABASE, the user must have the BACKUP privilege for each database to back up. For RESTORE, the user must have the RESTORE privilege for each database in the backup image. In addition, internal privilege elevation is used to enable backup and restore to to succeed even if the user does not otherwise have privileges to access the objects in the image. Privilege elevation is controlled by three new system variables:

(Bug#44787, Bug#46569)

The have_community_features system variable was renamed to have_profiling.

Previously, to enable profiling, it was necessary to run configure with the --enable-community-features and --enable-profiling options. Now only --enable-profiling is needed. (Bug#44651)

InnoDB took a shared row lock when executing SELECT statements inside a stored function as a part of a transaction using REPEATABLE READ. This prevented other transactions from updating the row. (Bug#44613)

With InnoDB Plugin, renaming a table column and then creating an index on the renamed column caused a server crash to the .frm file and the InnoDB data directory going out of sync. Now InnoDB Plugin 1.0.5 returns an error instead: ERROR 1034 (HY000): Incorrect key file for table 'tbl_name'; try to repair it. To work around the problem, create another table with the same structure and copy the original table to it. (Bug#44571)

BACKUP DATABASE was too conservative about blocking for current transactions before beginning to back up, and was sometimes blocking when it did not need to. (Bug#44568)

For debug builds, executing a stored procedure as a prepared statement could sometimes cause an assertion failure. (Bug#44521)

Using mysql_stmt_execute() to call a stored procedure could cause a server crash. (Bug#44495)

InnoDB did not always disallow creating tables containing columns with names that match the names of internal columns, such as DB_ROW_ID, DB_TRX_ID, DB_ROLL_PTR, and DB_MIX_ID. (Bug#44369)

An InnoDB error message incorrectly referred to the nonexistent innodb_max_files_open variable rather than to innodb_open_files. (Bug#44338)

Improper materialization of semijoin inner tables could cause an assertion failure. (Bug#44303)

SELECT ... WHERE ... IN (NULL, ...) was executed using a full table scan, even if the same query without the NULL used an efficient range scan. (Bug#44139)

See also Bug#18360.

For a VARCHAR(N) column, ORDER BY BINARY(col_name) sorted using only the first N bytes of the column, even though column values could be longer than N bytes if they contained multibyte characters. (Bug#44131)

Selecting from the process list in the embedded server caused a crash. (Bug#43733)

See also Bug#47304.

When used in conjunction with LOCK TABLES, FLUSH TABLE tbl_list waited for all tables with old versions to clear from the table definition list, rather than only the named tables. (Bug#43685)

For YEAR(2) values, MIN(), MAX(), and comparisons could yield incorrect results. (Bug#43668)

Queries for MyISAM tables that were processed using index condition pushdown could return incorrect results. (Bug#43618)

Attempts to enable large_pages with a shared memory segment larger than 4GB caused a server crash. (Bug#43606)

Queries executed using index condition pushdown could return incorrect results because the condition could evaluate to an unexpected result. (Bug#43600)

On systems with case-insensitive file systems or with lower_case_table_names=1, RESTORE did not detect collisions between object names that differed only in lowercase and could not be restored. Now it checks the backup image before deleting any objects for such collisions and terminates the restore operation with an error. (Bug#43596)

For ALTER TABLE, renaming a DATETIME or TIMESTAMP column unnecessarily caused a table copy operation. (Bug#43508)

MySQL Backup sometimes crashed when selecting information from INFORMATION_SCHEMA. (Bug#43357)

HANDLER statements are now disallowed if a table lock has been acquired with LOCK TABLES. (Bug#43272)

The weekday names for the Romanian lc_time_names locale 'ro_RO' were incorrect. Thanks to Andrei Boros for the patch to fix this bug. (Bug#43207)

In the embedded server, stack overflow checks for recursive stored procedure calls did not work and stack overflow could occur. (Bug#43201)

XA START could cause an assertion failure or server crash when it is called after a unilateral rollback issued by the Resource Manager (both in a regular transaction and after an XA transaction). (Bug#43171)

Redefining a trigger could cause an assertion failure. (Bug#43054)

The FORCE INDEX FOR ORDER BY index hint was ignored when join buffering was used. (Bug#43029)

The NUM_FLAG bit of the MYSQL_FIELD.flags member now is set for columns of type MYSQL_TYPE_NEWDECIMAL. (Bug#42980)

RESTORE locking did not always prevent other sessions from modifying tables. (Bug#42895)

The server could crash if an attempt to open a MERGE table child MyISAM table failed. (Bug#42862)

Incorrect handling of range predicates combined with OR operators could yield incorrect results. (Bug#42846)

Failure to treat BIT values as unsigned could lead to unpredictable results. (Bug#42803)

Comparison with NULL values sometimes did not produce a correct result. (Bug#42760)

Use of semijoin optimization could cause a server crash. Thanks to Sergey Petrunya for the patch to fix this bug. (Bug#42742)

With index condition pushdown enabled, InnoDB mishandled the <=> operator. (Bug#42580)

Due to work done for Bug#989, FLUSH TABLES is disallowed when there is an active LOCK TABLES ... READ. This caused a problem with mysqlhotcopy, which used that sequence of statements. mysqlhotcopy now uses FLUSH TABLES tbl_list WITH READ LOCK to flush and lock tables. If mysqlhotcopy is used with a server older than MySQL 5.5.3 that does not support this statement, it has a new option --old_server that causes it to use the previous statement sequence. (Bug#42465)

For the embedded server on Windows, InnoDB crashed when innodb_file_per_table was enabled and a table name was in full path format. (Bug#42383)

Using an initial command with mysql_options(..., MYSQL_INIT_COMMAND, ...) that generated multiple result sets (such as a stored procedure or a multi-statement command) left the connection unusable. (Bug#42373)

SHOW ERRORS returned an empty result set after an attempt to drop a nonexistent table. (Bug#42364)

Some queries with nested outer joins could lead to crashes or incorrect results because an internal data structure was handled improperly. (Bug#42116)

The server used the wrong lock type (always TL_READ instead of TL_READ_NO_INSERT when appropriate) for tables used in subqueries of UPDATE statements. This led in some cases to replication failure because statements were written in the wrong order to the binary log. (Bug#42108)

An assertion failure could occur if OPTIMIZE TABLE was started on an InnoDB table and the table was altered to a different storage engine during the optimization operation. (Bug#42074)

On Windows, BACKUP DATABASE to a named pipe did not work. (Bug#41843)

Purging the stored routine cache could take a long time and render the server unresponsive. (Bug#41804)

For a query that selected from a view and used an alias for the view, the metadata used the alias name rather than the view name in the MYSQL_FIELD.table member. (Bug#41788)

In a replication scenario with innodb_locks_unsafe_for_binlog enabled on the slave, where rows were changed only on the slave (not through replication), in some rare cases, many messages of the following form were written to the slave error log: InnoDB: Error: unlock row could not find a 4 mode lock on the record. (Bug#41756)

The server could crash when attempting to access a non-conformant mysql.proc system table. For example, the server could crash when invoking stored procedure-related statements after an upgrade from MySQL 5.0 to 5.1 without running mysql_upgrade. (Bug#41726)

Due to improper locking, another connection could insert rows into a table being restored, thus causing duplicate-key errors. The resulting error message was meaningless. (Bug#41716)

After renaming a user, granting that user privileges could result in the user having additional privileges other than those granted. (Bug#41597)

The mysql_upgrade command would create three additional fields to the mysql.proc table (character_set_client, collation_connection, and db_collation), but did not populate the fields with correct values. This would lead to error messages reported during stored procedure execution. (Bug#41569)

The mysql-stress-test.pl test script was missing from the noinstall packages on Windows. (Bug#41546)

With a nonstandard InnoDB page size, some error messages became inaccurate.

(Bug#41490)

Premature metadata lock downgrade for CREATE TABLE ... SELECT could result in an inconsistent binary log or failure with an ER_CANT_LOCK error. (Bug#41425)

On Windows, there was a linking failure for the object file for set_vars.cc in the embedded server. (Bug#41103)

mysql_upgrade did not create temporary files properly. (Bug#41057)

In some cases, the server did not recognize lettercase differences between GRANT attributes such as table name or user name. For example, a user was able to perform operations on a table with privileges of another user with the same user name but in a different lettercase.

In consequence of this bug fix, the collation for the Routine_name column of the mysql.proc table is changed from utf8_bin to utf8_general_ci. (Bug#41049)

See also Bug#48872.

It was possible for DROP TABLE of one MyISAM table to remove the data and index files of a different MyISAM table. (Bug#40980)

After a RESTORE operation that restored a compressed MyISAM table, the server crashed when the table was accessed. (Bug#40944)

Multiple-statement execution could fail. (Bug#40877)

If the arguments to a CONCAT() call included a local routine variable, selecting the return value into a user variable could produce an incorrect result. (Bug#40625)

SHOW CREATE VIEW returned invalid SQL if the definition contained a SELECT 'string' statement where the string was longer than the maximum length of a column name, due to the fact that this text was also used as an alias (in the AS clause).

Because not all names retrieved from arbitrary SELECT statements can be used as view column names due to length and format restrictions, the server now checks the conformity of automatically generated column names and rewrites according to a predefined format any names that are not acceptable as view column names before storing the final view definition on disk.

In such cases, the name is now rewritten as Name_exp_pos, where pos is the position of the column. To avoid this conversion scheme, define explicit, valid names for view columns using the column_list clause of the CREATE VIEW statement.

As part of this fix, aliases are now generated only for top-level statements. (Bug#40277)

CREATE TABLE failed if a column name in a FOREIGN KEY clause was given in a lettercase different from the corresponding index definition. (Bug#39932)

Plugin shutdown could lead to an assertion failure caused by using an already destroyed mutex in the metadata locking subsystem. (Bug#39674)

ALTER TABLE neglected to preserve ROW_FORMAT information from the original table, which could cause subsequent ALTER TABLE and OPTIMIZE TABLE statements to lose the row format for InnoDB tables. (Bug#39200)

BACKUP DATABASE could crash attempting to back up an invalid MERGE table. (Bug#39105)

When using UNINSTALL PLUGIN to remove a loaded plugin, open tables and connections caused mysqld to hang until the open connections had been closed. (Bug#39053)

flush_cache_records() did not correctly check for errors that should cause statement execution to stop, leading to a server crash. (Bug#39022)

Simultaneous ANALYZE TABLE operations for an InnoDB tables could be subject to a race condition. (Bug#38996)

InnoDB logged an error repeatedly trying to load a page into the buffer pool, filling the error log and using excessive disk space. Now the number of attempts is limited to 100, after which the operation aborts with a message. (Bug#38901)

Concurrent connections executing FLUSH TABLES and at least two statements using the same table could cause all three connections to stall with 100% CPU utilization. (Bug#38661)

An IPv6-enabled MySQL server did not resolve the IP addresses of incoming connections correctly, with the result that a connection that attempted to match any privilege table entries using fully-qualified domain names for hostnames or hostnames using wildcards were dropped. (Bug#38247)

See also Bug#43006, Bug#45283, Bug#45584, Bug#45606.

For certain SELECT statements using ref access, MySQL estimated an incorrect number of rows, which could lead to inefficient query plans. (Bug#38049)

When compressed MyISAM files were opened, they were always memory mapped, sometimes causing memory-swapping problems. To deal with this, a new system variable, myisam_mmap_size, was added to limit the amount of memory used for memory mapping of MyISAM files. (Bug#37408)

Concurrent execution of ALTER TABLE for InnoDB table and a transaction that tried to read and then update the table could result in a deadlock between table-level locks and InnoDB row locks, which was detected only after the innodb_lock_wait_timeout timeout occurred. (Bug#37346)

The MySQL client library mishandled EINPROGRESS errors for connections in nonblocking mode. This could lead to replication failures on hosts capable of resolving both IPv4 and IPv6 network addresses, when trying to resolve localhost. (Bug#37267)

See also Bug#44344.

With index condition pushdown enabled, InnoDB could crash due to a mismatch between what pushdown code expected to be in a record versus what was actually there. (Bug#36981)

mysql_install_db failed if run as root and the root directory (/) was not writable. (Bug#36462)

Reading from a temporary MERGE table, with two non-temporary child MyISAM tables, resulted in the error:

ERROR 1168 (HY000): Unable to open underlying table which is differently 
defined or of non-MyISAM type or doesn't exist

(Bug#36171)

Privileges for SHOW CREATE VIEW were not being checked correctly. (Bug#35996)

A race condition on the privilege hash tables allowed one thread to try to delete elements that had already been deleted by another thread. A consequence was that SET PASSWORD or FLUSH PRIVILEGES could cause a crash. (Bug#35589, Bug#35591)

Different invocations of CHECKSUM TABLE could return different results for a table containing columns with spatial data types. (Bug#35570)

When building MySQL when using a different target directory (for example using the VPATH environment variable), the build of the embedded readline component would fail. (Bug#35250)

The test for readline during configuration failed when trying to build MySQL in a directory other than the source tree root. (Bug#35250)

For its warning count, the mysql_info() C API function could print the number of truncated data items rather than the number of warnings. (Bug#34898)

Executing SHOW MASTER LOGS as a prepared statement without binary logging enabled caused a crash for debug builds. (Bug#34741)

If the --log-bin server option was set to a directory name with a trailing component separator character, the basename of the binary log files was empty so that the created files were named .000001 and .index. The same thing occurred with the --log-bin-index, --relay-log, and --relay-log-index options. Now the server reports and error and exits. (Bug#34739)

If a comparison involved a constant value that required type conversion, the converted value might not be cached, resulting in repeated conversion and poorer performance. (Bug#34384)

Compiling MySQL on FreeBSD would fail due to missing definitions for certain network constants. (Bug#34292)

A COMMENT longer than 64 characters caused CREATE PROCEDURE to fail. (Bug#34197)

The size of backup_history.backup_file was increased from 100 to 255 characters to reduce the chance of file name truncation when logging backup or restore operations. (Bug#34065)

1) In rare cases, if a thread was interrupted during a FLUSH PRIVILEGES operation, a debug assertion occurred later due to improper diagnostic area setup. 2) A KILL operation could cause a console error message referring to a diagnostic area state without first ensuring that the state existed. (Bug#33982)

INSERT INTO ... VALUES(DEFAULT) failed to insert the correct value for ENUM columns. For MyISAM tables, an empty value was inserted. For CSV tables, the table became corrupt. (Bug#33717)

When read_only was enabled, the server incorrectly prevented data modifications to TEMPORARY tables belonging to transactional storage engines such as InnoDB. (Bug#33669)

The LAST_DAY() and MAKEDATE() functions could return NULL, but the result metadata indicated NOT NULL. Thanks to Hiromichi Watari for the patch to fix this bug. (Bug#33629)

Constant expressions in WHERE, HAVING, or ON clauses were not cached, but were evaluated for each row. This caused a slowdown of query execution, especially if constant user-defined functions or stored functions were used. (Bug#33546)

RESTORE caused the default database to become NULL. (Bug#33354)

BACKUP DATABASE could enter a tight polling loop that used almost all processor time. (Bug#33019)

Using the SHOW ENGINE INNODB STATUS statement when using partitions in InnoDB tables caused Invalid (old?) table or database name errors to be logged. (Bug#32430)

A query on a FEDERATED table in which the data was ordered by a TEXT column returned incorrect results. For example, a query such as the following would result in incorrect results if column column1 was a TEXT column:

SELECT * FROM table1 ORDER BY column1;

(Bug#32426)

On Windows, mysqlslap crashed for attempts to connect via shared memory. (Bug#31173)

ALTER TABLE with both DROP COLUMN and ADD COLUMN clauses could crash or lock up the server. (Bug#31145)

Dropping a tablespace and specifying an engine type that does not support tablespaces reported a warning. The response has now been updated to report an error. (Bug#31110)

Concurrent statements using a stored function and DROP FUNCTION for that function could break statement-based replication. (Bug#30977)

MySQL Makefiles relied on GNU extensions. (Bug#30708)

For const tables that were optimized away EXPLAIN EXTENDED displayed them in the FROM clause. Now they are not displayed. If all tables are optimized away, FROM DUAL is displayed. (Bug#30302)

In mysql, using Control-C to kill the current query resulted in a ERROR 1053 (08S01): Server shutdown in progress" message if the query was waiting for a lock. (Bug#28141)

Output from mysql --html did not encode the <, >, or & characters. (Bug#27884)

The parser allocated too much memory for a query containing multiple statements. (Bug#27863)

When building MySQL on Windows from source, the WITH_BERKELEY_STORAGE_ENGINE option would fail to configure BDB support correctly. (Bug#27693)

If an operation had an InnoDB table, and two triggers, AFTER UPDATE and AFTER INSERT, competing for different resources (such as two distinct MyISAM tables), the triggers were unable to execute concurrently. In addition, INSERT and UPDATE statements for the InnoDB table were unable to run concurrently. (Bug#26141)

A statement that caused a circular wait among statements did not return a deadlock error. Now the server detects deadlock and returns ER_LOCK_DEADLOCK. (Bug#22876)

Under heavy load with a large query cache, invalidating part of the cache could cause the server to freeze (that is, to be unable to service other operations until the invalidation was complete). (Bug#21074)

See also Bug#39253.

If InnoDB reached its limit on the number of concurrent transactions (1023), it wrote a descriptive message to the error log but returned a misleading error message to the client, or an assertion failure occurred. (Bug#18828)

See also Bug#46672.

Referring to a stored function qualified with the name of one database and tables in another database caused a “table doesn't exist” error. (Bug#18444)

The character set was not being properly initialized for CAST() with a type such as CHAR(2) BINARY, which resulted in incorrect results or a server crash. (Bug#17903)

A Table ... doesn't exist error could occur for statements that called a function defined in another database. (Bug#17199)

Extraneous comparisons between NULL values in indexed columns were performed by the optimzer for operators such as = that are never true for NULL. (Bug#8877)

On some Windows systems, InnoDB could report Operating system error number 995 in a file operation due to transient driver or hardware problems. InnoDB now retries the operation and adds Retry attempt is made to the error message. (Bug#3139)

When using the EXAMPLE storage engine, when the engine had been built as a plugin (instead of built-in), and DTrace probes had been enabled during the build, loading the storage engine library would fail due to a missing object table entry.

Incompatible Change: MySQL Server now includes a plugin services interface that complements the plugin API. The services interface enables server functionality to be exposed as a “service” that plugins can access through a function-call interface. The libmysqlservices library provides access to the available services and dynamic plugins now must be linked against this library (use the -lmysqlservices flag). For an example showing what Makefile.am should look like, see Section 22.2.6, “MySQL Services for Plugins”. (Bug#48461)

The time zone tables for Windows available at http://dev.mysql.com/downloads/timezones.html have been updated. (Bug#39923)

The mysqltest program now has a move_file from_file to_file command for renaming files. This should be used in test cases rather than invoking an external command that might be platform specific. (Bug#39542)

Performance: If the character set for a column being compared was neither the default server character set nor latin1, InnoDB was slower than necessary due to excessive contention for a character set mutex.

As a workaround for earlier versions, set the default server character set to the character set other than latin1 that is most often used in indexed columns. (Bug#42649)

Important Change: Replication: The CHANGE MASTER TO statement required the value for RELAY_LOG_FILE to be an absolute path, while the MASTER_LOG_FILE path could be relative.

The inconsistent behavior is resolved by allowing relative paths for RELAY_LOG_FILE, and by using the same basename for RELAY_LOG_FILE as for MASTER_LOG_FILE. For more information, see Section 12.5.2.1, “CHANGE MASTER TO Syntax”. (Bug#12190)

Important Change: Replication: The transactional behavior of STOP SLAVE has changed. Formerly, it took effect immediately, even inside a transaction; now, it waits until the current replication event group (if any) has finished executing, or until the user issues a KILL QUERY or KILL CONNECTION statement.

This was done in order to solve the problem encountered when replication was stopped while a nontransactional slave was replicating a transaction on the master. (It was impossible to roll back a mixed-engines transaction when one of the engines was nontransactional, which meant that the slave could not safely re-apply any transaction that had been interrupted by STOP SLAVE.) (Bug#319, Bug#38205)

See also Bug#43217.

Important Change: An option that requires a value, when specified in an option file without a value, was assigned the text of the next line in the file as the value. Now, if you fail to specify a required value in an option file, the server aborts with an error.

This change does not effect how options are handled by the server when they are used on the command line. For example, starting the server using mysqld_safe --relay-log --relay-log-index & causes the server to create relay log files named --relay-log-index.000001, --relay-log-index.000002, and so on, because the --relay-log option expects an argument. (Bug#25192)

Partitioning: When a value was equal to a PARTITION ... VALUES LESS THAN (value) value other than MAXVALUE, the corresponding partition was not pruned. (Bug#42944)

Replication: Issuing the following statements, in the order shown, could cause a deadlock between the user thread and I/O thread:

START SLAVE;
STOP SLAVE SQL_THREAD;
START SLAVE;

(Bug#44312)

See also Bug#38715, Bug#38716.

Replication: Unrelated errors occurring during the execution of RESET SLAVE could cause the slave to crash. (Bug#44179)

Replication: When using semisynchronous replication:

(Bug#44058)

See also Bug#40935.

Replication: Replicating TEXT or VARCHAR columns declared as NULL on the master but NOT NULL on the slave caused the slave to crash. (Bug#43789)

See also Bug#38850, Bug#43783, Bug#43785, Bug#47741, Bug#48091.

Replication: Executing the sequence of statements RESET SLAVE, RESET MASTER, and FLUSH LOGS, when binary log or relay log files listed in the index file could not be found, could cause the server to crash. This could happen, for example, when these files had been moved or deleted manually. (Bug#41902)

Replication: MySQL creates binary logs in a numbered sequence, with a maximum possible 4294967295 concurrent log files, 4294967295 being the maximum value for an unsigned long integer. However, binary log file extensions were turned into negative numbers once the variable used to hold the value reached the maximum value for a signed long integer (2147483647). Consequently, when the sequence value was incremented to the next (negative) number, this caused MySQL to try to create the file using a .000000 extension, causing the server to fail since this file already existed.

Negative file extensions are now disallowed, and an error is returned when the limit is reached. In addition, FLUSH LOGS now also reports warnings to the user, if the extension number has reached the limit, and warnings are printed to the error log when the limit is approaching. (Bug#40611)

Replication: Updating a table having no primary key, using an unindexed CHAR column as the key, caused row-based replication to fail. (Bug#40045)

Replication: The --slave-skip-errors option had no effect when using row-based logging format. (Bug#39393)

Replication: Issuing concurrent STOP SLAVE, START SLAVE, and RESET SLAVE statements using different connections caused the replication slave to crash. (Bug#38716)

See also Bug#38715, Bug#44312.

Replication: The following errors were not correctly reported:

Information about these types of failures can now be found in the output of SHOW SLAVE STATUS. (Bug#38197)

Replication: Killing the thread executing a DDL statement, after it had finished its execution but before it had written the binlog event, caused the error code in the binlog event to be set (incorrectly) to ER_SERVER_SHUTDOWN or ER_QUERY_INTERRUPTED, which caused replication to fail. (Bug#37145)

See also Bug#27571, Bug#22725.

Replication: Column aliases used inside subqueries were ignored in the binary log. (Bug#35515)

For settings of lower_case_table_names greater than 0, some queries for INFORMATION_SCHEMA tables left entries with incorrect lettercase in the table definition cache. (Bug#44738)

Valgrind warnings for the DECODE(), ENCRYPT(), and FIND_IN_SET() functions were corrected. (Bug#44358, Bug#44365, Bug#44367)

On Windows, entries for build-vs9.bat and build-vs9_x64.bat were missing in win/Makefile.am. (Bug#44353)

Not all lock types had proper descriptive strings, resulting in garbage output from mysqladmin debug. (Bug#44164)

Use of HANDLER statements with INFORMATION_SCHEMA tables caused a server crash. Now HANDLER is prohibited with such tables. (Bug#44151)

On Windows, if the mysql client was reading input from a pipe, it could crash attempting to read after EOF. (Bug#44133)

MySQL Server allowed the creation of a merge table based on views but crashed when attempts were made to read from that table. The following example demonstrates this:

#Create a test table
CREATE TABLE tmp (id int, c char(2));                                           

#Create two VIEWs upon it
CREATE VIEW v1 AS SELECT * FROM tmp;                                            
CREATE VIEW v2 AS SELECT * FROM tmp;                                            

#Finally create a MERGE table upon the VIEWs
CREATE TABLE merge (id int, c char(2))
ENGINE=MERGE UNION(v1, v2);

#Reading from the merge table lead to a crash
SELECT * FROM merge;

The final line of the code generated the crash. (Bug#44040)

Some schema names longer than 8 characters were not supported by IBMDB2I. The engine has been updated to allow digits and underscore characters to be used in names longer than 8 characters. (Bug#44025)

In some circumstances, when a table is created with the IBMDB2I engine, the CREATE TABLE statement will return successfully but the table will not exist. (Bug#44022)

The ucs2_swedish_ci and utf8_swedish_ci collations did not work with indexes using the IBMDB2I storage engine. Support is now provided for MySQL when running on IBM i 6.1 or higher. (Bug#44020)

Invoking SHOW TABLE STATUS from within a stored procedure could cause a Packets out of order error. (Bug#43962)

myisamchk could display a negative Max keyfile length value. (Bug#43950)

On 64-bit systems, a key_buffer_size value larger than 4GB could couse MyISAM index corruption. (Bug#43932)

mysqld_multi incorrectly passed --no-defaults to mysqld_safe. (Bug#43876)

SHOW VARIABLES did not properly display the value of slave_skip_errors. (Bug#43835)

On Windows, a server crash occurred for attempts to insert a floating-point value into a CHAR column with a maximum length less than the converted floating-point value length. (Bug#43833)

Incorrect initialization of MyISAM table indexes could cause incorrect query results. (Bug#43737)

libmysqld crashed when it was reinitialized. (Bug#43706, Bug#44091)

UNION of floating-point numbers did unnecessary rounding. (Bug#43432)

ALTER DATABASE ... UPGRADE DATA DIRECTORY NAME failed when the database contained views. (Bug#43385)

Certain statements might open a table and then wait for an impending global read lock without noticing whether they hold a table being waiting for by the global read lock, causing a hang. Affected statements are SELECT ... FOR UPDATE, LOCK TABLES ... WRITE, TRUNCATE TABLE, and LOAD DATA INFILE. (Bug#43230)

Using an XML function such as ExtractValue() more than once in a single query could produce erroneous results. (Bug#43183)

See also Bug#43937.

DROP DATABASE did not clear the message list. (Bug#43012, Bug#43138)

Full-text prefix searches could hang the connection and cause 100% CPU consumption. (Bug#42907)

Comparison of TIME values could lose the sign of operands. (Bug#42664)

MAKETIME() could lose the sign of negative arguments. (Bug#42662)

SEC_TO_TIME() could lose the sign of negative arguments. (Bug#42661)

Incorrect elevation of warning messages to error messages for unsafe statements caused a server crash. (Bug#42640)

CHECK TABLE suggested use of REPAIR TABLE for corrupt tables for storage engines not supported by REPAIR TABLE. Now CHECK TABLE suggests that the user dump and reload the table. (Bug#42563)

A problem in plugin.h - plugins could be getting a definition of MYSQL_LEX_STRING which was different from the server expectations. It would cause affected plugins to crash. (Bug#42461)

The InnoDB btr_search_drop_page_hash_when_freed() function had a race condition. (Bug#42279)

There was a race condition when changing innodb_commit_concurrency at runtime from zero to nonzero or from nonzero to zero. Now this variable cannot be changed at runtime from zero to nonzero or vice versa. The value can still be changed from one nonzero value to another. (Bug#42101)

See also Bug#45749.

The state of a thread for the embedded server was always displayed as Writing to net, which is incorrect because there is no network connection for the embedded server. (Bug#41971)

The patch for Bug#10374 broke named-pipe and shared-memory connections on Windows. (Bug#41860)

Compressing a table with the myisampack utility caused the server to produce Valgrind warnings when it opened the table. (Bug#41541)

For a MyISAM table with DELAY_KEY_WRITE enabled, the index file could be corrupted without the table being marked as crashed if the server was killed. (Bug#41330)

Killing an INSERT ... SELECT statement for a MyISAM table could cause table corruption if the table had indexes. (Bug#40827)

mysqld_safe did not treat dashes and underscores as equivalent in option names. Thanks to Erik Ljungstrom for the patch to fix this bug. (Bug#40368)

If a transaction was implicitly committed by a START TRANSACTION or BEGIN statement, metadata locks held by the transaction incorrectly could be released before the commit actually occurred. (Bug#40188)

A multiple-table DELETE IGNORE statement involving a foreign key constraint caused an assertion failure. (Bug#40127)

Multiple-table UPDATE statements did not properly activate triggers. (Bug#39953)

The mysql_setpermission operation for removing database privileges removed global privileges instead. (Bug#39852)

A stored routine contain a C-style comment could not be dumped and reloaded. (Bug#39559)

In an UPDATE or DELETE via a secondary index, InnoDB did not store the cursor position. This made InnoDB crash in semi-consistent read while attempting to unlock a nonmatching record. (Bug#39320)

The functions listed in Section 11.13.4.2.3, “Creating Geometry Values Using MySQL-Specific Functions”, previously accepted WKB arguments and returned WKB values. They now accept WKB or geometry arguments and return geometry values.

The functions listed in Section 11.13.4.2.2, “Creating Geometry Values Using WKB Functions”, previously accepted WKB arguments and returned geometry values. They now accept WKB or geometry arguments and return geometry values. (Bug#38990)

On WIndows, running the server with myisam_use_mmap enabled caused MyISAM table corruption. (Bug#38848)

mysqlbinlog had a memory leak in its option-processing code. (Bug#38468)

Setting the general_log_file or slow_query_log_file system variable to a nonconstant expression caused the variable to become unset. (Bug#38124)

CHECK TABLE did not properly check whether MyISAM tables created by servers from MySQL 4.0 or older needed to be upgraded. This could cause problems upgrading to MySQL 5.1 or higher. (Bug#37631)

mysql_install_db failed if run as root and the root directory (/) was not writable. (Bug#36462)

An UPDATE statement that updated a column using the same DES_ENCRYPT() value for each row actually updated different rows with different values. (Bug#35087)

Inserting the result of CONCAT() invoked with a utf32 string and a number for arguments caused a server crash. (Bug#34021)

For shared-memory connections, the read and write methods did not properly handle asynchronous close events, which could lead to the client locking up waiting for a server response. For example, a call to mysql_real_query() would block forever on the client side if the executed statement was aborted on the server side. Thanks to Armin Schöffmann for the bug report and patch. (Bug#33899)

The default values for the general query log and slow query log file are documented to be based on the server host name and located in the data directory. However, they were in fact being based on the basename and location of the process ID (PID) file. The name and location defaults for the PID file are based on the server host name and data directory, so if it was not assigned a different name explicitly, its defaults were used and the general query log and slow query log file defaults were as documented. But if the PID file was assigned a value with the --pid-file option, the defaults for the general query log and slow query log file were incorrect. This has been rectified so that the defaults for all three files are based on the server host name and data directory.

A remaining problem is that the binary log and relay log .NNNNNN and .index basename defaults are based on the PID file basename, contrary to the documentation. This issue is to be addressed as Bug#45359. (Bug#33693)

The following statements generated an incorrect and confusing error message when used with ENGINE=MyISAM:

Such statements now fail with Error 1478, Table storage engine 'MyISAM' does not support the create option 'TABLESPACE or LOGFILE GROUP'. (Bug#31293)

myisamchk and myisampack were not being linked with the library that enabled support for * filename pattern expansion. (Bug#29248)

COMMIT did not delete savepoints if there were no changes in the transaction. (Bug#26288)

Several memory allocation functions were not being checked for out-of-memory return values. (Bug#25058)

Previously, the server handled character data types for a stored routine parameter, local routine variable created with DECLARE, or stored function return value as follows: If the CHARACTER SET attribute was present, the COLLATE attribute was not supported, so the character set's default collation was used. (This includes use of BINARY, which in this context specifies the binary collation of the character set.) If there was no CHARACTER SET attribute, the database character set and its default collation were used.

Now for character data types, if there is a CHARACTER SET attribute in the declaration, the specified character set and its default collation is used. If the COLLATE is also present, that collation is used rather than the default collation. If there is no CHARACTER SET attribute, the database character set and collation in effect at routine creation time are used. (The database character set and collation are given by the value of the character_set_database and collation_database system variables.) (Bug#24690)

Several data-modification statements were not being counted toward the MAX_UPDATES_PER_HOUR user resource limit. (Bug#21793)

Performance: The query cache now checks whether a SELECT statement begins with SQL_NO_CACHE to determine whether it can skip checking for the query result in the query cache. This is not supported when SQL_NO_CACHE occurs within a comment. (Bug#37416)

Incompatible Change: The optimizer_switch system variable controls optimizations that can be switched on and off. The syntax for flags in its value has changed from 'no_opt_name' to 'opt_name={on|off|default}'. For information about the new syntax, see Section 7.2.22, “Using optimizer_switch to Control the Optimizer”.

Replication: The global server variables sync_master_info and sync_relay_log_info are introduced for use on replication slaves to control synchronization of, respectively, the master.info and relay.info files.

In each case, setting the variable to a nonzero integer value N causes the slave to synchonize the corresponding file to disk after every N events. Setting its value to 0 allows the operating system to handle synchronization of the file instead.

The actions of these variables, when enabled, are analogous to how the sync_binlog variable works with regard to binary logs on a replication master.

These variables can also be set in my.cnf, or by using the server options --sync-master-info and --sync-relay-log-info respectively.

An additional system variable relay_log_recovery is also now available. When enabled, this variable causes a replication slave to discard relay log files obtained from the replication master following a crash.

This variable can also be set in my.cnf, or by using the --relay-log-recovery server option.

This fix improves and expands upon one made in MySQL 6.0.10 which introduced the sync_relay_log variable. For more information about all of the server system variables introduced by these fixes, see Section 16.1.3.3, “Replication Slave Options and Variables”. (Bug#31665, Bug#35542, Bug#40337)

mysql-test-run.pl now supports an --experimental=file_name option. It enables you to specify a file that contains a list of test cases that should be displayed with the [ exp-fail ] code rather than [ fail ] if they fail. (Bug#42888)

The deprecated mysql_fix_privilege_tables script has been removed. (Bug#42589)

The MD5 algorithm now uses the Xfree implementation. (Bug#42434)

The RESTORE statement now has a SKIP_GAP_EVENT option that causes the restore operation not to write the gap event to the binary log that causes any replication slaves to stop replication. This is useful when RESTORE is run on a master server and the backup image does not contain databases that are replicated to the slaves. (Bug#39780)

Previously, the --secure-file-priv option and secure_file_priv system variable, if set to a directory, limited BACKUP DATABASE and RESTORE operations to files in the given directory. Now the --secure-backup-file-priv option and secure_backup_file_priv system variable apply instead. (Bug#39581)

MySQL now implements the SQL standard SIGNAL and RESIGNAL statements. See Section 12.7.8, “SIGNAL and RESIGNAL”. (Bug#11661)

A new program, mysqlbackup, displays information from backups created with the BACKUP DATABASE statement.

Incompatible Change: For system variables that take values of ON or OFF, OF was accepted as a legal variable. Now system variables that take “enumeration” values must be assigned the full value. This affects some other variables that previously could be assigned using unambiguous prefixes of allowable values, such as tx_isolation. (Bug#34828)

Incompatible Change: If a data definition language (DDL) statement occurred for a table that was being used by another session in an active transaction, statements could be written to the binary log in the wrong order. For example, this could happen if DROP TABLE occurred for a table being used in a transaction. This is now prevented by deferring release of metadata locks on tables used within a transaction until the transaction ends.

This bug fix results in some incompatibilities with previous versions:

(Bug#989, Bug#39675)

Important Change: Replication: CHANGE MASTER TO ... MASTER_HOST=''—explicitly setting MASTER_HOST equal to an empty string—created a master.info file with an empty host field. This led to a The server is not configured as slave error when attempting to execute a START SLAVE statement. Now, if MASTER_HOST is set to an empty string, the CHANGE MASTER TO statement fails with an error. (Bug#28796)

Replication: Important Note: Binary logging with --binlog-format=ROW failed when a change to be logged included more than 251 columns. This issue was not known to occur with mixed-format or statement-based logging. (Bug#42977)

See also Bug#42914.

Replication: The SHOW SLAVE STATUS connection thread competed with the slave SQL thread for use of the error message buffer. As a result, the connection thread sometimes received incomplete messages. This issue was uncovered with valgrind when message strings were passed without NULL terminators, causing the error Conditional jump or move depends on uninitialised value(s). (Bug#43076)

Replication: This fix handles 2 issues encountered on replication slaves during startup:

(Bug#43075)

Replication: Assigning an invalid directory for the --slave-load-tmpdir caused the replication slave to crash. (Bug#42861)

Replication: The mysql.procs_priv system table was not replicated. (Bug#42217)

Replication: When binlog_format was set to STATEMENT, a statement unsafe for statement-based logging caused an error or warning to be issued even if sql_log_bin was set to 0. (Bug#41980)

Replication: An INSERT DELAYED into a TIMESTAMP column issued concurrently with an insert on the same column not using DELAYED, but applied after the other insert, was logged using the same timestamp as generated by the other (non-DELAYED) insert. (Bug#41719)

Replication: When using MIXED replication format and temporary tables were created in statement-based mode, but a later operation in the same session caused a switch to row-based mode, the temporary tables were not dropped on the slave at the end of the session. (Bug#40013)

See also Bug#43046.

This regression was introduced by Bug#20499.

Replication: When using the MIXED replication format, UPDATE and DELETE statements that searched for rows where part of the key had nullable BIT columns failed. This occurred because operations that inserted the data were replicated as statements, but UPDATE and DELETE statements affecting the same data were replicated using row-based format.

This issue did not occur when using statement-based replication (only) or row-based replication (only). (Bug#39753)

See also Bug#39648.

Replication: The MIXED binary logging format did not switch to row-based mode for statements containing the LOAD_FILE() function. (Bug#39701)

Replication: The server SQL mode in effect when a stored procedure was created was not retained in the binary log. This could cause a CREATE PROCEDURE statement that succeeded on the master to fail on the slave.

This issue was first noticed when a stored procedure was created when ANSI_QUOTES was in effect on the master, but could possibly cause failed CREATE PROCEDURE statements and other problems on the slave when using other server SQL modes as well. (Bug#39526)

Replication: If --secure-file-priv was set on the slave, it was unable to execute LOAD DATA INFILE statements sent from the master when using mixed-format or statement-based replication.

As a result of this fix, this security restriction is now ignored on the slave in such cases; instead the slave checks whether the files were created and should be read by the slave in its --slave-load-tmpdir. (Bug#38174)

Replication: When using row-based format, replication failed with the error Could not execute Write_rows event on table ...; Field '...' doesn't have a default value when an INSERT was made on the master without specifying a value for a column having no default, even if strict server SQL mode was not in use and the statement would otherwise have succeeded on the master. Now the SQL mode is checked, and the statement is replicated unless strict mode is in effect. For more information, see Section 5.1.7, “Server SQL Modes”. (Bug#38173)

See also Bug#38262, Bug#43992.

Replication: Server IDs greater than 2147483647 (2³² – 1) were represented by negative numbers in the binary log. (Bug#37313)

Replication: The value of Slave_IO_running in the output of SHOW SLAVE STATUS did not distinguish between all 3 possible states of the slave I/O thread (not running; running but not connected; connected). Now the value Connecting (rather than No) is shown when the slave I/O thread is running but the slave is not connected to a replication master.

The server system variable Slave_running also reflects this change, and is now consistent with what is shown for Slave_IO_running. (Bug#30703, Bug#41613, Bug#51089)

Replication: Queries which were written to the slow query log on the master were not written to the slow query log on the slave. (Bug#23300)

See also Bug#48632.

Replication: When the server SQL mode included IGNORE_SPACE, statement-based replication of LOAD DATA INFILE ... INTO tbl_name failed because the statement was read incorrectly from the binary log; a trailing space was omitted, causing the statement to fail with a syntax error when run on the slave. (Bug#22504)

See also Bug#43746.

Replication: When its disk becomes full, a replication slave may wait while writing the binary log, relay log or MyISAM tables, continuing after space has been made available. The error message provided in such cases was not clear about the frequency with which checking for free space is done (once every 60 seconds), and how long the server waits after space has been freed before continuing (also 60 seconds); this caused users to think that the server had hung.

These issues have been addressed by making the error message clearer, and dividing it into two separate messages:

(Bug#22082)

Memory corruption of join buffers could occur when using the Batched Key Access algorithm with incremental join buffers to execute join operations for a query over several tables that selects BLOB values. (Bug#44250)

The server could crash at startup when initializing plugins listed in the plugin table. (Bug#44137)

A RESTORE operation that restored a MyISAM table using the native MyISAM restore driver could cause the MyISAM key cache to be disabled. (Bug#44068)

In some cases, when the Batched Key Access algorithm is used with join_cache_level equal to 6, multi-join queries could return incorrect results. (Bug#44019)

valgrind would report errors for the StorageInterface, StorageHAndler and CmdGen portions of Falcon. (Bug#43995)

On 64-bit debug builds, code in safemalloc resulted in errors due to use of a 32-bit value for 64-bit allocations. (Bug#43885)

Incorrect string termination caused a Valgrind warning. (Bug#43884)

When performing a high number of concurrent index updates on a Falcon table, mysqld could crash due to an assertion. (Bug#43765)

An attempt by a user who did not have the SUPER privilege to kill a system thread could cause a server crash. (Bug#43748)

On Windows, incorrectly specified link dependencies in CMakeLists.txt resulted in link errors for mysql_embedded, mysqltest_embedded, and mysql_client_test_embedded. (Bug#43715)

make distcheck failed to properly handle subdirectories of storage/ndb. (Bug#43614)

Incorrect use of parser information could lead to acquisition of incorrect lock types. (Bug#43568)

Upgrading MySQL to 6.0.10 from 6.0.9 when using Falcon tables and the mysql_upgrade tool would cause mysqld to crash during start up. (Bug#43562)

Running a SELECT using a range query on FLOAT on a Maria table could return invalid result sets. (Bug#43552)

Running a SELECT using a range query on with <> or < with a negative values on a Maria table could return invalid result sets. (Bug#43530)

Running a SELECT on a multi-range query with a LIMIT clause on a Maria table could return invalid result sets. (Bug#43527)

Executing a LIMIT ... FOR UPDATE statement on a Falcon table when using transactions with concurrent threads could cause a crash because the record information cannot be accessed correctly. (Bug#43488)

When performing SELECT statements on a Falcon table using an indexed INTEGER column could return incorrect row matches. (Bug#43452)

RESTORE on a case-insensitive server failed if the backup image contained databases or tables with uppercase names. Now, RESTORE handles this case by converting the names to lowercase in the restore catalog, as long as there are no duplicate names after the conversion. (Bug#43363)

Use of USE INDEX hints could cause EXPLAIN EXTENDED to crash. (Bug#43354)

BACKUP DATABASE stored incorrect table counts in the backup image. (Bug#43324)

Assigning a value to the backupdir system variable resulted in Valgrind errors. (Bug#43303)

mysql crashed if a request for the current database name returned an empty result, such as after the client has executed a preceding SET sql_select_limit=0 statement. (Bug#43254)

SQL statements executed by BACKUP DATABASE and RESTORE were logged in the general query log. (Bug#43166)

If the value of the version_comment system variable was too long, the mysql client displayed a truncated startup message. (Bug#43153)

Compilation failures on Windows Vista using Visual Studio 2008 Professional were corrected. (Bug#43120)

Recovering a Falcon table from a failure when the table contains BLOB columns could cause an assertion failure. (Bug#43106)

On 32-bit Windows, mysqld could not use large buffers due to a 2GB user mode address limit. (Bug#43082)

mysqld would crash when using Falcon tables during shutdown if the server was running in embedded mode. (Bug#43048)

The MySQL Backup library had incorrect logic and error reporting for metadata saving. (Bug#42959)

Queries of the following form returned an empty result:

SELECT ... WHERE ... (col=col AND col=col) OR ... (false expression)

(Bug#42957)

A two-way join query with a GROUP BY or ORDER BY clause could produce incorrect results when rows of the first table are accessed by an index compatible with the GROUP BY or ORDER BY list while the second table is joined using the Batched Key Access algorithm. (Bug#42955)

The strings/CHARSET_INFO.txt file was not included in source distributions. (Bug#42937)

When running REPAIR on a crashed Falcon table can crash mysqld if pages have been incorrectly marked dirty, but not locked, during write. (Bug#42824)

stderr should be unbuffered, but when the server redirected stderr to a file, it became buffered. (Bug#42790)

The DATA_TYPE column of the INFORMATION_SCHEMA.COLUMNS table displayed the UNSIGNED attribute for floating-point data types. (The column should contain only the data type name.) (Bug#42758)

Recovery of Falcon tables while there were active transaction during the crash may fail to recover completely. (Bug#42743)

Use of semijoin optimization could cause a server crash. (Bug#42740)

When Falcon is populating the INFORMATION_SCHEMA.TABLESPACES table, an exception can be raised because required result set has been closed before the resultset has been completed. This can happen during a BACKUP DATABASE operation. (Bug#42725, Bug#42830)

Assigning a value to the backupdir system variable resulted in a memory leak. (Bug#42695)

Assigning an incorrect value to the backup_progress_log_file system variable resulted in Valgrind errors. (Bug#42685)

When performing SELECT queries on tables containing TIMESTAMP or DATETIME colums with indexes using a WHERE clause comparing the field value to NULL using the <= or <> operators, the wrong information would be returned. (Bug#42683, Bug#43623, Bug#43620, Bug#42681)

A dangling pointer in mysys/my_error.c could lead to client crashes. (Bug#42675)

mysqldump included views that were excluded with the --ignore-table option. (Bug#42635)

An earlier bug fix resulted in the problem that the InnoDB plugin could not be used with a server that was compiled with the built-in InnoDB. To handle this two changes were made:

(Bug#42610)

This regression was introduced by Bug#29263.

With the ONLY_FULL_GROUP_BY SQL mode enabled, some legal queries failed. (Bug#42567)

Recovery of a Falcon table with a large number of rows can cause a failure in the page type written for the internal FALCON_USER and FALCON_TEMPORARY tablespaces. (Bug#42560)

Passing an unknown time zone specification to CONVERT_TZ() resulted in a memory leak. (Bug#42502)

Tables could enter open table cache for a thread without being properly cleaned up, leading to a server crash. (Bug#42419)

Previously, RESTORE would crash if the backup image contained tables originally stored in a tablespace that no longer existed at RESTORE time. Now the tablespace is recreated like it was at BACKUP DATABASE time if it does not exist when RESTORE is executed. (Bug#42402)

The MySQL Instance Configuration Wizard would fail to start correctly on Windows Vista. (Bug#42386)

If the server was started with --thread_handling=pool-of-threads, the MAX_QUERIES_PER_HOUR user resource limit. (Bug#42384)

Recovery of Falcon tables with indexes can fail because the index page information has not been recorded properly. (Bug#42344)

Using a LIKE clause on a Maria table using an index and the CP1251 collation would return invalid data. (Bug#42299)

Running a SELECT using a JOIN on a Maria table could return invalid result sets. (Bug#42298)

Running multi-range queries on Maria tables could cause a crash. (Bug#42297)

Using a falcon-scavenge-schedule of * * * * * would cause Falcon to never execute the required threads to operate. (Bug#42275)

If the server was started with an option that had a missing or invalid value, a subsequent error that would cause normally the server to shut down could cause it to crash instead. (Bug#42244)

Using ORDER BY and or LIMIT on Falcon tables could give inconsistent results for rows that contain NULL columns in the corresponding ORDER BY clause. (Bug#42208)

For InnoDB tables, there was a race condition for ALTER TABLE, OPTIMIZE TABLE, CREATE INDEX, and DROP INDEX operations when periodically checking whether table copying can be committed. (Bug#42152)

In InnoDB recovery after a server crash, table lookup could fail and corrupt the data dictionary cache. (Bug#42075)

mysqldumpslow parsed the --debug and --verbose options incorrectly. (Bug#42027)

BACKUP DATABASE and RESTORE did not implement backup and restore of privileges for stored procedures and stored functions. (Bug#41979)

On Mac OS X, some of the universal client libraries were not actually universal and were missing code for one or more architectures. (Bug#41940)

Recovering a Falcon table that uses BLOB columns could cause unbounded tablespace growth before recovery completes. (Bug#41840)

Recovery of Falcon tables could fail with an indicating that a wrong page type was identified in the Falcon serial log. (Bug#41837, Bug#42745, Bug#44114)

RESTORE crashed for Falcon tables. (Bug#41722)

With more than two arguments, LEAST(), GREATEST(), and CASE could unnecessarily return Illegal mix of collations errors. (Bug#41627)

Queries that used the loose index scan access method could return no rows. (Bug#41610)

RESTORE failed if it tried to restore a privilege for a nonexistent object. (Bug#41578)

In InnoDB recovery after a server crash, rollback of a transaction that updated a column from NULL to NULL could cause another crash. (Bug#41571)

The mysql client could misinterpret its input if a line was longer than an internal buffer. (Bug#41486)

The error message for a too-long column comment was Unknown error rather than a more appropriate message. (Bug#41465)

The Falcon CycleManager has been updated, which addresses a number of issues when examining records in various transaction states and their visisbility/isolation in relation to other threads. (Bug#41391, Bug#41478, Bug#41742, Bug#41850, Bug#42459, Bug#41661, Bug#42185, Bug#43146, Bug#43298, Bug#43299, Bug#34624, Bug#42189)

Use of SELECT * allowed users with rights to only some columns of a view to access all columns. (Bug#41354)

If the tables underlying a MERGE table had a primary key but the MERGE table itself did not, inserting a duplicate row into the MERGE table caused a server crash. (Bug#41305)

In the help command output displayed by mysql, the description for the \c (clear) command was misleading. (Bug#41268)

Several resource leaks were corrected in the error-handling code for the MySQL Backup library. (Bug#41250, Bug#41294)

The server did not robustly handle problems hang if a table opened with HANDLER needed to be re-opened because it had been altered to use a different storage engine that does not support HANDLER. The server also failed to set an error if the re-open attempt failed. These problems could cause the server to crash or hang. (Bug#41110, Bug#41112)

SELECT statements executed concurrently with INSERT statements for a MyISAM table could cause incorrect results to be returned from the query cache. (Bug#41098)

For prepared statements, multibyte character sets were not taking into account when calculating max_length for string values and mysql_stmt_fetch() could return truncated strings. (Bug#41078)

For user-defined variables in a query result, incorrect length values were returned in the result metadata. (Bug#41030)

Using RESTORE to restore a database through a named pipe resulted in corrupt data. (Bug#40975)

Performing SELECT operations on Falcon tables using the maximum BIG INT value would fail to return matching rows. (Bug#40950)

For some queries, an equality propagation problem could cause a = b and b = a to be handled differently. (Bug#40925)

With strict SQL mode enabled, setting a system variable to an out-of-bounds value caused an assertion failure. (Bug#40657)

Table temporary scans were slower than necessary due to use of mmap rather than caching, even with the myisam_use_mmap system variable disabled. (Bug#40634)

Indexes on Falcon tables using numeric columns could return incorrect information. (Bug#40607, Bug#41582, Bug#40950)

The load_defaults(), my_search_option_files() and my_print_default_files() functions in the C client library were subject to a race condition in multi-threaded operation. (Bug#40552)

For a view that references a table in another database, mysqldump wrote the view name qualified with the current database name. This makes it impossible to reload the dump file into a different database. (Bug#40345)

On platforms where long and pointer variables have different sizes, MyISAM could copy key statistics incorrectly, resulting in a server crash or incorrect cardinality values. (Bug#40321)

Falcon could cause an assertion when the system has run out of memory and tries to report the memory allocation failure. (Bug#40155)

The backup logs became unusable if a BACKUP DATABASE operation was interrupted. (Bug#39924)

DELETE tried to acquire write (not read) locks for tables accessed within a subquery of the WHERE clause. (Bug#39843)

mysql_upgrade did not remove the online_backup and online_backup_progress tables from the mysql database. (These are what the backup_history and backup_progress tables were called previously.) (Bug#39655)

With row-based binary logging, replication of InnoDB tables containing NULL-valued BIT columns could fail. (Bug#39648)

When using Falcon and the system runs out of all memory and swap space, mysqld could hang while attempting to write an error message. (Bug#39552)

The mysql_stmt_close() C API function did not flush all pending data associated with the prepared statement. (Bug#39519)

Updating Falcon tables after an online ALTER ADD COLUMN operation could fail. (Bug#39445)

Following ALTER TABLE ... DISCARD TABLESPACE for an InnoDB table, an attempt to determine the free space for the table before the ALTER TABLE operation had completely finished could cause a server crash. (Bug#39438)

perror did not produce correct output for error codes 153 to 163. (Bug#39370)

If --basedir was specified, mysqld_safe did not use it when attempting to locate my_print_defaults. (Bug#39326)

Several functions in libmysqld called exit() when an error occurred rather than returning an error to the caller. (Bug#39289)

Performing an online ALTER TABLE statement against a Falcon table, the Falcon serial log could grow beyond the maximum permitted size for a serial log, ignoring both the rotation and truncation. (Bug#39130)

Previously, the num_objects column in the backup_history table showed only the number of tables in the backup image. It now shows the number of objects with names (tablespaces, databases, tables, views, stored programs). (Bug#39109)

BACKUP DATABASE treated the database list in case-sensitive fashion, even on case-insensitive file systems. (Bug#39063)

When running the MySQL Instance Configuration Wizard in command-line only mode, the service name would be ignored (effectively creating all instances with the default MySQL service name), irrespective of the name specified on the command line. However, the wizard would attempt to start the service with the specified name, and would fail. (Bug#38379)

The ALTER ROUTINE privilege incorrectly allowed SHOW CREATE TABLE. (Bug#38347)

BACKUP DATABASE crashed if there was no default database. (Bug#38294)

Setting a savepoint with the same name as an existing savepoint incorrectly deleted any other savepoints that had been set in the meantime. For example, setting savepoints named a, b, c, b resulted in savepoints a, b, rather than the correct savepoints a, c, b. (Bug#38187)

Locking of myisam.log did not work correctly on Windows. (Bug#38133, Bug#41224)

--help output for myisamchk did not list the --HELP option. (Bug#38103)

Setting the session value of the debug system variable also set the global value. (Bug#38054)

Comparisons between row constructors, such as (a, b) = (c, d) resulted in unnecessary Illegal mix of collations errors for string columns. (Bug#37601)

A workload consisting of CREATE TABLE ... SELECT and DML operations could cause deadlock. (Bug#37433)

If a user created a view that referenced tables for which the user had disjoint privileges, an assertion failure occurred. (Bug#37191)

Trying to recover Falcon tables after a crash when the corresponding tables and tablespaces have not been created before the crash could cause a recovery failure. (Bug#36993)

When MySQL was configured with the --with-max-indexes=128 option, mysqld crashed. (Bug#36751)

The event, general_log, and slow_log tables in the mysql database store server_id values, but did not use an UNSIGNED column and thus were not able to store the full range of ID values. (Bug#36540)

Setting the join_buffer_size variable to its minimum value produced spurious warnings. (Bug#36446)

The audit plugin was not receiving MYSQL_AUDIT_GENERAL_ERROR events. (Bug#36098)

The use of NAME_CONST() can result in a problem for CREATE TABLE ... SELECT statements when the source column expressions refer to local variables. Converting these references to NAME_CONST() expressions can result in column names that are different on the master and slave servers, or names that are too long to be legal column identifiers. A workaround is to supply aliases for columns that refer to local variables.

Now a warning is issued in such cases that indicate possible problems. (Bug#35383)

SHOW CREATE EVENT output did not include the DEFINER clause. (Bug#35297)

mysqld would crash in a concurrent workload with INSERT/CREATE TABLE/DROP TABLE or INSERT/ALTER TABLE combinations on Falcon tables. (Bug#35255)

It was not possible to interrupt a long running BACKUP DATABASE or RESTORE operation. (Bug#35079)

Several deprecated or obsolete settings were removed from the sample option files. (Bug#34521)

Searching for 0x00 in Falcon tables using the VARBINARY column type would fail to return the correct rows. In addition, a crash could be encountered when modifying a column to the VARBINARY type. (Bug#34478, Bug#33190, Bug#23692)

A subquery using SELECT ... FOR UPDATE on a Falcon table fails to lock table correctly during the UPDATE. (Bug#34182)

With Falcon tables running concurrent transactions, some transactions may not be rolled back correctly, leading to an infinite loop. (Bug#34174)

INSTALL PLUGIN and UNINSTALL PLUGIN did not handle plugin identifiers consistently with respect to lettercase. (Bug#33731)

RESTORE often would not correctly identify the tablespace into which a Falcon table should be restored. (Bug#33569)

mysqldump --compatible=mysql40 emitted statements referring to the character_set_client system variable, which is unknown before MySQL 4.1. Now the statements are enclosed in version-specific comments. (Bug#33550)

If Falcon runs out of memory while inserting records and you try to alter the affected table, you may get a record memory is exhausted error, and the table can no longer be used or accessed. (Bug#33177)

The DDL blocker for BACKUP DATABASE and RESTORE did not block all statements that it should. The blocker is now called the Backup Metadata Lock and blocks statements that change database metadata. (Bug#32702)

Detection by configure of several functions such as setsockopt(), bind(), sched_yield(), and gtty() could fail. (Bug#31506)

Use of MBR spatial functions such as MBRTouches() with columns of InnoDB tables caused a server crash rather than an error. (Bug#31435)

When an InnoDB tablespace filled up, an error was logged to the client, but not to the error log. Also, the error message was misleading and did not indicate the real source of the problem. (Bug#31183)

The mysql client mishandled input parsing if a delimiter command was not first on the line. (Bug#31060)

SHOW PRIVILEGES listed the CREATE ROUTINE privilege as having a context of Functions,Procedures, but it is a database-level privilege. (Bug#30305)

CHECK TABLE, REPAIR TABLE, ANALYZE TABLE, and OPTIMIZE TABLE erroneously reported a table to be corrupt if the table did not exist or the statement was terminated with KILL. (Bug#29458)

For InnoDB tables that have their own .ibd tablespace file, a superfluous ibuf cursor restoration fails! message could be written to the error log. This warning has been suppressed. (Bug#27276)

Internal base64_xxx() functions were renamed to have a prefix of my_ to avoid conflicts with other libraries. (Bug#26818)

The Time column for SHOW PROCESSLIST output and the value of the TIME column of the INFORMATION_SCHEMA.PROCESSLIST table now can have negative values. Previously, the column was unsigned and negative values were displayed incorrectly as large positive values. Negative values can occur if a thread alters the time into the future with SET TIMESTAMP = value or the thread is executing on a slave and processing events from a master that has its clock set ahead of the slave. (Bug#22047)

Restoring a mysqldump dump file containing FEDERATED tables failed because the file contained the data for the table. Now only the table definition is dumped (because the data is located elsewhere). (Bug#21360)

SHOW CREATE DATABASE did not account for the value of the lower_case_table_names system variable. (Bug#21317)

Incorrect length metadata could be returned for LONG TEXT columns when a multibyte server character set was used. (Bug#19829)

ROUND() sometimes returned different results on different platforms. (Bug#15936)

Important Change: Replication: RESET MASTER and RESET SLAVE now reset the values shown for Last_IO_Error, Last_IO_Errno, Last_SQL_Error, and Last_SQL_Errno in the output of SHOW SLAVE STATUS. (Bug#34654)

See also Bug#44270.

Replication: A new global server variable sync_relay_log is introduced for use on replication slaves. Setting this variable to a nonzero integer value N causes the slave to synchonize the relay log to disk after every N events. Setting its value to 0 allows the operating system to handle synchronization of the file. The action of this variable, when enabled, is analogous to how the sync_binlog variable works with regard to binary logs on a replication master.

This variable can also be set in my.cnf, or by using the server option --sync-relay-log.

For more information, see Section 16.1.3.3, “Replication Slave Options and Variables”. (Bug#31665, Bug#35542, Bug#40337)

Replication: In circular replication, it was sometimes possible for an event to propagate such that it would be reapplied on all servers. This could occur when the originating server was removed from the replication circle and so could no longer act as the terminator of its own events, as normally happens in circular replication.

In order to prevent this from occurring, a new IGNORE_SERVER_IDS option is introduced for the CHANGE MASTER TO statement. This option takes a list of replication server IDs; events having a server ID which appears in this list are ignored and not applied. For more information, see Section 12.5.2.1, “CHANGE MASTER TO Syntax”.

In conjunction with the introduction of IGNORE_SERVER_IDS, SHOW SLAVE STATUS has two new fields. Replicate_Ignore_Server_Ids displays information about ignored servers. Master_Server_Id displays the server_id value from the master. (Bug#25998)

See also Bug#27808.

The libedit library was upgraded to version 2.11. (Bug#42433)

A new status variable, Queries, indicates the number of statements executed by the server. This includes statements executed within stored programs, unlike the Questions variable which includes only statements sent to the server by clients. (Bug#41131)

Columns that provide a catalog value in INFORMATION_SCHEMA tables (for example, TABLES.TABLE_CATALOG) now have a value of def rather than NULL. (Bug#35427)

mysql-test-run.pl now supports --client-bindir and --client-libdir options for specifying the directory where client binaries and libraries are located. (Bug#34995)

Performance: For an InnoDB table, DROP TABLE or ALTER TABLE ... DISCARD TABLESPACE could take a long time or cause a server crash. (Bug#39939)

Security Fix: Using an XPath expression employing a scalar expression as a FilterExpr with ExtractValue() or UpdateXML() caused the server to crash. Such expressions now cause an error instead. (Bug#42495)

Incompatible Change: The fix for Bug#33699 introduced a change to the UPDATE statement such that assigning NULL to a NOT NULL column caused an error even when strict SQL mode was not enabled. The original behavior before was that such assignments caused an error only in strict SQL mode, and otherwise set the column to the implicit default value for the column data type and generated a warning. (For information about implicit default values, see Section 10.1.4, “Data Type Default Values”.)

The change caused compatibility problems for applications that relied on the original behavior. It also caused replication problems between servers that had the original behavior and those that did not, for applications that assigned NULL to NOT NULL columns in UPDATE statements without strict SQL mode enabled. This change has been reverted so that UPDATE again had the original behavior. Problems can still occur if you replicate between servers that have the modified UPDATE behavior and those that do not. (Bug#39265)

Incompatible Change: Falcon supported case-sensitive tablespace names. The code has been changed so that all tablespace names are converted to uppercase names during creation. Because of this change:

(Bug#35257, Bug#33719)

Important Change: Replication: If a trigger was defined on an InnoDB table and this trigger updated a nontransactional table, changes performed on the InnoDB table were replicated and were visible on the slave before they were committed on the master, and were not rolled back on the slave after a successful rollback of those changes on the master.

As a result of the fix for this issue, the semantics of mixing nontransactional and transactional tables in a transaction have changed. Previously, if the initial statements in a transaction contained nontransactional changes, those statements were written directly to the binary log. Now, any statement appearing after a BEGIN (or immediately following a COMMIT if autocommit = 0) is always considered part of the transaction and cached. This means that nontransactional changes do not propagate to the slave until the transaction is committed and thus written to the binary log.

See Section 16.4.1.26, “Replication and Transactions”, for more information about this change in behavior. (Bug#40116)

Important Change: Replication: MyISAM transactions replicated to a transactional slave left the slave in an unstable condition. This was due to the fact that, when replicating from a nontransactional storage engine to a transactional engine with autocommit turned off, no BEGIN and COMMIT statements were written to the binary log; thus, on the slave, a never-ending transaction was started.

The fix for this issue includes enforcing autocommit mode on the slave by replicating all autocommit=1 statements from the master. (Bug#29288)

Important Change: When using the MySQL Instance Configuration Wizard with a configuration where you already have an existing installation with a custom datadir, the wizard could reset the data to the default data directory. When performing an upgrade installation in this situation, you must re-specify your custom settings, including the datadir, to ensure that your configuration file is not reset to the default values. (Bug#37534)

Important Change: Uninstalling MySQL using the MySQL installer on Windows would delete the my.ini file. The file is no longer deleted. In addition, when a new installation is conducted, any existing cofiguration file will be renamed to myDATETIME.ini.bak during configuration. (Bug#36493)

Important Change: When installing MySQL on Windows, it was possible to install multiple editions (Complete, and Essential, for example) of the same version of MySQL, leading to two separate entries in the installed packages which were impossible to isolate. This could lead to problems with installation and uninstallation. The MySQL installer on Windows no longers allow multiple installations of the same version of MySQL on a single machine. (Bug#4217)

Partitioning: A comparison with an invalid DATE value in a query against a partitioned table could lead to a crash of the MySQL server.

(Bug#40972)

Partitioning: A query that timed out when run against a partitioned table failed silently, without providing any warnings or errors, rather than returning Lock wait timeout exceeded. (Bug#40515)

Partitioning: ALTER TABLE ... REORGANIZE PARTITION could crash the server when the number of partitions was not changed. (Bug#40389)

See also Bug#41945.

Partitioning: ALTER TABLE ... ADD PARTITION and ALTER TABLE ... DROP PARTITION could cause the MySQL server to crash. This was only known to occur on Windows platforms where MySQL had been built with the EXTRA_DEBUG option. (Bug#38784)

Partitioning: SHOW TABLE STATUS could show a nonzero value for the Mean record length of a partitioned InnoDB table, even if the table contained no rows. (Bug#36312)

Partitioning: Several error messages relating to partitioned tables were incorrect or missing. (Bug#36001)

Partitioning: Unnecessary calls were made in the server code for performing bulk inserts on partitions for which no inserts needed to be made. (Bug#35845)

See also Bug#35843.

Partitioning: For partitioned tables with more than ten partitions, a full table scan was used in some cases when only a subset of the partitions were needed. (Bug#33730)

Replication: On Windows, RESET MASTER failed in the event of a missing binlog file rather than issuing a warning and completing the rest of the statement. (Bug#42150, Bug#42218)

Replication: Per-table AUTO_INCREMENT option values were not replicated correctly for InnoDB tables. (Bug#41986)

Replication: Some log_event types did not skip the post-header when reading. (Bug#41961)

Replication: Attempting to read a binary log containing an Incident_log_event having an invalid incident number could cause the debug server to crash. (Bug#40482)

Replication: When CHANGE MASTER TO ... SET MASTER_HEARTBEAT_PERIOD ... failed, no error code was set. (Bug#40459)

Replication: When using row-based replication, an update of a primary key that was rolled back on the master due to a duplicate key error was not rolled back on the slave. (Bug#40221)

Replication: When rotating relay log files, the slave deletes relay log files and then edits the relay log index file. Formerly, if the slave shut down unexpectedly between these two events, the relay log index file could then reference relay logs that no longer existed. Depending on the circumstances, this could when restarting the slave cause either a race condition or the failure of replication. (Bug#38826, Bug#39325)

Replication: START SLAVE UNTIL did not work correctly with --replicate-same-server-id enabled; when started with this option, the slave did not perform events recorded in the relay log and that originated from a different master.

Log rotation events are automatically generated and written when rotating the binary log or relay log. Such events for relay logs are usually ignored by the slave SQL thread because they have the same server ID as that of the slave. However, when --replicate-same-server-id was enabled, the rotation event for the relay log was treated as if it originated on the master, because the log's name and position were incorrectly updated. This caused the MASTER_POS_WAIT() function always to return NULL and thus to fail. (Bug#38734, Bug#38934)

Replication: A slave compiled using --with-libevent and run with --thread-handling=pool-of-threads could sometimes crash. (Bug#36929)

Replication: TRUNCATE TABLE statements failed to replicate when statement-based binary logging mode was not available. The issue was observed when using InnoDB with the transaction isolation level set to READ UNCOMMITTED (thus forcing InnoDB not to allow statement-based logging). However, the same behavior could be reproduced using any transactional storage engine supporting only row-based logging, regardless of the isolation level. This was due to two separate problems:

As a result of this fix, TRUNCATE TABLE is now treated as DDL for purposes of binary logging and replication; that is, it is always logged as a statement and so no longer causes an error when replicated using a transactional storage engine such as InnoDB. (Bug#36763)

See also Bug#42643.

Replication: mysqlbinlog replay of CREATE TEMPORARY TABLE ... LIKE statements and of TRUNCATE TABLE statements used on temporary tables failed with Error 1146 (Table ... doesn't exist). (Bug#35583)

Replication: mysqlbinlog sometimes failed when trying to create temporary files; this was because it ignored the specified temp file directory and tried to use the system /tmp directory instead. (Bug#35546)

See also Bug#35543.

Replication: In statement mode, mysqlbinlog failed to issue a SET @@autommit statement when the autocommit mode was changed. (Bug#34541)

Replication: LOAD DATA INFILE statements did not replicate correctly from a master running MySQL 4.1 to a slave running MySQL 5.1 or later. (Bug#31240)

Replication: The statements DROP PROCEDURE IF EXISTS and DROP FUNCTION IF EXISTS were not written to the binary log if the procedure or function to be dropped did not exist. (Bug#13684)

See also Bug#25705.

The optimizer could underestimate the memory required for column descriptors during join processing and cause memory corruption or a server crash. (Bug#42744)

A '%' character in SQL statements could cause the server to crash. (Bug#42634)

For the batched-key access method, numbers of records were being specified rather than numbers of ranges. (Bug#42593)

Certain queries could result in Valgrind warnings in the optimizer. (Bug#42534)

An optimization introduced for Bug#37553 required an explicit cast to be added for some uses of TIMEDIFF() because automatic casting could produce incorrect results. (It was necessary to use TIME(TIMEDIFF(...)).) (Bug#42525)

On the IBM i5 platform, the MySQL configuration process caused the system version of pthread_setschedprio() to be used. This function returns SIGILL on i5 because it is not supported, causing the server to crash. Now the my_pthread_setprio() function in the mysys library is used instead. (Bug#42524)

Performing a BACKUP DATABASE and RESTORE on a Maria table while an existing workload is in progress could lead to a corrupted table and possible crash. (Bug#42519)

The default Falcon memory parameters have been updated, which should help to improve performance. The new settings for all the memory parameters are as follows:

(Bug#42510, Bug#36442)

When running Falcon during a very high concurrency workload, mysqld could fail. (Bug#42475)

Falcon would fail to create a table in a TABLESPACE that had not already been opened by a previous operation. (Bug#42414, Bug#42743)

The recovery of Falcon tablespaces could fail because the tablespace information had become corrupt. (Bug#42392)

The SSL certficates included with MySQL distributions were regenerated because the previous ones had expired. (Bug#42366)

A deadlocked Maria table would incorrectly be marked as crashed. (Bug#42201)

INSERT operations to a Falcon table involving BIT columns with an index would fail to find the correct rows to update. (Bug#42196)

User variables within triggers could cause a crash if the mysql_change_user() C API function was invoked. (Bug#42188)

Parsing of the optional microsecond component of DATETIME values did not fail gracefully when that component width was larger than the allowed six places. (Bug#42146)

For Falcon tables, range queries using an index prefix were slow when Multi-Range Read index scans were disabled. (Bug#42136, Bug#41890)

The ALTER ONLINE TABLE statement for Falcon tables would not include support for add a primary key. (Bug#42099)

Sequences and auto increment values in Falcon tables would not reset, even when a TRUNCATE TABLE operation was executed. The behavior has now been updated to reset the values to the original table definition when TRUNCATE TABLE is applied. (Bug#42079)

Dependent subqueries such as the following caused a memory leak proportional to the number of outer rows:

SELECT COUNT(*) FROM t1, t2 WHERE t2.b
  IN (SELECT DISTINCT t2.b FROM t2 WHERE t2.b = t1.a);

(Bug#42037)

Queries executed using a join buffer could return incorrect results. (Bug#42020)

Some queries using NAME_CONST(.. COLLATE ...) led to a server crash due to a failed type cast. (Bug#42014)

The MAP file was not included in Windows distribution, but is needed by the InnoDB plugin. MAP file generation has again been enabled. (Bug#42001)

The optimizer underestimated the number of field descriptors for the join buffer in some cases. (Bug#41919)

Internal misconfiguration of the hash table used for the join buffer could cause a server crash. (Bug#41894)

String reallocation could cause memory overruns. (Bug#41868)

Queries executed using semi-join materialization could cause a crash if the outer query has a HAVING clause. (Bug#41842)

Running concurrent nontransactional queries on a Falcon table could cause a crash. (Bug#41835)

mysql_install_db did not pass some relevant options to mysqld. (Bug#41828)

A Valgrind warning in open_tables() was corrected. (Bug#41759)

A Valgrind warning in setup_wild() was corrected. (Bug#41729)

For Falcon tables, concurrent execution of a statement which in the general case should acquire a TL_READ_NO_INSERT lock on the table (for example multiple-table update, DML with subqueries, or statements involving new foreign key checks) and a statement that modifies the table might lead to warnings in the error log or even to deadlocks. (Bug#41688, Bug#42069)