List:Announcements« Previous MessageNext Message »
From:Bjorn Munch Date:April 23 2013 7:00pm
Subject:MySQL Community Server 5.7.1 has been released (part 2)
View as plain text  
This is part 2 of the MySQL 5.7.1 announcement

     * Replication: In certain cases, the dump thread could send a
       heartbeat out of synchronisation with format description
       events. One of the effects of this issue what that, after
       provisioning a new server from a backup data directory and
       setting --gtid-mode=ON and enabling autopositioning (see
       CHANGE MASTER TO Syntax
       (http://dev.mysql.com/doc/refman/5.7/en/change-master-to.html)
       ), replication failed to start, with the error Read invalid
       event from master.... The same problem could also cause
       GTID-based replication to fail due to skipped events following
       a unplanned shutdown of the master. (Bug #16051857)

     * Replication: In some cases, when the slave could not recognize
       the server version of the master, this could cause the slave
       to fail. (Bug #16056365)

     * Replication: Dropping a table that includes non-regular ASCII
       characters in the table name caused a replication failure. The
       parser converted the table name into standard charset
       characters and stored the table name in the table_name
       variable. When the drop table query was regenerated using the
       table_name variable, the table name was not converted back to
       the original charset.
       Additionally, table and database names with 64 characters
       caused an assert failure. The assert required the table or
       database name to be less than 128 characters. Latin characters
       require two-bytes each, which requires an assert condition of
       less than or equal to 128 bits.
       The fix includes a new function to convert tables names back
       to the original charset, and a correction to the assert
       condition allowing table and database names be less than or
       equal to 128 bits. (Bug #16066637)

     * Replication: When using GTID-based replication, and whenever a
       transaction was executed on the master but was not sent to the
       slave because the slave already had a transaction with that
       ID, semisynchrononous replication timed out. One case in which
       this could happen was during a failover operation where the
       new master started behind the new slave. (Bug #15985893)

     * Replication: An unnecessary flush to disk performed after
       every transaction when using FILE as the replication info
       repository type could degrade performance. Now this is done
       only when both data and relay log info is stored in
       (transactional) tables. (Bug #15980626)

     * Replication: When reading row log events from the binary log,
       the slave assumed that these events were always valid; because
       of this, an event having an invalid binary log offset could
       cause the slave to crash. Now in such cases, the slave fails
       gracefully, and an error is reported, if any of the fields in
       a given row event are invalid. (Bug #15829568)

     * Replication: Table IDs used in replication were defined as
       type ulong on the master and uint on the slave. In addition,
       the maximum value for table IDs in binary log events is 6
       bytes (281474976710655). This combination of factors led to
       the following issues:

          + Data could be lost on the slave when a table was assigned
            an ID greater than uint.

          + Table IDs greater than 281474976710655 were written to
            the binary log as 281474976710655.

          + This led to a stopped slave when the slave encountered
            two tables having the same table ID.
       To fix these problems, IDs are now defined by both master and
       slave as type ulonglong but constrained to a range of 0 to
       281474976710655, restarting from 0 when it exceeds this value.
       (Bug #14801955, Bug #67352)

     * Replication: MASTER_POS_WAIT() could hang or return -1 due to
       invalid updates by the slave SQL thread when transactions were
       skipped by the GTID protocol. (Bug #14737388)
       References: See also Bug #15927032.

     * Replication: Trying to execute a Stop event on a multithreaded
       slave could cause unwanted updates to the relay log, leading
       the slave to lose synchronization with the master. (Bug
       #14737388)

     * Replication: Internal objects used for relay log information
       were only partially deleted before freeing their memory. (Bug
       #14677824)

     * Replication: When the server starts, it checks whether
       semisynchronous replication has been enabled without a lock,
       and, if so, it takes the lock, then tests again. Disabling
       semisynchronous replication following the first of the these
       tests, but prior to the second one, could lead to a crash of
       the server. (Bug #14511533, Bug #66411)

     * Replication: It was possible in certain cases---immediately
       after detecting an EOF in the dump thread read event loop, and
       before deciding whether to change to a new binary log
       file---for new events to be written to the binary log before
       this decision was made. If log rotation occurred at this time,
       any events that occurred following EOF detection were dropped,
       resulting in loss of data. Now in such cases, steps are taken
       to make sure that all events are processed before allowing the
       log rotation to take place. (Bug #13545447, Bug #67929)
       References: See also Bug #16016886.

     * Replication: It was possible for the MASTER_POS_WAIT()
       function to return prematurely following a CHANGE MASTER TO
       statement that updated the RELAY_LOG_POS or RELAY_LOG_NAME.
       This could happen because CHANGE MASTER TO did not update the
       master log position in such cases, causing MASTER_POS_WAIT()
       to read an invalid log position and to return immediately.
       To fix this problem, the master log position is flagged as
       invalid until the position is set to a valid value when the
       SQL thread reads the first event, after which it is flagged as
       valid. Functions such as MASTER_POS_WAIT() now defer any
       comparison with the master log position until a valid value
       can be obtained (that is, after the first event following the
       CHANGE MASTER TO statement has been applied). (Bug #11766010,
       Bug #59037)

     * Replication: If the disk becomes full while writing to the
       binary log, the server hangs until space is freed up manually.
       It was possible after this was done for the MySQL server to
       fail, due to an internal status value being set when not
       needed. Now in such cases, rather than trying to set this
       status, a warning is written in the error log instead. (Bug
       #11753923, Bug #45449)

     * Replication: The binary log and relay log files used the name
       of the PID file instead of the host name as the basename. (Bug
       #11753843, Bug #45359)

     * Microsoft Windows: In Shared Memory mode
       (http://dev.mysql.com/doc/refman/5.7/en/server-options.html#op
       tion_mysqld_shared-memory), the MySQL Server could crash when
       receiving requests from multiple threads. (Bug #13934876)

     * Windows MSI installers for MySQL 5.7 had a 5.6 upgrade code,
       not a 5.7 upgrade code. (Bug #16445344)

     * SHOW ENGINE PERFORMANCE_SCHEMA STATUS could report incorrect
       memory-allocation values when the correct values exceeded 4GB.
       (Bug #16414644)

     * Performance Schema statement tokenization overhead was
       reduced. (Bug #16382260)

     * A long database name in a GRANT statement could cause the
       server to exit. (Bug #16372927)

     * The server could exit if a prepared statement attempted to
       create a table using the name of an existing view while an SQL
       handler was opened. (Bug #16385711)

     * For debug builds, checking of password constraints could raise
       an assertion for statements that updated passwords. (Bug
       #16289303)

     * The BUILD-CMAKE file in MySQL distributions was updated with
       the correct URL for CMake information. (Bug #16328024)

     * A Valgrind failure could occur if a CREATE USER statement was
       logged to the general query log and the old_passwords system
       variable was set to 2. (Bug #16300620)

     * The optimizer's attempt to remove redundant subquery clauses
       raised an assertion when executing a prepared statement with a
       subquery in the ON clause of a join in a subquery. (Bug
       #16318585)
       References: This bug is a regression of Bug #15875919.

     * Very small join_buffer_size values could cause an assertion to
       be raised. (Bug #16328373)

     * Some aggregate queries attempted to allocate excessive memory.
       (Bug #16343992)

     * Incorrect results were returned if a query contained a
       subquery in an IN clause which contained an XOR operation in
       the WHERE clause. (Bug #16311231)

     * For debug builds, an assertion could be raised if a statement
       failed with autocommit enabled just before an XA START
       statement was issued. (Bug #16341673)

     * Conversion of numeric values to BIT could yield unexpected
       results. (Bug #16271540)

     * Certain legal HAVING clauses were rejected as invalid. (Bug
       #16221433)

     * Fixed warnings when compiling with XCode 4.6. Fixed warnings
       when compiling when the _XOPEN_SOURCE or isoctal macro was
       already defined in the environment. (Bug #16265300, Bug
       #60911, Bug #12407384)

     * Queries using range predicates that were evaluated using the
       LooseScan semi-join strategy could return duplicate rows. (Bug
       #16221623)
       References: This bug is a regression of Bug #14728469.

     * For upgrade operations, RPM packages produced unnecessary
       errors about being unable to access .err files. (Bug
       #16235828)

     * In the range optimizer, an index merge failure could cause a
       server exit. (Bug #16241773)

     * For debug builds, the server could exit due to incorrect
       calculation of applicable indexes for a join that involved
       const tables. (Bug #16165832)

     * The Performance Schema could return incorrect values for the
       PROCESSLIST_INFO column of the threads table. (Bug #16215165)

     * Invocation of the range optimizer for a NULL select caused the
       server to exit. (Bug #16192219)

     * mysql_config --libs displayed incorrect output. (Bug
       #16200717)

     * For a CREATE TABLE (... col_name TIMESTAMP DEFAULT
       CURRENT_TIMESTAMP ...) ... SELECT statement for which the
       SELECT did not provide a value for the TIMESTAMP column, that
       column was set to '0000-00-00 00:00:00', not the current
       timestamp. (Bug #16163936)

     * yaSSL did not perform proper padding checks, but instead
       examined only the last byte of plaintext and used it to
       determine how many bytes to remove. (Bug #16218104)

     * Using GROUP BY WITH ROLLUP in a prepared statement could cause
       the server to exit. (Bug #16163596)

     * References to the unused SIGNAL_WITH_VIO_SHUTDOWN macro in the
       CMake files were removed. (Bug #16066150)

     * Setting the slave_rows_search_algorithms system variable to an
       inappropriate value could cause the server to exit. (Bug
       #16074161)

     * Directory name manipulation could result in stack overflow on
       Mac OS X and Windows. (Bug #16066243)

     * For debug builds, if the server was started with binary
       logging disabled, executing SHOW RELAYLOG EVENTS from within a
       stored procedure raised an assertion. (Bug #16043173)

     * The query parser leaked memory for some syntax errors. (Bug
       #16040022)

     * With the thread pool plugin enabled, large numbers of
       connections could lead to a Valgrind panic or failure of
       clients to be able to connect. (Bug #16088658, Bug #16196591)

     * The server executed EXPLAIN FORMAT=JSON for some malformed
       queries improperly. (Bug #16078557)

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

     * If the error for a failed CACHE INDEX statement index within a
       stored program was processed by a condition handler, a
       malformed packet and "Command out of sync" error occurred.
       (Bug #16076180)

     * The initial test database contained a dummy.bak file that
       prevented DROP DATABASE from working. This file is no longer
       included. Also, a db.opt file is now included that contains
       these lines:
default-character-set=latin1
default-collation=latin1_swedish_ci
       (Bug #16062056)

     * Setting a system variable to DEFAULT could cause the server to
       exit. (Bug #16044655)

     * SET PASSWORD and GRANT ... IDENTIFIED BY have no effect on the
       password of a user who is authenticated using an
       authentication plugin that accesses passwords stored
       externally to the mysql.user table. But attempts to change the
       password of such a user produced no warning, leading to the
       impression that the password had been changed when it was not.
       Now MySQL issues an ER_SET_PASSWORD_AUTH_PLUGIN warning to
       indicate that the attempt was ignored. (Bug #16072004)

     * For debug builds, creating an InnoDB table in strict SQL mode
       that violated the maximum key length limit caused the server
       to exit. (Bug #16035659)

     * Issuing a PREPARE statement using certain combinations of
       stored functions and user variables caused the server to exit.
       (Bug #16056537)

     * Instances of #ifdef WITH_MYISAMMRG_STORAGE_ENGINE and #ifdef
       WITH_CSV_STORAGE_ENGINE in the server source code were removed
       because the CSV and MERGE storage engine plugins are
       mandatory. (Bug #15997345)

     * A mysys library string-formatting routine could mishandle
       width specifiers. (Bug #15960005)

     * The --character-set-server option could set connection
       character set system variables to values such as ucs2 that are
       not permitted. (Bug #15985752)

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

     * The --default-authentication-plugin option permitted invalid
       plugin values, and did not always set the old_passwords system
       variable to a value appropriate for the named plugin. (Bug
       #16014394)

     * For debug builds, executing a statement within a trigger or
       stored function that caused an implicit commit raised an
       assertion. (Bug #15985318)

     * Under some circumstances, mysql --secure-auth permitted
       passwords to be sent to the server using the old (pre-4.1)
       hashing format. (Bug #15977433)

     * With index condition pushdown enabled, queries for which the
       pushed-down condition contained no columns in the used index
       could be slow. (Bug #15896009)

     * Table creation operations added entries to the Performance
       Schema file_instances table, but these were not always removed
       for table drop operations. (Bug #15927620)

     * In special cases, the optimizer did not consider indexes that
       were applicable to query processing, resulting in potentially
       suboptimal execution and incorrect EXPLAIN output. (Bug
       #15849135, Bug #16094171)

     * A query with an EXISTS/IN/ALL/ANY subquery with an ORDER BY
       clause ordering by an outer column of type BLOB that is not in
       the select list caused an assertion to fire. (Bug #15875919)
       References: See also Bug #14728142.

     * Queries in the query cache involving a given table were
       incorrectly invalidated if a TEMPORARY table of the same name
       was dropped. (Bug #14839743)

     * The optimizer could return nonmatching records for queries
       that used ref access on string data types. (Bug #14826522)
       References: See also Bug #14682735.

     * Failure of CREATE SERVER due to a missing or read-only
       mysql.servers table resulted in a memory leak. (Bug #14781478)

     * Enabling the query cache during high client contention could
       cause the server to exit. (Bug #14727815)

     * Table names can be up to 64 characters, but the message string
       for the ER_TABLE_NEEDS_REBUILD and ER_TABLE_NEEDS_UPGRADE
       errors were truncating names longer than 32 characters. (Bug
       #14753226)

     * Enabling the slow query log at runtime when access permissions
       on the log file prevented the server from writing to it caused
       the server to exit. (Bug #14711347)

     * Table removal could fail and cause the server to exit for very
       long file names. (Bug #14581920)

     * The server sometimes failed to respect
       MAX_CONNECTIONS_PER_HOUR limits on user connections. (Bug
       #14627287)

     * The server could access the DEBUG_SYNC facility while closing
       temporary tables during connection shutdown, after the
       facility had been cleaned up, leading to an assertion being
       raised. (Bug #14626800)

     * The optimizer could return incorrect results after
       transforming an IN subquery with aggregate functions to an
       EXISTS subquery. (Bug #14586710)

     * If the optimizer calculated a row count of zero for the inner
       table of an outer join, it could not determine proper ordering
       for the following tables. (Bug #14628746)

     * When a client program loses the connection to the MySQL server
       or if the server begins a shutdown after the client has
       executed mysql_stmt_prepare(), the next mysql_stmt_prepare()
       returns an error (as expected) but subsequent
       mysql_stmt_execute() calls crash the client. (Bug #14553380)

     * Previously, if multiple --login-path options were given,
       mysql_config_editor ignored all but the last one. Now multiple
       --login-path options result in an error. (Bug #14551712)

     * If MySQL server was started with options to enable the general
       query log or slow query log, but access permissions on the log
       file prevented the server from writing to it, the server
       started with an error message indicating that logging was off
       and that the server needed to be restarted after the problem
       was corrected. This was incorrect because it is also possible
       to set the logging variables again at runtime (without a
       restart) after correcting the problem. The error message now
       indicates this possibility. (Bug #14512467)

     * For debug builds, creating a TEMPORARY table inside a trigger
       caused the server to exit. (Bug #14493938)

     * SHOW COLUMNS on a view defined as a UNION of Geometry columns
       could cause the server to exit. (Bug #14362617)

     * The sha256_password_private_key_path and
       sha256_password_public_key_path system variables indicate key
       files for the sha256_password authentication plugin, but the
       server failed to properly check whether the key files were
       valid. Now in the event that either key file is invalid, the
       server logs an error and exits. (Bug #14360513)

     * SET var_name = VALUES(col_name) could cause the server to
       exit. This syntax is now prohibited because in SET context
       there is no column name and the statement returns
       ER_BAD_FIELD_ERROR. (Bug #14211565)

     * The COM_CHANGE_USER command in the client/server protocol did
       not properly use the character set number in the command
       packet, leading to incorrect character set conversion of other
       values in the packet. (Bug #14163155)

     * If the server was started with --skip-grant-tables, the CREATE
       EVENT and ALTER EVENT statements resulted in a memory leak.
       (Bug #14059662)

     * Invoking the FORMAT() function with a locale and a very large
       number could cause the server to exit. (Bug #14040155)

     * For debug builds, improper handling for AUTO_INCREMENT value
       overflow could cause the server to exit. (Bug #13875572)

     * Certain plugin-related conditions can make a user account
       unusable:

          + The account requires an authentication plugin that is not
            loaded.

          + The account requires the sha256_password authentication
            plugin but the server was started with neither SSL nor
            RSA enabled as required by this plugin.
       The server now checks those conditions by default and produces
       warnings for unusable accounts. This checking slows down
       server initialization and FLUSH PRIVILEGES, so it is made
       optional by means of the new validate_user_plugins system
       variable. This variable is enabled by default, but if you do
       not require the additional checking, you can disable it at
       startup to avoid the performance decrement. (Bug #13010061,
       Bug #14506305)

     * Passing an unknown time zone specification to CONVERT_TZ()
       resulted in a memory leak. (Bug #12347040)

     * The obsolete linuxthreads.txt and glibc-2.2.5.patch files in
       the Docs directory of MySQL distributions have been removed.
       (Bug #11766326)

     * mysql_install_db did not escape '_' in the host name for
       statements written to the grant tables. (Bug #11746817)

     * The server could exit if built to permit a maximum number of
       indexes per table larger than 64.
       In the course of fixing this problem, a -DMAX_INDEXES=N CMake
       option was added to permit building the server to support a
       larger maximum number of indexes per table. The default is 64.
       The maximum is 255. Values smaller than 64 are ignored and the
       default of 64 is used. (Bug #11761614)

     * Source code in the mysys library for the my_malloc_lock and
       my_free_lock memory-locking APIs was never used and has been
       removed. (Bug #54662, Bug #11762107)

     * mysqld_safe used the nonportable -e test construct. (Bug
       #67976, Bug #16046140)

     * An out-of-memory condition could occur while handling an
       out-of-memory error, leading to recursion in error handling.
       (Bug #49514, Bug #11757464)

     * The optimizer used loose index scan for some queries for which
       this access method is inapplicable. (Bug #42785, Bug
       #11751794)

     * If a dump file contained a view with one character set and
       collation defined on a view with a different character set and
       collation, attempts to restore the dump file failed with an
       "illegal mix of collations" error. (Bug #65382, Bug #14117025)

     * If the server failed to read errmsg.sys, it could exit with a
       segmentation fault. (Bug #53393, Bug #11760944)

     * The REPLACE() function produced incorrect results when a user
       variable was supplied as an argument and the operation was
       performed on multiple rows. (Bug #49271, Bug #11757250)

     * The output for SHOW CREATE VIEW could vary depending on the
       DEFINER account privileges. (Bug #34553, Bug #11747931)

     * UNION type conversion could incorrectly turn unsigned values
       into signed values. (Bug #49003, Bug #11757005)

     * If one thread was rebuilding a result for the query cache,
       other threads in the middle of using the previous result could
       fail to discard the old result properly. For debug builds,
       this raised an assertion. (Bug #66781, Bug #14631798)

     * UNION ALL on BLOB columns could produce incorrect results.
       (Bug #50136, Bug #11758009)

     * View access in low memory conditions could raise a debugging
       assertion. (Bug #39307, Bug #11749556)

     * Attempts to create a trigger for which a trigger with the same
       action time and event already existed resulted in an
       ER_NOT_SUPPORTED_YET error rather than an
       ER_TRG_ALREADY_EXISTS error. (Bug #67357, Bug #14801721)

     * Queries with many values in a IN() clause were slow due to
       inclusion of debugging code in non-debugging builds. (Bug
       #68046, Bug #16078212)
       References: See also Bug #58731, Bug #11765737.

     * When a view definition contained a special character in the
       SEPARATOR clause of the GROUP_CONCAT() aggregate function,
       mysqldump created an invalid view definition that produced an
       error when the dump file was reloaded. (Bug #60920, Bug
       #12395512)

     * Setting max_connections to a value less than the current
       number of open connections caused the server to exit. (Bug
       #44100, Bug #11752803)

     * Some table I/O performed by the server when calling a storage
       engine were missing from the statistics collected by the
       Performance Schema. (Bug #68180, Bug #16222630)

     * For debug builds, some queries with SELECT ... FROM DUAL
       nested subqueries raised an assertion. (Bug #60305, Bug
       #11827369)

     * Nonspatial indexes only support exact-match lookups for
       spatial columns, but the optimizer incorrectly used range
       access in some cases, leading to incorrect results. (Bug
       #67889, Bug #15993693)

     * If mysql is built with the bundled libedit library, the
       library is built as static code, to avoid linking to a
       different dynamic version at runtime. Dynamic linking could
       result in use of a different, incompatible version and a
       segmentation fault. (Bug #68231, Bug #16296509)

     * SLEEP() produced no warning or error for NULL or negative
       arguments. Now it produces a warning, or an error in strict
       SQL mode. (Bug #67548, Bug #15859462)

     * The --log-slow-admin-statements and
       --log-slow-slave-statements command options now are exposed at
       runtime as the log_slow_admin_statements and
       log_slow_slave_statements system variables. Their values can
       be examined using SHOW VARIABLES. The variables are dynamic,
       so their values can can be set at runtime. (The options were
       actually replaced by the system variables, but as system
       variables can be set at server startup, no option
       functionality is lost.) (Bug #59860, Bug #11766693)

     * For arguments with fractional seconds greater than six
       decimals, SEC_TO_TIME() truncated, rather than rounding as it
       should have. (Bug #68061, Bug #16093024)

     * MySQL failed to build if configured with WITH_LIBWRAP enabled.
       (Bug #67018, Bug #16342793)

     * If the server was started without a --datadir option, SHOW
       VARIABLES could show an empty value for the datadir system
       variable. (Bug #60995, Bug #12546953)

     * If a table had rows in the
       INFORMATION_SCHEMA.INNODB_CMP_PER_INDEX table, dropping the
       table did not remove those rows. (Bug #67283, Bug #14779330)

     * Configuring with -DWITH_SSL=/path/to/openssl resulted in link
       errors due to selection of the incorrect libcrypto. (Bug
       #68277, Bug #16284051)

     * ALTER TABLE tbl_name ADD COLUMN col_name TIMESTAMP DEFAULT
       CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP inserted
       0000-00-00 00:00:00 rather than the current timestamp if the
       alteration was done in place rather than by making a table
       copy. (Bug #68040, Bug #16076089)

     * If the server was started with --skip-grant-tables, ALTER USER
       ... PASSWORD EXPIRE caused the server to exit. (Bug #68300,
       Bug #16295905)

     * CMake did not check whether the system zlib had certain
       functions required for MySQL, resulting in build errors. Now
       it checks and falls back to the bundled zlib if the functions
       are missing. (Bug #65856, Bug #14300733)

     * mysql_install_db did not work in Solaris 10 sparse root zones.
       (Bug #68117, Bug #16197860)

     * For EXPLAIN DELETE and EXPLAIN UPDATE the possible_keys column
       listed all indexes, not just the applicable indexes. (Bug
       #67830, Bug #15972078)

     * The Perl version of mysql_install_db mishandled some error
       messages. (Bug #68118, Bug #16197542)

     * Handling of SQL_CALC_FOUND_ROWS in combination with ORDER BY
       and LIMIT could lead to incorrect results for FOUND_ROWS().
       (Bug #68458, Bug #16383173)

     * The server did not enforce the port or report_port upper limit
       of 65,535 and truncated larger values. (Bug #67956, Bug
       #16035522)

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

     * If INET6_NTOA() or INET6_ATON() returned NULL for a row in a
       result set, following rows also returned NULL. (Bug #68454,
       Bug #16373973)

     * If XA support was activated by multiple storage engines, the
       server would exit. (Bug #47134, Bug #11755370)

     * A statement with an aggregated, nongrouped outer query and an
       aggregated, nongrouped subquery in the SELECT list could
       return incorrect results. (Bug #68372, Bug #16325175)

     * The SQL_NO_CACHE keyword is supposed to prevent the server
       from checking the query cache to see whether the query result
       is already cached, and to prevent it from caching the query
       result. However, the query cache check was suppressed only if
       SQL_NO_CACHE was preceded and followed by space characters.
       (For example, the server checked the cache if the keyword was
       followed by a newline.) Now the parser requires that the
       preceding and following characters be whitespace characters,
       not spaces. (Bug #64164, Bug #13641256)

     * With explicit_defaults_for_timestamp enabled, inserting NULL
       into a TIMESTAMP NOT NULL column now produces an error (as it
       already did for other NOT NULL data types), instead of
       inserting the current timestamp. (Bug #68472, Bug #16394472)

     * Use of KILL to kill a statement in another session could in
       some cases cause that session to return an incorrect error
       code. (Bug #45679, Bug #11754124)

     * If a column is declared as NOT NULL, it is not permitted to
       insert NULL into the column or update it to NULL. However,
       this constraint was enforced even if there was a BEFORE INSERT
       (or BEFORE UPDATE trigger) that set the column to a non-NULL
       value. Now the constraint is checked at the end of the
       statement, per the SQL standard. (Bug #6295, Bug #11744964)

     * On Windows, the log_error system variable did not accurately
       reflect the error log file name in some cases. For example, if
       the server was started without --console or --log-error, the
       default is to log to host_name.err in the data directory, but
       log_error remained blank.
       Now log_error should be nonblank and reflect the log file name
       in all cases, on all platforms. The value is stderr if the
       server does not write error messages to a file and sends them
       to the console (standard error output) instead. In particular,
       on Windows, --console overrides use of an error log and sends
       error messages to the console, so log_error will be set to
       stderr. (Bug #8307, Bug #11745049)

     * Important Change: Formerly, the ExtractValue() and UpdateXML()
       functions supported a maximum length of 127 characters for
       XPath expressions supplied to them as arguments. This
       limitation has now been removed. (Bug #13007062, Bug #62429)

     * InnoDB: Creating and altering tables repeatedly would result
       in a memory leak that was due to a duplicate key error. The
       duplicate key error occurred because the
       row_merge_build_indexes function did not call
       row_fts_psort_info_destroy often enough. As full-text search
       indexes were created with a unique index, the unique index
       would fail due to the duplicate key error, and full-text
       search build resource would not be released. (Bug #14759111)

     * InnoDB: InnoDB IO threads within Performance Schema were
       exposed with the following name: "io_handler_thread". This fix
       implements specific keys such as io_read_handler_thread,
       io_write_handler_thread, io_ibuf_handler_thread to
       differentiate InnoDB IO threads within Performance Schema.
       (Bug #14670810)

     * InnoDB: This fix addresses an assert condition that would
       occur when inserting large BLOBs into tablespaces with a 4KB
       physical page size or into some compressed tables. Extents
       would not be allocated soon enough for tablespaces with
       smaller physical page sizes. (Bug #14520559)

     * InnoDB: On Linux systems, certain I/O requests that read or
       wrote fewer than the requested number of bytes could cause the
       server to crash. This issue could happen more frequently with
       asynchronous I/O
       (http://dev.mysql.com/doc/refman/5.7/en/glossary.html#glos_asy
       nchronous_io) requests. The messages did not clearly identify
       what type of error occurred:
InnoDB: Operating system error number 0 in a file operation.
InnoDB: Error number 0 means 'Success'.
       With this fix, MySQL retries the operation several times
       before giving up. (The number of retries is defined by the
       constant NUM_RETRIES_ON_PARTIAL_IO in the source code, default
       value 10.) (Bug #11761646, Bug #54160)

     * Partitioning: When the server is started with
       --skip-partition, it should reject DDL or DML statements on
       partitioned tables. However, for DROP TABLE, the server
       dropped the .frm file, and for RENAME TABLE, the server
       renamed the .frm file. (Bug #11763795)

     * Replication: mysqlbinlog did not properly decode DECIMAL
       values in a row-based binary log. This could cause invalid
       values to be printed out for DECIMAL columns. (Bug #14309019)

     * Replication: When using mysqlbinlog with the --verbose option
       to read a binary log written by a MySQL server using row-based
       or mixed-format logging, invalid SQL could be produced when
       comments appeared inside BINLOG statements. One way in which
       this could happen was when a function that updated data was
       used within an INSERT ... SELECT statement. (Bug #12889121)

     * Replication: mysql_upgrade on the master broke replication
       when the slave was run with --log-output equal to FILE or
       NONE. (Bug #11763447)

     * Replication: Issuing STOP SLAVE caused a spurious Error
       reading packet from server: Lost connection to MySQL server
       during query message to be written to the error log. (Bug
       #11761457, Bug #12977988, Bug #53955)

     * Replication: When an error occurs in the slave SQL thread,
       this causes the Slave_SQL_Error and Slave_SQL_Errno columns
       from SHOW SLAVE STATUS to display the reason for the error.
       The error number should be one of the usual constants ER_*
       defined in sql/share/errmsg.txt, and the error message should
       be the corresponding string. However, in some cases,
       Slave_SQL_Errno was set to something other than an ER_*
       number, and Slave_SQL_Error to a hard-coded error message
       rather than a translatable string from sql/share/errmsg.txt.
       Now all errors shown by SHOW SLAVE STATUS originate in
       sql/share/errmsg.txt, as expected. (Bug #11760365, Bug #52768)

     * Microsoft Windows: On Microsoft Windows, CMake entries for
       POSIX API's not found on Microsoft Windows were added to the
       CMake cache. This decreases the number of expected "Not found"
       errors while compiling MySQL. (Bug #14790333)

     * Microsoft Windows: On Microsoft Windows, queries referring to
       a table with invalid characters would search the system for
       invalid file names. The generated system error code
       (ERROR_INVALID_NAME) was not recognized by MySQL, so this
       unknown error would be reported to the server log as "ERRNO:
       22 - INVALID ARGUMENT". MySQL now recognizes these errors and
       reports them as the table does not existing, and it no longer
       logs them to the server error log. (Bug #14642248)

     * Microsoft Windows: On Windows, starting the server with
       --log-error and --console caused the server to write to the
       log file but not the console. Before MySQL 5.5.3, this
       occurred only if --log-error was specified after --console.
       Now, --console overrides --log-error no matter the option
       order so that --console produces console output in all cases.
       (Bug #14207773, Bug #65592)

     * Microsoft Windows: It was possible to specify a Named Pipe
       (http://dev.mysql.com/doc/refman/5.7/en/server-options.html#op
       tion_mysqld_enable-named-pipe) that was already in use. This
       is no longer allowed, as an error is now emitted and the
       process is aborted. After mysqld.exe was started in Named Pipe
       mode with a pipe name that was already used by a different
       instance, neither instance was able to shut down properly when
       a shutdown command was received from a TCP socket in any of
       the processes. Therefore, mysqld.exe was not terminated. (Bug
       #13891058, Bug #61885)

     * Microsoft Windows: On Microsoft Windows, a failed API or
       function call in mysqld.exe could sometimes report the error
       code 22, instead of the proper error code. (Bug #11763004)

     * Joins of exactly 32 tables and containing a HAVING clause
       returned an empty result. (Bug #15972635)

     * The parser rejected some legal UNION statements. (Bug
       #14730856)

     * Setting thread_cache_size to a negative value at server
       startup resulted in a value of 16384 rather than 0. (Bug
       #14683107)

     * The return value from IS_USED_LOCK() was reported using the
       wrong data type. (Bug #14575699)

     * There was no warning at startup if the server was started with
       an invalid query_cache_size value. (Bug #14576423)

     * Activation of a stored program handler did not preserve the
       current diagnostics stack. (Bug #14342913)

     * In debug builds, killing a HELP statement caused an assertion
       to be raised. (Bug #14221840)

     * If an error occurred during evaluation of the BEFORE
       expression of a PURGE BINARY LOGS BEFORE statement, the
       statement did not abort as it should have and later raised an
       assertion. (Bug #14215847)

     * For the index merge access method, the optimizer could make a
       suboptimal choice of indexes to use. (Bug #14095506)

     * An assertion could be raised if the attempt to open the .frm
       file for a temporary table failed. (Bug #13359247)

     * If the state of the Event Scheduler was changed during server
       shutdown, the server could crash. (Bug #13002460)

     * When storing the definition for a view that used the UPPER()
       or LOWER() function, the function call was replaced by UCASE()
       or LCASE(), respectively (as shown in the output of SHOW
       CREATE VIEW). This was in spite of the fact that UPPER() and
       LOWER() are standard, with UCASE() and LCASE() being MySQL
       synonyms for these. This made it more difficult to move
       databases between MySQL and other database systems.
       With this fix, calls to UPPER() and LOWER() within views are
       no longer rewritten when storing their definitions; instead,
       UCASE() is now rewritten as UPPER() in stored view
       definitions, and LCASE() as LOWER(), which increases the
       portability of the views. (Bug #12844279)

     * For queries that accessed an INFORMATION_SCHEMA table in a
       subquery, and attempt to lock a mutex that had already been
       locked could cause a server crash. (Bug #11765744)

     * The Range checked for each record optimization is now used for
       conditions with outer query references. (Bug #11750963)

     * An INSERT INTO ... SELECT statement that inserted no rows
       unnecessarily invalidated statements in the query cache that
       used the target table. (Bug #50065, Bug #11757947)

     * The server refused client connections while executing FLUSH
       PRIVILEGES. (Bug #63178, Bug #13418619)

     * References to a stored function without a database name
       qualifier while there was no default database resulted in an
       ER_SP_DOES_NOT_EXIST error rather than ER_NO_DB_ERROR. (Bug
       #64692, Bug #13864485)

     * Concurrent inserts were blocked by selects if the inserts were
       generated from within a stored procedure. (Bug #58689, Bug
       #11765698)

     * Concurrent execution of DROP DATABASE and any of CREATE
       FUNCTION, CREATE PROCEDURE, or CREATE EVENT could be written
       to the binary log in the wrong order, causing replication
       failure. (Bug #65428, Bug #14127220)

     * INSERT INTO ... SELECT ... ON DUPLICATE KEY UPDATE and LOAD
       DATA CONCURRENT REPLACE took too weak a lock, leading to the
       possibility of concurrent SELECT statements returning
       inconsistent results. (Bug #38046, Bug #11749055)

     * If read_only is enabled, it is still permitted to create
       TEMPORARY tables. But in this case, a non-TEMPORARY table with
       the same name could also be created, which should not be
       permitted. (Bug #64992, Bug #13969578)

     * Enabling the session value of low_priority_updates had no
       effect for INSERT statements. (Bug #64892, Bug #13939940)

     * An event was not dropped from the mysql.event table under
       these circumstances: The event was created while the event
       scheduler was enabled; the scheduler was disabled and
       re-enabled; the event expiration time was reached. (Bug
       #34804, Bug #11748012)

     * Using ALTER TABLE to rename a table to . resulted in a table
       with no name. (Bug #49636, Bug #11757569)

     * SHOW CREATE VIEW failed if the tables underlying the view were
       changed. (Bug #61718, Bug #12762393)

     * SHOW GLOBAL STATUS caused performance problems on busy servers
       due to lock contention. (Bug #42930, Bug #11751904)

     * For a view defined on a UNION, the server could create an
       invalid view definition. (Bug #65388, Bug #14117018)

     * For queries using ref access on string data types, the ref
       access condition could be evaluated again as part of the query
       condition or pushed down as an index condition to the storage
       engine. (Bug #66983, Bug #14682735)

     * For an ALTER TABLE statement that renamed or changed the
       default value of a BINARY column, the alteration was done
       using a table copy and not in place. (Bug #67141, Bug
       #14735373)

     * A view was created with an incorrect definition if the WHERE
       clause contained string literals and character_set_client and
       character_set_connection were set to different character sets.
       (Bug #63094, Bug #13520710)

- Bjorn Munch
  MySQL Release Engineering
Thread
MySQL Community Server 5.7.1 has been released (part 2)Bjorn Munch24 Apr