From: Bjorn Munch
Date: April 23 2013 6:49pm
Subject: MySQL Community Server 5.7.1 has been released (part 1)
List-Archive: http://lists.mysql.com/mysql/229314
Message-Id: <20130423184929.GA9339@igil>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Dear MySQL users,
MySQL Server 5.7.1 (Milestone Release) is a new version of the world's
most popular open source database. This is the first milestone release
of MySQL 5.7.
http://dev.mysql.com/doc/mysql-development-cycle/en/development-milestone-releases.html
The new features in these releases are of Beta quality. As with any
other pre-production release, caution should be taken when installing
on production level systems or systems with critical data.
Note that 5.7.1 includes all features in MySQL 5.6.
For information on installing MySQL 5.7.1 on new servers, please see the
MySQL installation documentation at
http://dev.mysql.com/doc/refman/5.7/en/installing.html
MySQL Server 5.7.1 is available in source and binary form for a number of
platforms from the "Development Releases" selection of our download
pages at
http://dev.mysql.com/downloads/mysql/
The platforms and package formats available for MySQL 5.7.1 are the
same as for 5.6.
Windows packages are now available via the new Installer for Windows
Installer or .ZIP (no-install) packages for more advanced needs. It
should be noted that the previous MSI packaging is no longer available
and the point and click configuration wizards and all MySQL products
are now available in the unified Installer for Windows:
http://dev.mysql.com/downloads/installer/
Like the newly released MySQL 5.6.11, 5.7.1 also comes with a web
installer as an alternative to the full installer.
The web installer doesn't come bundled with any actual products
and instead relies on download-on-demand to fetch only the
products you choose to install. This makes the initial download
much smaller but increases install time as the individual products
will need to be downloaded.
We welcome and appreciate your feedback, bug reports, bug fixes,
patches, etc.:
http://bugs.mysql.com/report.php
The following section lists the changes in MySQL 5.7 since development
started, and bug fixes not already included in 5.6.10. It may also be
viewed online at
http://dev.mysql.com/doc/relnotes/mysql/5.7/en/news-5-7-1.html
Enjoy!
On behalf of the MySQL Build Team at Oracle,
- Bjorn Munch
[ Due to a 50K size limitation, this announcement is split in two
parts. This is part 1. ]
=======================================================================
Changes in MySQL 5.7.1 (23 April 2013, Milestone 11)
Note
This is a milestone release, for use at your own risk. Significant
development changes take place in milestone releases and you may
encounter compatibility issues, such as data format changes that
require attention in addition to the usual procedure of running
mysql_upgrade. For example, you may find it necessary to dump your
data with mysqldump before the upgrade and reload it afterward.
Functionality Added or Changed
* Performance: String hashing overhead was reduced. This also
improves performance for metadata locking, the table
definition cache, and Performance Schema table I/O and file
I/O instrumentation. (Bug #13944392)
* Incompatible Change: SHOW ENGINE PERFORMANCE_SCHEMA STATUS
output used a mix of row_count and count attributes. These are
now all count. Similarly, the output used a mix of row_size
and size attributes. These are now all size. (Bug #16165468)
* InnoDB: Online index renaming is supported by ALTER TABLE,
which now includes a RENAME INDEX clause, as shown in the
following example: "ALTER TABLE t RENAME INDEX i1 TO i2",
where i1 is the current name of the index and i2 is the new
name.
The result of "ALTER TABLE t RENAME INDEX i1 TO i2" would be a
table with contents and structure that is identical to the old
version of "t1" except for the index name, which is now "i2"
instead of "i1".
* InnoDB: You can now increase VARCHAR size online through ALTER
TABLE ...ALGORITHM=INPLACE, CHANGE COLUMN...VARCHAR(). VARCHAR
size may be increased from a value less than 255 bytes up to a
value equal to or less than 255 bytes. You may also increase
VARCHAR size online from a starting value greater than 255
bytes (Bug#15863023).
Note
Decreasing VARCHAR size online is not supported, nor is
increasing VARCHAR size online from a value less than 256
bytes to a value greater than 256 bytes.
* InnoDB: DDL performance for InnoDB temporary tables is
improved through optimization of CREATE TABLE, DROP TABLE,
TRUNCATE TABLE, ALTER TABLE ... IMPORT TABLESPACE, and ALTER
TABLE ...DISCARD TABLESPACE statements.
* InnoDB: Added support for spatial data types currently
supported by MySQL including POINT, LINE_STRING, POLYGON,
MULTI_POINT, MULTI_POLYGON, MULTI_LINE_STRING,
GEOMETRY_COLLECTION, and GEOMETRY.
Prior to this release, InnoDB would store spatial data, except
for POINT, as binary BLOB data. BLOB remains the underlying
data type but spatial data types are now mapped to a new
InnoDB internal data type, DATA_GEOMETRY. With BLOB as the
underlying data type, a prefix index can still be used on the
GEOMETRY data column.
* InnoDB: Added a separate tablespace for all non-compressed
user and system-generated temporary tables. The new
tablespace, which is always recreated on server startup,
provides persistent storage for temporary table
meta-information. Persistent meta-information enables proper
cleanup in crash recovery scenarios. Additionally, a separate
tablespace for temporary tables avoids having to store
persistent meta-information in system tablespaces.
The new tablespace, ibtmp1, is located in the /tmp directory
by default. A newly added configuration file option,
--innodb_temp_data_file_path, allows for a user-defined
temporary data file path.
* Replication: An Auto_Position column has been added to the
output generated by SHOW SLAVE STATUS. The value of this
column shows whether replication autopositioning is in use. If
autopositioning is enabled---that is, if MASTER_AUTO_POSITION
= 1 was set by the last successful CHANGE MASTER TO statement
that was executed on the slave---then the column's value is 1;
if not, then the value is 0. (Bug #15992220)
* Replication: The functions GTID_SUBTRACT() and GTID_SUBSET()
were formerly available in libmysqld only when it was built
with replication support. Now these functions are always
available when using this library, regardless of how it was
built.
* MySQL no longer uses the default OpenSSL compression. (Bug
#16235681)
* There is now a distinct error code
(ER_MUST_CHANGE_PASSWORD_LOGIN) for the error sent by the
server to a client authenticating with an expired password.
(Bug #16102943)
* In RPM packages built for Unbreakable Linux Network,
libmysqld.so now has a version number. (Bug #15972480)
* Error messages for ALTER TABLE statement using a LOCK or
ALGORITHM value not supported for the given operation were
very generic. The server now produces more informative
messages. (Bug #15902911)
* If a client with an expired password connected but
old_passwords was not the value required to select the
password hashing format appropriate for the client account,
there was no way for the client to determine the proper value.
Now the server automatically sets the session old_passwords
value appropriately for the account password. (Bug #15892194)
* mysql_config_editor now supports --port and --socket options
for specifying TCP/IP port number and Unix socket file name.
(Bug #15851247)
* mysqldump now supports an --ignore-error option. The option
value is a comma-separated list of error numbers specifying
the errors to ignore during mysqldump execution. If the
--force option is also given to ignore all errors, --force
takes precedence. (Bug #15855723)
* mysqlcheck has a new --skip-database option. The option value
is the name of a database (case sensitive) for which checks
should be skipped.
mysql_upgrade uses this option to upgrade the system tables in
the mysql database before tables in other databases: It
upgrade the mysql database, then all databases except the
mysql database. This avoids problems that can occur if user
tables are upgraded before the system tables. (Bug #14697538)
* The validate_password_policy_number system variable was
renamed to validate_password_policy. (Bug #14588121)
* Previously, on Linux the server failed to perform stack
backtrace attempts for versions of glibc older than the
current minimum supported version (2.3). Now on such attempts
the server displays a message that the glibc version is too
old to support backtracing. (Bug #14475946)
* In JSON-format EXPLAIN output, the attached_condition
information for subqueries now includes select# to indicate
the relative order of subquery execution. (Bug #13897507)
* The following changes were made to the sandbox mode that the
server uses to handle client connections for accounts with
expired passwords:
+ There is a new disconnect_on_expired_passwords system
variable (default: enabled). This controls how the server
treats expired-password accounts.
+ Two flags were added to the C API client library:
MYSQL_OPT_CAN_HANDLE_EXPIRED_PASSWORDS for
mysql_options() and CLIENT_CAN_HANDLE_EXPIRED_PASSWORDS
for mysql_real_connect(). Each flag enables a client
program to indicate whether it can handle sandbox mode
for accounts with expired passwords.
MYSQL_OPT_CAN_HANDLE_EXPIRED_PASSWORDS is enabled for
mysqltest unconditionally, for mysql in interactive mode,
and for mysqladmin if the first command is password.
For more information about how the client-side flags interact
with disconnect_on_expired_passwords, see Password Expiration
and Sandbox Mode
(http://dev.mysql.com/doc/refman/5.7/en/password-expiration.ht
ml). (Bug #67568, Bug #15874023)
* If a user attempted to access a nonexistent column for which
the user had no access, the server returned an error
indicating that the column did not exist. Now the server
returns an error indicating that the user does not have
privileges for the column, which provides no information about
column existence. (Bug #19947, Bug #11745788)
* The deprecated innodb_mirrored_log_groups system variable has
been removed.
* The mysql client now has a --syslog option that causes
interactive statements to be sent to the system syslog
facility. Logging is suppressed for statements that match the
default "ignore" pattern list ("*IDENTIFIED*:*PASSWORD*"), as
well as statements that match any patterns specified using the
--histignore option. For more information, see mysql Logging
(http://dev.mysql.com/doc/refman/5.7/en/mysql-logging.html).
* ALTER TABLE now supports a RENAME INDEX clause that renames an
index. The change is made in place without a table-copy
operation. See ALTER TABLE Syntax
(http://dev.mysql.com/doc/refman/5.7/en/alter-table.html).
* Important Change; Replication: Added the --idempotent option
for mysqlbinlog, which causes the MySQL Server to employ
idempotent mode. This causes suppression of all duplicate-key
and key-not-found errors when processing updates from the
binary log. The mode is in effect for the current mysqlbinlog
client and client session only.
* Important Change; Replication: SHOW SLAVE STATUS when run
concurrently with STOP SLAVE can take a long time to execute
if the slave SQL thread was in the midst of applying a large
update. To fix this problem, a new NONBLOCKING option has been
added to the SHOW SLAVE STATUS statement. When this option is
used, SHOW SLAVE STATUS does not wait on the SQL or I/O
threads but returns immediately. This means that the reported
states of these threads may not be completely up to date when
the option is used. NONBLOCKING is intended primarily for use
by monitoring tools in which obtaining an immediate response
is more important than having the most timely data.
* Microsoft Windows: Windows Vista, Windows Server 2008, and
newer support native symlinking using the mklink command. This
makes the MySQL Server implementation of database symbolic
links using .sym files redundant, so that mechanism is now
removed. This change has the following implications:
+ Existing .sym files are now ignored. Database symlinks
should be recreated using mklink. See Using Symbolic
Links for Databases on Windows
(http://dev.mysql.com/doc/refman/5.7/en/symbolic-links.ht
ml#windows-symbolic-links).
+ The --symbolic-links and --skip-symbolic-links options
and the have_symlink system variable now are meaningful
only for Unix systems, and not for Windows.
* The server now issues a warning if an index is created that
duplicates an existing index, or an error in strict SQL mode.
(Bug #37520, Bug #11748842)
* Previously, Control+C in mysql interrupted the current
statement if there was one, or exited mysql if not. Now
Control+C interrupts the current statement if there was one,
or cancels any partial input line otherwise, but does not
exit. (Bug #66583, Bug #14554568)
* The mysql_clear_password cleartext client-side authentication
plugin is intended for authentication schemes that require the
server to receive the password as entered on the client side,
without hashing. Because the password is sent in the clear,
this plugin should be used within the context of a secure
connection, such as an SSL connection, to avoid exposing the
password over the network. To make inadvertent use of this
plugin less likely, it is now required that clients explicitly
enable it. This can be done several ways:
+ Set the LIBMYSQL_ENABLE_CLEARTEXT_PLUGIN environment
variable to a value that begins with 1, Y, or y. This
enables the plugin for all client connections.
+ The mysql, mysqladmin, and mysqlslap client programs
support an --enable-cleartext-plugin option that enables
the plugin on a per-invocation basis.
+ The mysql_options() C API function supports a
MYSQL_ENABLE_CLEARTEXT_PLUGIN option that enables the
plugin on a per-connection basis. Also, any program that
uses libmysqlclient and reads option files can enable the
plugin by including an enable-cleartext-plugin option in
an option group read by the client library.
* INSERT DELAYED is no longer supported. The server recognizes
but ignores the DELAYED keyword, handles the insert as a
nondelayed insert, and generates an
ER_WARN_LEGACY_SYNTAX_CONVERTED warning. ("INSERT DELAYED is
no longer supported. The statement was converted to INSERT.").
Similarly, REPLACE DELAYED is handled as a nondelayed replace.
The DELAYED keyword will be removed in a future release.
In addition, several DELAYED-related options or features were
removed:
+ The --delayed-insert option for mysqldump.
+ The COUNT_WRITE_DELAYED, SUM_TIMER_WRITE_DELAYED,
MIN_TIMER_WRITE_DELAYED, AVG_TIMER_WRITE_DELAYED, and
MAX_TIMER_WRITE_DELAYED columns of the Performance Schema
table_lock_waits_summary_by_table table.
If you upgrade to this release of MySQL from an earlier
version, you must run mysql_upgrade (and restart the
server) to incorporate these changes into the
performance_schema database.
+ mysqlbinlog no longer writes comments mentioning INSERT
DELAYED.
* MySQL now supports stacked diagnostics areas and GET STACKED
DIAGNOSTICS can be used during condition handler activation to
retrieve information from the diagnostics area that was
current before the handler was activated. This enables
handlers to inspect information about the condition that
caused the handler to activate. As before, GET [CURRENT]
DIAGNOSTICS still retrieves information about the current
diagnostics area and can be used even if no handler is active.
For more information, see GET DIAGNOSTICS Syntax
(http://dev.mysql.com/doc/refman/5.7/en/get-diagnostics.html).
Bugs Fixed
* Performance; InnoDB: The DROP TABLE statement for a table
using compression
(http://dev.mysql.com/doc/refman/5.7/en/glossary.html#glos_com
pression) could be slower than necessary, causing a stall for
several seconds. MySQL was unnecessarily decompressing pages
(http://dev.mysql.com/doc/refman/5.7/en/glossary.html#glos_pag
e) in the buffer pool
(http://dev.mysql.com/doc/refman/5.7/en/glossary.html#glos_buf
fer_pool) related to the table as part of the DROP operation.
(Bug #16067973)
* Incompatible Change; Partitioning: Changes in the KEY
partitioning hashing functions used with numeric, date and
time, ENUM, and SET columns in MySQL 5.5 makes tables using
partitioning or subpartitioning by KEY on any of the affected
column types and created on a MySQL 5.5 or later server
incompatible with a MySQL 5.1 server. This is because the
partition IDs as calculated by a MySQL 5.5 or later server
almost certainly differ from those calculated by a MySQL 5.1
server for the same table definition and data as a result of
the changes in these functions.
The principal changes in the KEY partitioning implementation
in MySQL 5.5 resulting in this issue were as follows: 1. The
hash function used for numeric and date and time columns
changed from binary to character-based. 2. The base used for
hashing of ENUM and SET columns changed from latin1 ci
characters to binary.
The fix involves adding the capability in MySQL 5.5 and later
to choose which type of hashing to use for KEY partitioning,
which is implemented with a new ALGORITHM extension to the
PARTITION BY KEY option for CREATE TABLE and ALTER TABLE.
Specifying PARTITION BY KEY ALGORITHM=1 ([columns]) causes the
server to use the hashing functions as implemented in MySQL
5.1; using ALGORITHM=2 causes the server to use the hashing
functions from MySQL 5.5 and later. ALGORITHM=2 is the
default. Using the appropriate value for ALGORITHM, you can
perform any of the following tasks:
+ Create KEY partitioned tables in MySQL 5.5 and later that
are compatible with MySQL 5.1, using CREATE TABLE ...
PARTITION BY KEY ALGORITHM=1 (...).
+ Downgrade KEY partitioned tables that were created in
MySQL 5.5 or later to become compatible with MySQL 5.1,
using ALTER TABLE ... PARTITION BY KEY ALGORITHM=1 (...).
+ Upgrade KEY partitioned tables originally created in
MySQL 5.1 to use hashing as in MySQL 5.5 and later, using
ALTER TABLE ... PARTITION BY KEY ALGORITHM=2 (...).
Important: After such tables are upgraded, they cannot be
used any longer with MySQL 5.1 unless they are first
downgraded again using ALTER TABLE ... PARTITION BY KEY
ALGORITHM=1 (...) on a MySQL server supporting this
option.
This syntax is not backward compatible, and causes errors in
older versions of the MySQL server. When generating CREATE
TABLE ... PARTITION BY KEY statements, mysqldump brackets any
occurrence of ALGORITHM=1 or ALGORITHM=2 in conditional
comments such that it is ignored by a MySQL server whose
version is not at least 5.5.31. An additional consideration
for upgrades is that MySQL 5.6 servers prior to MySQL 5.6.11
do not ignore the ALGORITHM option in such statements when
generated by a MySQL 5.5 server, due to the that the
conditional comments refer to version 5.5.31; in this case,
you must edit the dump manually and remove or comment out the
option wherever it occurs before attempting to load it into a
MySQL 5.6.10 or earlier MySQL 5.6 server. This is not an issue
for dumps generated by MySQL 5.6.11 or later version of
mysqldump, where the version used in such comments is 5.6.11.
For more information, see ALTER TABLE Partition Operations
(http://dev.mysql.com/doc/refman/5.7/en/alter-table-partition-
operations.html).
As part of this fix, a spurious assertion by InnoDB that a
deleted row had previously been read, causing the server to
assert on delete of a row that the row was in the wrong
partition, was also removed. (Bug #14521864, Bug #66462, Bug
#16093958, Bug #16274455)
References: See also Bug #11759782.
* Important Change; Plugin API; Replication: Because the
behavior of the fulltext plugin may vary between MySQL
servers, it is not possible to guarantee that statements using
this plugin produce the same results on masters and slaves.
For this reason, statements depending on the fulltext plugin
are now marked as unsafe for statement-based logging. This
means that such statements are logged using row format when
binlog_format=MIXED, and cause a warning to be generated when
binlog_format=STATEMENT. (Bug #11756280, Bug #45449)
* Important Change; Replication: Executing a statement that
performs an implicit commit but whose changes are not logged
when gtid_next is set to any value other than AUTOMATIC is not
permitted. Now in such cases, the statement fails with an
error. This includes the statements in the following list:
+ CHANGE MASTER TO
+ START SLAVE
+ STOP SLAVE
+ REPAIR TABLE
+ OPTIMIZE TABLE
+ ANALYZE TABLE
+ CHECK TABLE
+ CREATE SERVER
+ ALTER SERVER
+ DROP SERVER
+ CACHE INDEX
+ LOAD INDEX INTO CACHE
+ FLUSH
+ RESET
(Bug #16062608)
References: See also Bug #16484323.
* Important Change; Replication: The version number reported by
mysqlbinlog --version has been increased to 3.4. (Bug
#15894381, Bug #67643)
* Important Change; Replication: The lettercasing used for
displaying UUIDs in global transaction identifiers was
inconsistent. Now, all GTID values use lowercase, including
those shown in the Retrieved_Gtid_Set and Executed_Gtid_Set
columns from the output of SHOW SLAVE STATUS. (Bug #15869441)
* Important Note; Replication: It was possible to replicate from
a table to a same-named view using statement-based logging,
while using row-based logging instead led to a failure on the
slave. Now the target object type is checked prior to
performing any DML, and an error is given if the target on the
slave is not actually a table. This is true regardless of the
binary logging format in use. (Bug #11752707, Bug #43975)
* InnoDB: When parsing a delimited search string such as
"abc-def" in a full-text search, InnoDB now uses the same word
delimiters as MyISAM. (Bug #16419661)
* InnoDB: This fix improves code readability by addressing
naming inconsistencies for InnoDB PERFORMANCE_SCHEMA key
declarations. (Bug #16414044)
* InnoDB: This fix disables a condition for extra splitting of
clustered index leaf pages, on compressed tables. Extra page
splitting was only done to reserve space for future updates,
so that future page splits could be avoided. (Bug #16401801)
* InnoDB: For InnoDB tables, if a PRIMARY KEY on a VARCHAR
column (or prefix) was empty, index page compression could
fail. (Bug #16400920)
* InnoDB: Status values in the INNODB_FT_CONFIG table would not
update. The INNODB_FT_CONFIG is intended for internal
configuration and should not be used for statistical
information purposes. To avoid confusion, column values that
are intended for internal use have been removed from the
INNODB_FT_CONFIG table. This fix also removes the
INNODB_FT_INSERTED table and other internal full text
search-related tables that were unintentionally exposed. (Bug
#16409494)
* InnoDB: With innodb_api_enable_mdl=OFF, an ALTER TABLE
operation on an InnoDB table that required a table copy could
cause a server exit. (Bug #16287411)
* InnoDB: Improper testing of compatibility between the
referencing and referenced during ALTER TABLE ... ADD FOREIGN
key could cause a server exit. (Bug #16330036)
* InnoDB: Rollback did not include changes made to temporary
tables by read-only transactions. (Bug #16310467)
* InnoDB: The InnoDB page-splitting algorithm could recurse
excessivly. (Bug #16345265)
* InnoDB: For debug builds, InnoDB status exporting was subject
to a race condition that could cause a server exit. (Bug
#16292043)
* InnoDB: When using ALTER TABLE to set an AUTO_INCREMENT column
value to a user-specified value, InnoDB would set the
AUTO_INCREMENT value to the user-specified value even when the
AUTO_INCREMENT value is greater than the user-specified value.
This fix ensures that the AUTO_INCREMENT value is set to the
maximum of the user-specified value and
MAX(auto_increment_column)+1, which is the expected behaviour.
(Bug #16310273)
* InnoDB: Importing a tablespace with the configuration file
present would not import the data file. This problem would
occur when all pages are not flushed from the buffer pool
after a table is altered using the copy and rename approach.
This fix ensures that all pages are flushed from the buffer
pool when a table is altered using the copy and rename
approach. (Bug #16318052)
* InnoDB: The lock_validate function, which is only present in
debug builds, acquired and released mutexes to avoid hogging
them. This behavior introduced a window wherein changes to the
hash table could occur while code traversed the same set of
data. This fix updates lock_validate logic to collect all
records for which locks must be validated, releases mutexes,
and runs a loop to validate record locks. (Bug #16235056)
* InnoDB: ALTER TABLE functions would perform a check to see if
InnoDB is in read-only mode (srv_read_only_mode=true). If
InnoDB was in read-only mode, the check would return a
successful status and do nothing else. This fix replaces
srv_read_only_mode check conditions with debug assertions.
(Bug #16227539)
* InnoDB: An improper call to abort() by InnoDB could result in
a server exit. (Bug #16263506)
* InnoDB: When the InnoDB buffer pool is almost filled with 4KB
compressed pages, inserting into 16KB compact tables would
cause 8KB pages_free to increase, which could potentially slow
or stall inserts. (Bug #16223169)
* InnoDB: An assertion failure would occur in heap->magic_n ==
MEM_BLOCK_MAGIC_N due to a race condition that appeared when
row_merge_read_clustered_index() returned an error. (Bug
#16275237)
* InnoDB: This fix removes an unnecessary debug assertion
related to page_hash locks which only affects debug builds.
The debug assertion is no longer valid and should have been
removed when hash_lock array was introduced in MySQL 5.6. (Bug
#16263167)
* InnoDB: Without warning, InnoDB would silently set
innodb-buffer-pool-instances to 1 if the buffer pool size is
less than 1GB. For example, if innodb-buffer-pool-size is set
to 200M and innodb-buffer-pool-instances is set to 4, InnoDB
would silently set innodb-buffer-pool-instances to 1. This fix
implements a warning message and new logic for
innodb-buffer-pool-size and innodb-buffer-pool-instances. (Bug
#16249500, Bug #61239)
* InnoDB: When the primary key of a table includes a column
prefix, and a full-text index is defined on the table, a
full-text search resulted in an unnecessary warning being
written to the error log. This fix suppresses the unnecessary
warning. (Bug #16169411)
* InnoDB: When InnoDB locking code was revised, a call to
register lock waits was inadvertently removed. This fix adds
the call back to the InnoDB locking code. (Bug #16208201)
* InnoDB: A direct call to the trx_start_if_not_started_xa_low()
function would cause a debug assertion. (Bug #16178995)
* InnoDB: In the case of LOCK WAIT for an insert in a foreign
key table, InnoDB could report a false dictionary-changed
error and cause the insert to fail rather than being retried.
(Bug #16174255)
* InnoDB: In some cases, deadlock detection did not work,
resulting in sessions hanging waiting for a lock-wait timeout.
(Bug #16169638)
* InnoDB: An in-place ALTER TABLE on an InnoDB table could fail
to delete the statistics for the old primary key from the
mysql.innodb_index_stats table. (Bug #16170451)
* InnoDB: This fix updates InnoDB code in ha_innodb.cc and
handler0alter.cc to use TABLE::key_info instead of both
TABLE::key_info and TABLE_SHARE::key_info. (Bug #16215361)
* InnoDB: Arithmetic underflow during page compression for
CREATE TABLE on an InnoDB table could cause a server exit.
(Bug #16089381)
* InnoDB: LOCK_TIME would not be logged correctly in the slow
query log. LOCK_TIME did not account for InnoDB row lock wait
time. (Bug #16097753)
* InnoDB: For debug builds, online ALTER TABLE operations for
InnoDB tables could cause a server exit during table
rebuilding. (Bug #16063835)
* InnoDB: In some cases, the InnoDB purge coordinator did not
use all available purge threads, resulting in suboptimal purge
activity. (Bug #16037372)
* InnoDB: ALTER TABLE for InnoDB tables was not fully atomic.
(Bug #15989081)
* InnoDB: This fix replaces most uses of UT_SORT_FUNCTION_BODY,
an InnoDB recursive merge sort, with the std::sort() function
from the C++ Standard Template Library (STL). The std::sort()
function requires less memory and is faster due to in-line
execution. (Bug #15920744)
* InnoDB: This fix implements a 256-byte boundary for extending
a VARCHAR column instead of 256-character boundary. This
change allows for in-place extension of a VARCHAR column
through an update of the data dictionary. (Bug #15863023)
* InnoDB: This fix addresses unnecessary buffer pool lookups
that would occur while freeing blob pages, and implements a
debug status instrument, innodb_ahi_drop_lookups, for testing
purposes. (Bug #15866009)
* InnoDB: Due to a resource related bug, creating numerous
tables that have a simple a full-text search index would cause
excessive memory usage. This fix adds a global configuration
parameter to limit the total memory size that full-text search
indexes can use. If the global memory limit is reached by an
index operation, a force sync is triggered. (Bug #14834698)
* InnoDB: This fix modifies InnoDB code to ensure that unused
thread handles are closed when the thread exits, instead of
leaving thread handles open until shutdown of mysqld on
Windows. (Bug #14762796)
* InnoDB: This fix removes unnecessary overhead by removing
table locking and disabling read view creation and MVCC when
InnoDB is started in read-only mode (--innodb-read-only=true).
(Bug #14729365)
* InnoDB: An error at the filesystem level, such as too many
open files, could cause an unhandled error during an ALTER
TABLE operation. The error could be accompanied by Valgrind
warnings, and by this assertion message:
Assertion `! is_set()' failed.
mysqld got signal 6 ;
(Bug #14628410, Bug #16000909)
* InnoDB: The INNODB_SYNC_ARRAY_SIZE variable was incorrectly
allowed to be configured at runtime. As documented,
INNODB_SYNC_ARRAY_SIZE must be configured when the MySQL
instance is starting up, and cannot be changed afterward. This
fix changes INNODB_SYNC_ARRAY_SIZE to a non-dynamic variable,
as intended. (Bug #14629979)
* InnoDB: The server could exit during an attempt by InnoDB to
reorganize or compress a compressed secondary index page. (Bug
#14606334)
* InnoDB: A DML operation performed while a RENAME TABLE
operation waits for pending I/O operations on the tablespace
to complete would result in a deadlock. (Bug #14556349)
* InnoDB: Attempting to unninstall the InnoDB memcached Plugin
while the plugin is still installing caused the Mysql server
to terminate. While the plugin deamon thread was still
initializing, plugin variables were not yet set and the
uninstall process could not cleanup resources. This fix adds a
variable to indicate initialization status. If initialization
is incomplete, the uninstall process will wait. (Bug
#14279541)
* InnoDB: If the value of innodb_force_recovery was less than 6,
opening a corrupted table might loop forever if a corrupted
page was read when calculating statistics for the table.
Information about the corrupted page was written repeatedly to
the error log, possibly causing a disk space issue. The fix
causes the server to halt after a fixed number of failed
attempts to read the page. To troubleshoot such a corruption
issue, set innodb_force_recovery=6 and restart. (Bug
#14147491, Bug #65469)
* InnoDB: When printing out long semaphore wait diagnostics,
sync_array_cell_print() ran into a segmentation violation
(SEGV) caused by a race condition. This fix addresses the race
condition by allowing the cell to be freed while it is being
printed. (Bug #13997024)
* InnoDB: Killing a query caused an InnoDB assertion failure
when the same table (cursor) instance was used again. This is
the result of a regression error introduced by the fix for
Bug#14704286. The fix introduced a check to handle kill
signals for long running queries but the cursor was not
restored to the proper state. (Bug #68051, Bug #16088883)
* InnoDB: On startup, InnoDB reported a message on 64-bit Linux
and 64-bit Windows systems stating that the CPU does not
support crc32 instructions. On Windows, InnoDB does not use
crc32 instructions even if supported by the CPU. This fix
revises the wording of the message and implements a check for
availability of crc32 instructions. (Bug #68035, Bug
#16075806)
* InnoDB: The length of internally generated foreign key names
was not checked. If internally generated foreign key names
were over the 64 character limit, this resulted in invalid DDL
from SHOW CREATE TABLE. This fix checks the length of
internally generated foreign key names and reports an error
message if the limit is exceeded. (Bug #44541, Bug #11753153)
* InnoDB: This fix removes left-over prototype code for
srv_parse_log_group_home_dirs, and related header comments.
(Bug #68133, Bug #16198764)
* InnoDB: Attempting to replace the default InnoDB FTS stopword
list by creating an InnoDB table with the same structure as
INFORMATION_SCHEMA.innodb_ft_default_stopword would result in
an error. SHOW CREATE TABLE revealed that the new InnoDB table
was created with CHARSET=utf8. The InnoDB FTS stopword table
validity check only supported latin1. This fix extends the
validity check for all supported character sets. (Bug #68450,
Bug #16373868)
* Partitioning: A query on a table partitioned by range and
using TO_DAYS() as a partitioing function always included the
first partition of the table when pruning. This happened
regardless of the range employed in the BETWEEN clause of such
a query. (Bug #15843818, Bug #49754)
* Partitioning: Partition pruning is now enabled for tables
using a storage engine that provides automatic partitioning,
such as the NDB storage engine, but which are explicitly
partitioned. Previously, pruning was disabled for all tables
using such a storage engine, whether or not the tables had
explicitly defined partitions.
In addition, as part of this fix, explicit partition selection
is now disabled for tables using a storage engine (such as
NDB) that provides automatic partitioning. (Bug #14827952)
References: See also Bug #14672885.
* Partitioning: Execution of ALTER TABLE ... DROP PARTITION
against a view caused the server to crash, rather than fail
with an error as expected. (Bug #14653504)
* Partitioning: A query result was not sorted if both DISTINCT
and ORDER BY were used and the underlying table was
partitioned. (Bug #14058167)
* Partitioning: Inserting any number of rows into an ARCHIVE
table that used more than 1000 partitions and then attempting
to drop the table caused the MySQL Server to fail. (Bug
#13819630, Bug #64580)
* Replication; Linux; Microsoft Windows: Replication failed
between a Linux master using lower_case_table_names set to 0
and a Windows slave having lower_case_table_names set to 2,
after a replicated table was opened on the slave; in addition,
FLUSH TABLES was required afterwards to see which updates had
actually been applied on the slave. This was because
lower_case_table_names was checked only to see whether it was
equal to 1 prior to forcing a conversion of replicated
database object names to lower case for checking the table
cache. Now in such cases, lower_case_table_names is checked to
see whether it is set to a nonzero value. (Bug #16061982)
* Replication: When using GTIDs and binary log auto-positioning,
the master had to scan all binary logs whenever the slave
reconnected (due to reasons such as I/O thread failure or a
change of master) before it could send any events to slave.
Now, the master starts from the oldest binary log that
contains any GTID not found on the slave. (Bug #16340322, Bug
#68386)
* Replication: When the server version of the master was greater
than or equal to 10, replication to a slave having a lower
server version failed. (Bug #16237051, Bug #68187)
* Replication: When replicating to a MySQL 5.6 master to an
older slave, Error 1193 (ER_UNKNOWN_SYSTEM_VARIABLE) was
logged with a message such as Unknown system variable
'SERVER_UUID' on master, maybe it is a *VERY OLD MASTER*. This
message has been improved to include more information, similar
to this one: Unknown system variable 'SERVER_UUID' on master.
A probable cause is that the variable is not supported on the
master (version: 5.5.31), even though it is on the slave
(version: 5.6.11). (Bug #16216404, Bug #68164)
* Replication: A zero-length name for a user variable (such as
@``) was incorrectly considered to be a sign of data or
network corruption when reading from the binary log. (Bug
#16200555, Bug #68135)
* Replication: Running SHOW RELAYLOG EVENTS at a slave where no
relay log file is present returned the following incorrect
error message: "Error when executing command SHOW BINLOG
EVENTS: Could not find target log." The error message text has
been changed to: "Error when executing command SHOW RELAYLOG
EVENTS: Could not find target log." (Bug #16191895)
* Replication: When MTS is on and transactions are being
applied, the slave coordinator would hang when encountering a
checksum error on a transaction event. This was due to a
deadlock situation in which the coordinator assumed a normal
stop while a worker waited for the coordinator to dispatch
more events. For debug builds, the problem appeared as an
assertion failure, which was due to the coordinator not
setting thd->is_error() when encountering an error. (Bug
#16210351)
* Replication: The print format specifier for the server_id was
incorrectly defined as a signed 32-bit integer with a range of
-2144783647 to 2144783648. This fix changes the server_id
integer type to an unsigned 32-bit integer type, with a range
of 0 to 4294967295, which is the documented range for the
--server-id option. (Bug #16210894)
* Replication: mysqlbinlog can connect to a remote server and
read its binary logs. In MySQL 5.6 and later, this tool can
also wait for the server to generate and send additional
events, in practice behaving like a slave connecting to a
master. In cases where the server sent a heartbeat,
mysqlbinlog was unable to handle it properly. As a
consequence, mysqlbinlog failed at this point, without reading
any more events from the server. To fix this problem,
mysqlbinlog now ignores any binary log events of type
HEARTBEAT_LOG_EVENT that it receives. (Bug #16104206)
* Replication: STOP SLAVE could cause a deadlock when issued
concurrently with a statement such as SHOW STATUS that
retrieved the values for one or more of the status variables
Slave_retried_transactions, Slave_heartbeat_period,
Slave_received_heartbeats, Slave_last_heartbeat, or
Slave_running. (Bug #16088188, Bug #67545)
References: See also Bug #16088114.
* Replication: Using the --replicate-* options (see Replication
Slave Options and Variables
(http://dev.mysql.com/doc/refman/5.7/en/replication-options-sl
ave.html)) could in some cases lead to a memory leak on the
slave. (Bug #16056813, Bug #67983)
* Replication: Backtick (`) characters were not always handled
correctly in internally generated SQL statements, which could
sometimes lead to errors on the slave. (Bug #16084594, Bug
#68045)
References: This bug is a regression of Bug #14548159, Bug
#66550.
* Replication: The session-level value for gtid_next was
incorrectly reset on the slave for all rollbacks, which meant
that GTIDs could be lost for multi-statement transactions,
causing the slave to stop with an
ER_GTID_NEXT_TYPE_UNDEFINED_GROUP error. Now this is done only
when a complete transaction is being rolled back, or when
autocommit is enabled. (Bug #16084206)
* Replication: In order to provision or to restore a server
using GTIDs, it is possible to set gtid_purged to a given GTID
set listing the transactions that were imported. This
operation requires that the global gtid_executed and
gtid_purged server system variables are empty. (This is done
in order to avoid the possibility of overriding
server-generated GTIDs.)
The error message GTID_PURGED can only be set when
GTID_EXECUTED is empty that was raised when this requirement
was not met could be confusing or misleading because it did
not specify the scope of the affected variables. To prevent
this from happening, error messages that refer to variables
relating to GTIDs now specify the scope of any such variables
when they do so. (Bug #16084426, Bug #68038)
=== END PART 1 ===
Part 2 will follow.