kpriv/pkgsrc
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
pkgsrc/databases/mysql56-server/PLIST

9772 lines
534 KiB
Text
Raw Normal View History

Changes 5.6.29: * InnoDB: A new InnoDB configuration option, innodb_tmpdir, allows you to configure a separate temporary file directory for online ALTER TABLE operations. This option was introduced to help avoid tmpdir overflows that could occur as a result of large temporary files created during online ALTER TABLE operations. innodb_tmpdir is a SESSION variable and can be configured dynamically using a SET statement. * yaSSL was upgraded to version 2.3.9. This upgrade corrects an issue in which yaSSL handled only cases of zero or one leading zeros for the key agreement instead of potentially any number, which in rare cases could cause connections to fail when using DHE cipher suites. * The Valgrind function signature in mysql-test/valgrind.supp was upgraded for Valgrind 3.11. * Bugs Fixed
2016-02-28 09:58:03 +01:00
@comment $NetBSD: PLIST,v 1.22 2016/02/28 08:58:03 adam Exp $
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
bin/innochecksum
bin/my_print_defaults
bin/myisam_ftdump
bin/myisamchk
bin/myisamlog
bin/myisampack
${PLIST.embedded}bin/mysql_client_test_embedded
${PLIST.embedded}bin/mysql_embedded
bin/mysql_tzinfo_to_sql
bin/mysql_waitpid
${PLIST.embedded}bin/mysqltest_embedded
bin/perror
bin/replace
bin/resolve_stack_dump
bin/resolveip
${PLIST.embedded}lib/libmysqld.a
lib/libmysqlservices.a
lib/mysql/plugin/adt_null.so
lib/mysql/plugin/auth.so
${PLIST.auth_socket}lib/mysql/plugin/auth_socket.so
lib/mysql/plugin/auth_test_plugin.so
lib/mysql/plugin/daemon_example.ini
Add optional Sphinx SE plugin support to MySQL 5.5 and 5.6. Intented as a clean implementation (replacement) of wip/mysql-sphinxse. SphinxSE is MySQL storage engine which can be compiled into MySQL server 5.x using its pluggable architecture. Despite the name, SphinxSE does not actually store any data itself. It is actually a built-in client which allows MySQL server to talk to searchd, run search queries, and obtain search results. All indexing and searching happen outside MySQL. See http://sphinxsearch.com/docs/current.html#sphinxse-overview
2014-10-17 19:07:44 +02:00
${PLIST.sphinx}lib/mysql/plugin/ha_sphinx.so
Add memcached option (disabled by default).
2015-08-20 14:24:45 +02:00
${PLIST.memcached}lib/mysql/plugin/innodb_engine.so
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
lib/mysql/plugin/libdaemon_example.so
Add memcached option (disabled by default).
2015-08-20 14:24:45 +02:00
${PLIST.memcached}lib/mysql/plugin/libmemcached.so
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
lib/mysql/plugin/mypluglib.so
Changes 5.6.24: * CMake support was updated to handle CMake version 3.1. * The server now includes its version number when it writes the initial “starting” message to the error log, to make it easier to tell which server instance error log output applies to. This value is the same as that available from the version system variable. * ALTER TABLE did not take advantage of fast alterations that might otherwise apply to the operation to be performed, if the table contained temporal columns found to be in pre-5.6.4 format (TIME, DATETIME, and TIMESTAMP columns without support for fractional seconds precision). * Statement digesting as done previously by the Performance Schema is now done at the SQL level regardless of whether the Performance Schema is compiled in and is available to other aspects of server operation that could benefit from it. The default space available for digesting is 1024 bytes, but can be changed at server startup using the max_digest_length system variable. * Bug fixes.
2015-04-08 12:38:48 +02:00
lib/mysql/plugin/mysql_no_login.so
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
lib/mysql/plugin/qa_auth_client.so
lib/mysql/plugin/qa_auth_interface.so
lib/mysql/plugin/qa_auth_server.so
lib/mysql/plugin/semisync_master.so
lib/mysql/plugin/semisync_slave.so
lib/mysql/plugin/validate_password.so
sbin/mysqld
share/aclocal/mysql.m4
share/doc/mysql/COPYING
share/doc/mysql/ChangeLog
share/doc/mysql/INFO_BIN
share/doc/mysql/INFO_SRC
share/doc/mysql/INSTALL-BINARY
share/doc/mysql/README
share/mysql/binary-configure
share/mysql/bulgarian/errmsg.sys
share/mysql/charsets/Index.xml
share/mysql/charsets/README
share/mysql/charsets/armscii8.xml
share/mysql/charsets/ascii.xml
share/mysql/charsets/cp1250.xml
share/mysql/charsets/cp1251.xml
share/mysql/charsets/cp1256.xml
share/mysql/charsets/cp1257.xml
share/mysql/charsets/cp850.xml
share/mysql/charsets/cp852.xml
share/mysql/charsets/cp866.xml
share/mysql/charsets/dec8.xml
share/mysql/charsets/geostd8.xml
share/mysql/charsets/greek.xml
share/mysql/charsets/hebrew.xml
share/mysql/charsets/hp8.xml
share/mysql/charsets/keybcs2.xml
share/mysql/charsets/koi8r.xml
share/mysql/charsets/koi8u.xml
share/mysql/charsets/latin1.xml
share/mysql/charsets/latin2.xml
share/mysql/charsets/latin5.xml
share/mysql/charsets/latin7.xml
share/mysql/charsets/macce.xml
share/mysql/charsets/macroman.xml
share/mysql/charsets/swe7.xml
share/mysql/czech/errmsg.sys
share/mysql/danish/errmsg.sys
share/mysql/dictionary.txt
share/mysql/dutch/errmsg.sys
share/mysql/english/errmsg.sys
share/mysql/errmsg-utf8.txt
share/mysql/estonian/errmsg.sys
share/mysql/french/errmsg.sys
share/mysql/german/errmsg.sys
share/mysql/greek/errmsg.sys
share/mysql/hungarian/errmsg.sys
share/mysql/innodb_memcached_config.sql
share/mysql/italian/errmsg.sys
share/mysql/japanese/errmsg.sys
share/mysql/korean/errmsg.sys
share/mysql/magic
share/mysql/my-default.cnf
share/mysql/mysql-log-rotate
share/mysql/mysql.server
share/mysql/mysqld_multi.server
share/mysql/norwegian-ny/errmsg.sys
share/mysql/norwegian/errmsg.sys
share/mysql/polish/errmsg.sys
share/mysql/portuguese/errmsg.sys
share/mysql/romanian/errmsg.sys
share/mysql/russian/errmsg.sys
share/mysql/serbian/errmsg.sys
share/mysql/slovak/errmsg.sys
share/mysql/spanish/errmsg.sys
share/mysql/sql-bench/sql-bench/Data/ATIS/aircraft.txt
share/mysql/sql-bench/sql-bench/Data/ATIS/airline.txt
share/mysql/sql-bench/sql-bench/Data/ATIS/airport.txt
share/mysql/sql-bench/sql-bench/Data/ATIS/airport_service.txt
share/mysql/sql-bench/sql-bench/Data/ATIS/city.txt
share/mysql/sql-bench/sql-bench/Data/ATIS/class_of_service.txt
share/mysql/sql-bench/sql-bench/Data/ATIS/code_description.txt
share/mysql/sql-bench/sql-bench/Data/ATIS/compound_class.txt
share/mysql/sql-bench/sql-bench/Data/ATIS/connect_leg.txt
share/mysql/sql-bench/sql-bench/Data/ATIS/date_day.txt
share/mysql/sql-bench/sql-bench/Data/ATIS/day_name.txt
share/mysql/sql-bench/sql-bench/Data/ATIS/dual_carrier.txt
share/mysql/sql-bench/sql-bench/Data/ATIS/fare.txt
share/mysql/sql-bench/sql-bench/Data/ATIS/fconnection.txt
share/mysql/sql-bench/sql-bench/Data/ATIS/flight.txt
share/mysql/sql-bench/sql-bench/Data/ATIS/flight_class.txt
share/mysql/sql-bench/sql-bench/Data/ATIS/flight_day.txt
share/mysql/sql-bench/sql-bench/Data/ATIS/flight_fare.txt
share/mysql/sql-bench/sql-bench/Data/ATIS/food_service.txt
share/mysql/sql-bench/sql-bench/Data/ATIS/ground_service.txt
share/mysql/sql-bench/sql-bench/Data/ATIS/month_name.txt
share/mysql/sql-bench/sql-bench/Data/ATIS/restrict_carrier.txt
share/mysql/sql-bench/sql-bench/Data/ATIS/restrict_class.txt
share/mysql/sql-bench/sql-bench/Data/ATIS/restriction.txt
share/mysql/sql-bench/sql-bench/Data/ATIS/state.txt
share/mysql/sql-bench/sql-bench/Data/ATIS/stop.txt
share/mysql/sql-bench/sql-bench/Data/ATIS/stop1.txt
share/mysql/sql-bench/sql-bench/Data/ATIS/time_interval.txt
share/mysql/sql-bench/sql-bench/Data/ATIS/time_zone.txt
share/mysql/sql-bench/sql-bench/Data/ATIS/transport.txt
share/mysql/sql-bench/sql-bench/Data/Wisconsin/onek.data
share/mysql/sql-bench/sql-bench/Data/Wisconsin/tenk.data
share/mysql/sql-bench/sql-bench/README
share/mysql/sql-bench/sql-bench/bench-count-distinct
share/mysql/sql-bench/sql-bench/bench-init.pl
share/mysql/sql-bench/sql-bench/compare-results
share/mysql/sql-bench/sql-bench/copy-db
share/mysql/sql-bench/sql-bench/crash-me
share/mysql/sql-bench/sql-bench/graph-compare-results
share/mysql/sql-bench/sql-bench/innotest1
share/mysql/sql-bench/sql-bench/innotest1a
share/mysql/sql-bench/sql-bench/innotest1b
share/mysql/sql-bench/sql-bench/innotest2
share/mysql/sql-bench/sql-bench/innotest2a
share/mysql/sql-bench/sql-bench/innotest2b
share/mysql/sql-bench/sql-bench/limits/Adabas.cfg
share/mysql/sql-bench/sql-bench/limits/Informix.cfg
share/mysql/sql-bench/sql-bench/limits/access.cfg
share/mysql/sql-bench/sql-bench/limits/access_odbc.cfg
share/mysql/sql-bench/sql-bench/limits/db2.cfg
share/mysql/sql-bench/sql-bench/limits/empress.cfg
share/mysql/sql-bench/sql-bench/limits/frontbase.cfg
share/mysql/sql-bench/sql-bench/limits/interbase-dialect1.cfg
share/mysql/sql-bench/sql-bench/limits/interbase-dialect3.cfg
share/mysql/sql-bench/sql-bench/limits/interbase-superserver.cfg
share/mysql/sql-bench/sql-bench/limits/interbase.cfg
share/mysql/sql-bench/sql-bench/limits/mimer.cfg
share/mysql/sql-bench/sql-bench/limits/ms-sql.cfg
share/mysql/sql-bench/sql-bench/limits/ms-sql65.cfg
share/mysql/sql-bench/sql-bench/limits/msql.cfg
share/mysql/sql-bench/sql-bench/limits/mysql-3.22.cfg
share/mysql/sql-bench/sql-bench/limits/mysql-3.23.cfg
share/mysql/sql-bench/sql-bench/limits/mysql-4.0.cfg
share/mysql/sql-bench/sql-bench/limits/mysql-4.1.cfg
share/mysql/sql-bench/sql-bench/limits/mysql.cfg
share/mysql/sql-bench/sql-bench/limits/oracle.cfg
share/mysql/sql-bench/sql-bench/limits/pg.cfg
share/mysql/sql-bench/sql-bench/limits/solid-nt4.cfg
share/mysql/sql-bench/sql-bench/limits/solid.cfg
share/mysql/sql-bench/sql-bench/limits/sybase.cfg
share/mysql/sql-bench/sql-bench/run-all-tests
share/mysql/sql-bench/sql-bench/server-cfg
share/mysql/sql-bench/sql-bench/test-ATIS
share/mysql/sql-bench/sql-bench/test-alter-table
share/mysql/sql-bench/sql-bench/test-big-tables
share/mysql/sql-bench/sql-bench/test-connect
share/mysql/sql-bench/sql-bench/test-create
share/mysql/sql-bench/sql-bench/test-insert
share/mysql/sql-bench/sql-bench/test-select
share/mysql/sql-bench/sql-bench/test-transactions
share/mysql/sql-bench/sql-bench/test-wisconsin
share/mysql/swedish/errmsg.sys
share/mysql/test/README
share/mysql/test/README.gcov
share/mysql/test/README.stress
share/mysql/test/collections/README
share/mysql/test/collections/README.experimental
share/mysql/test/collections/default.daily
Changes 5.6.13: * Important Change; Replication: By default, when promoting integers from a smaller type on the master to a larger type on the slave (for example, from a SMALLINT column on the master to a BIGINT column on the slave), the promoted values are treated as though they are signed. Now in such cases it is possible to modify or override this behavior using one or both of ALL_SIGNED, ALL_UNSIGNED in the set of values specified for the slave_type_conversions server system variable. For more information, see Row-based replication: attribute promotion and demotion, as well as the description of the variable. * Previously, program options could be specified in full or as any unambiguous prefix. For example, the --compress option could be given to mysqldump as --compr, but not as --comp because the latter is ambiguous. Option prefixes now are deprecated. They can cause problems when new options are implemented for programs. A prefix that is currently unambiguous might become ambiguous in the future. If an unambiguous prefix is given, a warning now occurs to provide feedback. For example: Warning: Using unique option prefix compr instead of compress is deprecated and will be removed in a future release. Please use the full name instead. Option prefixes are no longer supported in MySQL 5.7; only full options are accepted. * The C API libmysqlclient shared-library .so files now have version 18.1.0 (up from version 18.0.0 used in MySQL 5.5). * In batch mode, mysql formatted result status messages such as “"Query OK, 1 row affected"” but did not print them. Now these messages are not formatted. * Bugs Fixed
2013-07-31 11:51:38 +02:00
share/mysql/test/collections/default.daily-valgrind
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/collections/default.experimental
share/mysql/test/collections/default.push
Changes 5.6.13: * Important Change; Replication: By default, when promoting integers from a smaller type on the master to a larger type on the slave (for example, from a SMALLINT column on the master to a BIGINT column on the slave), the promoted values are treated as though they are signed. Now in such cases it is possible to modify or override this behavior using one or both of ALL_SIGNED, ALL_UNSIGNED in the set of values specified for the slave_type_conversions server system variable. For more information, see Row-based replication: attribute promotion and demotion, as well as the description of the variable. * Previously, program options could be specified in full or as any unambiguous prefix. For example, the --compress option could be given to mysqldump as --compr, but not as --comp because the latter is ambiguous. Option prefixes now are deprecated. They can cause problems when new options are implemented for programs. A prefix that is currently unambiguous might become ambiguous in the future. If an unambiguous prefix is given, a warning now occurs to provide feedback. For example: Warning: Using unique option prefix compr instead of compress is deprecated and will be removed in a future release. Please use the full name instead. Option prefixes are no longer supported in MySQL 5.7; only full options are accepted. * The C API libmysqlclient shared-library .so files now have version 18.1.0 (up from version 18.0.0 used in MySQL 5.5). * In batch mode, mysql formatted result status messages such as “"Query OK, 1 row affected"” but did not print them. Now these messages are not formatted. * Bugs Fixed
2013-07-31 11:51:38 +02:00
share/mysql/test/collections/default.push-valgrind
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/collections/default.release
share/mysql/test/collections/default.release.done
share/mysql/test/collections/default.weekly
Changes 5.6.13: * Important Change; Replication: By default, when promoting integers from a smaller type on the master to a larger type on the slave (for example, from a SMALLINT column on the master to a BIGINT column on the slave), the promoted values are treated as though they are signed. Now in such cases it is possible to modify or override this behavior using one or both of ALL_SIGNED, ALL_UNSIGNED in the set of values specified for the slave_type_conversions server system variable. For more information, see Row-based replication: attribute promotion and demotion, as well as the description of the variable. * Previously, program options could be specified in full or as any unambiguous prefix. For example, the --compress option could be given to mysqldump as --compr, but not as --comp because the latter is ambiguous. Option prefixes now are deprecated. They can cause problems when new options are implemented for programs. A prefix that is currently unambiguous might become ambiguous in the future. If an unambiguous prefix is given, a warning now occurs to provide feedback. For example: Warning: Using unique option prefix compr instead of compress is deprecated and will be removed in a future release. Please use the full name instead. Option prefixes are no longer supported in MySQL 5.7; only full options are accepted. * The C API libmysqlclient shared-library .so files now have version 18.1.0 (up from version 18.0.0 used in MySQL 5.5). * In batch mode, mysql formatted result status messages such as “"Query OK, 1 row affected"” but did not print them. Now these messages are not formatted. * Bugs Fixed
2013-07-31 11:51:38 +02:00
share/mysql/test/collections/default.weekly-valgrind
Changes 5.6.15: * Previously, MySQL Server distributions included the MySQL Reference Manual in Info format (the Docs/mysql.info file). Because the license for the manual restricts redistribution, its inclusion in Community packages caused problems for downstream redistributors, such as those who create Linux distributions. Community distributions of MySQL Server no longer include the mysql.info file, to make the repackaging and redistribution process easier (for example, the source tarball and its checksum can be used directly). This change applies to all source and binary Community packaging formats. Commercial (Enterprise) distributions are unchanged. * Incompatible Change: Several statement instruments in the setup_instruments table are used by the Performance Schema during the early stages of statement classification before the exact statement type is known. * The Performance Schema now instruments the read/write lock Delegate::lock * A new CMake option, WITH_ASAN, permits enabling address sanitization for compilers that support it. * The hash function used for metadata locking was modified to reduce overhead. * Bugs Fixed
2013-12-03 21:02:41 +01:00
share/mysql/test/collections/default.weekly.basic
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/collections/disabled-daily.list
share/mysql/test/collections/disabled-gtid-on.list
share/mysql/test/collections/disabled-per-push.list
share/mysql/test/collections/disabled-weekly.list
share/mysql/test/extra/binlog_tests/binlog.test
share/mysql/test/extra/binlog_tests/binlog_cache_stat.test
Changes 5.6.11: 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. 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. mysql_config_editor now supports --port and --socket options for specifying TCP/IP port number and Unix socket file name. 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. The only supported value for the innodb_mirrored_log_groups system variable is 1, so this variable is now deprecated. Setting it to 1 at startup results in a warning. Setting it to a value other than 1 at startup results in an error and the server exits. This variable will be removed in a future release.
2013-04-20 10:06:01 +02:00
share/mysql/test/extra/binlog_tests/binlog_implicit_commit.inc
share/mysql/test/extra/binlog_tests/binlog_innodb.inc
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/extra/binlog_tests/binlog_insert_delayed.test
Changes 5.6.20: Security Fix: The linked OpenSSL library for the MySQL 5.6 Commercial Server has been updated from version 1.0.1g to version 1.0.1h. Versions of OpenSSL prior to and including 1.0.1g are reported to be vulnerable to CVE-2014-0224. This change does not affect the Oracle-produced MySQL Community build of MySQL Server 5.6, which uses the yaSSL library instead. DTrace Support MySQL now includes DTrace support on Oracle Linux 6 or higher with UEK kernel. If DTrace is present, server builds will detect it with no special CMake options required. For information about using DTrace on MySQL, see Tracing mysqld Using DTrace. InnoDB Notes Important Change: Redo log writes for large, externally stored BLOB fields could overwrite the most recent checkpoint. The 5.6.20 patch limits the size of redo log BLOB writes to 10% of the redo log file size. The 5.7.5 patch addresses the bug without imposing a limitation. For MySQL 5.5, the bug remains a known limitation. As a result of the redo log BLOB write limit introduced for MySQL 5.6, innodb_log_file_size should be set to a value greater than 10 times the largest BLOB data size found in the rows of your tables plus the length of other variable length fields (VARCHAR, VARBINARY, and TEXT type fields). Failing to do so could result in “Row size too large” errors. No action is required if your innodb_log_file_size setting is already sufficiently large or your tables contain no BLOB data. Functionality Added or Changed Replication: The new system variable binlog_impossible_mode controls what happens if the server cannot write to the binary log, for example, due to a file error. For backward compatibility, the default for binlog_impossible_mode is IGNORE_ERROR, meaning the server logs the error, halts logging, and continues updates to the database. Setting this variable to ABORT_SERVER makes the server halt logging and shut down if it cannot write to the binary log. CMake support was updated to handle CMake version 3. New Debian7, Ubuntu12.04, and Ubuntu14.04 distribution support that was introduced with 5.6.17 now comes with the platform-specific packaging source placed under the packaging directory, in the deb-precise, deb-wheezy, and deb-trusty directories. Support for LinuxThreads has been removed from the source code. LinuxThreads was superseded by NPTL in Linux 2.6. By default, mysql_install_db creates a my.cnf file in the installation base directory using a template. This may be undesireable for some deployments. To enable this behavior to be suppressed, mysql_install_db now supports a --keep-my-cnf option to preserve any existing my.cnf file and not create a new my.cnf file. The mysqlhotcopy utility is now deprecated and will be removed in a future version of MySQL. Among the reasons for this: It works only for the MyISAM and ARCHIVE storage engines; it works on Unix but not Windows. Alternatives include mysqldump and MySQL Enterprise Backup. The timed_mutexes system variable has no effect and is deprecated. Bugs Fixed
2014-08-10 17:11:57 +02:00
share/mysql/test/extra/binlog_tests/binlog_mysqlbinlog_fill.inc
Changes 5.6.11: 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. 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. mysql_config_editor now supports --port and --socket options for specifying TCP/IP port number and Unix socket file name. 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. The only supported value for the innodb_mirrored_log_groups system variable is 1, so this variable is now deprecated. Setting it to 1 at startup results in a warning. Setting it to a value other than 1 at startup results in an error and the server exits. This variable will be removed in a future release.
2013-04-20 10:06:01 +02:00
share/mysql/test/extra/binlog_tests/binlog_mysqlbinlog_row.inc
share/mysql/test/extra/binlog_tests/binlog_mysqlbinlog_start_stop.inc
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/extra/binlog_tests/binlog_truncate.test
share/mysql/test/extra/binlog_tests/blackhole.test
share/mysql/test/extra/binlog_tests/ctype_cp932.test
share/mysql/test/extra/binlog_tests/ctype_cp932_binlog.test
share/mysql/test/extra/binlog_tests/ctype_ucs_binlog.test
share/mysql/test/extra/binlog_tests/database.test
share/mysql/test/extra/binlog_tests/drop_table.test
share/mysql/test/extra/binlog_tests/drop_temp_table.test
share/mysql/test/extra/binlog_tests/implicit.test
share/mysql/test/extra/binlog_tests/insert_select-binlog.test
share/mysql/test/extra/binlog_tests/mix_innodb_myisam_binlog.test
share/mysql/test/extra/binlog_tests/mix_innodb_myisam_side_effects.test
share/mysql/test/extra/binlog_tests/mysqlbinlog_row_engine.inc
share/mysql/test/extra/binlog_tests/mysqlbinlog_start_stop_1.inc
share/mysql/test/extra/binlog_tests/mysqlbinlog_start_stop_2.inc
share/mysql/test/extra/rpl_tests/check_type.inc
share/mysql/test/extra/rpl_tests/create_recursive_construct.inc
share/mysql/test/extra/rpl_tests/delayed_slave_wait_on_query.inc
Changes 5.6.17: Functionality Added or Changed Incompatible Change: The AES_ENCRYPT() and AES_DECRYPT() functions now permit control of the block encryption mode and take an optional initialization vector argument: The new block_encryption_mode system variable controls the mode for block-based encryption algorithms. Its default value is aes-128-ecb, which signifies encryption using a key length of 128 bits and ECB mode. An optional init_vector argument provides an initialization vector for encryption modes that require it: AES_ENCRYPT(str,key_str[,init_vector]) AES_DECRYPT(crypt_str,key_str[,init_vector]) A random string of bytes to use for the initialization vector can be produced by calling the new RANDOM_BYTES() function. For more information, see Encryption and Compression Functions. These changes make statements that use AES_ENCRYPT() or AES_DECRYPT() unsafe for statement-based replication and they cannot be stored in the query cache. Queries that use RANDOM_BYTES() are unsafe for statement-based replication and cannot be stored in the query cache. Incompatible Change: The ERROR_FOR_DIVISION_BY_ZERO, NO_ZERO_DATE, and NO_ZERO_IN_DATE SQL modes now are deprecated and setting the sql_mode value to include any of them generates a warning. In MySQL 5.7, these modes do nothing. Instead, their effects are included in the effects of strict SQL mode (STRICT_ALL_TABLES or STRICT_TRANS_TABLES). The motivation for the change in MySQL 5.7 is to reduce the number of SQL modes with an effect dependent on strict mode and make them part of strict mode itself. To make advance preparation for an upgrade to MySQL 5.7, see SQL Mode Changes in MySQL 5.7. That discussion provides guidelines to assess whether your applications will be affected by the SQL mode changes in MySQL 5.7. InnoDB: MySQL now supports rebuilding regular and partitioned InnoDB tables using online DDL (ALGORITHM=INPLACE) for the following operations: OPTIMIZE TABLE ALTER TABLE ... FORCE ALTER TABLE ... ENGINE=INNODB (when run on an InnoDB table) Online DDL support reduces table rebuild time and permits concurrent DML, which helps reduce user application downtime. For additional information, see Overview of Online DDL. On Solaris, mysql_config --libs now includes -R/path/to/library so that libraries can be found at runtime. mysql_install_db provides a more informative diagnostic message when required Perl modules are missing. The IGNORE clause for ALTER TABLE is now deprecated and will be removed in a future version of MySQL. ALTER IGNORE TABLE causes problems for replication, prevents online ALTER TABLE for unique index creation, and causes problems with foreign keys (rows removed in the parent table). Bugs Fixed
2014-03-31 12:32:13 +02:00
share/mysql/test/extra/rpl_tests/grep_pattern.inc
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/extra/rpl_tests/rpl_EE_err.test
share/mysql/test/extra/rpl_tests/rpl_auto_increment.test
share/mysql/test/extra/rpl_tests/rpl_auto_increment_insert_view.test
share/mysql/test/extra/rpl_tests/rpl_auto_increment_invoke_trigger.test
share/mysql/test/extra/rpl_tests/rpl_autoinc_func_invokes_trigger.test
Changes 5.6.17: Functionality Added or Changed Incompatible Change: The AES_ENCRYPT() and AES_DECRYPT() functions now permit control of the block encryption mode and take an optional initialization vector argument: The new block_encryption_mode system variable controls the mode for block-based encryption algorithms. Its default value is aes-128-ecb, which signifies encryption using a key length of 128 bits and ECB mode. An optional init_vector argument provides an initialization vector for encryption modes that require it: AES_ENCRYPT(str,key_str[,init_vector]) AES_DECRYPT(crypt_str,key_str[,init_vector]) A random string of bytes to use for the initialization vector can be produced by calling the new RANDOM_BYTES() function. For more information, see Encryption and Compression Functions. These changes make statements that use AES_ENCRYPT() or AES_DECRYPT() unsafe for statement-based replication and they cannot be stored in the query cache. Queries that use RANDOM_BYTES() are unsafe for statement-based replication and cannot be stored in the query cache. Incompatible Change: The ERROR_FOR_DIVISION_BY_ZERO, NO_ZERO_DATE, and NO_ZERO_IN_DATE SQL modes now are deprecated and setting the sql_mode value to include any of them generates a warning. In MySQL 5.7, these modes do nothing. Instead, their effects are included in the effects of strict SQL mode (STRICT_ALL_TABLES or STRICT_TRANS_TABLES). The motivation for the change in MySQL 5.7 is to reduce the number of SQL modes with an effect dependent on strict mode and make them part of strict mode itself. To make advance preparation for an upgrade to MySQL 5.7, see SQL Mode Changes in MySQL 5.7. That discussion provides guidelines to assess whether your applications will be affected by the SQL mode changes in MySQL 5.7. InnoDB: MySQL now supports rebuilding regular and partitioned InnoDB tables using online DDL (ALGORITHM=INPLACE) for the following operations: OPTIMIZE TABLE ALTER TABLE ... FORCE ALTER TABLE ... ENGINE=INNODB (when run on an InnoDB table) Online DDL support reduces table rebuild time and permits concurrent DML, which helps reduce user application downtime. For additional information, see Overview of Online DDL. On Solaris, mysql_config --libs now includes -R/path/to/library so that libraries can be found at runtime. mysql_install_db provides a more informative diagnostic message when required Perl modules are missing. The IGNORE clause for ALTER TABLE is now deprecated and will be removed in a future version of MySQL. ALTER IGNORE TABLE causes problems for replication, prevents online ALTER TABLE for unique index creation, and causes problems with foreign keys (rows removed in the parent table). Bugs Fixed
2014-03-31 12:32:13 +02:00
share/mysql/test/extra/rpl_tests/rpl_binlog_error.inc
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/extra/rpl_tests/rpl_binlog_max_cache_size.test
share/mysql/test/extra/rpl_tests/rpl_blackhole.test
share/mysql/test/extra/rpl_tests/rpl_change_master.test
share/mysql/test/extra/rpl_tests/rpl_change_master_bind.inc
share/mysql/test/extra/rpl_tests/rpl_charset.test
share/mysql/test/extra/rpl_tests/rpl_check_gtid.inc
share/mysql/test/extra/rpl_tests/rpl_commit_after_flush.test
share/mysql/test/extra/rpl_tests/rpl_conflicts.test
share/mysql/test/extra/rpl_tests/rpl_crash_safe.inc
share/mysql/test/extra/rpl_tests/rpl_crash_safe.test
share/mysql/test/extra/rpl_tests/rpl_ddl.test
share/mysql/test/extra/rpl_tests/rpl_deadlock.test
share/mysql/test/extra/rpl_tests/rpl_delete_no_where.test
Changes 5.6.17: Functionality Added or Changed Incompatible Change: The AES_ENCRYPT() and AES_DECRYPT() functions now permit control of the block encryption mode and take an optional initialization vector argument: The new block_encryption_mode system variable controls the mode for block-based encryption algorithms. Its default value is aes-128-ecb, which signifies encryption using a key length of 128 bits and ECB mode. An optional init_vector argument provides an initialization vector for encryption modes that require it: AES_ENCRYPT(str,key_str[,init_vector]) AES_DECRYPT(crypt_str,key_str[,init_vector]) A random string of bytes to use for the initialization vector can be produced by calling the new RANDOM_BYTES() function. For more information, see Encryption and Compression Functions. These changes make statements that use AES_ENCRYPT() or AES_DECRYPT() unsafe for statement-based replication and they cannot be stored in the query cache. Queries that use RANDOM_BYTES() are unsafe for statement-based replication and cannot be stored in the query cache. Incompatible Change: The ERROR_FOR_DIVISION_BY_ZERO, NO_ZERO_DATE, and NO_ZERO_IN_DATE SQL modes now are deprecated and setting the sql_mode value to include any of them generates a warning. In MySQL 5.7, these modes do nothing. Instead, their effects are included in the effects of strict SQL mode (STRICT_ALL_TABLES or STRICT_TRANS_TABLES). The motivation for the change in MySQL 5.7 is to reduce the number of SQL modes with an effect dependent on strict mode and make them part of strict mode itself. To make advance preparation for an upgrade to MySQL 5.7, see SQL Mode Changes in MySQL 5.7. That discussion provides guidelines to assess whether your applications will be affected by the SQL mode changes in MySQL 5.7. InnoDB: MySQL now supports rebuilding regular and partitioned InnoDB tables using online DDL (ALGORITHM=INPLACE) for the following operations: OPTIMIZE TABLE ALTER TABLE ... FORCE ALTER TABLE ... ENGINE=INNODB (when run on an InnoDB table) Online DDL support reduces table rebuild time and permits concurrent DML, which helps reduce user application downtime. For additional information, see Overview of Online DDL. On Solaris, mysql_config --libs now includes -R/path/to/library so that libraries can be found at runtime. mysql_install_db provides a more informative diagnostic message when required Perl modules are missing. The IGNORE clause for ALTER TABLE is now deprecated and will be removed in a future version of MySQL. ALTER IGNORE TABLE causes problems for replication, prevents online ALTER TABLE for unique index creation, and causes problems with foreign keys (rows removed in the parent table). Bugs Fixed
2014-03-31 12:32:13 +02:00
share/mysql/test/extra/rpl_tests/rpl_do_table_filter_insensitive.inc
share/mysql/test/extra/rpl_tests/rpl_do_table_filter_sensitive.inc
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/extra/rpl_tests/rpl_drop_create_temp_table.inc
share/mysql/test/extra/rpl_tests/rpl_drop_create_temp_table.test
share/mysql/test/extra/rpl_tests/rpl_extra_col_master.test
share/mysql/test/extra/rpl_tests/rpl_extra_col_slave.test
share/mysql/test/extra/rpl_tests/rpl_failed_optimize.test
share/mysql/test/extra/rpl_tests/rpl_filters.test
share/mysql/test/extra/rpl_tests/rpl_flsh_tbls.test
share/mysql/test/extra/rpl_tests/rpl_foreign_key.test
share/mysql/test/extra/rpl_tests/rpl_get_master_version_and_clock.test
Changes 5.6.20: Security Fix: The linked OpenSSL library for the MySQL 5.6 Commercial Server has been updated from version 1.0.1g to version 1.0.1h. Versions of OpenSSL prior to and including 1.0.1g are reported to be vulnerable to CVE-2014-0224. This change does not affect the Oracle-produced MySQL Community build of MySQL Server 5.6, which uses the yaSSL library instead. DTrace Support MySQL now includes DTrace support on Oracle Linux 6 or higher with UEK kernel. If DTrace is present, server builds will detect it with no special CMake options required. For information about using DTrace on MySQL, see Tracing mysqld Using DTrace. InnoDB Notes Important Change: Redo log writes for large, externally stored BLOB fields could overwrite the most recent checkpoint. The 5.6.20 patch limits the size of redo log BLOB writes to 10% of the redo log file size. The 5.7.5 patch addresses the bug without imposing a limitation. For MySQL 5.5, the bug remains a known limitation. As a result of the redo log BLOB write limit introduced for MySQL 5.6, innodb_log_file_size should be set to a value greater than 10 times the largest BLOB data size found in the rows of your tables plus the length of other variable length fields (VARCHAR, VARBINARY, and TEXT type fields). Failing to do so could result in “Row size too large” errors. No action is required if your innodb_log_file_size setting is already sufficiently large or your tables contain no BLOB data. Functionality Added or Changed Replication: The new system variable binlog_impossible_mode controls what happens if the server cannot write to the binary log, for example, due to a file error. For backward compatibility, the default for binlog_impossible_mode is IGNORE_ERROR, meaning the server logs the error, halts logging, and continues updates to the database. Setting this variable to ABORT_SERVER makes the server halt logging and shut down if it cannot write to the binary log. CMake support was updated to handle CMake version 3. New Debian7, Ubuntu12.04, and Ubuntu14.04 distribution support that was introduced with 5.6.17 now comes with the platform-specific packaging source placed under the packaging directory, in the deb-precise, deb-wheezy, and deb-trusty directories. Support for LinuxThreads has been removed from the source code. LinuxThreads was superseded by NPTL in Linux 2.6. By default, mysql_install_db creates a my.cnf file in the installation base directory using a template. This may be undesireable for some deployments. To enable this behavior to be suppressed, mysql_install_db now supports a --keep-my-cnf option to preserve any existing my.cnf file and not create a new my.cnf file. The mysqlhotcopy utility is now deprecated and will be removed in a future version of MySQL. Among the reasons for this: It works only for the MyISAM and ARCHIVE storage engines; it works on Unix but not Windows. Alternatives include mysqldump and MySQL Enterprise Backup. The timed_mutexes system variable has no effect and is deprecated. Bugs Fixed
2014-08-10 17:11:57 +02:00
share/mysql/test/extra/rpl_tests/rpl_gtid_drop_table.inc
Changes 5.6.26: * Security Fix: Due to the LogJam issue (https://weakdh.org/), OpenSSL has changed the Diffie-Hellman key length parameters for openssl-1.0.1n and up. * Replication: When using a multi-threaded slave, each worker thread has its own queue of transactions to process. In previous MySQL versions, STOP SLAVE waited for all workers to process their entire queue. This logic has been changed so that STOP SLAVE first finds the newest transaction that was committed by any worker thread. Then, it waits for all workers to complete transactions older than that. Newer transactions are not processed. The new logic allows STOP SLAVE to complete faster in case some worker queues contain multiple transactions. * Previously, the max_digest_length system variable controlled the maximum digest length for all server functions that computed statement digests. However, whereas the Performance Schema may need to maintain many digest values, other server functions such as MySQL Enterprise Firewall need only one digest per session. Increasing the max_digest_length value has little impact on total memory requirements for those functions, but can increase Performance Schema memory requirements significantly. To enable configuring digest length separately for the Performance Schema, its digest length is now controlled by the new performance_schema_max_digest_length system variable. * Previously, changes to the validate_password plugin dictionary file (named by the validate_password_dictionary_file system variable) while the server was running required a restart for the server to recognize the changes. Now validate_password_dictionary_file can be set at runtime and assigning a value causes the named file to be read without a restart. In addition, two new status variables are available. validate_password_dictionary_file_last_parsed indicates when the dictionary file was last read, and validate_password_dictionary_file_words_count indicates how many words it contains. * Bugs fixed
2015-07-30 16:39:18 +02:00
share/mysql/test/extra/rpl_tests/rpl_gtid_mts_relay_log_recovery.test
Changes 5.6.29: * InnoDB: A new InnoDB configuration option, innodb_tmpdir, allows you to configure a separate temporary file directory for online ALTER TABLE operations. This option was introduced to help avoid tmpdir overflows that could occur as a result of large temporary files created during online ALTER TABLE operations. innodb_tmpdir is a SESSION variable and can be configured dynamically using a SET statement. * yaSSL was upgraded to version 2.3.9. This upgrade corrects an issue in which yaSSL handled only cases of zero or one leading zeros for the key agreement instead of potentially any number, which in rare cases could cause connections to fail when using DHE cipher suites. * The Valgrind function signature in mysql-test/valgrind.supp was upgraded for Valgrind 3.11. * Bugs Fixed
2016-02-28 09:58:03 +01:00
share/mysql/test/extra/rpl_tests/rpl_gtid_temp_table_in_func_or_trigger.inc
Changes 5.6.21: The --skip-innodb option is now deprecated and its use results in a warning. It will be removed in a future MySQL release. This also applies to its synonyms (--innodb=OFF, --disable-innodb, and so forth). MySQL Enterprise Edition now includes a set of encryption functions based on the OpenSSL library that expose OpenSSL capabilities at the SQL level. Replication: The new variable simplified_binlog_gtid_recovery can be used to change the way binary log files are searched for previous GTIDs during recovery, speeding up the process when a large number of binary log files exist. Internally, spatial data types such as Geometry are represented as BLOB values, so when invoked with the --hex-blob option, mysqldump now displays spatial values in hex. Bugs Fixed...
2014-10-01 10:34:23 +02:00
share/mysql/test/extra/rpl_tests/rpl_gtids_restart_slave_io_lost_trx.test
Changes 5.6.17: Functionality Added or Changed Incompatible Change: The AES_ENCRYPT() and AES_DECRYPT() functions now permit control of the block encryption mode and take an optional initialization vector argument: The new block_encryption_mode system variable controls the mode for block-based encryption algorithms. Its default value is aes-128-ecb, which signifies encryption using a key length of 128 bits and ECB mode. An optional init_vector argument provides an initialization vector for encryption modes that require it: AES_ENCRYPT(str,key_str[,init_vector]) AES_DECRYPT(crypt_str,key_str[,init_vector]) A random string of bytes to use for the initialization vector can be produced by calling the new RANDOM_BYTES() function. For more information, see Encryption and Compression Functions. These changes make statements that use AES_ENCRYPT() or AES_DECRYPT() unsafe for statement-based replication and they cannot be stored in the query cache. Queries that use RANDOM_BYTES() are unsafe for statement-based replication and cannot be stored in the query cache. Incompatible Change: The ERROR_FOR_DIVISION_BY_ZERO, NO_ZERO_DATE, and NO_ZERO_IN_DATE SQL modes now are deprecated and setting the sql_mode value to include any of them generates a warning. In MySQL 5.7, these modes do nothing. Instead, their effects are included in the effects of strict SQL mode (STRICT_ALL_TABLES or STRICT_TRANS_TABLES). The motivation for the change in MySQL 5.7 is to reduce the number of SQL modes with an effect dependent on strict mode and make them part of strict mode itself. To make advance preparation for an upgrade to MySQL 5.7, see SQL Mode Changes in MySQL 5.7. That discussion provides guidelines to assess whether your applications will be affected by the SQL mode changes in MySQL 5.7. InnoDB: MySQL now supports rebuilding regular and partitioned InnoDB tables using online DDL (ALGORITHM=INPLACE) for the following operations: OPTIMIZE TABLE ALTER TABLE ... FORCE ALTER TABLE ... ENGINE=INNODB (when run on an InnoDB table) Online DDL support reduces table rebuild time and permits concurrent DML, which helps reduce user application downtime. For additional information, see Overview of Online DDL. On Solaris, mysql_config --libs now includes -R/path/to/library so that libraries can be found at runtime. mysql_install_db provides a more informative diagnostic message when required Perl modules are missing. The IGNORE clause for ALTER TABLE is now deprecated and will be removed in a future version of MySQL. ALTER IGNORE TABLE causes problems for replication, prevents online ALTER TABLE for unique index creation, and causes problems with foreign keys (rows removed in the parent table). Bugs Fixed
2014-03-31 12:32:13 +02:00
share/mysql/test/extra/rpl_tests/rpl_heartbeat_2slaves.inc
share/mysql/test/extra/rpl_tests/rpl_ignore_table_filter_insensitive.inc
share/mysql/test/extra/rpl_tests/rpl_ignore_table_filter_sensitive.inc
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/extra/rpl_tests/rpl_implicit_commit_binlog.test
share/mysql/test/extra/rpl_tests/rpl_innodb.test
share/mysql/test/extra/rpl_tests/rpl_insert_delayed.test
share/mysql/test/extra/rpl_tests/rpl_insert_id.test
share/mysql/test/extra/rpl_tests/rpl_insert_id_pk.test
share/mysql/test/extra/rpl_tests/rpl_insert_ignore.test
Changes 5.6.17: Functionality Added or Changed Incompatible Change: The AES_ENCRYPT() and AES_DECRYPT() functions now permit control of the block encryption mode and take an optional initialization vector argument: The new block_encryption_mode system variable controls the mode for block-based encryption algorithms. Its default value is aes-128-ecb, which signifies encryption using a key length of 128 bits and ECB mode. An optional init_vector argument provides an initialization vector for encryption modes that require it: AES_ENCRYPT(str,key_str[,init_vector]) AES_DECRYPT(crypt_str,key_str[,init_vector]) A random string of bytes to use for the initialization vector can be produced by calling the new RANDOM_BYTES() function. For more information, see Encryption and Compression Functions. These changes make statements that use AES_ENCRYPT() or AES_DECRYPT() unsafe for statement-based replication and they cannot be stored in the query cache. Queries that use RANDOM_BYTES() are unsafe for statement-based replication and cannot be stored in the query cache. Incompatible Change: The ERROR_FOR_DIVISION_BY_ZERO, NO_ZERO_DATE, and NO_ZERO_IN_DATE SQL modes now are deprecated and setting the sql_mode value to include any of them generates a warning. In MySQL 5.7, these modes do nothing. Instead, their effects are included in the effects of strict SQL mode (STRICT_ALL_TABLES or STRICT_TRANS_TABLES). The motivation for the change in MySQL 5.7 is to reduce the number of SQL modes with an effect dependent on strict mode and make them part of strict mode itself. To make advance preparation for an upgrade to MySQL 5.7, see SQL Mode Changes in MySQL 5.7. That discussion provides guidelines to assess whether your applications will be affected by the SQL mode changes in MySQL 5.7. InnoDB: MySQL now supports rebuilding regular and partitioned InnoDB tables using online DDL (ALGORITHM=INPLACE) for the following operations: OPTIMIZE TABLE ALTER TABLE ... FORCE ALTER TABLE ... ENGINE=INNODB (when run on an InnoDB table) Online DDL support reduces table rebuild time and permits concurrent DML, which helps reduce user application downtime. For additional information, see Overview of Online DDL. On Solaris, mysql_config --libs now includes -R/path/to/library so that libraries can be found at runtime. mysql_install_db provides a more informative diagnostic message when required Perl modules are missing. The IGNORE clause for ALTER TABLE is now deprecated and will be removed in a future version of MySQL. ALTER IGNORE TABLE causes problems for replication, prevents online ALTER TABLE for unique index creation, and causes problems with foreign keys (rows removed in the parent table). Bugs Fixed
2014-03-31 12:32:13 +02:00
share/mysql/test/extra/rpl_tests/rpl_insert_ignore_gtid_on.inc
Changes 5.6.19: Functionality Added or Changed The obsolete and unmaintained charset2html utility has been removed from MySQL distributions. The mysqlbug, mysql_waitpid, and mysql_zap utilities have been deprecated and will be removed in MySQL 5.7. Bugs Fixed InnoDB: After upgrading from 5.6.10 to MySQL versions up to and including MySQL 5.6.18, InnoDB would attempt to rename obsolete full-text search auxiliary tables on server startup, resulting in an assertion failure. InnoDB: For each insert, memset would be called three times to allocate memory for system fields. To reduce CPU usage, the three memset calls are now combined into a single call. InnoDB: Enabling the InnoDB Table Monitor would result in a ib_table->stat_initialized assertion failure. InnoDB: Setting innodb_max_dirty_pages_pct=0 would leave 1% of dirty pages unflushed. Buffer pool flushing is initiated when the percentage of dirty pages is greater innodb_max_dirty_pages_pct. The internal variables that store the innodb_max_dirty_pages_pct value and the percentage of dirty pages (buf_get_modified_ratio_pct and srv_max_buf_pool_modified_pct) were defined as unsigned integer data types, which meant that a innodb_max_dirty_pages_pct value of 0 required a dirty pages percentage of 1 or greater to initiate buffer pool flushing. To address this problem, the buf_get_modified_ratio_pct and srv_max_buf_pool_modified_pct internal variables are redefined as double data types, which changes the range value for innodb_max_dirty_pages_pct and innodb_max_dirty_pages_pct_lwm from 0 .. 99 to 0 .. 99.99. Additionally, buffer pool flushing is now initiated when the percentage of dirty pages is “greater than or equal to” innodb_max_dirty_pages_pct. Replication: Log rotation events could cause group_relay_log_pos to be moved forward incorrectly within a group. This meant that, when the transaction was retried, or if the SQL thread was stopped in the middle of a transaction following one or more log rotations (such that the transaction or group spanned multiple relay log files), part or all of the group was silently skipped. This issue has been addressed by correcting a problem in the logic used to avoid touching the coordinates of the SQL thread when updating the log position as part of a relay log rotation whereby it was possible to update the SQL thread's coordinates when not using a multi-threaded slave, even in the middle of a group. Replication: When running the server with --gtid-mode=ON, STOP SLAVE followed by START SLAVE resulted in a mismatch between the information provided by INFORMATION_SCHEMA.INNODB_TEMP_TABLE_INFO and the Slave_open_temp_tables status variable: the INNODB_TEMP_TABLE_INFO table showed that no temporary tables existed, but Slave_open_temp_tables had a nonzero value. Replication: In certain cases, the server mishandled triggers and stored procedures that tried to modify other tables when called by CREATE TABLE ... SELECT. This is now handled correctly as an error. Replication: When used on a table employing a transactional storage engine, a failed TRUNCATE TABLE was still written to the binary log and thus replayed on the slave. This could lead to inconsistency when the master retained data that was removed on the slave. Now in such cases TRUNCATE TABLE is logged only when it executes successfully. Replication: The server did not always handle the auto.cnf file correctly in cases where this file's permissions were incorrect. Replication: When the binary log was rotated due to receipt of a SIGHUP signal, the new binary log did not contain the Previous_gtid_event required for subsequent processing of that binary log's GTID events. Now when SIGHUP is received, steps are taken to insure that the server writes the necessary Previous_gtid_event to the new log before writing any GTID events to the new log.
2014-06-02 09:30:38 +02:00
share/mysql/test/extra/rpl_tests/rpl_kill_query.inc
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/extra/rpl_tests/rpl_loaddata.test
Changes 5.6.17: Functionality Added or Changed Incompatible Change: The AES_ENCRYPT() and AES_DECRYPT() functions now permit control of the block encryption mode and take an optional initialization vector argument: The new block_encryption_mode system variable controls the mode for block-based encryption algorithms. Its default value is aes-128-ecb, which signifies encryption using a key length of 128 bits and ECB mode. An optional init_vector argument provides an initialization vector for encryption modes that require it: AES_ENCRYPT(str,key_str[,init_vector]) AES_DECRYPT(crypt_str,key_str[,init_vector]) A random string of bytes to use for the initialization vector can be produced by calling the new RANDOM_BYTES() function. For more information, see Encryption and Compression Functions. These changes make statements that use AES_ENCRYPT() or AES_DECRYPT() unsafe for statement-based replication and they cannot be stored in the query cache. Queries that use RANDOM_BYTES() are unsafe for statement-based replication and cannot be stored in the query cache. Incompatible Change: The ERROR_FOR_DIVISION_BY_ZERO, NO_ZERO_DATE, and NO_ZERO_IN_DATE SQL modes now are deprecated and setting the sql_mode value to include any of them generates a warning. In MySQL 5.7, these modes do nothing. Instead, their effects are included in the effects of strict SQL mode (STRICT_ALL_TABLES or STRICT_TRANS_TABLES). The motivation for the change in MySQL 5.7 is to reduce the number of SQL modes with an effect dependent on strict mode and make them part of strict mode itself. To make advance preparation for an upgrade to MySQL 5.7, see SQL Mode Changes in MySQL 5.7. That discussion provides guidelines to assess whether your applications will be affected by the SQL mode changes in MySQL 5.7. InnoDB: MySQL now supports rebuilding regular and partitioned InnoDB tables using online DDL (ALGORITHM=INPLACE) for the following operations: OPTIMIZE TABLE ALTER TABLE ... FORCE ALTER TABLE ... ENGINE=INNODB (when run on an InnoDB table) Online DDL support reduces table rebuild time and permits concurrent DML, which helps reduce user application downtime. For additional information, see Overview of Online DDL. On Solaris, mysql_config --libs now includes -R/path/to/library so that libraries can be found at runtime. mysql_install_db provides a more informative diagnostic message when required Perl modules are missing. The IGNORE clause for ALTER TABLE is now deprecated and will be removed in a future version of MySQL. ALTER IGNORE TABLE causes problems for replication, prevents online ALTER TABLE for unique index creation, and causes problems with foreign keys (rows removed in the parent table). Bugs Fixed
2014-03-31 12:32:13 +02:00
share/mysql/test/extra/rpl_tests/rpl_loaddata_s.inc
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/extra/rpl_tests/rpl_loadfile.test
share/mysql/test/extra/rpl_tests/rpl_log.test
share/mysql/test/extra/rpl_tests/rpl_lower_case_table_names.test
share/mysql/test/extra/rpl_tests/rpl_max_relay_size.test
share/mysql/test/extra/rpl_tests/rpl_mixing_engines.inc
share/mysql/test/extra/rpl_tests/rpl_mixing_engines.test
share/mysql/test/extra/rpl_tests/rpl_mts_crash_safe.inc
share/mysql/test/extra/rpl_tests/rpl_mts_crash_safe.test
Changes 5.6.22: * Noisy compiler warnings on FreeBSD 10 were silenced. * CMake workarounds for older Mac OS X and XCode versions were removed. On Mac OS X, compilation always uses Clang, even for 32-bit builds. * Previously, the MYSQL_MAINTAINER_MODE CMake option was turned on by default for debug builds and off for release builds, and MYSQL_MAINTAINER_MODE caused -Werror to be enabled when building with GCC. This made it cumbersome to enable -Werror under certain conditions, such as when compiling with Clang. * Build support was modified to produce the same warnings for Clang as for gcc. * CMake configuration for the Clang compiler sets more appropriate flags for building on Linux. Specifically, -g -fno-omit-frame-pointer -fno-strict-aliasing is now added. * Bugs fixed.
2014-12-02 13:40:09 +01:00
share/mysql/test/extra/rpl_tests/rpl_mts_execute_partial_trx_in_relay_log.inc
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/extra/rpl_tests/rpl_multi_query.test
share/mysql/test/extra/rpl_tests/rpl_multi_update.test
share/mysql/test/extra/rpl_tests/rpl_multi_update2.test
share/mysql/test/extra/rpl_tests/rpl_multi_update3.test
share/mysql/test/extra/rpl_tests/rpl_not_null.test
share/mysql/test/extra/rpl_tests/rpl_parallel_load.test
share/mysql/test/extra/rpl_tests/rpl_parallel_load_innodb.test
share/mysql/test/extra/rpl_tests/rpl_partition.test
share/mysql/test/extra/rpl_tests/rpl_record_compare.test
share/mysql/test/extra/rpl_tests/rpl_relayrotate.test
share/mysql/test/extra/rpl_tests/rpl_reset_slave.test
Changes 5.6.27: * InnoDB: The new innodb_numa_interleave read-only configuration option allows you to enable the NUMA interleave memory policy for allocation of the InnoDB buffer pool. When innodb_numa_interleave is enabled, the NUMA memory policy is set to MPOL_INTERLEAVE for the mysqld process. After the InnoDB buffer pool is allocated, the NUMA memory policy is set back to MPOL_DEFAULT. This option is only available on NUMA-enabled systems. * yaSSL was upgraded to version 2.3.8. * RPM .spec files were updated so that MySQL Server builds from source RPM packages will include the proper files to take advantage of operating system NUMA capabilities. This introduces a runtime dependency on libnuma.so.1. RPM and yum detect this and refuse to install if that library is not installed. * InnoDB: Reloading a table that was evicted while empty caused an AUTO_INCREMENT value to be reset. * InnoDB: Memory allocation sanity checks were added to the memcached code. * InnoDB: A memcached flush_all command raised an assertion. A function that starts a transaction was called from within assertion code. * InnoDB: A data corruption occurred on ARM64. GCC builtins did not issue the correct fences when setting or unsetting the lock word. * InnoDB: Server shutdown was delayed waiting for the purge thread to exit. To avoid this problem, the number of calls to trx_purge() was reduced, and the trx_purge() batch size was reduced to 20. * InnoDB: In READ COMMITTED mode, a REPLACE operation on a unique secondary index resulted in a constraint violation. * InnoDB: The IBUF_BITMAP_FREE bit indicated that there was more free space in the leaf page than was actually available. * InnoDB: Setting lower_case_table_names=0 on a case-insensitive file system could result in a hang condition when running an INSERT INTO ... SELECT ... FROM tbl_name operation with the wrong tbl_name letter case. An error message is now printed and the server exits when attempting to start the server with --lower_case_table_names=0 on a case-insensitive file system. * InnoDB: The server failed to start with an innodb_force_recovery setting greater than 3. InnoDB was set to read-only mode before redo logs were applied. * InnoDB: The trx_sys_read_pertable_file_format_id() function reported the wrong file format. * Partitioning: CREATE TABLE statements that used an invalid function in a subpartitioning expression did not always fail gracefully as expected. * Partitioning: Error handling for failed partitioning-related ALTER TABLE operations against non-partitioned tables was not performed correctly * Partitioning: ALTER TABLE when executed from a stored procedure did not always work correctly with tables partitioned by RANGE. * Replication: Repeatedly checking for ERR_LOCK_WAIT_TIMEOUT (as done, for example by repeatedly executing SHOW SLAVE STATUS) during a prolonged write lock on a table led to an assert. * Replication: If statement based logging was in use, when updating multiple tables in a single statement, a single transaction could be logged as two different transactions. This was due to the binary logging process not properly identifying statements which were operating over transactional tables. The fix ensures that they are correctly identified, even if such statements do not change the contents of the tables.
2015-10-03 14:46:13 +02:00
share/mysql/test/extra/rpl_tests/rpl_rollback_to_savepoint.inc
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/extra/rpl_tests/rpl_row_001.test
share/mysql/test/extra/rpl_tests/rpl_row_UUID.test
share/mysql/test/extra/rpl_tests/rpl_row_basic.test
share/mysql/test/extra/rpl_tests/rpl_row_blob.test
share/mysql/test/extra/rpl_tests/rpl_row_delayed_ins.test
share/mysql/test/extra/rpl_tests/rpl_row_empty_imgs.test
Changes 5.6.17: Functionality Added or Changed Incompatible Change: The AES_ENCRYPT() and AES_DECRYPT() functions now permit control of the block encryption mode and take an optional initialization vector argument: The new block_encryption_mode system variable controls the mode for block-based encryption algorithms. Its default value is aes-128-ecb, which signifies encryption using a key length of 128 bits and ECB mode. An optional init_vector argument provides an initialization vector for encryption modes that require it: AES_ENCRYPT(str,key_str[,init_vector]) AES_DECRYPT(crypt_str,key_str[,init_vector]) A random string of bytes to use for the initialization vector can be produced by calling the new RANDOM_BYTES() function. For more information, see Encryption and Compression Functions. These changes make statements that use AES_ENCRYPT() or AES_DECRYPT() unsafe for statement-based replication and they cannot be stored in the query cache. Queries that use RANDOM_BYTES() are unsafe for statement-based replication and cannot be stored in the query cache. Incompatible Change: The ERROR_FOR_DIVISION_BY_ZERO, NO_ZERO_DATE, and NO_ZERO_IN_DATE SQL modes now are deprecated and setting the sql_mode value to include any of them generates a warning. In MySQL 5.7, these modes do nothing. Instead, their effects are included in the effects of strict SQL mode (STRICT_ALL_TABLES or STRICT_TRANS_TABLES). The motivation for the change in MySQL 5.7 is to reduce the number of SQL modes with an effect dependent on strict mode and make them part of strict mode itself. To make advance preparation for an upgrade to MySQL 5.7, see SQL Mode Changes in MySQL 5.7. That discussion provides guidelines to assess whether your applications will be affected by the SQL mode changes in MySQL 5.7. InnoDB: MySQL now supports rebuilding regular and partitioned InnoDB tables using online DDL (ALGORITHM=INPLACE) for the following operations: OPTIMIZE TABLE ALTER TABLE ... FORCE ALTER TABLE ... ENGINE=INNODB (when run on an InnoDB table) Online DDL support reduces table rebuild time and permits concurrent DML, which helps reduce user application downtime. For additional information, see Overview of Online DDL. On Solaris, mysql_config --libs now includes -R/path/to/library so that libraries can be found at runtime. mysql_install_db provides a more informative diagnostic message when required Perl modules are missing. The IGNORE clause for ALTER TABLE is now deprecated and will be removed in a future version of MySQL. ALTER IGNORE TABLE causes problems for replication, prevents online ALTER TABLE for unique index creation, and causes problems with foreign keys (rows removed in the parent table). Bugs Fixed
2014-03-31 12:32:13 +02:00
share/mysql/test/extra/rpl_tests/rpl_row_event_max_size.inc
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/extra/rpl_tests/rpl_row_func003.test
share/mysql/test/extra/rpl_tests/rpl_row_idempotency.test
share/mysql/test/extra/rpl_tests/rpl_row_img.test
share/mysql/test/extra/rpl_tests/rpl_row_img_blobs.test
share/mysql/test/extra/rpl_tests/rpl_row_img_diff_indexes.test
Changes 5.6.17: Functionality Added or Changed Incompatible Change: The AES_ENCRYPT() and AES_DECRYPT() functions now permit control of the block encryption mode and take an optional initialization vector argument: The new block_encryption_mode system variable controls the mode for block-based encryption algorithms. Its default value is aes-128-ecb, which signifies encryption using a key length of 128 bits and ECB mode. An optional init_vector argument provides an initialization vector for encryption modes that require it: AES_ENCRYPT(str,key_str[,init_vector]) AES_DECRYPT(crypt_str,key_str[,init_vector]) A random string of bytes to use for the initialization vector can be produced by calling the new RANDOM_BYTES() function. For more information, see Encryption and Compression Functions. These changes make statements that use AES_ENCRYPT() or AES_DECRYPT() unsafe for statement-based replication and they cannot be stored in the query cache. Queries that use RANDOM_BYTES() are unsafe for statement-based replication and cannot be stored in the query cache. Incompatible Change: The ERROR_FOR_DIVISION_BY_ZERO, NO_ZERO_DATE, and NO_ZERO_IN_DATE SQL modes now are deprecated and setting the sql_mode value to include any of them generates a warning. In MySQL 5.7, these modes do nothing. Instead, their effects are included in the effects of strict SQL mode (STRICT_ALL_TABLES or STRICT_TRANS_TABLES). The motivation for the change in MySQL 5.7 is to reduce the number of SQL modes with an effect dependent on strict mode and make them part of strict mode itself. To make advance preparation for an upgrade to MySQL 5.7, see SQL Mode Changes in MySQL 5.7. That discussion provides guidelines to assess whether your applications will be affected by the SQL mode changes in MySQL 5.7. InnoDB: MySQL now supports rebuilding regular and partitioned InnoDB tables using online DDL (ALGORITHM=INPLACE) for the following operations: OPTIMIZE TABLE ALTER TABLE ... FORCE ALTER TABLE ... ENGINE=INNODB (when run on an InnoDB table) Online DDL support reduces table rebuild time and permits concurrent DML, which helps reduce user application downtime. For additional information, see Overview of Online DDL. On Solaris, mysql_config --libs now includes -R/path/to/library so that libraries can be found at runtime. mysql_install_db provides a more informative diagnostic message when required Perl modules are missing. The IGNORE clause for ALTER TABLE is now deprecated and will be removed in a future version of MySQL. ALTER IGNORE TABLE causes problems for replication, prevents online ALTER TABLE for unique index creation, and causes problems with foreign keys (rows removed in the parent table). Bugs Fixed
2014-03-31 12:32:13 +02:00
share/mysql/test/extra/rpl_tests/rpl_row_show_relaylog_events.inc
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/extra/rpl_tests/rpl_row_sp002.test
share/mysql/test/extra/rpl_tests/rpl_row_sp003.test
share/mysql/test/extra/rpl_tests/rpl_row_sp006.test
share/mysql/test/extra/rpl_tests/rpl_row_sp007.test
share/mysql/test/extra/rpl_tests/rpl_row_tabledefs.test
share/mysql/test/extra/rpl_tests/rpl_set_null.test
share/mysql/test/extra/rpl_tests/rpl_show_binlog_events.inc
share/mysql/test/extra/rpl_tests/rpl_show_log_events_with_varying_options.inc
share/mysql/test/extra/rpl_tests/rpl_show_relaylog_events.inc
share/mysql/test/extra/rpl_tests/rpl_start_stop_slave.test
share/mysql/test/extra/rpl_tests/rpl_stm_EE_err2.test
share/mysql/test/extra/rpl_tests/rpl_stm_create_if_not_exists.test
Changes 5.6.17: Functionality Added or Changed Incompatible Change: The AES_ENCRYPT() and AES_DECRYPT() functions now permit control of the block encryption mode and take an optional initialization vector argument: The new block_encryption_mode system variable controls the mode for block-based encryption algorithms. Its default value is aes-128-ecb, which signifies encryption using a key length of 128 bits and ECB mode. An optional init_vector argument provides an initialization vector for encryption modes that require it: AES_ENCRYPT(str,key_str[,init_vector]) AES_DECRYPT(crypt_str,key_str[,init_vector]) A random string of bytes to use for the initialization vector can be produced by calling the new RANDOM_BYTES() function. For more information, see Encryption and Compression Functions. These changes make statements that use AES_ENCRYPT() or AES_DECRYPT() unsafe for statement-based replication and they cannot be stored in the query cache. Queries that use RANDOM_BYTES() are unsafe for statement-based replication and cannot be stored in the query cache. Incompatible Change: The ERROR_FOR_DIVISION_BY_ZERO, NO_ZERO_DATE, and NO_ZERO_IN_DATE SQL modes now are deprecated and setting the sql_mode value to include any of them generates a warning. In MySQL 5.7, these modes do nothing. Instead, their effects are included in the effects of strict SQL mode (STRICT_ALL_TABLES or STRICT_TRANS_TABLES). The motivation for the change in MySQL 5.7 is to reduce the number of SQL modes with an effect dependent on strict mode and make them part of strict mode itself. To make advance preparation for an upgrade to MySQL 5.7, see SQL Mode Changes in MySQL 5.7. That discussion provides guidelines to assess whether your applications will be affected by the SQL mode changes in MySQL 5.7. InnoDB: MySQL now supports rebuilding regular and partitioned InnoDB tables using online DDL (ALGORITHM=INPLACE) for the following operations: OPTIMIZE TABLE ALTER TABLE ... FORCE ALTER TABLE ... ENGINE=INNODB (when run on an InnoDB table) Online DDL support reduces table rebuild time and permits concurrent DML, which helps reduce user application downtime. For additional information, see Overview of Online DDL. On Solaris, mysql_config --libs now includes -R/path/to/library so that libraries can be found at runtime. mysql_install_db provides a more informative diagnostic message when required Perl modules are missing. The IGNORE clause for ALTER TABLE is now deprecated and will be removed in a future version of MySQL. ALTER IGNORE TABLE causes problems for replication, prevents online ALTER TABLE for unique index creation, and causes problems with foreign keys (rows removed in the parent table). Bugs Fixed
2014-03-31 12:32:13 +02:00
share/mysql/test/extra/rpl_tests/rpl_stm_insert_delayed.inc
share/mysql/test/extra/rpl_tests/rpl_stm_mix_show_relaylog_events.inc
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/extra/rpl_tests/rpl_stop_middle_group.test
share/mysql/test/extra/rpl_tests/rpl_stop_slave.test
Changes 5.6.12: * mysql_upgrade now verifies that the server version matches the version against which it was compiled, and exits if there is a mismatch. In addiion, a --version-check option permits specifying whether to enable version checking (the default), or disable checking if given as --skip-version-checking. * Bugs Fixed
2013-06-04 20:17:25 +02:00
share/mysql/test/extra/rpl_tests/rpl_stress_test.inc
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/extra/rpl_tests/rpl_sv_relay_space.test
share/mysql/test/extra/rpl_tests/rpl_temp_error.test
share/mysql/test/extra/rpl_tests/rpl_test_framework.inc
share/mysql/test/extra/rpl_tests/rpl_tmp_table_and_DDL.test
share/mysql/test/extra/rpl_tests/rpl_trig004.test
share/mysql/test/extra/rpl_tests/rpl_truncate.test
share/mysql/test/extra/rpl_tests/rpl_truncate_helper.test
share/mysql/test/extra/rpl_tests/type_conversions.test
share/mysql/test/include/Load_data.inc
share/mysql/test/include/add_anonymous_users.inc
share/mysql/test/include/analyze-sync_with_master.test
share/mysql/test/include/analyze-timeout.test
share/mysql/test/include/assert.inc
share/mysql/test/include/assert_command_output.inc
Changes 5.6.25: Functionality Added or Changed * MySQL Enterprise Firewall operates on parser states and does not work well together with the query cache, which circumvents the parser. MySQL Enterprise Firewall now checks whether the query cache is enabled. If so, it displays a message that the query cache must be disabled and does not load. * my_print_defaults now masks passwords. To display passwords in cleartext, use the new --show option. * MySQL distributions now include an innodb_stress suite of test cases. Thanks to Mark Callaghan for the contribution. Bugs Fixed * InnoDB; Partitioning: The CREATE_TIME column of the INFORMATION_SCHEMA.TABLES table now shows the correct table creation time for partitioned InnoDB tables. The CREATE_TIME column of the INFORMATION_SCHEMA.PARTITIONS table now shows the correct partition creation time for a partition of partitioned InnoDB tables. The UPDATE_TIME column of the INFORMATION_SCHEMA.TABLES table now shows when a partitioned InnoDB table was last updated by an INSERT, DELETE, or UPDATE. The UPDATE_TIME column of the INFORMATION_SCHEMA.PARTITIONS table now shows when a partition of a partitioned InnoDB table was last updated. * InnoDB: An assertion was raised on shutdown due to XA PREPARE transactions holding explicit locks. * InnoDB: The strict_* forms of innodb_checksum_algorithm settings (strict_none, strict_innodb, and strict_crc32) caused the server to halt when a non-matching checksum was encountered, even though the non-matching checksum was valid. For example, with innodb_checksum_algorithm=strict_crc32, encountering a valid innodb checksum caused the server to halt. Instead of halting the server, a message is now printed to the error log and the page is accepted as valid if it matches an innodb, crc32 or none checksum. * InnoDB: The memcached set command permitted a negative expire time value. Expire time is stored internally as an unsigned integer. A negative value would be converted to a large number and accepted. The maximum expire time value is now restricted to INT_MAX32 to prevent negative expire time values. * InnoDB: Removal of a foreign key object from the data dictionary cache during error handling caused the server to exit. * InnoDB: SHOW ENGINE INNODB STATUS output showed negative reservation and signal count values due to a counter overflow error. * InnoDB: Failure to check the status of a cursor transaction read-only option before reusing the cursor transaction for a write operation resulted in a server exit during a memcached workload. * InnoDB: MDL locks taken by memcached clients caused a MySQL Enterprise Backup FLUSH TABLES WITH READ LOCK operation to hang. * InnoDB: Estimates that were too low for the size of merge chunks in the result sorting algorithm caused a server exit. * InnoDB: For full-text searches, the optimizer could choose an index that does not produce correct relevancy rankings. * Partitioning: When creating a partitioned table, partition-level DATA DIRECTORY or INDEX DIRECTORY option values that contained an excessive number of characters were handled incorrectly. * Partitioning: Executing an ALTER TABLE on a partitioned table on which a write lock was in effect could cause subsequent SQL statements on this table to fail. * Replication: When binary logging was enabled, using stored functions and triggers resulting in a long running procedure that inserted many records caused the memory use to increase rapidly. This was due to memory being allocated per variable. The fix ensures that in such a situation, memory is allocated once and the same memory is reused. * Replication: If an error was encountered while adding a GTID to the received GTID set, the log lock was not being correctly released. This could cause a deadlock. more...
2015-06-01 10:15:05 +02:00
share/mysql/test/include/assert_grep.inc
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/include/begin_include_file.inc
share/mysql/test/include/big_test.inc
share/mysql/test/include/binlog_inject_error.inc
share/mysql/test/include/bug38347.inc
Changes 5.6.19: Functionality Added or Changed The obsolete and unmaintained charset2html utility has been removed from MySQL distributions. The mysqlbug, mysql_waitpid, and mysql_zap utilities have been deprecated and will be removed in MySQL 5.7. Bugs Fixed InnoDB: After upgrading from 5.6.10 to MySQL versions up to and including MySQL 5.6.18, InnoDB would attempt to rename obsolete full-text search auxiliary tables on server startup, resulting in an assertion failure. InnoDB: For each insert, memset would be called three times to allocate memory for system fields. To reduce CPU usage, the three memset calls are now combined into a single call. InnoDB: Enabling the InnoDB Table Monitor would result in a ib_table->stat_initialized assertion failure. InnoDB: Setting innodb_max_dirty_pages_pct=0 would leave 1% of dirty pages unflushed. Buffer pool flushing is initiated when the percentage of dirty pages is greater innodb_max_dirty_pages_pct. The internal variables that store the innodb_max_dirty_pages_pct value and the percentage of dirty pages (buf_get_modified_ratio_pct and srv_max_buf_pool_modified_pct) were defined as unsigned integer data types, which meant that a innodb_max_dirty_pages_pct value of 0 required a dirty pages percentage of 1 or greater to initiate buffer pool flushing. To address this problem, the buf_get_modified_ratio_pct and srv_max_buf_pool_modified_pct internal variables are redefined as double data types, which changes the range value for innodb_max_dirty_pages_pct and innodb_max_dirty_pages_pct_lwm from 0 .. 99 to 0 .. 99.99. Additionally, buffer pool flushing is now initiated when the percentage of dirty pages is “greater than or equal to” innodb_max_dirty_pages_pct. Replication: Log rotation events could cause group_relay_log_pos to be moved forward incorrectly within a group. This meant that, when the transaction was retried, or if the SQL thread was stopped in the middle of a transaction following one or more log rotations (such that the transaction or group spanned multiple relay log files), part or all of the group was silently skipped. This issue has been addressed by correcting a problem in the logic used to avoid touching the coordinates of the SQL thread when updating the log position as part of a relay log rotation whereby it was possible to update the SQL thread's coordinates when not using a multi-threaded slave, even in the middle of a group. Replication: When running the server with --gtid-mode=ON, STOP SLAVE followed by START SLAVE resulted in a mismatch between the information provided by INFORMATION_SCHEMA.INNODB_TEMP_TABLE_INFO and the Slave_open_temp_tables status variable: the INNODB_TEMP_TABLE_INFO table showed that no temporary tables existed, but Slave_open_temp_tables had a nonzero value. Replication: In certain cases, the server mishandled triggers and stored procedures that tried to modify other tables when called by CREATE TABLE ... SELECT. This is now handled correctly as an error. Replication: When used on a table employing a transactional storage engine, a failed TRUNCATE TABLE was still written to the binary log and thus replayed on the slave. This could lead to inconsistency when the master retained data that was removed on the slave. Now in such cases TRUNCATE TABLE is logged only when it executes successfully. Replication: The server did not always handle the auto.cnf file correctly in cases where this file's permissions were incorrect. Replication: When the binary log was rotated due to receipt of a SIGHUP signal, the new binary log did not contain the Previous_gtid_event required for subsequent processing of that binary log's GTID events. Now when SIGHUP is received, steps are taken to insure that the server writes the necessary Previous_gtid_event to the new log before writing any GTID events to the new log.
2014-06-02 09:30:38 +02:00
share/mysql/test/include/change_file_perms.inc
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/include/check-testcase.test
share/mysql/test/include/check-warnings.test
share/mysql/test/include/check_concurrent_insert.inc
share/mysql/test/include/check_events_off.inc
share/mysql/test/include/check_ftwrl_compatible.inc
share/mysql/test/include/check_ftwrl_incompatible.inc
share/mysql/test/include/check_ipv4_mapped.inc
share/mysql/test/include/check_ipv6.inc
share/mysql/test/include/check_key_reads.inc
share/mysql/test/include/check_key_req.inc
share/mysql/test/include/check_no_concurrent_insert.inc
share/mysql/test/include/check_no_row_lock.inc
share/mysql/test/include/check_qep.inc
share/mysql/test/include/check_shared_row_lock.inc
share/mysql/test/include/check_slave_is_running.inc
share/mysql/test/include/check_slave_no_error.inc
share/mysql/test/include/check_slave_param.inc
share/mysql/test/include/check_var_limit.inc
share/mysql/test/include/cleanup_fake_relay_log.inc
share/mysql/test/include/commit.inc
share/mysql/test/include/common-tests.inc
share/mysql/test/include/concurrent.inc
share/mysql/test/include/connect2.inc
share/mysql/test/include/count_sessions.inc
share/mysql/test/include/create_table.inc
share/mysql/test/include/ctype_8bit.inc
share/mysql/test/include/ctype_ascii_order.inc
share/mysql/test/include/ctype_common.inc
share/mysql/test/include/ctype_czech.inc
share/mysql/test/include/ctype_datetime.inc
share/mysql/test/include/ctype_filesort.inc
share/mysql/test/include/ctype_filesort2.inc
share/mysql/test/include/ctype_german.inc
share/mysql/test/include/ctype_heap.inc
share/mysql/test/include/ctype_inet.inc
share/mysql/test/include/ctype_innodb_like.inc
share/mysql/test/include/ctype_like.inc
share/mysql/test/include/ctype_like_escape.inc
share/mysql/test/include/ctype_like_ignorable.inc
share/mysql/test/include/ctype_like_range_f1f2.inc
share/mysql/test/include/ctype_numconv.inc
share/mysql/test/include/ctype_pad_space.inc
share/mysql/test/include/ctype_regex.inc
share/mysql/test/include/ctype_unicode520.inc
share/mysql/test/include/ctype_unicode_latin.inc
share/mysql/test/include/ctype_utf8_table.inc
share/mysql/test/include/ctype_utf8mb4.inc
share/mysql/test/include/daemon_example_bad_format.ini
share/mysql/test/include/daemon_example_bad_soname.ini
share/mysql/test/include/ddl_i18n.check_events.inc
share/mysql/test/include/ddl_i18n.check_sp.inc
share/mysql/test/include/ddl_i18n.check_triggers.inc
share/mysql/test/include/ddl_i18n.check_views.inc
share/mysql/test/include/deadlock.inc
share/mysql/test/include/default_client.cnf
share/mysql/test/include/default_my.cnf
share/mysql/test/include/default_mysqld.cnf
share/mysql/test/include/default_mysqld_autosize.cnf
share/mysql/test/include/default_ndbd.cnf
share/mysql/test/include/delete_anonymous_users.inc
share/mysql/test/include/diff_servers.inc
share/mysql/test/include/diff_tables.inc
share/mysql/test/include/end_include_file.inc
share/mysql/test/include/endspace.inc
share/mysql/test/include/eval.inc
share/mysql/test/include/execute_with_statistics.inc
share/mysql/test/include/expect_qep.inc
share/mysql/test/include/explain.inc
share/mysql/test/include/explain_json.inc
share/mysql/test/include/explain_non_select.inc
share/mysql/test/include/explain_utils.inc
share/mysql/test/include/file_does_not_exist.inc
share/mysql/test/include/filter_file.inc
share/mysql/test/include/force_restart.inc
share/mysql/test/include/force_restart_if_skipped.inc
Changes 5.6.17: Functionality Added or Changed Incompatible Change: The AES_ENCRYPT() and AES_DECRYPT() functions now permit control of the block encryption mode and take an optional initialization vector argument: The new block_encryption_mode system variable controls the mode for block-based encryption algorithms. Its default value is aes-128-ecb, which signifies encryption using a key length of 128 bits and ECB mode. An optional init_vector argument provides an initialization vector for encryption modes that require it: AES_ENCRYPT(str,key_str[,init_vector]) AES_DECRYPT(crypt_str,key_str[,init_vector]) A random string of bytes to use for the initialization vector can be produced by calling the new RANDOM_BYTES() function. For more information, see Encryption and Compression Functions. These changes make statements that use AES_ENCRYPT() or AES_DECRYPT() unsafe for statement-based replication and they cannot be stored in the query cache. Queries that use RANDOM_BYTES() are unsafe for statement-based replication and cannot be stored in the query cache. Incompatible Change: The ERROR_FOR_DIVISION_BY_ZERO, NO_ZERO_DATE, and NO_ZERO_IN_DATE SQL modes now are deprecated and setting the sql_mode value to include any of them generates a warning. In MySQL 5.7, these modes do nothing. Instead, their effects are included in the effects of strict SQL mode (STRICT_ALL_TABLES or STRICT_TRANS_TABLES). The motivation for the change in MySQL 5.7 is to reduce the number of SQL modes with an effect dependent on strict mode and make them part of strict mode itself. To make advance preparation for an upgrade to MySQL 5.7, see SQL Mode Changes in MySQL 5.7. That discussion provides guidelines to assess whether your applications will be affected by the SQL mode changes in MySQL 5.7. InnoDB: MySQL now supports rebuilding regular and partitioned InnoDB tables using online DDL (ALGORITHM=INPLACE) for the following operations: OPTIMIZE TABLE ALTER TABLE ... FORCE ALTER TABLE ... ENGINE=INNODB (when run on an InnoDB table) Online DDL support reduces table rebuild time and permits concurrent DML, which helps reduce user application downtime. For additional information, see Overview of Online DDL. On Solaris, mysql_config --libs now includes -R/path/to/library so that libraries can be found at runtime. mysql_install_db provides a more informative diagnostic message when required Perl modules are missing. The IGNORE clause for ALTER TABLE is now deprecated and will be removed in a future version of MySQL. ALTER IGNORE TABLE causes problems for replication, prevents online ALTER TABLE for unique index creation, and causes problems with foreign keys (rows removed in the parent table). Bugs Fixed
2014-03-31 12:32:13 +02:00
share/mysql/test/include/func_aes_block.inc
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/include/func_in.inc
share/mysql/test/include/function_defaults.inc
share/mysql/test/include/function_defaults_notembedded.inc
Changes 5.6.23: * The linked OpenSSL library for the MySQL Commercial Server has been updated from version 1.0.1j to version 1.0.1k. * Support for the SSL 2.0 and SSL 3.0 protocols has been disabled because they provide weak encryption. * yaSSL was upgraded to version 2.3.7. * The valid date range of the SSL certificates in mysql-test/std_data has been extended to the year 2029. * Bugs Fixed
2015-02-07 20:23:40 +01:00
share/mysql/test/include/get_file_permissions.inc
Changes 5.6.20: Security Fix: The linked OpenSSL library for the MySQL 5.6 Commercial Server has been updated from version 1.0.1g to version 1.0.1h. Versions of OpenSSL prior to and including 1.0.1g are reported to be vulnerable to CVE-2014-0224. This change does not affect the Oracle-produced MySQL Community build of MySQL Server 5.6, which uses the yaSSL library instead. DTrace Support MySQL now includes DTrace support on Oracle Linux 6 or higher with UEK kernel. If DTrace is present, server builds will detect it with no special CMake options required. For information about using DTrace on MySQL, see Tracing mysqld Using DTrace. InnoDB Notes Important Change: Redo log writes for large, externally stored BLOB fields could overwrite the most recent checkpoint. The 5.6.20 patch limits the size of redo log BLOB writes to 10% of the redo log file size. The 5.7.5 patch addresses the bug without imposing a limitation. For MySQL 5.5, the bug remains a known limitation. As a result of the redo log BLOB write limit introduced for MySQL 5.6, innodb_log_file_size should be set to a value greater than 10 times the largest BLOB data size found in the rows of your tables plus the length of other variable length fields (VARCHAR, VARBINARY, and TEXT type fields). Failing to do so could result in “Row size too large” errors. No action is required if your innodb_log_file_size setting is already sufficiently large or your tables contain no BLOB data. Functionality Added or Changed Replication: The new system variable binlog_impossible_mode controls what happens if the server cannot write to the binary log, for example, due to a file error. For backward compatibility, the default for binlog_impossible_mode is IGNORE_ERROR, meaning the server logs the error, halts logging, and continues updates to the database. Setting this variable to ABORT_SERVER makes the server halt logging and shut down if it cannot write to the binary log. CMake support was updated to handle CMake version 3. New Debian7, Ubuntu12.04, and Ubuntu14.04 distribution support that was introduced with 5.6.17 now comes with the platform-specific packaging source placed under the packaging directory, in the deb-precise, deb-wheezy, and deb-trusty directories. Support for LinuxThreads has been removed from the source code. LinuxThreads was superseded by NPTL in Linux 2.6. By default, mysql_install_db creates a my.cnf file in the installation base directory using a template. This may be undesireable for some deployments. To enable this behavior to be suppressed, mysql_install_db now supports a --keep-my-cnf option to preserve any existing my.cnf file and not create a new my.cnf file. The mysqlhotcopy utility is now deprecated and will be removed in a future version of MySQL. Among the reasons for this: It works only for the MyISAM and ARCHIVE storage engines; it works on Unix but not Windows. Alternatives include mysqldump and MySQL Enterprise Backup. The timed_mutexes system variable has no effect and is deprecated. Bugs Fixed
2014-08-10 17:11:57 +02:00
share/mysql/test/include/get_ndb_epochs.inc
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/include/get_relay_log_pos.inc
share/mysql/test/include/gis_debug.inc
share/mysql/test/include/gis_generic.inc
share/mysql/test/include/gis_keys.inc
share/mysql/test/include/grant_cache.inc
share/mysql/test/include/greedy_search_drop_tables.inc
share/mysql/test/include/greedy_search_load_tables.inc
Changes 5.6.19: Functionality Added or Changed The obsolete and unmaintained charset2html utility has been removed from MySQL distributions. The mysqlbug, mysql_waitpid, and mysql_zap utilities have been deprecated and will be removed in MySQL 5.7. Bugs Fixed InnoDB: After upgrading from 5.6.10 to MySQL versions up to and including MySQL 5.6.18, InnoDB would attempt to rename obsolete full-text search auxiliary tables on server startup, resulting in an assertion failure. InnoDB: For each insert, memset would be called three times to allocate memory for system fields. To reduce CPU usage, the three memset calls are now combined into a single call. InnoDB: Enabling the InnoDB Table Monitor would result in a ib_table->stat_initialized assertion failure. InnoDB: Setting innodb_max_dirty_pages_pct=0 would leave 1% of dirty pages unflushed. Buffer pool flushing is initiated when the percentage of dirty pages is greater innodb_max_dirty_pages_pct. The internal variables that store the innodb_max_dirty_pages_pct value and the percentage of dirty pages (buf_get_modified_ratio_pct and srv_max_buf_pool_modified_pct) were defined as unsigned integer data types, which meant that a innodb_max_dirty_pages_pct value of 0 required a dirty pages percentage of 1 or greater to initiate buffer pool flushing. To address this problem, the buf_get_modified_ratio_pct and srv_max_buf_pool_modified_pct internal variables are redefined as double data types, which changes the range value for innodb_max_dirty_pages_pct and innodb_max_dirty_pages_pct_lwm from 0 .. 99 to 0 .. 99.99. Additionally, buffer pool flushing is now initiated when the percentage of dirty pages is “greater than or equal to” innodb_max_dirty_pages_pct. Replication: Log rotation events could cause group_relay_log_pos to be moved forward incorrectly within a group. This meant that, when the transaction was retried, or if the SQL thread was stopped in the middle of a transaction following one or more log rotations (such that the transaction or group spanned multiple relay log files), part or all of the group was silently skipped. This issue has been addressed by correcting a problem in the logic used to avoid touching the coordinates of the SQL thread when updating the log position as part of a relay log rotation whereby it was possible to update the SQL thread's coordinates when not using a multi-threaded slave, even in the middle of a group. Replication: When running the server with --gtid-mode=ON, STOP SLAVE followed by START SLAVE resulted in a mismatch between the information provided by INFORMATION_SCHEMA.INNODB_TEMP_TABLE_INFO and the Slave_open_temp_tables status variable: the INNODB_TEMP_TABLE_INFO table showed that no temporary tables existed, but Slave_open_temp_tables had a nonzero value. Replication: In certain cases, the server mishandled triggers and stored procedures that tried to modify other tables when called by CREATE TABLE ... SELECT. This is now handled correctly as an error. Replication: When used on a table employing a transactional storage engine, a failed TRUNCATE TABLE was still written to the binary log and thus replayed on the slave. This could lead to inconsistency when the master retained data that was removed on the slave. Now in such cases TRUNCATE TABLE is logged only when it executes successfully. Replication: The server did not always handle the auto.cnf file correctly in cases where this file's permissions were incorrect. Replication: When the binary log was rotated due to receipt of a SIGHUP signal, the new binary log did not contain the Previous_gtid_event required for subsequent processing of that binary log's GTID events. Now when SIGHUP is received, steps are taken to insure that the server writes the necessary Previous_gtid_event to the new log before writing any GTID events to the new log.
2014-06-02 09:30:38 +02:00
share/mysql/test/include/gtid_step_assert.inc
share/mysql/test/include/gtid_step_reset.inc
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/include/gtid_utils.inc
share/mysql/test/include/gtid_utils_end.inc
share/mysql/test/include/handler.inc
share/mysql/test/include/have_32bit.inc
share/mysql/test/include/have_64bit.inc
Changes 5.6.15: * Previously, MySQL Server distributions included the MySQL Reference Manual in Info format (the Docs/mysql.info file). Because the license for the manual restricts redistribution, its inclusion in Community packages caused problems for downstream redistributors, such as those who create Linux distributions. Community distributions of MySQL Server no longer include the mysql.info file, to make the repackaging and redistribution process easier (for example, the source tarball and its checksum can be used directly). This change applies to all source and binary Community packaging formats. Commercial (Enterprise) distributions are unchanged. * Incompatible Change: Several statement instruments in the setup_instruments table are used by the Performance Schema during the early stages of statement classification before the exact statement type is known. * The Performance Schema now instruments the read/write lock Delegate::lock * A new CMake option, WITH_ASAN, permits enabling address sanitization for compilers that support it. * The hash function used for metadata locking was modified to reduce overhead. * Bugs Fixed
2013-12-03 21:02:41 +01:00
share/mysql/test/include/have_QC_Disabled.inc
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/include/have_archive.inc
share/mysql/test/include/have_archive_plugin.inc
share/mysql/test/include/have_big5.inc
share/mysql/test/include/have_binlog_checksum_off.inc
share/mysql/test/include/have_binlog_format_mixed.inc
share/mysql/test/include/have_binlog_format_mixed_or_row.inc
share/mysql/test/include/have_binlog_format_mixed_or_statement.inc
share/mysql/test/include/have_binlog_format_row.inc
share/mysql/test/include/have_binlog_format_row_or_statement.inc
share/mysql/test/include/have_binlog_format_statement.inc
share/mysql/test/include/have_binlog_rows_query.inc
share/mysql/test/include/have_blackhole.inc
share/mysql/test/include/have_blackhole_plugin.inc
share/mysql/test/include/have_case_insensitive_file_system.inc
share/mysql/test/include/have_case_sensitive_file_system.inc
share/mysql/test/include/have_compress.inc
share/mysql/test/include/have_cp1250_ch.inc
share/mysql/test/include/have_cp1251.inc
share/mysql/test/include/have_cp866.inc
share/mysql/test/include/have_cp932.inc
share/mysql/test/include/have_crypt.inc
share/mysql/test/include/have_csv.inc
Changes 5.6.13: * Important Change; Replication: By default, when promoting integers from a smaller type on the master to a larger type on the slave (for example, from a SMALLINT column on the master to a BIGINT column on the slave), the promoted values are treated as though they are signed. Now in such cases it is possible to modify or override this behavior using one or both of ALL_SIGNED, ALL_UNSIGNED in the set of values specified for the slave_type_conversions server system variable. For more information, see Row-based replication: attribute promotion and demotion, as well as the description of the variable. * Previously, program options could be specified in full or as any unambiguous prefix. For example, the --compress option could be given to mysqldump as --compr, but not as --comp because the latter is ambiguous. Option prefixes now are deprecated. They can cause problems when new options are implemented for programs. A prefix that is currently unambiguous might become ambiguous in the future. If an unambiguous prefix is given, a warning now occurs to provide feedback. For example: Warning: Using unique option prefix compr instead of compress is deprecated and will be removed in a future release. Please use the full name instead. Option prefixes are no longer supported in MySQL 5.7; only full options are accepted. * The C API libmysqlclient shared-library .so files now have version 18.1.0 (up from version 18.0.0 used in MySQL 5.5). * In batch mode, mysql formatted result status messages such as “"Query OK, 1 row affected"” but did not print them. Now these messages are not formatted. * Bugs Fixed
2013-07-31 11:51:38 +02:00
share/mysql/test/include/have_daemon_example_plugin.inc
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/include/have_dbi_dbd-mysql.inc
share/mysql/test/include/have_debug.inc
share/mysql/test/include/have_debug_sync.inc
share/mysql/test/include/have_dynamic_loading.inc
share/mysql/test/include/have_engine_condition_pushdown.inc
share/mysql/test/include/have_eucjpms.inc
share/mysql/test/include/have_euckr.inc
share/mysql/test/include/have_example_plugin.inc
share/mysql/test/include/have_exampledb.inc
share/mysql/test/include/have_federated_plugin.inc
share/mysql/test/include/have_firstmatch.inc
share/mysql/test/include/have_gb2312.inc
share/mysql/test/include/have_gbk.inc
share/mysql/test/include/have_geometry.inc
share/mysql/test/include/have_gtid.inc
share/mysql/test/include/have_index_condition_pushdown.inc
share/mysql/test/include/have_innodb.inc
share/mysql/test/include/have_innodb_16k.inc
share/mysql/test/include/have_innodb_4k.inc
share/mysql/test/include/have_innodb_8k.inc
share/mysql/test/include/have_ipv4_mapped.inc
share/mysql/test/include/have_ipv6.inc
share/mysql/test/include/have_koi8r.inc
share/mysql/test/include/have_latin2_ch.inc
share/mysql/test/include/have_local_infile.inc
share/mysql/test/include/have_log_bin.inc
share/mysql/test/include/have_loosescan.inc
share/mysql/test/include/have_lowercase0.inc
share/mysql/test/include/have_lowercase1.inc
share/mysql/test/include/have_lowercase2.inc
share/mysql/test/include/have_materialization.inc
share/mysql/test/include/have_memcached_plugin.inc
share/mysql/test/include/have_mrr.inc
share/mysql/test/include/have_multi_ndb.inc
Changes 5.6.24: * CMake support was updated to handle CMake version 3.1. * The server now includes its version number when it writes the initial “starting” message to the error log, to make it easier to tell which server instance error log output applies to. This value is the same as that available from the version system variable. * ALTER TABLE did not take advantage of fast alterations that might otherwise apply to the operation to be performed, if the table contained temporal columns found to be in pre-5.6.4 format (TIME, DATETIME, and TIMESTAMP columns without support for fractional seconds precision). * Statement digesting as done previously by the Performance Schema is now done at the SQL level regardless of whether the Performance Schema is compiled in and is available to other aspects of server operation that could benefit from it. The default space available for digesting is 1024 bytes, but can be changed at server startup using the max_digest_length system variable. * Bug fixes.
2015-04-08 12:38:48 +02:00
share/mysql/test/include/have_mysql_no_login_plugin.inc
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/include/have_mysql_upgrade.inc
share/mysql/test/include/have_ndb.inc
share/mysql/test/include/have_ndb_extra.inc
share/mysql/test/include/have_ndbapi_examples.inc
share/mysql/test/include/have_nodebug.inc
share/mysql/test/include/have_not_innodb_plugin.inc
share/mysql/test/include/have_null_audit_plugin.inc
Changes 5.6.27: * InnoDB: The new innodb_numa_interleave read-only configuration option allows you to enable the NUMA interleave memory policy for allocation of the InnoDB buffer pool. When innodb_numa_interleave is enabled, the NUMA memory policy is set to MPOL_INTERLEAVE for the mysqld process. After the InnoDB buffer pool is allocated, the NUMA memory policy is set back to MPOL_DEFAULT. This option is only available on NUMA-enabled systems. * yaSSL was upgraded to version 2.3.8. * RPM .spec files were updated so that MySQL Server builds from source RPM packages will include the proper files to take advantage of operating system NUMA capabilities. This introduces a runtime dependency on libnuma.so.1. RPM and yum detect this and refuse to install if that library is not installed. * InnoDB: Reloading a table that was evicted while empty caused an AUTO_INCREMENT value to be reset. * InnoDB: Memory allocation sanity checks were added to the memcached code. * InnoDB: A memcached flush_all command raised an assertion. A function that starts a transaction was called from within assertion code. * InnoDB: A data corruption occurred on ARM64. GCC builtins did not issue the correct fences when setting or unsetting the lock word. * InnoDB: Server shutdown was delayed waiting for the purge thread to exit. To avoid this problem, the number of calls to trx_purge() was reduced, and the trx_purge() batch size was reduced to 20. * InnoDB: In READ COMMITTED mode, a REPLACE operation on a unique secondary index resulted in a constraint violation. * InnoDB: The IBUF_BITMAP_FREE bit indicated that there was more free space in the leaf page than was actually available. * InnoDB: Setting lower_case_table_names=0 on a case-insensitive file system could result in a hang condition when running an INSERT INTO ... SELECT ... FROM tbl_name operation with the wrong tbl_name letter case. An error message is now printed and the server exits when attempting to start the server with --lower_case_table_names=0 on a case-insensitive file system. * InnoDB: The server failed to start with an innodb_force_recovery setting greater than 3. InnoDB was set to read-only mode before redo logs were applied. * InnoDB: The trx_sys_read_pertable_file_format_id() function reported the wrong file format. * Partitioning: CREATE TABLE statements that used an invalid function in a subpartitioning expression did not always fail gracefully as expected. * Partitioning: Error handling for failed partitioning-related ALTER TABLE operations against non-partitioned tables was not performed correctly * Partitioning: ALTER TABLE when executed from a stored procedure did not always work correctly with tables partitioned by RANGE. * Replication: Repeatedly checking for ERR_LOCK_WAIT_TIMEOUT (as done, for example by repeatedly executing SHOW SLAVE STATUS) during a prolonged write lock on a table led to an assert. * Replication: If statement based logging was in use, when updating multiple tables in a single statement, a single transaction could be logged as two different transactions. This was due to the binary logging process not properly identifying statements which were operating over transactional tables. The fix ensures that they are correctly identified, even if such statements do not change the contents of the tables.
2015-10-03 14:46:13 +02:00
share/mysql/test/include/have_numa.inc
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/include/have_openssl.inc
share/mysql/test/include/have_optimizer_trace.inc
share/mysql/test/include/have_outfile.inc
share/mysql/test/include/have_partition.inc
share/mysql/test/include/have_partition_open_file_limit.inc
share/mysql/test/include/have_perfschema.inc
share/mysql/test/include/have_plugin_auth.inc
share/mysql/test/include/have_plugin_interface.inc
share/mysql/test/include/have_plugin_server.inc
share/mysql/test/include/have_profiling.inc
share/mysql/test/include/have_query_cache.inc
share/mysql/test/include/have_semijoin.inc
share/mysql/test/include/have_semisync_plugin.inc
share/mysql/test/include/have_sha256_rsa_auth.inc
share/mysql/test/include/have_simple_parser.inc
share/mysql/test/include/have_sjis.inc
share/mysql/test/include/have_ssl.inc
share/mysql/test/include/have_ssl_communication.inc
share/mysql/test/include/have_ssl_crypto_functs.inc
share/mysql/test/include/have_symlink.inc
share/mysql/test/include/have_tis620.inc
share/mysql/test/include/have_ucs2.inc
share/mysql/test/include/have_udf.inc
share/mysql/test/include/have_ujis.inc
share/mysql/test/include/have_utf16.inc
share/mysql/test/include/have_utf32.inc
share/mysql/test/include/have_utf8.inc
share/mysql/test/include/have_utf8mb4.inc
Changes 5.6.22: * Noisy compiler warnings on FreeBSD 10 were silenced. * CMake workarounds for older Mac OS X and XCode versions were removed. On Mac OS X, compilation always uses Clang, even for 32-bit builds. * Previously, the MYSQL_MAINTAINER_MODE CMake option was turned on by default for debug builds and off for release builds, and MYSQL_MAINTAINER_MODE caused -Werror to be enabled when building with GCC. This made it cumbersome to enable -Werror under certain conditions, such as when compiling with Clang. * Build support was modified to produce the same warnings for Clang as for gcc. * CMake configuration for the Clang compiler sets more appropriate flags for building on Linux. Specifically, -g -fno-omit-frame-pointer -fno-strict-aliasing is now added. * Bugs fixed.
2014-12-02 13:40:09 +01:00
share/mysql/test/include/have_util_nc.inc
Changes 5.6.14: * MySQL 5.7 changed audit log file output to a new format that has better compatibility with Oracle Audit Vault. This format has been backported to MySQL 5.6 and it is possible to select either the old or new format using the new audit_log_format system variable, which has permitted values of OLD and NEW (default OLD). For details about each format, see The Audit Log File. * Important Change; Replication: START SLAVE UNTIL SQL_AFTER_GTIDS did not cause the slave to stop until the next GTID event was received following execution of the transaction having the indicated GTID, which could cause issues in the case when the next GTID event is delayed, or does not exist. Now the slave stops after completing the transaction with that GTID. * InnoDB; Partitioning: Following any query on the INFORMATION_SCHEMA.PARTITIONS table, InnoDB index statistics as shown in the output of statements such as SELECT * FROM INFORMATION_SCHEMA.STATISTICS were read from the last partition, instead of from the partition containing the greatest number of rows. * InnoDB: When logging the delete-marking of a record during online ALTER TABLE...ADD PRIMARY KEY, InnoDB writes the transaction ID to the log as it was before the deletion or delete-marking of the record. When doing this, InnoDB would overwrite the DB_TRX_ID field in the original table, which could result in locking issues. * InnoDB: The row_sel_sec_rec_is_for_clust_rec function would incorrectly prepare to compare a NULL column prefix in a secondary index with a non-NULL column in a clustered index. * InnoDB: An incorrect purge would occur when rolling back an update to a delete-marked record. * InnoDB: An assertion would be raised in fil_node_open_file due to a missing .ibd file. Instead of asserting, InnoDB should return false and the caller of fil_node_open_file should handle the return message. * InnoDB: The assertion ut_ad(oldest_lsn <= cur_lsn) in file buf0flu.cc would fail because the current max LSN would be retrieved from the buffer pool before the oldest LSN. * InnoDB: InnoDB memcached add and set operations would perform more slowly than SQL INSERT operations. * InnoDB: The InnoDB memcached plugin could be initialized to insert into an InnoDB table with an INTEGER primary key. More...
2013-10-01 12:26:39 +02:00
share/mysql/test/include/have_valgrind.inc
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/include/have_validate_password_plugin.inc
share/mysql/test/include/ib_logfile_size_check.inc
share/mysql/test/include/icp_tests.inc
share/mysql/test/include/implicit_commit_helper.inc
share/mysql/test/include/index_merge1.inc
share/mysql/test/include/index_merge2.inc
share/mysql/test/include/index_merge_2sweeps.inc
Changes 5.6.12: * mysql_upgrade now verifies that the server version matches the version against which it was compiled, and exits if there is a mismatch. In addiion, a --version-check option permits specifying whether to enable version checking (the default), or disable checking if given as --skip-version-checking. * Bugs Fixed
2013-06-04 20:17:25 +02:00
share/mysql/test/include/index_merge_delete.inc
share/mysql/test/include/index_merge_insert-and-replace.inc
share/mysql/test/include/index_merge_intersect_dml.inc
share/mysql/test/include/index_merge_multi_col_setup.inc
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/include/index_merge_ror.inc
share/mysql/test/include/index_merge_ror_cpk.inc
Changes 5.6.12: * mysql_upgrade now verifies that the server version matches the version against which it was compiled, and exits if there is a mismatch. In addiion, a --version-check option permits specifying whether to enable version checking (the default), or disable checking if given as --skip-version-checking. * Bugs Fixed
2013-06-04 20:17:25 +02:00
share/mysql/test/include/index_merge_single_col_setup.inc
share/mysql/test/include/index_merge_update.inc
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/include/innodb-index.inc
share/mysql/test/include/innodb-util.inc
share/mysql/test/include/innodb_pk_extension.inc
share/mysql/test/include/innodb_rollback_on_timeout.inc
share/mysql/test/include/innodb_trx_weight.inc
Changes 5.6.12: * mysql_upgrade now verifies that the server version matches the version against which it was compiled, and exits if there is a mismatch. In addiion, a --version-check option permits specifying whether to enable version checking (the default), or disable checking if given as --skip-version-checking. * Bugs Fixed
2013-06-04 20:17:25 +02:00
share/mysql/test/include/install_semisync.inc
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/include/io_thd_fault_injection.inc
share/mysql/test/include/ipv6.inc
share/mysql/test/include/ipv6_clients.inc
share/mysql/test/include/ipv6_func.inc
share/mysql/test/include/is_embedded.inc
share/mysql/test/include/join_cache.inc
share/mysql/test/include/kill_query.inc
share/mysql/test/include/kill_query_and_diff_master_slave.inc
share/mysql/test/include/libdaemon_example.ini
Changes 5.6.19: Functionality Added or Changed The obsolete and unmaintained charset2html utility has been removed from MySQL distributions. The mysqlbug, mysql_waitpid, and mysql_zap utilities have been deprecated and will be removed in MySQL 5.7. Bugs Fixed InnoDB: After upgrading from 5.6.10 to MySQL versions up to and including MySQL 5.6.18, InnoDB would attempt to rename obsolete full-text search auxiliary tables on server startup, resulting in an assertion failure. InnoDB: For each insert, memset would be called three times to allocate memory for system fields. To reduce CPU usage, the three memset calls are now combined into a single call. InnoDB: Enabling the InnoDB Table Monitor would result in a ib_table->stat_initialized assertion failure. InnoDB: Setting innodb_max_dirty_pages_pct=0 would leave 1% of dirty pages unflushed. Buffer pool flushing is initiated when the percentage of dirty pages is greater innodb_max_dirty_pages_pct. The internal variables that store the innodb_max_dirty_pages_pct value and the percentage of dirty pages (buf_get_modified_ratio_pct and srv_max_buf_pool_modified_pct) were defined as unsigned integer data types, which meant that a innodb_max_dirty_pages_pct value of 0 required a dirty pages percentage of 1 or greater to initiate buffer pool flushing. To address this problem, the buf_get_modified_ratio_pct and srv_max_buf_pool_modified_pct internal variables are redefined as double data types, which changes the range value for innodb_max_dirty_pages_pct and innodb_max_dirty_pages_pct_lwm from 0 .. 99 to 0 .. 99.99. Additionally, buffer pool flushing is now initiated when the percentage of dirty pages is “greater than or equal to” innodb_max_dirty_pages_pct. Replication: Log rotation events could cause group_relay_log_pos to be moved forward incorrectly within a group. This meant that, when the transaction was retried, or if the SQL thread was stopped in the middle of a transaction following one or more log rotations (such that the transaction or group spanned multiple relay log files), part or all of the group was silently skipped. This issue has been addressed by correcting a problem in the logic used to avoid touching the coordinates of the SQL thread when updating the log position as part of a relay log rotation whereby it was possible to update the SQL thread's coordinates when not using a multi-threaded slave, even in the middle of a group. Replication: When running the server with --gtid-mode=ON, STOP SLAVE followed by START SLAVE resulted in a mismatch between the information provided by INFORMATION_SCHEMA.INNODB_TEMP_TABLE_INFO and the Slave_open_temp_tables status variable: the INNODB_TEMP_TABLE_INFO table showed that no temporary tables existed, but Slave_open_temp_tables had a nonzero value. Replication: In certain cases, the server mishandled triggers and stored procedures that tried to modify other tables when called by CREATE TABLE ... SELECT. This is now handled correctly as an error. Replication: When used on a table employing a transactional storage engine, a failed TRUNCATE TABLE was still written to the binary log and thus replayed on the slave. This could lead to inconsistency when the master retained data that was removed on the slave. Now in such cases TRUNCATE TABLE is logged only when it executes successfully. Replication: The server did not always handle the auto.cnf file correctly in cases where this file's permissions were incorrect. Replication: When the binary log was rotated due to receipt of a SIGHUP signal, the new binary log did not contain the Previous_gtid_event required for subsequent processing of that binary log's GTID events. Now when SIGHUP is received, steps are taken to insure that the server writes the necessary Previous_gtid_event to the new log before writing any GTID events to the new log.
2014-06-02 09:30:38 +02:00
share/mysql/test/include/linux.inc
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/include/linux_sys_vars.inc
share/mysql/test/include/load_sysvars.inc
share/mysql/test/include/loaddata_autocom.inc
share/mysql/test/include/master-slave.inc
Changes 5.6.16: Functionality Added or Changed * InnoDB: New global configuration parameters, innodb_status_output and innodb_status_output_locks, allow you to dynamically enable and disable the standard InnoDB Monitor and InnoDB Lock Monitor for periodic output. Enabling and disabling monitors for periodic output by creating and dropping specially named tables is deprecated and may be removed in a future release. * Previously, ALTER TABLE in MySQL 5.6 could alter a table such that the result had temporal columns in both 5.5 and 5.6 format. Now ALTER TABLE upgrades old temporal columns to 5.6 format for ADD COLUMN, CHANGE COLUMN, MODIFY COLUMN, ADD INDEX, and FORCE operations. This conversion cannot be done using the INPLACE algorithm, so specifying ALGORITHM=INPLACE in these cases results in an error. * CMake now supports a -DTMPDIR=dir_name option to specify the default tmpdir value. If unspecified, the value defaults to P_tmpdir in <stdio.h>. Bugs Fixed * InnoDB; Replication: Using the InnoDB memcached plugin (see InnoDB Integration with memcached) with innodb_api_enable_binlog set to 1 caused the server to leak memory. * InnoDB: A boolean mode full-text search query would result in a memory access violation during parsing. * InnoDB: When new indexes are added by an ALTER TABLE operation, instead of only saving table-level statistics and statistics for the new indexes, InnoDB would save statistics for the entire table, including the table's other indexes. This behavior slowed ALTER TABLE performance. * InnoDB: Due to a parser error, full-text search queries that include a sub-expression could return the wrong result. * InnoDB: The innochecksum tool did not use a Windows-specific API to retrieve file size information, which resulted in an incorrect error message (Error: ibdata1 cannot be found) when the MySQL 5.6 innochecksum 2GB file size limit was exceeded. innochecksum now provides support for files larger than 2GB in both MySQL 5.6 and MySQL 5.7. * InnoDB: Due to a regression introduced by the fix for Bug17371537, memory was not allocated for the default memcached engine when using the default memcached engine as the backstore for data instead of InnoDB. * InnoDB: InnoDB would report an incorrect operating system error code after failing to initialize. * InnoDB: Manipulating a table after discarding its tablespace using ALTER TABLE ... DISCARD TABLESPACE could result in a serious error. * InnoDB: Persistent optimizer statistics would cause stalls due to latch contention. * InnoDB: MATCH() ... AGAINST queries that use a long string as an argument for AGAINST() could result in an error when run on an InnoDB table with a full-text search index. * InnoDB: An InnoDB full-text search failure would occur due to an “unended” token. The string and string length should be passed for string comparison. * InnoDB: In debug builds, a merge insert buffer during a page read would cause a memory access violation. * InnoDB: Truncating a memcached InnoDB table while memcached is performing DML operations would result in a serious error. * InnoDB: In sync0rw.ic, rw_lock_x_lock_func_nowait would needlessly call os_thread_get_curr_id. * InnoDB: Attempting to rename a table to a missing database would result in a serious error. more...
2014-02-13 08:49:56 +01:00
share/mysql/test/include/memcache_config.inc
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/include/min_null_cond.inc
share/mysql/test/include/mix1.inc
share/mysql/test/include/mix2.inc
share/mysql/test/include/mix2_ucs2.inc
share/mysql/test/include/mrr_innodb_tests.inc
share/mysql/test/include/mrr_tests.inc
share/mysql/test/include/mtr_check.sql
share/mysql/test/include/mtr_warnings.sql
share/mysql/test/include/mysql_upgrade_preparation.inc
share/mysql/test/include/mysqlbinlog_have_debug.inc
share/mysql/test/include/mysqlbinlog_raw_mode.inc
share/mysql/test/include/mysqld--help.inc
share/mysql/test/include/mysqldump.inc
share/mysql/test/include/mysqlhotcopy.inc
share/mysql/test/include/mysqltest-x.inc
share/mysql/test/include/ndb_backup.inc
share/mysql/test/include/ndb_backup_id.inc
share/mysql/test/include/ndb_backup_print.inc
share/mysql/test/include/ndb_default_cluster.inc
share/mysql/test/include/ndb_have_online_alter.inc
share/mysql/test/include/ndb_not_readonly.inc
share/mysql/test/include/ndb_restore_master.inc
share/mysql/test/include/ndb_restore_slave_eoption.inc
share/mysql/test/include/ndb_setup_slave.inc
share/mysql/test/include/ndb_wait_connected.inc
Changes 5.6.25: Functionality Added or Changed * MySQL Enterprise Firewall operates on parser states and does not work well together with the query cache, which circumvents the parser. MySQL Enterprise Firewall now checks whether the query cache is enabled. If so, it displays a message that the query cache must be disabled and does not load. * my_print_defaults now masks passwords. To display passwords in cleartext, use the new --show option. * MySQL distributions now include an innodb_stress suite of test cases. Thanks to Mark Callaghan for the contribution. Bugs Fixed * InnoDB; Partitioning: The CREATE_TIME column of the INFORMATION_SCHEMA.TABLES table now shows the correct table creation time for partitioned InnoDB tables. The CREATE_TIME column of the INFORMATION_SCHEMA.PARTITIONS table now shows the correct partition creation time for a partition of partitioned InnoDB tables. The UPDATE_TIME column of the INFORMATION_SCHEMA.TABLES table now shows when a partitioned InnoDB table was last updated by an INSERT, DELETE, or UPDATE. The UPDATE_TIME column of the INFORMATION_SCHEMA.PARTITIONS table now shows when a partition of a partitioned InnoDB table was last updated. * InnoDB: An assertion was raised on shutdown due to XA PREPARE transactions holding explicit locks. * InnoDB: The strict_* forms of innodb_checksum_algorithm settings (strict_none, strict_innodb, and strict_crc32) caused the server to halt when a non-matching checksum was encountered, even though the non-matching checksum was valid. For example, with innodb_checksum_algorithm=strict_crc32, encountering a valid innodb checksum caused the server to halt. Instead of halting the server, a message is now printed to the error log and the page is accepted as valid if it matches an innodb, crc32 or none checksum. * InnoDB: The memcached set command permitted a negative expire time value. Expire time is stored internally as an unsigned integer. A negative value would be converted to a large number and accepted. The maximum expire time value is now restricted to INT_MAX32 to prevent negative expire time values. * InnoDB: Removal of a foreign key object from the data dictionary cache during error handling caused the server to exit. * InnoDB: SHOW ENGINE INNODB STATUS output showed negative reservation and signal count values due to a counter overflow error. * InnoDB: Failure to check the status of a cursor transaction read-only option before reusing the cursor transaction for a write operation resulted in a server exit during a memcached workload. * InnoDB: MDL locks taken by memcached clients caused a MySQL Enterprise Backup FLUSH TABLES WITH READ LOCK operation to hang. * InnoDB: Estimates that were too low for the size of merge chunks in the result sorting algorithm caused a server exit. * InnoDB: For full-text searches, the optimizer could choose an index that does not produce correct relevancy rankings. * Partitioning: When creating a partitioned table, partition-level DATA DIRECTORY or INDEX DIRECTORY option values that contained an excessive number of characters were handled incorrectly. * Partitioning: Executing an ALTER TABLE on a partitioned table on which a write lock was in effect could cause subsequent SQL statements on this table to fail. * Replication: When binary logging was enabled, using stored functions and triggers resulting in a long running procedure that inserted many records caused the memory use to increase rapidly. This was due to memory being allocated per variable. The fix ensures that in such a situation, memory is allocated once and the same memory is reused. * Replication: If an error was encountered while adding a GTID to the received GTID set, the log lock was not being correctly released. This could cause a deadlock. more...
2015-06-01 10:15:05 +02:00
share/mysql/test/include/no_protocol.inc
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/include/no_running_event_scheduler.inc
share/mysql/test/include/no_running_events.inc
share/mysql/test/include/no_valgrind_without_big.inc
share/mysql/test/include/not_as_root.inc
share/mysql/test/include/not_binlog_format_row.inc
share/mysql/test/include/not_blackhole.inc
share/mysql/test/include/not_crashrep.inc
share/mysql/test/include/not_embedded.inc
share/mysql/test/include/not_gtid_enabled.inc
share/mysql/test/include/not_master_info_table.inc
share/mysql/test/include/not_mts_slave_parallel_workers.inc
share/mysql/test/include/not_ndb.inc
share/mysql/test/include/not_ndb_default.inc
share/mysql/test/include/not_openssl.inc
share/mysql/test/include/not_parallel.inc
share/mysql/test/include/not_relay_log_info_table.inc
share/mysql/test/include/not_sha256_rsa_auth.inc
Changes 5.6.11: 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. 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. mysql_config_editor now supports --port and --socket options for specifying TCP/IP port number and Unix socket file name. 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. The only supported value for the innodb_mirrored_log_groups system variable is 1, so this variable is now deprecated. Setting it to 1 at startup results in a warning. Setting it to a value other than 1 at startup results in an error and the server exits. This variable will be removed in a future release.
2013-04-20 10:06:01 +02:00
share/mysql/test/include/not_ssl.inc
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/include/not_threadpool.inc
share/mysql/test/include/not_valgrind.inc
share/mysql/test/include/not_var_link.inc
share/mysql/test/include/not_windows.inc
share/mysql/test/include/not_windows_embedded.inc
share/mysql/test/include/null_key.inc
share/mysql/test/include/one_thread_per_connection.inc
share/mysql/test/include/only_mts_slave_parallel_workers.inc
share/mysql/test/include/order_by.inc
share/mysql/test/include/parser_bug21114.inc
share/mysql/test/include/partition_date_range.inc
share/mysql/test/include/partition_default_functions.inc
share/mysql/test/include/plugin.defs
share/mysql/test/include/print_greedy_search_count.inc
share/mysql/test/include/ps_conv.inc
share/mysql/test/include/ps_create.inc
share/mysql/test/include/ps_ddl_1.inc
share/mysql/test/include/ps_modify.inc
share/mysql/test/include/ps_modify1.inc
share/mysql/test/include/ps_query.inc
share/mysql/test/include/ps_renew.inc
share/mysql/test/include/purge_first_log.inc
share/mysql/test/include/python_with_json.inc
share/mysql/test/include/query_cache.inc
share/mysql/test/include/query_cache_sql_prepare.inc
share/mysql/test/include/rand.inc
share/mysql/test/include/range.inc
share/mysql/test/include/read_file_to_var.inc
share/mysql/test/include/read_many_rows.inc
share/mysql/test/include/relocate_binlogs.inc
share/mysql/test/include/report-features.test
share/mysql/test/include/restart_mysqld.inc
Changes 5.6.13: * Important Change; Replication: By default, when promoting integers from a smaller type on the master to a larger type on the slave (for example, from a SMALLINT column on the master to a BIGINT column on the slave), the promoted values are treated as though they are signed. Now in such cases it is possible to modify or override this behavior using one or both of ALL_SIGNED, ALL_UNSIGNED in the set of values specified for the slave_type_conversions server system variable. For more information, see Row-based replication: attribute promotion and demotion, as well as the description of the variable. * Previously, program options could be specified in full or as any unambiguous prefix. For example, the --compress option could be given to mysqldump as --compr, but not as --comp because the latter is ambiguous. Option prefixes now are deprecated. They can cause problems when new options are implemented for programs. A prefix that is currently unambiguous might become ambiguous in the future. If an unambiguous prefix is given, a warning now occurs to provide feedback. For example: Warning: Using unique option prefix compr instead of compress is deprecated and will be removed in a future release. Please use the full name instead. Option prefixes are no longer supported in MySQL 5.7; only full options are accepted. * The C API libmysqlclient shared-library .so files now have version 18.1.0 (up from version 18.0.0 used in MySQL 5.5). * In batch mode, mysql formatted result status messages such as “"Query OK, 1 row affected"” but did not print them. Now these messages are not formatted. * Bugs Fixed
2013-07-31 11:51:38 +02:00
share/mysql/test/include/restart_readonly_mysqld.inc
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/include/restart_slave_sql.inc
share/mysql/test/include/rowid_order.inc
share/mysql/test/include/rpl_change_topology.inc
share/mysql/test/include/rpl_connect.inc
share/mysql/test/include/rpl_connection.inc
share/mysql/test/include/rpl_connection_master.inc
Changes 5.6.19: Functionality Added or Changed The obsolete and unmaintained charset2html utility has been removed from MySQL distributions. The mysqlbug, mysql_waitpid, and mysql_zap utilities have been deprecated and will be removed in MySQL 5.7. Bugs Fixed InnoDB: After upgrading from 5.6.10 to MySQL versions up to and including MySQL 5.6.18, InnoDB would attempt to rename obsolete full-text search auxiliary tables on server startup, resulting in an assertion failure. InnoDB: For each insert, memset would be called three times to allocate memory for system fields. To reduce CPU usage, the three memset calls are now combined into a single call. InnoDB: Enabling the InnoDB Table Monitor would result in a ib_table->stat_initialized assertion failure. InnoDB: Setting innodb_max_dirty_pages_pct=0 would leave 1% of dirty pages unflushed. Buffer pool flushing is initiated when the percentage of dirty pages is greater innodb_max_dirty_pages_pct. The internal variables that store the innodb_max_dirty_pages_pct value and the percentage of dirty pages (buf_get_modified_ratio_pct and srv_max_buf_pool_modified_pct) were defined as unsigned integer data types, which meant that a innodb_max_dirty_pages_pct value of 0 required a dirty pages percentage of 1 or greater to initiate buffer pool flushing. To address this problem, the buf_get_modified_ratio_pct and srv_max_buf_pool_modified_pct internal variables are redefined as double data types, which changes the range value for innodb_max_dirty_pages_pct and innodb_max_dirty_pages_pct_lwm from 0 .. 99 to 0 .. 99.99. Additionally, buffer pool flushing is now initiated when the percentage of dirty pages is “greater than or equal to” innodb_max_dirty_pages_pct. Replication: Log rotation events could cause group_relay_log_pos to be moved forward incorrectly within a group. This meant that, when the transaction was retried, or if the SQL thread was stopped in the middle of a transaction following one or more log rotations (such that the transaction or group spanned multiple relay log files), part or all of the group was silently skipped. This issue has been addressed by correcting a problem in the logic used to avoid touching the coordinates of the SQL thread when updating the log position as part of a relay log rotation whereby it was possible to update the SQL thread's coordinates when not using a multi-threaded slave, even in the middle of a group. Replication: When running the server with --gtid-mode=ON, STOP SLAVE followed by START SLAVE resulted in a mismatch between the information provided by INFORMATION_SCHEMA.INNODB_TEMP_TABLE_INFO and the Slave_open_temp_tables status variable: the INNODB_TEMP_TABLE_INFO table showed that no temporary tables existed, but Slave_open_temp_tables had a nonzero value. Replication: In certain cases, the server mishandled triggers and stored procedures that tried to modify other tables when called by CREATE TABLE ... SELECT. This is now handled correctly as an error. Replication: When used on a table employing a transactional storage engine, a failed TRUNCATE TABLE was still written to the binary log and thus replayed on the slave. This could lead to inconsistency when the master retained data that was removed on the slave. Now in such cases TRUNCATE TABLE is logged only when it executes successfully. Replication: The server did not always handle the auto.cnf file correctly in cases where this file's permissions were incorrect. Replication: When the binary log was rotated due to receipt of a SIGHUP signal, the new binary log did not contain the Previous_gtid_event required for subsequent processing of that binary log's GTID events. Now when SIGHUP is received, steps are taken to insure that the server writes the necessary Previous_gtid_event to the new log before writing any GTID events to the new log.
2014-06-02 09:30:38 +02:00
share/mysql/test/include/rpl_connection_master1.inc
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/include/rpl_connection_slave.inc
share/mysql/test/include/rpl_connection_slave1.inc
share/mysql/test/include/rpl_default_connections.inc
share/mysql/test/include/rpl_diff.inc
share/mysql/test/include/rpl_end.inc
share/mysql/test/include/rpl_events.inc
share/mysql/test/include/rpl_for_each_slave.inc
share/mysql/test/include/rpl_generate_sync_chain.inc
share/mysql/test/include/rpl_hash_scan_assertion.inc
share/mysql/test/include/rpl_init.inc
share/mysql/test/include/rpl_ip_mix.inc
share/mysql/test/include/rpl_ip_mix2.inc
share/mysql/test/include/rpl_ipv6.inc
share/mysql/test/include/rpl_loaddata_charset.inc
share/mysql/test/include/rpl_multi_engine.inc
share/mysql/test/include/rpl_multi_engine2.inc
share/mysql/test/include/rpl_multi_engine3.inc
share/mysql/test/include/rpl_reconnect.inc
share/mysql/test/include/rpl_reset.inc
share/mysql/test/include/rpl_restart_server.inc
share/mysql/test/include/rpl_row_img_general_loop.inc
share/mysql/test/include/rpl_row_img_parts_assertion.inc
share/mysql/test/include/rpl_row_img_parts_master_slave.inc
share/mysql/test/include/rpl_row_img_set.inc
share/mysql/test/include/rpl_set_gtid_mode.inc
share/mysql/test/include/rpl_start_server.inc
share/mysql/test/include/rpl_start_slaves.inc
share/mysql/test/include/rpl_stmt_seq.inc
share/mysql/test/include/rpl_stop_server.inc
share/mysql/test/include/rpl_stop_slaves.inc
share/mysql/test/include/rpl_sync.inc
share/mysql/test/include/rpl_udf.inc
share/mysql/test/include/running_event_scheduler.inc
share/mysql/test/include/safe_set_to_maybe_ro_var.inc
share/mysql/test/include/save_io_thread_pos.inc
share/mysql/test/include/save_master_pos.inc
Changes 5.6.16: Functionality Added or Changed * InnoDB: New global configuration parameters, innodb_status_output and innodb_status_output_locks, allow you to dynamically enable and disable the standard InnoDB Monitor and InnoDB Lock Monitor for periodic output. Enabling and disabling monitors for periodic output by creating and dropping specially named tables is deprecated and may be removed in a future release. * Previously, ALTER TABLE in MySQL 5.6 could alter a table such that the result had temporal columns in both 5.5 and 5.6 format. Now ALTER TABLE upgrades old temporal columns to 5.6 format for ADD COLUMN, CHANGE COLUMN, MODIFY COLUMN, ADD INDEX, and FORCE operations. This conversion cannot be done using the INPLACE algorithm, so specifying ALGORITHM=INPLACE in these cases results in an error. * CMake now supports a -DTMPDIR=dir_name option to specify the default tmpdir value. If unspecified, the value defaults to P_tmpdir in <stdio.h>. Bugs Fixed * InnoDB; Replication: Using the InnoDB memcached plugin (see InnoDB Integration with memcached) with innodb_api_enable_binlog set to 1 caused the server to leak memory. * InnoDB: A boolean mode full-text search query would result in a memory access violation during parsing. * InnoDB: When new indexes are added by an ALTER TABLE operation, instead of only saving table-level statistics and statistics for the new indexes, InnoDB would save statistics for the entire table, including the table's other indexes. This behavior slowed ALTER TABLE performance. * InnoDB: Due to a parser error, full-text search queries that include a sub-expression could return the wrong result. * InnoDB: The innochecksum tool did not use a Windows-specific API to retrieve file size information, which resulted in an incorrect error message (Error: ibdata1 cannot be found) when the MySQL 5.6 innochecksum 2GB file size limit was exceeded. innochecksum now provides support for files larger than 2GB in both MySQL 5.6 and MySQL 5.7. * InnoDB: Due to a regression introduced by the fix for Bug17371537, memory was not allocated for the default memcached engine when using the default memcached engine as the backstore for data instead of InnoDB. * InnoDB: InnoDB would report an incorrect operating system error code after failing to initialize. * InnoDB: Manipulating a table after discarding its tablespace using ALTER TABLE ... DISCARD TABLESPACE could result in a serious error. * InnoDB: Persistent optimizer statistics would cause stalls due to latch contention. * InnoDB: MATCH() ... AGAINST queries that use a long string as an argument for AGAINST() could result in an error when run on an InnoDB table with a full-text search index. * InnoDB: An InnoDB full-text search failure would occur due to an “unended” token. The string and string length should be passed for string comparison. * InnoDB: In debug builds, a merge insert buffer during a page read would cause a memory access violation. * InnoDB: Truncating a memcached InnoDB table while memcached is performing DML operations would result in a serious error. * InnoDB: In sync0rw.ic, rw_lock_x_lock_func_nowait would needlessly call os_thread_get_curr_id. * InnoDB: Attempting to rename a table to a missing database would result in a serious error. more...
2014-02-13 08:49:56 +01:00
share/mysql/test/include/search_pattern.inc
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/include/search_pattern_in_file.inc
share/mysql/test/include/select.inc
share/mysql/test/include/set_binlog_format_mixed.sql
share/mysql/test/include/set_binlog_format_row.sql
share/mysql/test/include/set_binlog_format_statement.sql
share/mysql/test/include/setup_fake_relay_log.inc
Changes 5.6.21: The --skip-innodb option is now deprecated and its use results in a warning. It will be removed in a future MySQL release. This also applies to its synonyms (--innodb=OFF, --disable-innodb, and so forth). MySQL Enterprise Edition now includes a set of encryption functions based on the OpenSSL library that expose OpenSSL capabilities at the SQL level. Replication: The new variable simplified_binlog_gtid_recovery can be used to change the way binary log files are searched for previous GTIDs during recovery, speeding up the process when a large number of binary log files exist. Internally, spatial data types such as Geometry are represented as BLOB values, so when invoked with the --hex-blob option, mysqldump now displays spatial values in hex. Bugs Fixed...
2014-10-01 10:34:23 +02:00
share/mysql/test/include/show_all_binlogs.inc
share/mysql/test/include/show_all_relay_logs.inc
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/include/show_binary_logs.inc
share/mysql/test/include/show_binlog_events.inc
share/mysql/test/include/show_binlog_events2.inc
share/mysql/test/include/show_binlog_using_logname.inc
share/mysql/test/include/show_delayed_slave_state.inc
share/mysql/test/include/show_events.inc
share/mysql/test/include/show_master_logs.inc
share/mysql/test/include/show_master_status.inc
share/mysql/test/include/show_msg.inc
share/mysql/test/include/show_msg80.inc
share/mysql/test/include/show_relaylog_events.inc
share/mysql/test/include/show_rpl_debug_info.inc
share/mysql/test/include/show_slave_hosts.inc
share/mysql/test/include/show_slave_status.inc
share/mysql/test/include/shutdown_mysqld.inc
share/mysql/test/include/sp-vars.inc
share/mysql/test/include/start_mysqld.inc
share/mysql/test/include/start_slave.inc
share/mysql/test/include/start_slave_io.inc
share/mysql/test/include/start_slave_sql.inc
share/mysql/test/include/stop_dump_threads.inc
share/mysql/test/include/stop_slave.inc
share/mysql/test/include/stop_slave_io.inc
share/mysql/test/include/stop_slave_sql.inc
share/mysql/test/include/strict_autoinc.inc
share/mysql/test/include/subquery.inc
share/mysql/test/include/subquery_mat.inc
share/mysql/test/include/subquery_sj.inc
share/mysql/test/include/subquery_sj_innodb.inc
share/mysql/test/include/sync_slave_io.inc
share/mysql/test/include/sync_slave_io_with_master.inc
share/mysql/test/include/sync_slave_sql.inc
share/mysql/test/include/sync_slave_sql_with_io.inc
share/mysql/test/include/sync_slave_sql_with_master.inc
share/mysql/test/include/system_db_struct.inc
share/mysql/test/include/test_fieldsize.inc
share/mysql/test/include/test_outfile.inc
share/mysql/test/include/testdb_only.inc
share/mysql/test/include/tpcb.inc
share/mysql/test/include/tpcb_disk_data.inc
share/mysql/test/include/truncate_file.inc
Changes 5.6.12: * mysql_upgrade now verifies that the server version matches the version against which it was compiled, and exits if there is a mismatch. In addiion, a --version-check option permits specifying whether to enable version checking (the default), or disable checking if given as --skip-version-checking. * Bugs Fixed
2013-06-04 20:17:25 +02:00
share/mysql/test/include/uninstall_semisync.inc
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/include/unsafe_binlog.inc
share/mysql/test/include/uses_vardir.inc
share/mysql/test/include/varchar.inc
share/mysql/test/include/vardir_size_check.inc
share/mysql/test/include/view_alias.inc
share/mysql/test/include/wait_condition.inc
share/mysql/test/include/wait_condition_sp.inc
share/mysql/test/include/wait_for_binlog_event.inc
Changes 5.6.20: Security Fix: The linked OpenSSL library for the MySQL 5.6 Commercial Server has been updated from version 1.0.1g to version 1.0.1h. Versions of OpenSSL prior to and including 1.0.1g are reported to be vulnerable to CVE-2014-0224. This change does not affect the Oracle-produced MySQL Community build of MySQL Server 5.6, which uses the yaSSL library instead. DTrace Support MySQL now includes DTrace support on Oracle Linux 6 or higher with UEK kernel. If DTrace is present, server builds will detect it with no special CMake options required. For information about using DTrace on MySQL, see Tracing mysqld Using DTrace. InnoDB Notes Important Change: Redo log writes for large, externally stored BLOB fields could overwrite the most recent checkpoint. The 5.6.20 patch limits the size of redo log BLOB writes to 10% of the redo log file size. The 5.7.5 patch addresses the bug without imposing a limitation. For MySQL 5.5, the bug remains a known limitation. As a result of the redo log BLOB write limit introduced for MySQL 5.6, innodb_log_file_size should be set to a value greater than 10 times the largest BLOB data size found in the rows of your tables plus the length of other variable length fields (VARCHAR, VARBINARY, and TEXT type fields). Failing to do so could result in “Row size too large” errors. No action is required if your innodb_log_file_size setting is already sufficiently large or your tables contain no BLOB data. Functionality Added or Changed Replication: The new system variable binlog_impossible_mode controls what happens if the server cannot write to the binary log, for example, due to a file error. For backward compatibility, the default for binlog_impossible_mode is IGNORE_ERROR, meaning the server logs the error, halts logging, and continues updates to the database. Setting this variable to ABORT_SERVER makes the server halt logging and shut down if it cannot write to the binary log. CMake support was updated to handle CMake version 3. New Debian7, Ubuntu12.04, and Ubuntu14.04 distribution support that was introduced with 5.6.17 now comes with the platform-specific packaging source placed under the packaging directory, in the deb-precise, deb-wheezy, and deb-trusty directories. Support for LinuxThreads has been removed from the source code. LinuxThreads was superseded by NPTL in Linux 2.6. By default, mysql_install_db creates a my.cnf file in the installation base directory using a template. This may be undesireable for some deployments. To enable this behavior to be suppressed, mysql_install_db now supports a --keep-my-cnf option to preserve any existing my.cnf file and not create a new my.cnf file. The mysqlhotcopy utility is now deprecated and will be removed in a future version of MySQL. Among the reasons for this: It works only for the MyISAM and ARCHIVE storage engines; it works on Unix but not Windows. Alternatives include mysqldump and MySQL Enterprise Backup. The timed_mutexes system variable has no effect and is deprecated. Bugs Fixed
2014-08-10 17:11:57 +02:00
share/mysql/test/include/wait_for_ndb_committed_to_binlog.inc
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/include/wait_for_query_to_fail.inc
share/mysql/test/include/wait_for_query_to_succeed.inc
share/mysql/test/include/wait_for_slave_io_error.inc
share/mysql/test/include/wait_for_slave_io_to_start.inc
share/mysql/test/include/wait_for_slave_io_to_stop.inc
share/mysql/test/include/wait_for_slave_param.inc
share/mysql/test/include/wait_for_slave_sql_error.inc
share/mysql/test/include/wait_for_slave_sql_error_and_skip.inc
share/mysql/test/include/wait_for_slave_sql_to_start.inc
share/mysql/test/include/wait_for_slave_sql_to_stop.inc
share/mysql/test/include/wait_for_slave_to_start.inc
share/mysql/test/include/wait_for_slave_to_stop.inc
Changes 5.6.25: Functionality Added or Changed * MySQL Enterprise Firewall operates on parser states and does not work well together with the query cache, which circumvents the parser. MySQL Enterprise Firewall now checks whether the query cache is enabled. If so, it displays a message that the query cache must be disabled and does not load. * my_print_defaults now masks passwords. To display passwords in cleartext, use the new --show option. * MySQL distributions now include an innodb_stress suite of test cases. Thanks to Mark Callaghan for the contribution. Bugs Fixed * InnoDB; Partitioning: The CREATE_TIME column of the INFORMATION_SCHEMA.TABLES table now shows the correct table creation time for partitioned InnoDB tables. The CREATE_TIME column of the INFORMATION_SCHEMA.PARTITIONS table now shows the correct partition creation time for a partition of partitioned InnoDB tables. The UPDATE_TIME column of the INFORMATION_SCHEMA.TABLES table now shows when a partitioned InnoDB table was last updated by an INSERT, DELETE, or UPDATE. The UPDATE_TIME column of the INFORMATION_SCHEMA.PARTITIONS table now shows when a partition of a partitioned InnoDB table was last updated. * InnoDB: An assertion was raised on shutdown due to XA PREPARE transactions holding explicit locks. * InnoDB: The strict_* forms of innodb_checksum_algorithm settings (strict_none, strict_innodb, and strict_crc32) caused the server to halt when a non-matching checksum was encountered, even though the non-matching checksum was valid. For example, with innodb_checksum_algorithm=strict_crc32, encountering a valid innodb checksum caused the server to halt. Instead of halting the server, a message is now printed to the error log and the page is accepted as valid if it matches an innodb, crc32 or none checksum. * InnoDB: The memcached set command permitted a negative expire time value. Expire time is stored internally as an unsigned integer. A negative value would be converted to a large number and accepted. The maximum expire time value is now restricted to INT_MAX32 to prevent negative expire time values. * InnoDB: Removal of a foreign key object from the data dictionary cache during error handling caused the server to exit. * InnoDB: SHOW ENGINE INNODB STATUS output showed negative reservation and signal count values due to a counter overflow error. * InnoDB: Failure to check the status of a cursor transaction read-only option before reusing the cursor transaction for a write operation resulted in a server exit during a memcached workload. * InnoDB: MDL locks taken by memcached clients caused a MySQL Enterprise Backup FLUSH TABLES WITH READ LOCK operation to hang. * InnoDB: Estimates that were too low for the size of merge chunks in the result sorting algorithm caused a server exit. * InnoDB: For full-text searches, the optimizer could choose an index that does not produce correct relevancy rankings. * Partitioning: When creating a partitioned table, partition-level DATA DIRECTORY or INDEX DIRECTORY option values that contained an excessive number of characters were handled incorrectly. * Partitioning: Executing an ALTER TABLE on a partitioned table on which a write lock was in effect could cause subsequent SQL statements on this table to fail. * Replication: When binary logging was enabled, using stored functions and triggers resulting in a long running procedure that inserted many records caused the memory use to increase rapidly. This was due to memory being allocated per variable. The fix ensures that in such a situation, memory is allocated once and the same memory is reused. * Replication: If an error was encountered while adding a GTID to the received GTID set, the log lock was not being correctly released. This could cause a deadlock. more...
2015-06-01 10:15:05 +02:00
share/mysql/test/include/wait_for_slave_to_sync_with_master.inc
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/include/wait_for_status_var.inc
Changes 5.6.15: * Previously, MySQL Server distributions included the MySQL Reference Manual in Info format (the Docs/mysql.info file). Because the license for the manual restricts redistribution, its inclusion in Community packages caused problems for downstream redistributors, such as those who create Linux distributions. Community distributions of MySQL Server no longer include the mysql.info file, to make the repackaging and redistribution process easier (for example, the source tarball and its checksum can be used directly). This change applies to all source and binary Community packaging formats. Commercial (Enterprise) distributions are unchanged. * Incompatible Change: Several statement instruments in the setup_instruments table are used by the Performance Schema during the early stages of statement classification before the exact statement type is known. * The Performance Schema now instruments the read/write lock Delegate::lock * A new CMake option, WITH_ASAN, permits enabling address sanitization for compilers that support it. * The hash function used for metadata locking was modified to reduce overhead. * Bugs Fixed
2013-12-03 21:02:41 +01:00
share/mysql/test/include/wait_innodb_all_purged.inc
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/include/wait_show_condition.inc
share/mysql/test/include/wait_time_until_connected_again.inc
share/mysql/test/include/wait_until_connected_again.inc
share/mysql/test/include/wait_until_count_sessions.inc
share/mysql/test/include/wait_until_disconnected.inc
share/mysql/test/include/wait_until_rows_count.inc
share/mysql/test/include/weight_string.inc
share/mysql/test/include/weight_string_8140.inc
share/mysql/test/include/weight_string_8EA1.inc
share/mysql/test/include/weight_string_8FA2C3.inc
share/mysql/test/include/weight_string_A1A1.inc
share/mysql/test/include/weight_string_chde.inc
share/mysql/test/include/weight_string_euro.inc
share/mysql/test/include/weight_string_l1.inc
share/mysql/test/include/weight_string_l12.inc
share/mysql/test/include/weight_string_l14.inc
share/mysql/test/include/weight_string_l2.inc
share/mysql/test/include/weight_string_l3.inc
share/mysql/test/include/weight_string_l4.inc
share/mysql/test/include/windows.inc
share/mysql/test/include/windows_sys_vars.inc
share/mysql/test/include/wl6219-engine.test
share/mysql/test/include/wl6301.inc
share/mysql/test/include/world.inc
share/mysql/test/include/world_schema.inc
share/mysql/test/include/world_schema1.inc
share/mysql/test/include/write_result_to_file.inc
share/mysql/test/include/write_var_to_file.inc
share/mysql/test/lib/My/Config.pm
share/mysql/test/lib/My/ConfigFactory.pm
share/mysql/test/lib/My/CoreDump.pm
share/mysql/test/lib/My/Exec.pm
share/mysql/test/lib/My/File/Path.pm
share/mysql/test/lib/My/Find.pm
share/mysql/test/lib/My/Handles.pm
share/mysql/test/lib/My/Memcache.pm
share/mysql/test/lib/My/Options.pm
share/mysql/test/lib/My/Platform.pm
share/mysql/test/lib/My/SafeProcess.pm
share/mysql/test/lib/My/SafeProcess/Base.pm
share/mysql/test/lib/My/SafeProcess/my_safe_process
share/mysql/test/lib/My/SysInfo.pm
share/mysql/test/lib/My/Test.pm
share/mysql/test/lib/mtr_cases.pm
share/mysql/test/lib/mtr_gcov.pl
share/mysql/test/lib/mtr_gprof.pl
share/mysql/test/lib/mtr_io.pl
share/mysql/test/lib/mtr_match.pm
share/mysql/test/lib/mtr_misc.pl
share/mysql/test/lib/mtr_process.pl
share/mysql/test/lib/mtr_report.pm
share/mysql/test/lib/mtr_results.pm
share/mysql/test/lib/mtr_stress.pl
share/mysql/test/lib/mtr_unique.pm
share/mysql/test/lib/v1/My/Config.pm
share/mysql/test/lib/v1/incompatible.tests
share/mysql/test/lib/v1/mtr_cases.pl
share/mysql/test/lib/v1/mtr_gcov.pl
share/mysql/test/lib/v1/mtr_gprof.pl
share/mysql/test/lib/v1/mtr_im.pl
share/mysql/test/lib/v1/mtr_io.pl
share/mysql/test/lib/v1/mtr_match.pl
share/mysql/test/lib/v1/mtr_misc.pl
share/mysql/test/lib/v1/mtr_process.pl
share/mysql/test/lib/v1/mtr_report.pl
share/mysql/test/lib/v1/mtr_stress.pl
share/mysql/test/lib/v1/mtr_timer.pl
share/mysql/test/lib/v1/mtr_unique.pl
share/mysql/test/lib/v1/mysql-test-run.pl
share/mysql/test/lib/v1/ndb_config_1_node.ini
share/mysql/test/lib/v1/ndb_config_2_node.ini
share/mysql/test/mtr
share/mysql/test/mysql-stress-test.pl
share/mysql/test/mysql-test-run
share/mysql/test/mysql-test-run.pl
share/mysql/test/purify.supp
share/mysql/test/r/1st.result
share/mysql/test/r/alias.result
share/mysql/test/r/almost_full.result
share/mysql/test/r/alter_table-big.result
share/mysql/test/r/alter_table.result
share/mysql/test/r/analyze.result
share/mysql/test/r/ansi.result
share/mysql/test/r/archive-big.result
share/mysql/test/r/archive.result
share/mysql/test/r/archive_bitfield.result
share/mysql/test/r/archive_debug.result
share/mysql/test/r/archive_gis.result
share/mysql/test/r/archive_no_symlink.result
share/mysql/test/r/archive_plugin.result
share/mysql/test/r/archive_symlink.result
share/mysql/test/r/audit_plugin.result
share/mysql/test/r/auth_rpl.result
share/mysql/test/r/auto_increment.result
share/mysql/test/r/backup.result
share/mysql/test/r/bench_count_distinct.result
share/mysql/test/r/big_test.require
share/mysql/test/r/bigint.result
share/mysql/test/r/binary.result
share/mysql/test/r/binlog_tx_isolation.result
share/mysql/test/r/blackhole.result
share/mysql/test/r/blackhole_plugin.result
share/mysql/test/r/bool.result
share/mysql/test/r/bootstrap.result
share/mysql/test/r/bug12427262.result
share/mysql/test/r/bug12969156.result
Changes 5.6.20: Security Fix: The linked OpenSSL library for the MySQL 5.6 Commercial Server has been updated from version 1.0.1g to version 1.0.1h. Versions of OpenSSL prior to and including 1.0.1g are reported to be vulnerable to CVE-2014-0224. This change does not affect the Oracle-produced MySQL Community build of MySQL Server 5.6, which uses the yaSSL library instead. DTrace Support MySQL now includes DTrace support on Oracle Linux 6 or higher with UEK kernel. If DTrace is present, server builds will detect it with no special CMake options required. For information about using DTrace on MySQL, see Tracing mysqld Using DTrace. InnoDB Notes Important Change: Redo log writes for large, externally stored BLOB fields could overwrite the most recent checkpoint. The 5.6.20 patch limits the size of redo log BLOB writes to 10% of the redo log file size. The 5.7.5 patch addresses the bug without imposing a limitation. For MySQL 5.5, the bug remains a known limitation. As a result of the redo log BLOB write limit introduced for MySQL 5.6, innodb_log_file_size should be set to a value greater than 10 times the largest BLOB data size found in the rows of your tables plus the length of other variable length fields (VARCHAR, VARBINARY, and TEXT type fields). Failing to do so could result in “Row size too large” errors. No action is required if your innodb_log_file_size setting is already sufficiently large or your tables contain no BLOB data. Functionality Added or Changed Replication: The new system variable binlog_impossible_mode controls what happens if the server cannot write to the binary log, for example, due to a file error. For backward compatibility, the default for binlog_impossible_mode is IGNORE_ERROR, meaning the server logs the error, halts logging, and continues updates to the database. Setting this variable to ABORT_SERVER makes the server halt logging and shut down if it cannot write to the binary log. CMake support was updated to handle CMake version 3. New Debian7, Ubuntu12.04, and Ubuntu14.04 distribution support that was introduced with 5.6.17 now comes with the platform-specific packaging source placed under the packaging directory, in the deb-precise, deb-wheezy, and deb-trusty directories. Support for LinuxThreads has been removed from the source code. LinuxThreads was superseded by NPTL in Linux 2.6. By default, mysql_install_db creates a my.cnf file in the installation base directory using a template. This may be undesireable for some deployments. To enable this behavior to be suppressed, mysql_install_db now supports a --keep-my-cnf option to preserve any existing my.cnf file and not create a new my.cnf file. The mysqlhotcopy utility is now deprecated and will be removed in a future version of MySQL. Among the reasons for this: It works only for the MyISAM and ARCHIVE storage engines; it works on Unix but not Windows. Alternatives include mysqldump and MySQL Enterprise Backup. The timed_mutexes system variable has no effect and is deprecated. Bugs Fixed
2014-08-10 17:11:57 +02:00
share/mysql/test/r/bug17076131.result
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/r/bug33509.result
share/mysql/test/r/bug39022.result
share/mysql/test/r/bug46080.result
share/mysql/test/r/bug46261.result
share/mysql/test/r/bug46760.result
share/mysql/test/r/bug47671.result
share/mysql/test/r/bug58669.result
share/mysql/test/r/bulk_replace.result
share/mysql/test/r/cache_innodb.result
share/mysql/test/r/case.result
share/mysql/test/r/case_insensitive_file_system.require
share/mysql/test/r/case_sensitive_file_system.require
share/mysql/test/r/cast.result
share/mysql/test/r/change_user.result
share/mysql/test/r/check.result
Changes 5.6.19: Functionality Added or Changed The obsolete and unmaintained charset2html utility has been removed from MySQL distributions. The mysqlbug, mysql_waitpid, and mysql_zap utilities have been deprecated and will be removed in MySQL 5.7. Bugs Fixed InnoDB: After upgrading from 5.6.10 to MySQL versions up to and including MySQL 5.6.18, InnoDB would attempt to rename obsolete full-text search auxiliary tables on server startup, resulting in an assertion failure. InnoDB: For each insert, memset would be called three times to allocate memory for system fields. To reduce CPU usage, the three memset calls are now combined into a single call. InnoDB: Enabling the InnoDB Table Monitor would result in a ib_table->stat_initialized assertion failure. InnoDB: Setting innodb_max_dirty_pages_pct=0 would leave 1% of dirty pages unflushed. Buffer pool flushing is initiated when the percentage of dirty pages is greater innodb_max_dirty_pages_pct. The internal variables that store the innodb_max_dirty_pages_pct value and the percentage of dirty pages (buf_get_modified_ratio_pct and srv_max_buf_pool_modified_pct) were defined as unsigned integer data types, which meant that a innodb_max_dirty_pages_pct value of 0 required a dirty pages percentage of 1 or greater to initiate buffer pool flushing. To address this problem, the buf_get_modified_ratio_pct and srv_max_buf_pool_modified_pct internal variables are redefined as double data types, which changes the range value for innodb_max_dirty_pages_pct and innodb_max_dirty_pages_pct_lwm from 0 .. 99 to 0 .. 99.99. Additionally, buffer pool flushing is now initiated when the percentage of dirty pages is “greater than or equal to” innodb_max_dirty_pages_pct. Replication: Log rotation events could cause group_relay_log_pos to be moved forward incorrectly within a group. This meant that, when the transaction was retried, or if the SQL thread was stopped in the middle of a transaction following one or more log rotations (such that the transaction or group spanned multiple relay log files), part or all of the group was silently skipped. This issue has been addressed by correcting a problem in the logic used to avoid touching the coordinates of the SQL thread when updating the log position as part of a relay log rotation whereby it was possible to update the SQL thread's coordinates when not using a multi-threaded slave, even in the middle of a group. Replication: When running the server with --gtid-mode=ON, STOP SLAVE followed by START SLAVE resulted in a mismatch between the information provided by INFORMATION_SCHEMA.INNODB_TEMP_TABLE_INFO and the Slave_open_temp_tables status variable: the INNODB_TEMP_TABLE_INFO table showed that no temporary tables existed, but Slave_open_temp_tables had a nonzero value. Replication: In certain cases, the server mishandled triggers and stored procedures that tried to modify other tables when called by CREATE TABLE ... SELECT. This is now handled correctly as an error. Replication: When used on a table employing a transactional storage engine, a failed TRUNCATE TABLE was still written to the binary log and thus replayed on the slave. This could lead to inconsistency when the master retained data that was removed on the slave. Now in such cases TRUNCATE TABLE is logged only when it executes successfully. Replication: The server did not always handle the auto.cnf file correctly in cases where this file's permissions were incorrect. Replication: When the binary log was rotated due to receipt of a SIGHUP signal, the new binary log did not contain the Previous_gtid_event required for subsequent processing of that binary log's GTID events. Now when SIGHUP is received, steps are taken to insure that the server writes the necessary Previous_gtid_event to the new log before writing any GTID events to the new log.
2014-06-02 09:30:38 +02:00
share/mysql/test/r/check_auto_permission.result
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/r/check_var_limit.require
share/mysql/test/r/client_xml.result
share/mysql/test/r/comment_column.result
share/mysql/test/r/comment_column2.result
share/mysql/test/r/comment_index.result
share/mysql/test/r/comment_table.result
share/mysql/test/r/comments.result
share/mysql/test/r/commit.result
share/mysql/test/r/commit_1innodb.result
share/mysql/test/r/compare.result
share/mysql/test/r/compress.result
share/mysql/test/r/concurrent_innodb_safelog.result
share/mysql/test/r/concurrent_innodb_unsafelog.result
share/mysql/test/r/connect.result
Changes 5.6.29: * InnoDB: A new InnoDB configuration option, innodb_tmpdir, allows you to configure a separate temporary file directory for online ALTER TABLE operations. This option was introduced to help avoid tmpdir overflows that could occur as a result of large temporary files created during online ALTER TABLE operations. innodb_tmpdir is a SESSION variable and can be configured dynamically using a SET statement. * yaSSL was upgraded to version 2.3.9. This upgrade corrects an issue in which yaSSL handled only cases of zero or one leading zeros for the key agreement instead of potentially any number, which in rare cases could cause connections to fail when using DHE cipher suites. * The Valgrind function signature in mysql-test/valgrind.supp was upgraded for Valgrind 3.11. * Bugs Fixed
2016-02-28 09:58:03 +01:00
share/mysql/test/r/connect_debug.result
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/r/consistent_snapshot.result
share/mysql/test/r/constraints.result
share/mysql/test/r/count_distinct.result
share/mysql/test/r/count_distinct2.result
share/mysql/test/r/count_distinct3.result
share/mysql/test/r/create-big.result
share/mysql/test/r/create.result
share/mysql/test/r/create_not_windows.result
share/mysql/test/r/create_select_tmp.result
share/mysql/test/r/csv.result
share/mysql/test/r/csv_alter_table.result
share/mysql/test/r/csv_not_null.result
share/mysql/test/r/ctype_ascii.result
share/mysql/test/r/ctype_big5.result
share/mysql/test/r/ctype_binary.result
share/mysql/test/r/ctype_collate.result
share/mysql/test/r/ctype_cp1250_ch.result
share/mysql/test/r/ctype_cp1251.result
Changes 5.6.21: The --skip-innodb option is now deprecated and its use results in a warning. It will be removed in a future MySQL release. This also applies to its synonyms (--innodb=OFF, --disable-innodb, and so forth). MySQL Enterprise Edition now includes a set of encryption functions based on the OpenSSL library that expose OpenSSL capabilities at the SQL level. Replication: The new variable simplified_binlog_gtid_recovery can be used to change the way binary log files are searched for previous GTIDs during recovery, speeding up the process when a large number of binary log files exist. Internally, spatial data types such as Geometry are represented as BLOB values, so when invoked with the --hex-blob option, mysqldump now displays spatial values in hex. Bugs Fixed...
2014-10-01 10:34:23 +02:00
share/mysql/test/r/ctype_cp932.result
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/r/ctype_cp932_binlog_row.result
share/mysql/test/r/ctype_cp932_binlog_stm.result
share/mysql/test/r/ctype_create.result
share/mysql/test/r/ctype_errors.result
share/mysql/test/r/ctype_eucjpms.result
share/mysql/test/r/ctype_euckr.result
share/mysql/test/r/ctype_filename.result
share/mysql/test/r/ctype_filesystem.result
share/mysql/test/r/ctype_gb2312.result
share/mysql/test/r/ctype_gbk.result
share/mysql/test/r/ctype_gbk_binlog.result
share/mysql/test/r/ctype_hebrew.result
share/mysql/test/r/ctype_latin1.result
share/mysql/test/r/ctype_latin1_de.result
share/mysql/test/r/ctype_latin2.result
share/mysql/test/r/ctype_latin2_ch.result
share/mysql/test/r/ctype_ldml.result
share/mysql/test/r/ctype_like_range.result
share/mysql/test/r/ctype_many.result
share/mysql/test/r/ctype_mb.result
share/mysql/test/r/ctype_recoding.result
share/mysql/test/r/ctype_sjis.result
share/mysql/test/r/ctype_tis620.result
share/mysql/test/r/ctype_uca.result
share/mysql/test/r/ctype_ucs.result
share/mysql/test/r/ctype_ucs2_def.result
share/mysql/test/r/ctype_ujis.result
share/mysql/test/r/ctype_ujis_ucs2.result
share/mysql/test/r/ctype_utf16.result
share/mysql/test/r/ctype_utf16_def.result
share/mysql/test/r/ctype_utf16_uca.result
share/mysql/test/r/ctype_utf16le.result
share/mysql/test/r/ctype_utf32.result
share/mysql/test/r/ctype_utf32_uca.result
share/mysql/test/r/ctype_utf8.result
share/mysql/test/r/ctype_utf8mb4.result
share/mysql/test/r/ctype_utf8mb4_heap.result
share/mysql/test/r/ctype_utf8mb4_innodb.result
share/mysql/test/r/ctype_utf8mb4_myisam.result
share/mysql/test/r/ctype_utf8mb4_uca.result
share/mysql/test/r/date_formats.result
share/mysql/test/r/ddl_i18n_koi8r.result
share/mysql/test/r/ddl_i18n_utf8.result
share/mysql/test/r/deadlock_innodb.result
share/mysql/test/r/debug_sync.result
share/mysql/test/r/debug_sync2.result
share/mysql/test/r/default.result
share/mysql/test/r/delayed.result
share/mysql/test/r/delete.result
share/mysql/test/r/deprecated_features.result
share/mysql/test/r/derived.result
share/mysql/test/r/dirty_close.result
share/mysql/test/r/disabled_replication.result
share/mysql/test/r/disconnect_on_expired_password_default.result
share/mysql/test/r/disconnect_on_expired_password_off.result
share/mysql/test/r/distinct.result
share/mysql/test/r/drop-no_root.result
share/mysql/test/r/drop.result
share/mysql/test/r/drop_debug.result
share/mysql/test/r/ds_mrr-big.result
Changes 5.6.20: Security Fix: The linked OpenSSL library for the MySQL 5.6 Commercial Server has been updated from version 1.0.1g to version 1.0.1h. Versions of OpenSSL prior to and including 1.0.1g are reported to be vulnerable to CVE-2014-0224. This change does not affect the Oracle-produced MySQL Community build of MySQL Server 5.6, which uses the yaSSL library instead. DTrace Support MySQL now includes DTrace support on Oracle Linux 6 or higher with UEK kernel. If DTrace is present, server builds will detect it with no special CMake options required. For information about using DTrace on MySQL, see Tracing mysqld Using DTrace. InnoDB Notes Important Change: Redo log writes for large, externally stored BLOB fields could overwrite the most recent checkpoint. The 5.6.20 patch limits the size of redo log BLOB writes to 10% of the redo log file size. The 5.7.5 patch addresses the bug without imposing a limitation. For MySQL 5.5, the bug remains a known limitation. As a result of the redo log BLOB write limit introduced for MySQL 5.6, innodb_log_file_size should be set to a value greater than 10 times the largest BLOB data size found in the rows of your tables plus the length of other variable length fields (VARCHAR, VARBINARY, and TEXT type fields). Failing to do so could result in “Row size too large” errors. No action is required if your innodb_log_file_size setting is already sufficiently large or your tables contain no BLOB data. Functionality Added or Changed Replication: The new system variable binlog_impossible_mode controls what happens if the server cannot write to the binary log, for example, due to a file error. For backward compatibility, the default for binlog_impossible_mode is IGNORE_ERROR, meaning the server logs the error, halts logging, and continues updates to the database. Setting this variable to ABORT_SERVER makes the server halt logging and shut down if it cannot write to the binary log. CMake support was updated to handle CMake version 3. New Debian7, Ubuntu12.04, and Ubuntu14.04 distribution support that was introduced with 5.6.17 now comes with the platform-specific packaging source placed under the packaging directory, in the deb-precise, deb-wheezy, and deb-trusty directories. Support for LinuxThreads has been removed from the source code. LinuxThreads was superseded by NPTL in Linux 2.6. By default, mysql_install_db creates a my.cnf file in the installation base directory using a template. This may be undesireable for some deployments. To enable this behavior to be suppressed, mysql_install_db now supports a --keep-my-cnf option to preserve any existing my.cnf file and not create a new my.cnf file. The mysqlhotcopy utility is now deprecated and will be removed in a future version of MySQL. Among the reasons for this: It works only for the MyISAM and ARCHIVE storage engines; it works on Unix but not Windows. Alternatives include mysqldump and MySQL Enterprise Backup. The timed_mutexes system variable has no effect and is deprecated. Bugs Fixed
2014-08-10 17:11:57 +02:00
share/mysql/test/r/dynamic_tracing.result
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/r/empty_table.result
Changes 5.6.28: MySQL Server RPM packages now contain a conflict indicator for MySQL Connector C, such that an error occurs when installing MySQL Server if MySQL Connector C is also installed. To install MySQL Server, remove any MySQL Connector C packages first. mysql_upgrade now attempts to print more informative errors than FATAL ERROR: Upgrade failed. These client programs now support the --enable-cleartext-plugin option: mysqlcheck, mysqldump, mysqlimport, mysqlshow. This option enables the mysql_clear_password cleartext authentication plugin. (See The Cleartext Client-Side Authentication Plugin.) Support for building with Solaris Studio 5.13 was added. Performance Schema digests in DIGEST_TEXT columns have ... appended to the end to indicate when statements exceed the maximum statement size and were truncated. This is also now done for statement text values in SQL_TEXT columns. Bugs Fixed
2015-12-08 09:49:50 +01:00
share/mysql/test/r/enable_cleartext_plugin.result
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/r/endspace.result
share/mysql/test/r/eq_range_idx_stat.result
share/mysql/test/r/error_simulation.result
share/mysql/test/r/errors.result
share/mysql/test/r/events_1.result
share/mysql/test/r/events_2.result
share/mysql/test/r/events_bugs.result
share/mysql/test/r/events_embedded.result
share/mysql/test/r/events_grant.result
share/mysql/test/r/events_logs_tests.result
share/mysql/test/r/events_microsec.result
share/mysql/test/r/events_restart.result
share/mysql/test/r/events_scheduling.result
share/mysql/test/r/events_stress.result
share/mysql/test/r/events_time_zone.result
share/mysql/test/r/events_trans.result
share/mysql/test/r/events_trans_notembedded.result
share/mysql/test/r/execution_constants.result
share/mysql/test/r/explain.result
share/mysql/test/r/explain_json_all.result
share/mysql/test/r/explain_json_none.result
share/mysql/test/r/file_contents.result
share/mysql/test/r/filesort_debug.result
share/mysql/test/r/fix_priv_tables.result
share/mysql/test/r/flush.result
share/mysql/test/r/flush2.result
share/mysql/test/r/flush_block_commit.result
share/mysql/test/r/flush_block_commit_notembedded.result
share/mysql/test/r/flush_read_lock.result
share/mysql/test/r/flush_read_lock_kill.result
share/mysql/test/r/flush_table.result
share/mysql/test/r/foreign_key.result
share/mysql/test/r/fulltext.result
share/mysql/test/r/fulltext2.result
share/mysql/test/r/fulltext3.result
share/mysql/test/r/fulltext_cache.result
share/mysql/test/r/fulltext_distinct.result
share/mysql/test/r/fulltext_left_join.result
share/mysql/test/r/fulltext_multi.result
share/mysql/test/r/fulltext_order_by.result
share/mysql/test/r/fulltext_plugin.result
share/mysql/test/r/fulltext_update.result
share/mysql/test/r/fulltext_var.result
Changes 5.6.17: Functionality Added or Changed Incompatible Change: The AES_ENCRYPT() and AES_DECRYPT() functions now permit control of the block encryption mode and take an optional initialization vector argument: The new block_encryption_mode system variable controls the mode for block-based encryption algorithms. Its default value is aes-128-ecb, which signifies encryption using a key length of 128 bits and ECB mode. An optional init_vector argument provides an initialization vector for encryption modes that require it: AES_ENCRYPT(str,key_str[,init_vector]) AES_DECRYPT(crypt_str,key_str[,init_vector]) A random string of bytes to use for the initialization vector can be produced by calling the new RANDOM_BYTES() function. For more information, see Encryption and Compression Functions. These changes make statements that use AES_ENCRYPT() or AES_DECRYPT() unsafe for statement-based replication and they cannot be stored in the query cache. Queries that use RANDOM_BYTES() are unsafe for statement-based replication and cannot be stored in the query cache. Incompatible Change: The ERROR_FOR_DIVISION_BY_ZERO, NO_ZERO_DATE, and NO_ZERO_IN_DATE SQL modes now are deprecated and setting the sql_mode value to include any of them generates a warning. In MySQL 5.7, these modes do nothing. Instead, their effects are included in the effects of strict SQL mode (STRICT_ALL_TABLES or STRICT_TRANS_TABLES). The motivation for the change in MySQL 5.7 is to reduce the number of SQL modes with an effect dependent on strict mode and make them part of strict mode itself. To make advance preparation for an upgrade to MySQL 5.7, see SQL Mode Changes in MySQL 5.7. That discussion provides guidelines to assess whether your applications will be affected by the SQL mode changes in MySQL 5.7. InnoDB: MySQL now supports rebuilding regular and partitioned InnoDB tables using online DDL (ALGORITHM=INPLACE) for the following operations: OPTIMIZE TABLE ALTER TABLE ... FORCE ALTER TABLE ... ENGINE=INNODB (when run on an InnoDB table) Online DDL support reduces table rebuild time and permits concurrent DML, which helps reduce user application downtime. For additional information, see Overview of Online DDL. On Solaris, mysql_config --libs now includes -R/path/to/library so that libraries can be found at runtime. mysql_install_db provides a more informative diagnostic message when required Perl modules are missing. The IGNORE clause for ALTER TABLE is now deprecated and will be removed in a future version of MySQL. ALTER IGNORE TABLE causes problems for replication, prevents online ALTER TABLE for unique index creation, and causes problems with foreign keys (rows removed in the parent table). Bugs Fixed
2014-03-31 12:32:13 +02:00
share/mysql/test/r/func_aes.result
share/mysql/test/r/func_aes_cfb1.result
share/mysql/test/r/func_aes_cfb128.result
share/mysql/test/r/func_aes_cfb8.result
share/mysql/test/r/func_aes_misc.result
share/mysql/test/r/func_aes_ofb.result
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/r/func_analyse.result
share/mysql/test/r/func_compress.result
share/mysql/test/r/func_concat.result
share/mysql/test/r/func_crypt.result
share/mysql/test/r/func_date_add.result
share/mysql/test/r/func_default.result
share/mysql/test/r/func_des_encrypt.result
share/mysql/test/r/func_digest.result
share/mysql/test/r/func_encrypt.result
share/mysql/test/r/func_encrypt_nossl.result
share/mysql/test/r/func_encrypt_ucs2.result
share/mysql/test/r/func_equal.result
share/mysql/test/r/func_gconcat.result
share/mysql/test/r/func_group.result
share/mysql/test/r/func_group_innodb.result
share/mysql/test/r/func_group_innodb_16k.result
share/mysql/test/r/func_if.result
share/mysql/test/r/func_in_all.result
share/mysql/test/r/func_in_icp.result
share/mysql/test/r/func_in_icp_mrr.result
share/mysql/test/r/func_in_mrr.result
share/mysql/test/r/func_in_mrr_cost.result
share/mysql/test/r/func_in_none.result
share/mysql/test/r/func_isnull.result
share/mysql/test/r/func_like.result
share/mysql/test/r/func_math.result
share/mysql/test/r/func_misc.result
share/mysql/test/r/func_op.result
share/mysql/test/r/func_regexp.result
share/mysql/test/r/func_rollback.result
share/mysql/test/r/func_sapdb.result
share/mysql/test/r/func_set.result
share/mysql/test/r/func_str.result
Changes 5.6.27: * InnoDB: The new innodb_numa_interleave read-only configuration option allows you to enable the NUMA interleave memory policy for allocation of the InnoDB buffer pool. When innodb_numa_interleave is enabled, the NUMA memory policy is set to MPOL_INTERLEAVE for the mysqld process. After the InnoDB buffer pool is allocated, the NUMA memory policy is set back to MPOL_DEFAULT. This option is only available on NUMA-enabled systems. * yaSSL was upgraded to version 2.3.8. * RPM .spec files were updated so that MySQL Server builds from source RPM packages will include the proper files to take advantage of operating system NUMA capabilities. This introduces a runtime dependency on libnuma.so.1. RPM and yum detect this and refuse to install if that library is not installed. * InnoDB: Reloading a table that was evicted while empty caused an AUTO_INCREMENT value to be reset. * InnoDB: Memory allocation sanity checks were added to the memcached code. * InnoDB: A memcached flush_all command raised an assertion. A function that starts a transaction was called from within assertion code. * InnoDB: A data corruption occurred on ARM64. GCC builtins did not issue the correct fences when setting or unsetting the lock word. * InnoDB: Server shutdown was delayed waiting for the purge thread to exit. To avoid this problem, the number of calls to trx_purge() was reduced, and the trx_purge() batch size was reduced to 20. * InnoDB: In READ COMMITTED mode, a REPLACE operation on a unique secondary index resulted in a constraint violation. * InnoDB: The IBUF_BITMAP_FREE bit indicated that there was more free space in the leaf page than was actually available. * InnoDB: Setting lower_case_table_names=0 on a case-insensitive file system could result in a hang condition when running an INSERT INTO ... SELECT ... FROM tbl_name operation with the wrong tbl_name letter case. An error message is now printed and the server exits when attempting to start the server with --lower_case_table_names=0 on a case-insensitive file system. * InnoDB: The server failed to start with an innodb_force_recovery setting greater than 3. InnoDB was set to read-only mode before redo logs were applied. * InnoDB: The trx_sys_read_pertable_file_format_id() function reported the wrong file format. * Partitioning: CREATE TABLE statements that used an invalid function in a subpartitioning expression did not always fail gracefully as expected. * Partitioning: Error handling for failed partitioning-related ALTER TABLE operations against non-partitioned tables was not performed correctly * Partitioning: ALTER TABLE when executed from a stored procedure did not always work correctly with tables partitioned by RANGE. * Replication: Repeatedly checking for ERR_LOCK_WAIT_TIMEOUT (as done, for example by repeatedly executing SHOW SLAVE STATUS) during a prolonged write lock on a table led to an assert. * Replication: If statement based logging was in use, when updating multiple tables in a single statement, a single transaction could be logged as two different transactions. This was due to the binary logging process not properly identifying statements which were operating over transactional tables. The fix ensures that they are correctly identified, even if such statements do not change the contents of the tables.
2015-10-03 14:46:13 +02:00
share/mysql/test/r/func_str_debug.result
share/mysql/test/r/func_str_no_ps.result
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/r/func_system.result
share/mysql/test/r/func_test.result
share/mysql/test/r/func_time.result
share/mysql/test/r/func_timestamp.result
share/mysql/test/r/func_weight_string.result
share/mysql/test/r/function_defaults.result
share/mysql/test/r/function_defaults_notembedded.result
share/mysql/test/r/gcc296.result
share/mysql/test/r/get_diagnostics.result
share/mysql/test/r/gis-debug.result
share/mysql/test/r/gis-precise.result
share/mysql/test/r/gis-rt-precise.result
share/mysql/test/r/gis-rtree.result
share/mysql/test/r/gis.result
share/mysql/test/r/grant.result
share/mysql/test/r/grant2.result
share/mysql/test/r/grant3.result
share/mysql/test/r/grant4.result
share/mysql/test/r/grant_cache.result
share/mysql/test/r/grant_explain_non_select.result
share/mysql/test/r/grant_lowercase_fs.result
share/mysql/test/r/greedy_optimizer.result
share/mysql/test/r/greedy_search.result
share/mysql/test/r/group_by.result
share/mysql/test/r/group_min_max.result
share/mysql/test/r/group_min_max_innodb.result
share/mysql/test/r/handler_innodb.result
share/mysql/test/r/handler_myisam.result
share/mysql/test/r/handler_read_last.result
share/mysql/test/r/have_big5.require
share/mysql/test/r/have_binlog_format_mixed.require
share/mysql/test/r/have_binlog_format_row.require
share/mysql/test/r/have_binlog_format_statement.require
share/mysql/test/r/have_binlog_rows_query.require
share/mysql/test/r/have_compress.require
share/mysql/test/r/have_cp1250_ch.require
share/mysql/test/r/have_cp1251.require
share/mysql/test/r/have_cp866.require
share/mysql/test/r/have_cp932.require
share/mysql/test/r/have_crypt.require
share/mysql/test/r/have_debug.require
share/mysql/test/r/have_debug_sync.require
share/mysql/test/r/have_eucjpms.require
share/mysql/test/r/have_euckr.require
share/mysql/test/r/have_gb2312.require
share/mysql/test/r/have_gbk.require
share/mysql/test/r/have_geometry.require
share/mysql/test/r/have_koi8r.require
share/mysql/test/r/have_latin2_ch.require
share/mysql/test/r/have_local_infile.require
share/mysql/test/r/have_log_bin.require
share/mysql/test/r/have_met_timezone.require
share/mysql/test/r/have_moscow_leap_timezone.require
share/mysql/test/r/have_mysql_upgrade.result
share/mysql/test/r/have_ndb_extra.require
share/mysql/test/r/have_ndbapi_examples.require
share/mysql/test/r/have_nodebug.require
share/mysql/test/r/have_optimizer_switch.require
share/mysql/test/r/have_outfile.require
share/mysql/test/r/have_partition.require
share/mysql/test/r/have_perror.require
share/mysql/test/r/have_profiling.require
share/mysql/test/r/have_query_cache.require
share/mysql/test/r/have_sjis.require
share/mysql/test/r/have_ssl.require
share/mysql/test/r/have_ssl_is_yes_or_disabled_only.require
share/mysql/test/r/have_symlink.require
share/mysql/test/r/have_tis620.require
share/mysql/test/r/have_ucs2.require
share/mysql/test/r/have_ujis.require
share/mysql/test/r/have_utf16.require
share/mysql/test/r/have_utf32.require
share/mysql/test/r/have_utf8.require
share/mysql/test/r/have_utf8mb4.require
share/mysql/test/r/having.result
share/mysql/test/r/heap.result
share/mysql/test/r/heap_auto_increment.result
share/mysql/test/r/heap_btree.result
share/mysql/test/r/heap_hash.result
share/mysql/test/r/help.result
share/mysql/test/r/host_cache_size_functionality.result
share/mysql/test/r/implicit_char_to_num_conversion.result
share/mysql/test/r/implicit_commit.result
Changes 5.6.12: * mysql_upgrade now verifies that the server version matches the version against which it was compiled, and exits if there is a mismatch. In addiion, a --version-check option permits specifying whether to enable version checking (the default), or disable checking if given as --skip-version-checking. * Bugs Fixed
2013-06-04 20:17:25 +02:00
share/mysql/test/r/index_merge_delete.result
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/r/index_merge_innodb.result
Changes 5.6.12: * mysql_upgrade now verifies that the server version matches the version against which it was compiled, and exits if there is a mismatch. In addiion, a --version-check option permits specifying whether to enable version checking (the default), or disable checking if given as --skip-version-checking. * Bugs Fixed
2013-06-04 20:17:25 +02:00
share/mysql/test/r/index_merge_insert-and-replace.result
share/mysql/test/r/index_merge_intersect_dml.result
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/r/index_merge_myisam.result
Changes 5.6.12: * mysql_upgrade now verifies that the server version matches the version against which it was compiled, and exits if there is a mismatch. In addiion, a --version-check option permits specifying whether to enable version checking (the default), or disable checking if given as --skip-version-checking. * Bugs Fixed
2013-06-04 20:17:25 +02:00
share/mysql/test/r/index_merge_update.result
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/r/information_schema-big.result
share/mysql/test/r/information_schema.result
share/mysql/test/r/information_schema_chmod.result
share/mysql/test/r/information_schema_db.result
share/mysql/test/r/information_schema_inno.result
share/mysql/test/r/information_schema_parameters.result
share/mysql/test/r/information_schema_part.result
share/mysql/test/r/information_schema_routines.result
share/mysql/test/r/init_connect.result
share/mysql/test/r/init_file.result
share/mysql/test/r/innodb_explain_json_non_select_all.result
share/mysql/test/r/innodb_explain_json_non_select_none.result
share/mysql/test/r/innodb_explain_non_select_all.result
share/mysql/test/r/innodb_explain_non_select_none.result
share/mysql/test/r/innodb_icp.result
share/mysql/test/r/innodb_icp_all.result
share/mysql/test/r/innodb_icp_none.result
share/mysql/test/r/innodb_ignore_builtin.result
share/mysql/test/r/innodb_log_file_size_functionality.result
share/mysql/test/r/innodb_mrr.result
share/mysql/test/r/innodb_mrr_all.result
share/mysql/test/r/innodb_mrr_cost.result
share/mysql/test/r/innodb_mrr_cost_all.result
share/mysql/test/r/innodb_mrr_cost_icp.result
share/mysql/test/r/innodb_mrr_icp.result
share/mysql/test/r/innodb_mrr_none.result
share/mysql/test/r/innodb_mysql_lock.result
share/mysql/test/r/innodb_mysql_lock2.result
share/mysql/test/r/innodb_mysql_sync.result
share/mysql/test/r/innodb_pk_extension_off.result
share/mysql/test/r/innodb_pk_extension_on.result
Changes 5.6.22: * Noisy compiler warnings on FreeBSD 10 were silenced. * CMake workarounds for older Mac OS X and XCode versions were removed. On Mac OS X, compilation always uses Clang, even for 32-bit builds. * Previously, the MYSQL_MAINTAINER_MODE CMake option was turned on by default for debug builds and off for release builds, and MYSQL_MAINTAINER_MODE caused -Werror to be enabled when building with GCC. This made it cumbersome to enable -Werror under certain conditions, such as when compiling with Clang. * Build support was modified to produce the same warnings for Clang as for gcc. * CMake configuration for the Clang compiler sets more appropriate flags for building on Linux. Specifically, -g -fno-omit-frame-pointer -fno-strict-aliasing is now added. * Bugs fixed.
2014-12-02 13:40:09 +01:00
share/mysql/test/r/innodb_recovery_with_upper_case_names.result
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/r/insert.result
share/mysql/test/r/insert_notembedded.result
share/mysql/test/r/insert_select.result
share/mysql/test/r/insert_update.result
share/mysql/test/r/ipv4_as_ipv6.result
share/mysql/test/r/ipv6.result
share/mysql/test/r/is_debug_build.require
share/mysql/test/r/is_embedded.require
share/mysql/test/r/isam.result
share/mysql/test/r/join.result
share/mysql/test/r/join_cache_bka.result
share/mysql/test/r/join_cache_bka_nixbnl.result
share/mysql/test/r/join_cache_bkaunique.result
share/mysql/test/r/join_cache_bnl.result
share/mysql/test/r/join_cache_nojb.result
share/mysql/test/r/join_crash.result
share/mysql/test/r/join_nested.result
share/mysql/test/r/join_nested_bka.result
share/mysql/test/r/join_nested_bka_nixbnl.result
share/mysql/test/r/join_optimizer.result
share/mysql/test/r/join_outer.result
share/mysql/test/r/join_outer_bka.result
share/mysql/test/r/join_outer_bka_nixbnl.result
share/mysql/test/r/join_outer_innodb.result
share/mysql/test/r/key.result
share/mysql/test/r/key_cache.result
share/mysql/test/r/key_diff.result
share/mysql/test/r/key_primary.result
share/mysql/test/r/keywords.result
share/mysql/test/r/kill.result
share/mysql/test/r/kill_debug.result
share/mysql/test/r/limit.result
share/mysql/test/r/loaddata.result
share/mysql/test/r/loaddata_autocom_innodb.result
share/mysql/test/r/loadxml.result
share/mysql/test/r/locale.result
share/mysql/test/r/lock.result
share/mysql/test/r/lock_multi.result
share/mysql/test/r/lock_multi_bug38499.result
share/mysql/test/r/lock_multi_bug38691.result
share/mysql/test/r/lock_sync.result
share/mysql/test/r/lock_tables_lost_commit.result
Changes 5.6.25: Functionality Added or Changed * MySQL Enterprise Firewall operates on parser states and does not work well together with the query cache, which circumvents the parser. MySQL Enterprise Firewall now checks whether the query cache is enabled. If so, it displays a message that the query cache must be disabled and does not load. * my_print_defaults now masks passwords. To display passwords in cleartext, use the new --show option. * MySQL distributions now include an innodb_stress suite of test cases. Thanks to Mark Callaghan for the contribution. Bugs Fixed * InnoDB; Partitioning: The CREATE_TIME column of the INFORMATION_SCHEMA.TABLES table now shows the correct table creation time for partitioned InnoDB tables. The CREATE_TIME column of the INFORMATION_SCHEMA.PARTITIONS table now shows the correct partition creation time for a partition of partitioned InnoDB tables. The UPDATE_TIME column of the INFORMATION_SCHEMA.TABLES table now shows when a partitioned InnoDB table was last updated by an INSERT, DELETE, or UPDATE. The UPDATE_TIME column of the INFORMATION_SCHEMA.PARTITIONS table now shows when a partition of a partitioned InnoDB table was last updated. * InnoDB: An assertion was raised on shutdown due to XA PREPARE transactions holding explicit locks. * InnoDB: The strict_* forms of innodb_checksum_algorithm settings (strict_none, strict_innodb, and strict_crc32) caused the server to halt when a non-matching checksum was encountered, even though the non-matching checksum was valid. For example, with innodb_checksum_algorithm=strict_crc32, encountering a valid innodb checksum caused the server to halt. Instead of halting the server, a message is now printed to the error log and the page is accepted as valid if it matches an innodb, crc32 or none checksum. * InnoDB: The memcached set command permitted a negative expire time value. Expire time is stored internally as an unsigned integer. A negative value would be converted to a large number and accepted. The maximum expire time value is now restricted to INT_MAX32 to prevent negative expire time values. * InnoDB: Removal of a foreign key object from the data dictionary cache during error handling caused the server to exit. * InnoDB: SHOW ENGINE INNODB STATUS output showed negative reservation and signal count values due to a counter overflow error. * InnoDB: Failure to check the status of a cursor transaction read-only option before reusing the cursor transaction for a write operation resulted in a server exit during a memcached workload. * InnoDB: MDL locks taken by memcached clients caused a MySQL Enterprise Backup FLUSH TABLES WITH READ LOCK operation to hang. * InnoDB: Estimates that were too low for the size of merge chunks in the result sorting algorithm caused a server exit. * InnoDB: For full-text searches, the optimizer could choose an index that does not produce correct relevancy rankings. * Partitioning: When creating a partitioned table, partition-level DATA DIRECTORY or INDEX DIRECTORY option values that contained an excessive number of characters were handled incorrectly. * Partitioning: Executing an ALTER TABLE on a partitioned table on which a write lock was in effect could cause subsequent SQL statements on this table to fail. * Replication: When binary logging was enabled, using stored functions and triggers resulting in a long running procedure that inserted many records caused the memory use to increase rapidly. This was due to memory being allocated per variable. The fix ensures that in such a situation, memory is allocated once and the same memory is reused. * Replication: If an error was encountered while adding a GTID to the received GTID set, the log lock was not being correctly released. This could cause a deadlock. more...
2015-06-01 10:15:05 +02:00
share/mysql/test/r/log_empty_name.result
Changes 5.6.21: The --skip-innodb option is now deprecated and its use results in a warning. It will be removed in a future MySQL release. This also applies to its synonyms (--innodb=OFF, --disable-innodb, and so forth). MySQL Enterprise Edition now includes a set of encryption functions based on the OpenSSL library that expose OpenSSL capabilities at the SQL level. Replication: The new variable simplified_binlog_gtid_recovery can be used to change the way binary log files are searched for previous GTIDs during recovery, speeding up the process when a large number of binary log files exist. Internally, spatial data types such as Geometry are represented as BLOB values, so when invoked with the --hex-blob option, mysqldump now displays spatial values in hex. Bugs Fixed...
2014-10-01 10:34:23 +02:00
share/mysql/test/r/log_errchk.result
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/r/log_state.result
share/mysql/test/r/log_state_bug33693.result
share/mysql/test/r/log_tables-big.result
share/mysql/test/r/log_tables.result
share/mysql/test/r/log_tables_debug.result
share/mysql/test/r/log_tables_upgrade.result
share/mysql/test/r/long_tmpdir.result
share/mysql/test/r/lowercase0.require
share/mysql/test/r/lowercase1.require
share/mysql/test/r/lowercase2.require
share/mysql/test/r/lowercase_fs_off.result
Changes 5.6.27: * InnoDB: The new innodb_numa_interleave read-only configuration option allows you to enable the NUMA interleave memory policy for allocation of the InnoDB buffer pool. When innodb_numa_interleave is enabled, the NUMA memory policy is set to MPOL_INTERLEAVE for the mysqld process. After the InnoDB buffer pool is allocated, the NUMA memory policy is set back to MPOL_DEFAULT. This option is only available on NUMA-enabled systems. * yaSSL was upgraded to version 2.3.8. * RPM .spec files were updated so that MySQL Server builds from source RPM packages will include the proper files to take advantage of operating system NUMA capabilities. This introduces a runtime dependency on libnuma.so.1. RPM and yum detect this and refuse to install if that library is not installed. * InnoDB: Reloading a table that was evicted while empty caused an AUTO_INCREMENT value to be reset. * InnoDB: Memory allocation sanity checks were added to the memcached code. * InnoDB: A memcached flush_all command raised an assertion. A function that starts a transaction was called from within assertion code. * InnoDB: A data corruption occurred on ARM64. GCC builtins did not issue the correct fences when setting or unsetting the lock word. * InnoDB: Server shutdown was delayed waiting for the purge thread to exit. To avoid this problem, the number of calls to trx_purge() was reduced, and the trx_purge() batch size was reduced to 20. * InnoDB: In READ COMMITTED mode, a REPLACE operation on a unique secondary index resulted in a constraint violation. * InnoDB: The IBUF_BITMAP_FREE bit indicated that there was more free space in the leaf page than was actually available. * InnoDB: Setting lower_case_table_names=0 on a case-insensitive file system could result in a hang condition when running an INSERT INTO ... SELECT ... FROM tbl_name operation with the wrong tbl_name letter case. An error message is now printed and the server exits when attempting to start the server with --lower_case_table_names=0 on a case-insensitive file system. * InnoDB: The server failed to start with an innodb_force_recovery setting greater than 3. InnoDB was set to read-only mode before redo logs were applied. * InnoDB: The trx_sys_read_pertable_file_format_id() function reported the wrong file format. * Partitioning: CREATE TABLE statements that used an invalid function in a subpartitioning expression did not always fail gracefully as expected. * Partitioning: Error handling for failed partitioning-related ALTER TABLE operations against non-partitioned tables was not performed correctly * Partitioning: ALTER TABLE when executed from a stored procedure did not always work correctly with tables partitioned by RANGE. * Replication: Repeatedly checking for ERR_LOCK_WAIT_TIMEOUT (as done, for example by repeatedly executing SHOW SLAVE STATUS) during a prolonged write lock on a table led to an assert. * Replication: If statement based logging was in use, when updating multiple tables in a single statement, a single transaction could be logged as two different transactions. This was due to the binary logging process not properly identifying statements which were operating over transactional tables. The fix ensures that they are correctly identified, even if such statements do not change the contents of the tables.
2015-10-03 14:46:13 +02:00
share/mysql/test/r/lowercase_fs_on.result
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/r/lowercase_mixed_tmpdir.result
share/mysql/test/r/lowercase_mixed_tmpdir_innodb.result
share/mysql/test/r/lowercase_table.result
share/mysql/test/r/lowercase_table2.result
share/mysql/test/r/lowercase_table4.result
share/mysql/test/r/lowercase_table_grant.result
share/mysql/test/r/lowercase_table_qcache.result
share/mysql/test/r/lowercase_utf8.result
share/mysql/test/r/lowercase_view.result
share/mysql/test/r/mdl_sync.result
share/mysql/test/r/merge-big.result
share/mysql/test/r/merge.result
share/mysql/test/r/merge_innodb.result
share/mysql/test/r/merge_mmap.result
share/mysql/test/r/metadata.result
share/mysql/test/r/mix2_myisam.result
share/mysql/test/r/mix2_myisam_ucs2.result
share/mysql/test/r/multi_plugin_load.result
share/mysql/test/r/multi_plugin_load_add.result
share/mysql/test/r/multi_plugin_load_add2.result
share/mysql/test/r/multi_statement.result
share/mysql/test/r/multi_update.result
share/mysql/test/r/multi_update2.result
share/mysql/test/r/multi_update_innodb.result
share/mysql/test/r/multi_update_tiny_hash.result
share/mysql/test/r/myisam-blob.result
share/mysql/test/r/myisam-system.result
share/mysql/test/r/myisam.result
share/mysql/test/r/myisam_crash_before_flush_keys.result
share/mysql/test/r/myisam_debug.result
share/mysql/test/r/myisam_explain_json_non_select_all.result
share/mysql/test/r/myisam_explain_json_non_select_none.result
share/mysql/test/r/myisam_explain_non_select_all.result
share/mysql/test/r/myisam_explain_non_select_none.result
share/mysql/test/r/myisam_icp.result
share/mysql/test/r/myisam_icp_all.result
share/mysql/test/r/myisam_icp_none.result
share/mysql/test/r/myisam_mrr.result
share/mysql/test/r/myisam_mrr_all.result
share/mysql/test/r/myisam_mrr_cost.result
share/mysql/test/r/myisam_mrr_cost_all.result
share/mysql/test/r/myisam_mrr_cost_icp.result
share/mysql/test/r/myisam_mrr_icp.result
share/mysql/test/r/myisam_mrr_none.result
Changes 5.6.26: * Security Fix: Due to the LogJam issue (https://weakdh.org/), OpenSSL has changed the Diffie-Hellman key length parameters for openssl-1.0.1n and up. * Replication: When using a multi-threaded slave, each worker thread has its own queue of transactions to process. In previous MySQL versions, STOP SLAVE waited for all workers to process their entire queue. This logic has been changed so that STOP SLAVE first finds the newest transaction that was committed by any worker thread. Then, it waits for all workers to complete transactions older than that. Newer transactions are not processed. The new logic allows STOP SLAVE to complete faster in case some worker queues contain multiple transactions. * Previously, the max_digest_length system variable controlled the maximum digest length for all server functions that computed statement digests. However, whereas the Performance Schema may need to maintain many digest values, other server functions such as MySQL Enterprise Firewall need only one digest per session. Increasing the max_digest_length value has little impact on total memory requirements for those functions, but can increase Performance Schema memory requirements significantly. To enable configuring digest length separately for the Performance Schema, its digest length is now controlled by the new performance_schema_max_digest_length system variable. * Previously, changes to the validate_password plugin dictionary file (named by the validate_password_dictionary_file system variable) while the server was running required a restart for the server to recognize the changes. Now validate_password_dictionary_file can be set at runtime and assigning a value causes the named file to be read without a restart. In addition, two new status variables are available. validate_password_dictionary_file_last_parsed indicates when the dictionary file was last read, and validate_password_dictionary_file_words_count indicates how many words it contains. * Bugs fixed
2015-07-30 16:39:18 +02:00
share/mysql/test/r/myisam_recover.result
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/r/myisam_row_rpl.result
share/mysql/test/r/myisampack.result
share/mysql/test/r/mysql-bug41486.result
share/mysql/test/r/mysql-bug45236.result
share/mysql/test/r/mysql.result
share/mysql/test/r/mysql_binary_mode.result
share/mysql/test/r/mysql_client_test.result
share/mysql/test/r/mysql_client_test_embedded.result
share/mysql/test/r/mysql_comments.result
share/mysql/test/r/mysql_config_editor.result
share/mysql/test/r/mysql_cp932.result
share/mysql/test/r/mysql_embedded.result
share/mysql/test/r/mysql_embedded_client_test.result
share/mysql/test/r/mysql_locale_posix.result
share/mysql/test/r/mysql_not_windows.result
share/mysql/test/r/mysql_plugin.result
share/mysql/test/r/mysql_protocols.result
share/mysql/test/r/mysql_upgrade.result
share/mysql/test/r/mysql_upgrade_ssl.result
share/mysql/test/r/mysqladmin.result
share/mysql/test/r/mysqlbinlog.result
Changes 5.6.20: Security Fix: The linked OpenSSL library for the MySQL 5.6 Commercial Server has been updated from version 1.0.1g to version 1.0.1h. Versions of OpenSSL prior to and including 1.0.1g are reported to be vulnerable to CVE-2014-0224. This change does not affect the Oracle-produced MySQL Community build of MySQL Server 5.6, which uses the yaSSL library instead. DTrace Support MySQL now includes DTrace support on Oracle Linux 6 or higher with UEK kernel. If DTrace is present, server builds will detect it with no special CMake options required. For information about using DTrace on MySQL, see Tracing mysqld Using DTrace. InnoDB Notes Important Change: Redo log writes for large, externally stored BLOB fields could overwrite the most recent checkpoint. The 5.6.20 patch limits the size of redo log BLOB writes to 10% of the redo log file size. The 5.7.5 patch addresses the bug without imposing a limitation. For MySQL 5.5, the bug remains a known limitation. As a result of the redo log BLOB write limit introduced for MySQL 5.6, innodb_log_file_size should be set to a value greater than 10 times the largest BLOB data size found in the rows of your tables plus the length of other variable length fields (VARCHAR, VARBINARY, and TEXT type fields). Failing to do so could result in “Row size too large” errors. No action is required if your innodb_log_file_size setting is already sufficiently large or your tables contain no BLOB data. Functionality Added or Changed Replication: The new system variable binlog_impossible_mode controls what happens if the server cannot write to the binary log, for example, due to a file error. For backward compatibility, the default for binlog_impossible_mode is IGNORE_ERROR, meaning the server logs the error, halts logging, and continues updates to the database. Setting this variable to ABORT_SERVER makes the server halt logging and shut down if it cannot write to the binary log. CMake support was updated to handle CMake version 3. New Debian7, Ubuntu12.04, and Ubuntu14.04 distribution support that was introduced with 5.6.17 now comes with the platform-specific packaging source placed under the packaging directory, in the deb-precise, deb-wheezy, and deb-trusty directories. Support for LinuxThreads has been removed from the source code. LinuxThreads was superseded by NPTL in Linux 2.6. By default, mysql_install_db creates a my.cnf file in the installation base directory using a template. This may be undesireable for some deployments. To enable this behavior to be suppressed, mysql_install_db now supports a --keep-my-cnf option to preserve any existing my.cnf file and not create a new my.cnf file. The mysqlhotcopy utility is now deprecated and will be removed in a future version of MySQL. Among the reasons for this: It works only for the MyISAM and ARCHIVE storage engines; it works on Unix but not Windows. Alternatives include mysqldump and MySQL Enterprise Backup. The timed_mutexes system variable has no effect and is deprecated. Bugs Fixed
2014-08-10 17:11:57 +02:00
share/mysql/test/r/mysqlbinlog_debug.result
Changes 5.6.22: * Noisy compiler warnings on FreeBSD 10 were silenced. * CMake workarounds for older Mac OS X and XCode versions were removed. On Mac OS X, compilation always uses Clang, even for 32-bit builds. * Previously, the MYSQL_MAINTAINER_MODE CMake option was turned on by default for debug builds and off for release builds, and MYSQL_MAINTAINER_MODE caused -Werror to be enabled when building with GCC. This made it cumbersome to enable -Werror under certain conditions, such as when compiling with Clang. * Build support was modified to produce the same warnings for Clang as for gcc. * CMake configuration for the Clang compiler sets more appropriate flags for building on Linux. Specifically, -g -fno-omit-frame-pointer -fno-strict-aliasing is now added. * Bugs fixed.
2014-12-02 13:40:09 +01:00
share/mysql/test/r/mysqlbinlog_mixed_or_statment.result
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/r/mysqlbinlog_raw_mode.result
share/mysql/test/r/mysqlbinlog_raw_mode_win.result
share/mysql/test/r/mysqlbinlog_row_big.result
share/mysql/test/r/mysqlcheck.result
share/mysql/test/r/mysqld--defaults-file.result
share/mysql/test/r/mysqld--help-notwin.result
share/mysql/test/r/mysqld--help-win.result
share/mysql/test/r/mysqldump-compat.result
share/mysql/test/r/mysqldump-max.result
share/mysql/test/r/mysqldump-no-binlog.result
share/mysql/test/r/mysqldump.result
share/mysql/test/r/mysqldump_restore.result
share/mysql/test/r/mysqlhotcopy_archive.result
share/mysql/test/r/mysqlhotcopy_myisam.result
share/mysql/test/r/mysqlimport.result
share/mysql/test/r/mysqlshow.result
share/mysql/test/r/mysqlslap.result
share/mysql/test/r/mysqltest.result
share/mysql/test/r/named_pipe.result
share/mysql/test/r/ndb_default_cluster.require
share/mysql/test/r/negation_elimination.result
share/mysql/test/r/no-threads.result
share/mysql/test/r/no_binlog.result
share/mysql/test/r/not_embedded.require
share/mysql/test/r/not_embedded_server.result
share/mysql/test/r/not_ndb.require
share/mysql/test/r/not_openssl.require
share/mysql/test/r/not_partition.result
Changes 5.6.11: 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. 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. mysql_config_editor now supports --port and --socket options for specifying TCP/IP port number and Unix socket file name. 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. The only supported value for the innodb_mirrored_log_groups system variable is 1, so this variable is now deprecated. Setting it to 1 at startup results in a warning. Setting it to a value other than 1 at startup results in an error and the server exits. This variable will be removed in a future release.
2013-04-20 10:06:01 +02:00
share/mysql/test/r/not_ssl.require
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/r/not_true.require
share/mysql/test/r/not_valgrind.require
share/mysql/test/r/not_windows.require
share/mysql/test/r/null.result
share/mysql/test/r/null_key_all.result
share/mysql/test/r/null_key_icp.result
share/mysql/test/r/null_key_none.result
share/mysql/test/r/odbc.result
share/mysql/test/r/olap.result
share/mysql/test/r/one_thread_per_connection.require
share/mysql/test/r/openssl.require
share/mysql/test/r/openssl_1.result
share/mysql/test/r/optimizer_bug12837084.result
share/mysql/test/r/optimizer_debug_sync.result
share/mysql/test/r/optimizer_switch.result
share/mysql/test/r/order_by_all.result
share/mysql/test/r/order_by_icp_mrr.result
share/mysql/test/r/order_by_none.result
share/mysql/test/r/order_by_sortkey.result
share/mysql/test/r/order_fill_sortbuf.result
share/mysql/test/r/outfile.result
share/mysql/test/r/outfile_loaddata.result
share/mysql/test/r/overflow.result
share/mysql/test/r/packet.result
share/mysql/test/r/parser.result
share/mysql/test/r/parser_bug21114_innodb.result
share/mysql/test/r/parser_not_embedded.result
share/mysql/test/r/parser_precedence.result
share/mysql/test/r/parser_stack.result
share/mysql/test/r/partition.result
share/mysql/test/r/partition_archive.result
share/mysql/test/r/partition_binlog.result
share/mysql/test/r/partition_binlog_stmt.result
share/mysql/test/r/partition_blackhole.result
share/mysql/test/r/partition_bug18198.result
share/mysql/test/r/partition_cache.result
share/mysql/test/r/partition_charset.result
share/mysql/test/r/partition_column.result
share/mysql/test/r/partition_column_prune.result
share/mysql/test/r/partition_csv.result
share/mysql/test/r/partition_datatype.result
share/mysql/test/r/partition_debug_sync.result
share/mysql/test/r/partition_disabled.result
share/mysql/test/r/partition_error.result
share/mysql/test/r/partition_exchange.result
share/mysql/test/r/partition_explicit_prune.result
share/mysql/test/r/partition_federated.result
share/mysql/test/r/partition_grant.result
share/mysql/test/r/partition_hash.result
Changes 5.6.17: Functionality Added or Changed Incompatible Change: The AES_ENCRYPT() and AES_DECRYPT() functions now permit control of the block encryption mode and take an optional initialization vector argument: The new block_encryption_mode system variable controls the mode for block-based encryption algorithms. Its default value is aes-128-ecb, which signifies encryption using a key length of 128 bits and ECB mode. An optional init_vector argument provides an initialization vector for encryption modes that require it: AES_ENCRYPT(str,key_str[,init_vector]) AES_DECRYPT(crypt_str,key_str[,init_vector]) A random string of bytes to use for the initialization vector can be produced by calling the new RANDOM_BYTES() function. For more information, see Encryption and Compression Functions. These changes make statements that use AES_ENCRYPT() or AES_DECRYPT() unsafe for statement-based replication and they cannot be stored in the query cache. Queries that use RANDOM_BYTES() are unsafe for statement-based replication and cannot be stored in the query cache. Incompatible Change: The ERROR_FOR_DIVISION_BY_ZERO, NO_ZERO_DATE, and NO_ZERO_IN_DATE SQL modes now are deprecated and setting the sql_mode value to include any of them generates a warning. In MySQL 5.7, these modes do nothing. Instead, their effects are included in the effects of strict SQL mode (STRICT_ALL_TABLES or STRICT_TRANS_TABLES). The motivation for the change in MySQL 5.7 is to reduce the number of SQL modes with an effect dependent on strict mode and make them part of strict mode itself. To make advance preparation for an upgrade to MySQL 5.7, see SQL Mode Changes in MySQL 5.7. That discussion provides guidelines to assess whether your applications will be affected by the SQL mode changes in MySQL 5.7. InnoDB: MySQL now supports rebuilding regular and partitioned InnoDB tables using online DDL (ALGORITHM=INPLACE) for the following operations: OPTIMIZE TABLE ALTER TABLE ... FORCE ALTER TABLE ... ENGINE=INNODB (when run on an InnoDB table) Online DDL support reduces table rebuild time and permits concurrent DML, which helps reduce user application downtime. For additional information, see Overview of Online DDL. On Solaris, mysql_config --libs now includes -R/path/to/library so that libraries can be found at runtime. mysql_install_db provides a more informative diagnostic message when required Perl modules are missing. The IGNORE clause for ALTER TABLE is now deprecated and will be removed in a future version of MySQL. ALTER IGNORE TABLE causes problems for replication, prevents online ALTER TABLE for unique index creation, and causes problems with foreign keys (rows removed in the parent table). Bugs Fixed
2014-03-31 12:32:13 +02:00
share/mysql/test/r/partition_index_innodb.result
share/mysql/test/r/partition_index_myisam.result
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/r/partition_innodb.result
share/mysql/test/r/partition_innodb_plugin.result
share/mysql/test/r/partition_innodb_semi_consistent.result
share/mysql/test/r/partition_innodb_stmt.result
share/mysql/test/r/partition_innodb_tablespace.result
share/mysql/test/r/partition_key_cache.result
share/mysql/test/r/partition_list.result
share/mysql/test/r/partition_locking.result
share/mysql/test/r/partition_locking_4.result
share/mysql/test/r/partition_mgm.result
share/mysql/test/r/partition_mgm_err.result
share/mysql/test/r/partition_mgm_err2.result
share/mysql/test/r/partition_myisam.result
share/mysql/test/r/partition_not_blackhole.result
share/mysql/test/r/partition_not_windows.result
share/mysql/test/r/partition_open_files_limit.result
share/mysql/test/r/partition_order.result
share/mysql/test/r/partition_pruning.result
share/mysql/test/r/partition_range.result
share/mysql/test/r/partition_rename_longfilename.result
share/mysql/test/r/partition_symlink.result
share/mysql/test/r/partition_sync.result
share/mysql/test/r/partition_truncate.result
share/mysql/test/r/partition_utf8.result
share/mysql/test/r/partition_windows.result
share/mysql/test/r/perror-win.result
share/mysql/test/r/perror.result
share/mysql/test/r/plugin.result
share/mysql/test/r/plugin_auth.result
share/mysql/test/r/plugin_auth_qa.result
share/mysql/test/r/plugin_auth_qa_1.result
share/mysql/test/r/plugin_auth_qa_2.result
share/mysql/test/r/plugin_auth_qa_3.result
share/mysql/test/r/plugin_auth_sha256.result
share/mysql/test/r/plugin_auth_sha256_2.result
share/mysql/test/r/plugin_auth_sha256_server_default.result
share/mysql/test/r/plugin_auth_sha256_server_default_tls.result
share/mysql/test/r/plugin_auth_sha256_tls.result
share/mysql/test/r/plugin_load.result
share/mysql/test/r/plugin_load_option.result
share/mysql/test/r/plugin_not_embedded.result
share/mysql/test/r/preload.result
share/mysql/test/r/profiling.result
share/mysql/test/r/ps.result
share/mysql/test/r/ps_10nestset.result
share/mysql/test/r/ps_11bugs.result
share/mysql/test/r/ps_1general.result
share/mysql/test/r/ps_2myisam.result
share/mysql/test/r/ps_3innodb.result
share/mysql/test/r/ps_4heap.result
share/mysql/test/r/ps_5merge.result
share/mysql/test/r/ps_ddl.result
share/mysql/test/r/ps_ddl1.result
share/mysql/test/r/ps_grant.result
share/mysql/test/r/ps_not_windows.result
share/mysql/test/r/python_with_json.require
share/mysql/test/r/query_cache.result
share/mysql/test/r/query_cache_28249.result
share/mysql/test/r/query_cache_debug.result
share/mysql/test/r/query_cache_disabled.result
share/mysql/test/r/query_cache_merge.result
share/mysql/test/r/query_cache_notembedded.result
share/mysql/test/r/query_cache_ps_no_prot.result
share/mysql/test/r/query_cache_ps_ps_prot.result
share/mysql/test/r/query_cache_size_functionality.result
share/mysql/test/r/query_cache_type_functionality.result
share/mysql/test/r/query_cache_with_views.result
share/mysql/test/r/range_all.result
share/mysql/test/r/range_icp.result
share/mysql/test/r/range_icp_mrr.result
share/mysql/test/r/range_mrr.result
share/mysql/test/r/range_mrr_cost.result
share/mysql/test/r/range_none.result
share/mysql/test/r/read_many_rows_innodb.result
share/mysql/test/r/read_only.result
share/mysql/test/r/read_only_innodb.result
share/mysql/test/r/rename.result
share/mysql/test/r/renamedb.result
share/mysql/test/r/repair.result
share/mysql/test/r/replace.result
share/mysql/test/r/rewrite_general_log.result
share/mysql/test/r/rewrite_slow_log.result
share/mysql/test/r/rollback.result
share/mysql/test/r/round.result
share/mysql/test/r/row.result
share/mysql/test/r/rowid_order_innodb.result
share/mysql/test/r/rpl_colSize.result
share/mysql/test/r/rpl_extraColmaster_innodb.result
share/mysql/test/r/rpl_extraColmaster_myisam.result
share/mysql/test/r/rpl_mysqldump_slave.result
share/mysql/test/r/schema.result
share/mysql/test/r/secure_file_priv_win.result
share/mysql/test/r/select_all.result
share/mysql/test/r/select_all_bka.result
share/mysql/test/r/select_all_bka_nixbnl.result
share/mysql/test/r/select_found.result
share/mysql/test/r/select_icp_mrr.result
share/mysql/test/r/select_icp_mrr_bka.result
share/mysql/test/r/select_icp_mrr_bka_nixbnl.result
share/mysql/test/r/select_none.result
share/mysql/test/r/select_none_bka.result
share/mysql/test/r/select_none_bka_nixbnl.result
share/mysql/test/r/select_safe.result
share/mysql/test/r/server_id.require
share/mysql/test/r/server_id1.require
share/mysql/test/r/server_uuid.result
share/mysql/test/r/server_uuid_embedded.result
share/mysql/test/r/shm.result
share/mysql/test/r/show_check.result
Changes 5.6.20: Security Fix: The linked OpenSSL library for the MySQL 5.6 Commercial Server has been updated from version 1.0.1g to version 1.0.1h. Versions of OpenSSL prior to and including 1.0.1g are reported to be vulnerable to CVE-2014-0224. This change does not affect the Oracle-produced MySQL Community build of MySQL Server 5.6, which uses the yaSSL library instead. DTrace Support MySQL now includes DTrace support on Oracle Linux 6 or higher with UEK kernel. If DTrace is present, server builds will detect it with no special CMake options required. For information about using DTrace on MySQL, see Tracing mysqld Using DTrace. InnoDB Notes Important Change: Redo log writes for large, externally stored BLOB fields could overwrite the most recent checkpoint. The 5.6.20 patch limits the size of redo log BLOB writes to 10% of the redo log file size. The 5.7.5 patch addresses the bug without imposing a limitation. For MySQL 5.5, the bug remains a known limitation. As a result of the redo log BLOB write limit introduced for MySQL 5.6, innodb_log_file_size should be set to a value greater than 10 times the largest BLOB data size found in the rows of your tables plus the length of other variable length fields (VARCHAR, VARBINARY, and TEXT type fields). Failing to do so could result in “Row size too large” errors. No action is required if your innodb_log_file_size setting is already sufficiently large or your tables contain no BLOB data. Functionality Added or Changed Replication: The new system variable binlog_impossible_mode controls what happens if the server cannot write to the binary log, for example, due to a file error. For backward compatibility, the default for binlog_impossible_mode is IGNORE_ERROR, meaning the server logs the error, halts logging, and continues updates to the database. Setting this variable to ABORT_SERVER makes the server halt logging and shut down if it cannot write to the binary log. CMake support was updated to handle CMake version 3. New Debian7, Ubuntu12.04, and Ubuntu14.04 distribution support that was introduced with 5.6.17 now comes with the platform-specific packaging source placed under the packaging directory, in the deb-precise, deb-wheezy, and deb-trusty directories. Support for LinuxThreads has been removed from the source code. LinuxThreads was superseded by NPTL in Linux 2.6. By default, mysql_install_db creates a my.cnf file in the installation base directory using a template. This may be undesireable for some deployments. To enable this behavior to be suppressed, mysql_install_db now supports a --keep-my-cnf option to preserve any existing my.cnf file and not create a new my.cnf file. The mysqlhotcopy utility is now deprecated and will be removed in a future version of MySQL. Among the reasons for this: It works only for the MyISAM and ARCHIVE storage engines; it works on Unix but not Windows. Alternatives include mysqldump and MySQL Enterprise Backup. The timed_mutexes system variable has no effect and is deprecated. Bugs Fixed
2014-08-10 17:11:57 +02:00
share/mysql/test/r/show_processlist.result
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/r/show_profile.result
share/mysql/test/r/signal.result
share/mysql/test/r/signal_code.result
share/mysql/test/r/signal_demo1.result
share/mysql/test/r/signal_demo2.result
share/mysql/test/r/signal_demo3.result
share/mysql/test/r/signal_sqlmode.result
share/mysql/test/r/single_delete_update.result
share/mysql/test/r/skip_grants.result
share/mysql/test/r/skip_log_bin.result
share/mysql/test/r/skip_name_resolve.result
share/mysql/test/r/slave-running.result
share/mysql/test/r/slave-stopped.result
share/mysql/test/r/sort_buffer_size_functionality.result
share/mysql/test/r/sp-big.result
share/mysql/test/r/sp-bugs.result
share/mysql/test/r/sp-code.result
share/mysql/test/r/sp-destruct.result
share/mysql/test/r/sp-dynamic.result
share/mysql/test/r/sp-error.result
share/mysql/test/r/sp-fib.result
share/mysql/test/r/sp-lock.result
share/mysql/test/r/sp-no-code.result
share/mysql/test/r/sp-prelocking.result
share/mysql/test/r/sp-security.result
share/mysql/test/r/sp-threads.result
share/mysql/test/r/sp-ucs2.result
share/mysql/test/r/sp-vars.result
share/mysql/test/r/sp.result
share/mysql/test/r/sp_gis.result
share/mysql/test/r/sp_notembedded.result
share/mysql/test/r/sp_stress_case.result
share/mysql/test/r/sp_sync.result
share/mysql/test/r/sp_trans.result
share/mysql/test/r/sp_trans_log.result
share/mysql/test/r/sp_validation.result
share/mysql/test/r/sql_mode.result
share/mysql/test/r/ssl-big.result
share/mysql/test/r/ssl-crl-revoked-crl.result
Changes 5.6.11: 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. 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. mysql_config_editor now supports --port and --socket options for specifying TCP/IP port number and Unix socket file name. 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. The only supported value for the innodb_mirrored_log_groups system variable is 1, so this variable is now deprecated. Setting it to 1 at startup results in a warning. Setting it to a value other than 1 at startup results in an error and the server exits. This variable will be removed in a future release.
2013-04-20 10:06:01 +02:00
share/mysql/test/r/ssl-sha512.result
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/r/ssl.result
share/mysql/test/r/ssl_8k_key.result
share/mysql/test/r/ssl_and_innodb.result
share/mysql/test/r/ssl_cipher.result
share/mysql/test/r/ssl_compress.result
share/mysql/test/r/ssl_connect.result
share/mysql/test/r/ssl_crl.result
share/mysql/test/r/ssl_crl_clients-valid.result
share/mysql/test/r/ssl_crl_clients.result
share/mysql/test/r/ssl_crl_clients_valid.result
share/mysql/test/r/ssl_crl_crlpath.result
share/mysql/test/r/status.result
share/mysql/test/r/status2.result
share/mysql/test/r/status_bug17954.result
Changes 5.6.26: * Security Fix: Due to the LogJam issue (https://weakdh.org/), OpenSSL has changed the Diffie-Hellman key length parameters for openssl-1.0.1n and up. * Replication: When using a multi-threaded slave, each worker thread has its own queue of transactions to process. In previous MySQL versions, STOP SLAVE waited for all workers to process their entire queue. This logic has been changed so that STOP SLAVE first finds the newest transaction that was committed by any worker thread. Then, it waits for all workers to complete transactions older than that. Newer transactions are not processed. The new logic allows STOP SLAVE to complete faster in case some worker queues contain multiple transactions. * Previously, the max_digest_length system variable controlled the maximum digest length for all server functions that computed statement digests. However, whereas the Performance Schema may need to maintain many digest values, other server functions such as MySQL Enterprise Firewall need only one digest per session. Increasing the max_digest_length value has little impact on total memory requirements for those functions, but can increase Performance Schema memory requirements significantly. To enable configuring digest length separately for the Performance Schema, its digest length is now controlled by the new performance_schema_max_digest_length system variable. * Previously, changes to the validate_password plugin dictionary file (named by the validate_password_dictionary_file system variable) while the server was running required a restart for the server to recognize the changes. Now validate_password_dictionary_file can be set at runtime and assigning a value causes the named file to be read without a restart. In addition, two new status variables are available. validate_password_dictionary_file_last_parsed indicates when the dictionary file was last read, and validate_password_dictionary_file_words_count indicates how many words it contains. * Bugs fixed
2015-07-30 16:39:18 +02:00
share/mysql/test/r/status_debug.result
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/r/strict.result
share/mysql/test/r/strict_autoinc_1myisam.result
share/mysql/test/r/strict_autoinc_2innodb.result
share/mysql/test/r/strict_autoinc_3heap.result
share/mysql/test/r/subquery_all.result
share/mysql/test/r/subquery_all_bka.result
share/mysql/test/r/subquery_all_bka_nixbnl.result
share/mysql/test/r/subquery_mat.result
share/mysql/test/r/subquery_mat_all.result
share/mysql/test/r/subquery_mat_none.result
share/mysql/test/r/subquery_nomat_nosj.result
share/mysql/test/r/subquery_nomat_nosj_bka.result
share/mysql/test/r/subquery_nomat_nosj_bka_nixbnl.result
share/mysql/test/r/subquery_none.result
share/mysql/test/r/subquery_none_bka.result
share/mysql/test/r/subquery_none_bka_nixbnl.result
share/mysql/test/r/subquery_sj_all.result
share/mysql/test/r/subquery_sj_all_bka.result
share/mysql/test/r/subquery_sj_all_bka_nixbnl.result
share/mysql/test/r/subquery_sj_all_bkaunique.result
share/mysql/test/r/subquery_sj_dupsweed.result
share/mysql/test/r/subquery_sj_dupsweed_bka.result
share/mysql/test/r/subquery_sj_dupsweed_bka_nixbnl.result
share/mysql/test/r/subquery_sj_dupsweed_bkaunique.result
share/mysql/test/r/subquery_sj_firstmatch.result
share/mysql/test/r/subquery_sj_firstmatch_bka.result
share/mysql/test/r/subquery_sj_firstmatch_bka_nixbnl.result
share/mysql/test/r/subquery_sj_firstmatch_bkaunique.result
share/mysql/test/r/subquery_sj_innodb_all.result
share/mysql/test/r/subquery_sj_innodb_all_bka.result
share/mysql/test/r/subquery_sj_innodb_all_bka_nixbnl.result
share/mysql/test/r/subquery_sj_innodb_all_bkaunique.result
share/mysql/test/r/subquery_sj_innodb_none.result
share/mysql/test/r/subquery_sj_innodb_none_bka.result
share/mysql/test/r/subquery_sj_innodb_none_bka_nixbnl.result
share/mysql/test/r/subquery_sj_innodb_none_bkaunique.result
share/mysql/test/r/subquery_sj_loosescan.result
share/mysql/test/r/subquery_sj_loosescan_bka.result
share/mysql/test/r/subquery_sj_loosescan_bka_nixbnl.result
share/mysql/test/r/subquery_sj_loosescan_bkaunique.result
share/mysql/test/r/subquery_sj_mat.result
share/mysql/test/r/subquery_sj_mat_bka.result
share/mysql/test/r/subquery_sj_mat_bka_nixbnl.result
share/mysql/test/r/subquery_sj_mat_bkaunique.result
share/mysql/test/r/subquery_sj_mat_nosj.result
share/mysql/test/r/subquery_sj_none.result
share/mysql/test/r/subquery_sj_none_bka.result
share/mysql/test/r/subquery_sj_none_bka_nixbnl.result
share/mysql/test/r/subquery_sj_none_bkaunique.result
share/mysql/test/r/subselect_debug.result
share/mysql/test/r/subselect_gis.result
share/mysql/test/r/subselect_innodb.result
share/mysql/test/r/subselect_notembedded.result
share/mysql/test/r/sum_distinct-big.result
share/mysql/test/r/sum_distinct.result
share/mysql/test/r/symlink.result
share/mysql/test/r/symlink_windows.result
share/mysql/test/r/synchronization.result
share/mysql/test/r/sysdate_is_now.result
share/mysql/test/r/system_mysql_db.result
share/mysql/test/r/system_mysql_db_refs.result
share/mysql/test/r/table_definition_cache_functionality.result
share/mysql/test/r/table_open_cache_functionality.result
share/mysql/test/r/tablelock.result
share/mysql/test/r/tablespace.result
Changes 5.6.23: * The linked OpenSSL library for the MySQL Commercial Server has been updated from version 1.0.1j to version 1.0.1k. * Support for the SSL 2.0 and SSL 3.0 protocols has been disabled because they provide weak encryption. * yaSSL was upgraded to version 2.3.7. * The valid date range of the SSL certificates in mysql-test/std_data has been extended to the year 2029. * Bugs Fixed
2015-02-07 20:23:40 +01:00
share/mysql/test/r/temp_pool.result
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/r/temp_table.result
share/mysql/test/r/temporal_literal.result
share/mysql/test/r/testdb_only.require
share/mysql/test/r/thread_cache_size_functionality.result
share/mysql/test/r/timezone.result
share/mysql/test/r/timezone2.result
share/mysql/test/r/timezone3.result
share/mysql/test/r/timezone4.result
share/mysql/test/r/timezone_grant.result
share/mysql/test/r/trans_read_only.result
share/mysql/test/r/trigger-compat.result
share/mysql/test/r/trigger-trans.result
share/mysql/test/r/trigger.result
share/mysql/test/r/trigger_notembedded.result
share/mysql/test/r/true.require
share/mysql/test/r/truncate.result
share/mysql/test/r/truncate_coverage.result
share/mysql/test/r/type_binary.result
share/mysql/test/r/type_bit.result
share/mysql/test/r/type_bit_innodb.result
share/mysql/test/r/type_blob.result
share/mysql/test/r/type_date.result
share/mysql/test/r/type_datetime.result
share/mysql/test/r/type_decimal.result
share/mysql/test/r/type_enum.result
share/mysql/test/r/type_float.result
share/mysql/test/r/type_nchar.result
share/mysql/test/r/type_newdecimal-big.result
share/mysql/test/r/type_newdecimal.result
share/mysql/test/r/type_ranges.result
share/mysql/test/r/type_set.result
share/mysql/test/r/type_temporal_fractional.result
share/mysql/test/r/type_temporal_upgrade.result
share/mysql/test/r/type_time.result
share/mysql/test/r/type_timestamp.result
Changes 5.6.11: 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. 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. mysql_config_editor now supports --port and --socket options for specifying TCP/IP port number and Unix socket file name. 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. The only supported value for the innodb_mirrored_log_groups system variable is 1, so this variable is now deprecated. Setting it to 1 at startup results in a warning. Setting it to a value other than 1 at startup results in an error and the server exits. This variable will be removed in a future release.
2013-04-20 10:06:01 +02:00
share/mysql/test/r/type_timestamp_explicit.result
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/r/type_uint.result
share/mysql/test/r/type_varchar.result
share/mysql/test/r/type_year.result
share/mysql/test/r/udf.result
share/mysql/test/r/udf_skip_grants.result
share/mysql/test/r/union.result
share/mysql/test/r/unsafe_binlog_innodb.result
share/mysql/test/r/update.result
share/mysql/test/r/upgrade.result
share/mysql/test/r/user_limits.result
share/mysql/test/r/user_var-binlog.result
share/mysql/test/r/user_var.result
share/mysql/test/r/validate_password_plugin.result
share/mysql/test/r/varbinary.result
share/mysql/test/r/variables-big.result
share/mysql/test/r/variables-notembedded.result
share/mysql/test/r/variables.result
share/mysql/test/r/variables_community.result
share/mysql/test/r/variables_debug.result
share/mysql/test/r/view.result
share/mysql/test/r/view_alias.result
share/mysql/test/r/view_grant.result
share/mysql/test/r/wait_timeout.result
share/mysql/test/r/warnings.result
share/mysql/test/r/warnings_engine_disabled.result
share/mysql/test/r/windows.require
share/mysql/test/r/windows.result
share/mysql/test/r/wl6219-csv.result
share/mysql/test/r/wl6219-innodb.result
share/mysql/test/r/wl6219-memory.result
share/mysql/test/r/wl6219-merge.result
share/mysql/test/r/wl6219-myisam.result
share/mysql/test/r/wl6219-upgrade.result
share/mysql/test/r/wl6301_1_not_windows.result
share/mysql/test/r/wl6301_2_not_windows.result
share/mysql/test/r/wl6301_3.result
share/mysql/test/r/wl6443_deprecation.result
share/mysql/test/r/xa.result
share/mysql/test/r/xml.result
share/mysql/test/std_data/.mylogin.cnf
share/mysql/test/std_data/14897.frm
share/mysql/test/std_data/55_temporal.MYD
share/mysql/test/std_data/55_temporal.MYI
share/mysql/test/std_data/55_temporal.frm
share/mysql/test/std_data/Index.xml
share/mysql/test/std_data/Moscow_leap
share/mysql/test/std_data/bad_gis_data.dat
share/mysql/test/std_data/binlog_savepoint.000001
share/mysql/test/std_data/binlog_transaction.000001
Changes 5.6.24: * CMake support was updated to handle CMake version 3.1. * The server now includes its version number when it writes the initial “starting” message to the error log, to make it easier to tell which server instance error log output applies to. This value is the same as that available from the version system variable. * ALTER TABLE did not take advantage of fast alterations that might otherwise apply to the operation to be performed, if the table contained temporal columns found to be in pre-5.6.4 format (TIME, DATETIME, and TIMESTAMP columns without support for fractional seconds precision). * Statement digesting as done previously by the Performance Schema is now done at the SQL level regardless of whether the Performance Schema is compiled in and is available to other aspects of server operation that could benefit from it. The default space available for digesting is 1024 bytes, but can be changed at server startup using the max_digest_length system variable. * Bug fixes.
2015-04-08 12:38:48 +02:00
share/mysql/test/std_data/binlog_transaction_with_GTID.000001
share/mysql/test/std_data/binlog_transaction_with_anonymous_GTID.000001
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/std_data/bug15328.cnf
Changes 5.6.27: * InnoDB: The new innodb_numa_interleave read-only configuration option allows you to enable the NUMA interleave memory policy for allocation of the InnoDB buffer pool. When innodb_numa_interleave is enabled, the NUMA memory policy is set to MPOL_INTERLEAVE for the mysqld process. After the InnoDB buffer pool is allocated, the NUMA memory policy is set back to MPOL_DEFAULT. This option is only available on NUMA-enabled systems. * yaSSL was upgraded to version 2.3.8. * RPM .spec files were updated so that MySQL Server builds from source RPM packages will include the proper files to take advantage of operating system NUMA capabilities. This introduces a runtime dependency on libnuma.so.1. RPM and yum detect this and refuse to install if that library is not installed. * InnoDB: Reloading a table that was evicted while empty caused an AUTO_INCREMENT value to be reset. * InnoDB: Memory allocation sanity checks were added to the memcached code. * InnoDB: A memcached flush_all command raised an assertion. A function that starts a transaction was called from within assertion code. * InnoDB: A data corruption occurred on ARM64. GCC builtins did not issue the correct fences when setting or unsetting the lock word. * InnoDB: Server shutdown was delayed waiting for the purge thread to exit. To avoid this problem, the number of calls to trx_purge() was reduced, and the trx_purge() batch size was reduced to 20. * InnoDB: In READ COMMITTED mode, a REPLACE operation on a unique secondary index resulted in a constraint violation. * InnoDB: The IBUF_BITMAP_FREE bit indicated that there was more free space in the leaf page than was actually available. * InnoDB: Setting lower_case_table_names=0 on a case-insensitive file system could result in a hang condition when running an INSERT INTO ... SELECT ... FROM tbl_name operation with the wrong tbl_name letter case. An error message is now printed and the server exits when attempting to start the server with --lower_case_table_names=0 on a case-insensitive file system. * InnoDB: The server failed to start with an innodb_force_recovery setting greater than 3. InnoDB was set to read-only mode before redo logs were applied. * InnoDB: The trx_sys_read_pertable_file_format_id() function reported the wrong file format. * Partitioning: CREATE TABLE statements that used an invalid function in a subpartitioning expression did not always fail gracefully as expected. * Partitioning: Error handling for failed partitioning-related ALTER TABLE operations against non-partitioned tables was not performed correctly * Partitioning: ALTER TABLE when executed from a stored procedure did not always work correctly with tables partitioned by RANGE. * Replication: Repeatedly checking for ERR_LOCK_WAIT_TIMEOUT (as done, for example by repeatedly executing SHOW SLAVE STATUS) during a prolonged write lock on a table led to an assert. * Replication: If statement based logging was in use, when updating multiple tables in a single statement, a single transaction could be logged as two different transactions. This was due to the binary logging process not properly identifying statements which were operating over transactional tables. The fix ensures that they are correctly identified, even if such statements do not change the contents of the tables.
2015-10-03 14:46:13 +02:00
share/mysql/test/std_data/bug16171518_1.dat
share/mysql/test/std_data/bug16171518_2.dat
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/std_data/bug16266.000001
Changes 5.6.20: Security Fix: The linked OpenSSL library for the MySQL 5.6 Commercial Server has been updated from version 1.0.1g to version 1.0.1h. Versions of OpenSSL prior to and including 1.0.1g are reported to be vulnerable to CVE-2014-0224. This change does not affect the Oracle-produced MySQL Community build of MySQL Server 5.6, which uses the yaSSL library instead. DTrace Support MySQL now includes DTrace support on Oracle Linux 6 or higher with UEK kernel. If DTrace is present, server builds will detect it with no special CMake options required. For information about using DTrace on MySQL, see Tracing mysqld Using DTrace. InnoDB Notes Important Change: Redo log writes for large, externally stored BLOB fields could overwrite the most recent checkpoint. The 5.6.20 patch limits the size of redo log BLOB writes to 10% of the redo log file size. The 5.7.5 patch addresses the bug without imposing a limitation. For MySQL 5.5, the bug remains a known limitation. As a result of the redo log BLOB write limit introduced for MySQL 5.6, innodb_log_file_size should be set to a value greater than 10 times the largest BLOB data size found in the rows of your tables plus the length of other variable length fields (VARCHAR, VARBINARY, and TEXT type fields). Failing to do so could result in “Row size too large” errors. No action is required if your innodb_log_file_size setting is already sufficiently large or your tables contain no BLOB data. Functionality Added or Changed Replication: The new system variable binlog_impossible_mode controls what happens if the server cannot write to the binary log, for example, due to a file error. For backward compatibility, the default for binlog_impossible_mode is IGNORE_ERROR, meaning the server logs the error, halts logging, and continues updates to the database. Setting this variable to ABORT_SERVER makes the server halt logging and shut down if it cannot write to the binary log. CMake support was updated to handle CMake version 3. New Debian7, Ubuntu12.04, and Ubuntu14.04 distribution support that was introduced with 5.6.17 now comes with the platform-specific packaging source placed under the packaging directory, in the deb-precise, deb-wheezy, and deb-trusty directories. Support for LinuxThreads has been removed from the source code. LinuxThreads was superseded by NPTL in Linux 2.6. By default, mysql_install_db creates a my.cnf file in the installation base directory using a template. This may be undesireable for some deployments. To enable this behavior to be suppressed, mysql_install_db now supports a --keep-my-cnf option to preserve any existing my.cnf file and not create a new my.cnf file. The mysqlhotcopy utility is now deprecated and will be removed in a future version of MySQL. Among the reasons for this: It works only for the MyISAM and ARCHIVE storage engines; it works on Unix but not Windows. Alternatives include mysqldump and MySQL Enterprise Backup. The timed_mutexes system variable has no effect and is deprecated. Bugs Fixed
2014-08-10 17:11:57 +02:00
share/mysql/test/std_data/bug17532932.MYD
share/mysql/test/std_data/bug17532932.MYI
share/mysql/test/std_data/bug17532932.frm
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/std_data/bug19371.MYD
share/mysql/test/std_data/bug19371.MYI
share/mysql/test/std_data/bug19371.frm
share/mysql/test/std_data/bug30435_10k_items.txt
share/mysql/test/std_data/bug30435_5k.txt
share/mysql/test/std_data/bug33029-slave-relay-bin.000001
share/mysql/test/std_data/bug35469.dat
share/mysql/test/std_data/bug36055.MYD
share/mysql/test/std_data/bug36055.MYI
share/mysql/test/std_data/bug36055.frm
share/mysql/test/std_data/bug37631.MYD
share/mysql/test/std_data/bug37631.MYI
share/mysql/test/std_data/bug37631.frm
share/mysql/test/std_data/bug40482-bin.000001
share/mysql/test/std_data/bug46565.ARZ
share/mysql/test/std_data/bug46565.frm
share/mysql/test/std_data/bug47012.ARM
share/mysql/test/std_data/bug47012.ARZ
share/mysql/test/std_data/bug47012.frm
share/mysql/test/std_data/bug47205.frm
share/mysql/test/std_data/bug48265.frm
share/mysql/test/std_data/bug48449.frm
share/mysql/test/std_data/bug48633.ARM
share/mysql/test/std_data/bug48633.ARZ
share/mysql/test/std_data/bug48633.frm
share/mysql/test/std_data/bug49823.CSM
share/mysql/test/std_data/bug49823.CSV
share/mysql/test/std_data/bug49823.frm
Changes 5.6.29: * InnoDB: A new InnoDB configuration option, innodb_tmpdir, allows you to configure a separate temporary file directory for online ALTER TABLE operations. This option was introduced to help avoid tmpdir overflows that could occur as a result of large temporary files created during online ALTER TABLE operations. innodb_tmpdir is a SESSION variable and can be configured dynamically using a SET statement. * yaSSL was upgraded to version 2.3.9. This upgrade corrects an issue in which yaSSL handled only cases of zero or one leading zeros for the key agreement instead of potentially any number, which in rare cases could cause connections to fail when using DHE cipher suites. * The Valgrind function signature in mysql-test/valgrind.supp was upgraded for Valgrind 3.11. * Bugs Fixed
2016-02-28 09:58:03 +01:00
share/mysql/test/std_data/ca-cert-verify.pem
Changes 5.6.11: 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. 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. mysql_config_editor now supports --port and --socket options for specifying TCP/IP port number and Unix socket file name. 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. The only supported value for the innodb_mirrored_log_groups system variable is 1, so this variable is now deprecated. Setting it to 1 at startup results in a warning. Setting it to a value other than 1 at startup results in an error and the server exits. This variable will be removed in a future release.
2013-04-20 10:06:01 +02:00
share/mysql/test/std_data/ca-sha512.pem
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/std_data/cacert.pem
share/mysql/test/std_data/charset_utf8.txt
share/mysql/test/std_data/checkDBI_DBD-mysql.pl
share/mysql/test/std_data/client-cert.pem
share/mysql/test/std_data/client-key.pem
share/mysql/test/std_data/cluster_7022_table.MYD
share/mysql/test/std_data/cluster_7022_table.MYI
share/mysql/test/std_data/cluster_7022_table.frm
share/mysql/test/std_data/corrupt-relay-bin.000624
share/mysql/test/std_data/corrupt_t1#P#p1.MYI
share/mysql/test/std_data/corrupt_t1.MYI
share/mysql/test/std_data/crl-ca-cert.pem
share/mysql/test/std_data/crl-certificate-readme.txt
share/mysql/test/std_data/crl-client-cert.pem
share/mysql/test/std_data/crl-client-key.pem
share/mysql/test/std_data/crl-client-revoked-cert.pem
share/mysql/test/std_data/crl-client-revoked-key.pem
share/mysql/test/std_data/crl-client-revoked.crl
share/mysql/test/std_data/crl-server-cert.pem
share/mysql/test/std_data/crl-server-key.pem
share/mysql/test/std_data/crldir/ab8a3803.r0
share/mysql/test/std_data/des_key_file
Changes 5.6.20: Security Fix: The linked OpenSSL library for the MySQL 5.6 Commercial Server has been updated from version 1.0.1g to version 1.0.1h. Versions of OpenSSL prior to and including 1.0.1g are reported to be vulnerable to CVE-2014-0224. This change does not affect the Oracle-produced MySQL Community build of MySQL Server 5.6, which uses the yaSSL library instead. DTrace Support MySQL now includes DTrace support on Oracle Linux 6 or higher with UEK kernel. If DTrace is present, server builds will detect it with no special CMake options required. For information about using DTrace on MySQL, see Tracing mysqld Using DTrace. InnoDB Notes Important Change: Redo log writes for large, externally stored BLOB fields could overwrite the most recent checkpoint. The 5.6.20 patch limits the size of redo log BLOB writes to 10% of the redo log file size. The 5.7.5 patch addresses the bug without imposing a limitation. For MySQL 5.5, the bug remains a known limitation. As a result of the redo log BLOB write limit introduced for MySQL 5.6, innodb_log_file_size should be set to a value greater than 10 times the largest BLOB data size found in the rows of your tables plus the length of other variable length fields (VARCHAR, VARBINARY, and TEXT type fields). Failing to do so could result in “Row size too large” errors. No action is required if your innodb_log_file_size setting is already sufficiently large or your tables contain no BLOB data. Functionality Added or Changed Replication: The new system variable binlog_impossible_mode controls what happens if the server cannot write to the binary log, for example, due to a file error. For backward compatibility, the default for binlog_impossible_mode is IGNORE_ERROR, meaning the server logs the error, halts logging, and continues updates to the database. Setting this variable to ABORT_SERVER makes the server halt logging and shut down if it cannot write to the binary log. CMake support was updated to handle CMake version 3. New Debian7, Ubuntu12.04, and Ubuntu14.04 distribution support that was introduced with 5.6.17 now comes with the platform-specific packaging source placed under the packaging directory, in the deb-precise, deb-wheezy, and deb-trusty directories. Support for LinuxThreads has been removed from the source code. LinuxThreads was superseded by NPTL in Linux 2.6. By default, mysql_install_db creates a my.cnf file in the installation base directory using a template. This may be undesireable for some deployments. To enable this behavior to be suppressed, mysql_install_db now supports a --keep-my-cnf option to preserve any existing my.cnf file and not create a new my.cnf file. The mysqlhotcopy utility is now deprecated and will be removed in a future version of MySQL. Among the reasons for this: It works only for the MyISAM and ARCHIVE storage engines; it works on Unix but not Windows. Alternatives include mysqldump and MySQL Enterprise Backup. The timed_mutexes system variable has no effect and is deprecated. Bugs Fixed
2014-08-10 17:11:57 +02:00
share/mysql/test/std_data/dtrace.d
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/std_data/funcs_1/innodb_tb1.txt
share/mysql/test/std_data/funcs_1/innodb_tb2.txt
share/mysql/test/std_data/funcs_1/innodb_tb3.txt
share/mysql/test/std_data/funcs_1/innodb_tb4.txt
share/mysql/test/std_data/funcs_1/load_file.txt
share/mysql/test/std_data/funcs_1/memory_tb1.txt
share/mysql/test/std_data/funcs_1/memory_tb2.txt
share/mysql/test/std_data/funcs_1/memory_tb3.txt
share/mysql/test/std_data/funcs_1/memory_tb4.txt
share/mysql/test/std_data/funcs_1/myisam_tb1.txt
share/mysql/test/std_data/funcs_1/myisam_tb2.txt
share/mysql/test/std_data/funcs_1/myisam_tb3.txt
share/mysql/test/std_data/funcs_1/myisam_tb4.txt
share/mysql/test/std_data/funcs_1/ndb_tb1.txt
share/mysql/test/std_data/funcs_1/ndb_tb2.txt
share/mysql/test/std_data/funcs_1/ndb_tb3.txt
share/mysql/test/std_data/funcs_1/ndb_tb4.txt
share/mysql/test/std_data/funcs_1/t3.txt
share/mysql/test/std_data/funcs_1/t4.txt
share/mysql/test/std_data/funcs_1/t7.txt
share/mysql/test/std_data/funcs_1/t9.txt
share/mysql/test/std_data/init_file.dat
share/mysql/test/std_data/intersect-bug50389.tsv
share/mysql/test/std_data/latin1.xml
share/mysql/test/std_data/loaddata1.dat
share/mysql/test/std_data/loaddata2.dat
share/mysql/test/std_data/loaddata3.dat
share/mysql/test/std_data/loaddata4.dat
share/mysql/test/std_data/loaddata5.dat
share/mysql/test/std_data/loaddata6.dat
share/mysql/test/std_data/loaddata_dq.dat
share/mysql/test/std_data/loaddata_pair.dat
share/mysql/test/std_data/loaddata_utf8.dat
share/mysql/test/std_data/loadxml.dat
share/mysql/test/std_data/loadxml2.dat
share/mysql/test/std_data/master-bin.000001
share/mysql/test/std_data/numbers.txt
share/mysql/test/std_data/old-format-relay-log-win.info
share/mysql/test/std_data/old-format-relay-log.info
share/mysql/test/std_data/old_table-323.frm
share/mysql/test/std_data/onerow.xml
share/mysql/test/std_data/parts/part_supported_sql_funcs_int_ch1.inc
share/mysql/test/std_data/parts/part_supported_sql_funcs_int_date.inc
share/mysql/test/std_data/parts/part_supported_sql_funcs_int_float.inc
share/mysql/test/std_data/parts/part_supported_sql_funcs_int_int.inc
share/mysql/test/std_data/parts/part_supported_sql_funcs_int_time.inc
share/mysql/test/std_data/parts/t1.frm
share/mysql/test/std_data/parts/t1TIMESTAMP.frm
share/mysql/test/std_data/parts/t1_blackhole.frm
share/mysql/test/std_data/parts/t1_blackhole.par
share/mysql/test/std_data/parts/t1_will_crash#P#p1_first_1024.MYD
share/mysql/test/std_data/parts/t1_will_crash#P#p2.MYD
share/mysql/test/std_data/parts/t1_will_crash#P#p2.MYI
share/mysql/test/std_data/parts/t1_will_crash#P#p3.MYI
share/mysql/test/std_data/parts/t1_will_crash#P#p4.MYI
share/mysql/test/std_data/parts/t1_will_crash#P#p6.MYD
share/mysql/test/std_data/parts/t1_will_crash#P#p6_2.MYD
share/mysql/test/std_data/parts/t1_will_crash#P#p6_3.MYD
share/mysql/test/std_data/rpl_bug28618.dat
share/mysql/test/std_data/rpl_loaddata.dat
share/mysql/test/std_data/rpl_loaddata2.dat
share/mysql/test/std_data/rpl_mixed.dat
share/mysql/test/std_data/rpl_timezone.dat
share/mysql/test/std_data/rpl_timezone2.dat
share/mysql/test/std_data/rsa_private_key.pem
share/mysql/test/std_data/rsa_public_key.pem
Changes 5.6.11: 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. 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. mysql_config_editor now supports --port and --socket options for specifying TCP/IP port number and Unix socket file name. 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. The only supported value for the innodb_mirrored_log_groups system variable is 1, so this variable is now deprecated. Setting it to 1 at startup results in a warning. Setting it to a value other than 1 at startup results in an error and the server exits. This variable will be removed in a future release.
2013-04-20 10:06:01 +02:00
share/mysql/test/std_data/server-cert-sha512.pem
Changes 5.6.29: * InnoDB: A new InnoDB configuration option, innodb_tmpdir, allows you to configure a separate temporary file directory for online ALTER TABLE operations. This option was introduced to help avoid tmpdir overflows that could occur as a result of large temporary files created during online ALTER TABLE operations. innodb_tmpdir is a SESSION variable and can be configured dynamically using a SET statement. * yaSSL was upgraded to version 2.3.9. This upgrade corrects an issue in which yaSSL handled only cases of zero or one leading zeros for the key agreement instead of potentially any number, which in rare cases could cause connections to fail when using DHE cipher suites. * The Valgrind function signature in mysql-test/valgrind.supp was upgraded for Valgrind 3.11. * Bugs Fixed
2016-02-28 09:58:03 +01:00
share/mysql/test/std_data/server-cert-verify-fail.pem
share/mysql/test/std_data/server-cert-verify-pass.pem
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/std_data/server-cert.pem
Changes 5.6.11: 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. 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. mysql_config_editor now supports --port and --socket options for specifying TCP/IP port number and Unix socket file name. 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. The only supported value for the innodb_mirrored_log_groups system variable is 1, so this variable is now deprecated. Setting it to 1 at startup results in a warning. Setting it to a value other than 1 at startup results in an error and the server exits. This variable will be removed in a future release.
2013-04-20 10:06:01 +02:00
share/mysql/test/std_data/server-key-sha512.pem
Changes 5.6.29: * InnoDB: A new InnoDB configuration option, innodb_tmpdir, allows you to configure a separate temporary file directory for online ALTER TABLE operations. This option was introduced to help avoid tmpdir overflows that could occur as a result of large temporary files created during online ALTER TABLE operations. innodb_tmpdir is a SESSION variable and can be configured dynamically using a SET statement. * yaSSL was upgraded to version 2.3.9. This upgrade corrects an issue in which yaSSL handled only cases of zero or one leading zeros for the key agreement instead of potentially any number, which in rare cases could cause connections to fail when using DHE cipher suites. * The Valgrind function signature in mysql-test/valgrind.supp was upgraded for Valgrind 3.11. * Bugs Fixed
2016-02-28 09:58:03 +01:00
share/mysql/test/std_data/server-key-verify-fail.pem
share/mysql/test/std_data/server-key-verify-pass.pem
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/std_data/server-key.pem
share/mysql/test/std_data/server8k-cert.pem
share/mysql/test/std_data/server8k-key.pem
Changes 5.6.24: * CMake support was updated to handle CMake version 3.1. * The server now includes its version number when it writes the initial “starting” message to the error log, to make it easier to tell which server instance error log output applies to. This value is the same as that available from the version system variable. * ALTER TABLE did not take advantage of fast alterations that might otherwise apply to the operation to be performed, if the table contained temporal columns found to be in pre-5.6.4 format (TIME, DATETIME, and TIMESTAMP columns without support for fractional seconds precision). * Statement digesting as done previously by the Performance Schema is now done at the SQL level regardless of whether the Performance Schema is compiled in and is available to other aspects of server operation that could benefit from it. The default space available for digesting is 1024 bytes, but can be changed at server startup using the max_digest_length system variable. * Bug fixes.
2015-04-08 12:38:48 +02:00
share/mysql/test/std_data/slave-relay-bin_linux.index
share/mysql/test/std_data/slave-relay-bin_win.index
Changes 5.6.20: Security Fix: The linked OpenSSL library for the MySQL 5.6 Commercial Server has been updated from version 1.0.1g to version 1.0.1h. Versions of OpenSSL prior to and including 1.0.1g are reported to be vulnerable to CVE-2014-0224. This change does not affect the Oracle-produced MySQL Community build of MySQL Server 5.6, which uses the yaSSL library instead. DTrace Support MySQL now includes DTrace support on Oracle Linux 6 or higher with UEK kernel. If DTrace is present, server builds will detect it with no special CMake options required. For information about using DTrace on MySQL, see Tracing mysqld Using DTrace. InnoDB Notes Important Change: Redo log writes for large, externally stored BLOB fields could overwrite the most recent checkpoint. The 5.6.20 patch limits the size of redo log BLOB writes to 10% of the redo log file size. The 5.7.5 patch addresses the bug without imposing a limitation. For MySQL 5.5, the bug remains a known limitation. As a result of the redo log BLOB write limit introduced for MySQL 5.6, innodb_log_file_size should be set to a value greater than 10 times the largest BLOB data size found in the rows of your tables plus the length of other variable length fields (VARCHAR, VARBINARY, and TEXT type fields). Failing to do so could result in “Row size too large” errors. No action is required if your innodb_log_file_size setting is already sufficiently large or your tables contain no BLOB data. Functionality Added or Changed Replication: The new system variable binlog_impossible_mode controls what happens if the server cannot write to the binary log, for example, due to a file error. For backward compatibility, the default for binlog_impossible_mode is IGNORE_ERROR, meaning the server logs the error, halts logging, and continues updates to the database. Setting this variable to ABORT_SERVER makes the server halt logging and shut down if it cannot write to the binary log. CMake support was updated to handle CMake version 3. New Debian7, Ubuntu12.04, and Ubuntu14.04 distribution support that was introduced with 5.6.17 now comes with the platform-specific packaging source placed under the packaging directory, in the deb-precise, deb-wheezy, and deb-trusty directories. Support for LinuxThreads has been removed from the source code. LinuxThreads was superseded by NPTL in Linux 2.6. By default, mysql_install_db creates a my.cnf file in the installation base directory using a template. This may be undesireable for some deployments. To enable this behavior to be suppressed, mysql_install_db now supports a --keep-my-cnf option to preserve any existing my.cnf file and not create a new my.cnf file. The mysqlhotcopy utility is now deprecated and will be removed in a future version of MySQL. Among the reasons for this: It works only for the MyISAM and ARCHIVE storage engines; it works on Unix but not Windows. Alternatives include mysqldump and MySQL Enterprise Backup. The timed_mutexes system variable has no effect and is deprecated. Bugs Fixed
2014-08-10 17:11:57 +02:00
share/mysql/test/std_data/system_tap.stp
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/std_data/trunc_binlog.000001
share/mysql/test/std_data/untrusted-cacert.pem
share/mysql/test/std_data/vchar.frm
share/mysql/test/std_data/warnings_loaddata.dat
share/mysql/test/std_data/wl6219_41.MYD
share/mysql/test/std_data/wl6219_41.MYI
share/mysql/test/std_data/wl6219_41.frm
share/mysql/test/std_data/wl6219_55.MYD
share/mysql/test/std_data/wl6219_55.MYI
share/mysql/test/std_data/wl6219_55.frm
share/mysql/test/std_data/wl6219_55_innodb.frm
share/mysql/test/std_data/words.dat
share/mysql/test/std_data/words2.dat
Changes 5.6.11: 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. 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. mysql_config_editor now supports --port and --socket options for specifying TCP/IP port number and Unix socket file name. 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. The only supported value for the innodb_mirrored_log_groups system variable is 1, so this variable is now deprecated. Setting it to 1 at startup results in a warning. Setting it to a value other than 1 at startup results in an error and the server exits. This variable will be removed in a future release.
2013-04-20 10:06:01 +02:00
share/mysql/test/suite/auth_sec/include/have_openssl.inc
share/mysql/test/suite/auth_sec/include/have_sha256_rsa_auth.inc
share/mysql/test/suite/auth_sec/include/have_ssl.inc
share/mysql/test/suite/auth_sec/include/have_ssl_communication.inc
share/mysql/test/suite/auth_sec/include/mysql_upgrade_preparation.inc
share/mysql/test/suite/auth_sec/include/not_embedded.inc
share/mysql/test/suite/auth_sec/include/not_openssl.inc
share/mysql/test/suite/auth_sec/include/not_sha256_rsa_auth.inc
share/mysql/test/suite/auth_sec/include/not_ssl.inc
share/mysql/test/suite/auth_sec/r/access_credential_control.result
Changes 5.6.29: * InnoDB: A new InnoDB configuration option, innodb_tmpdir, allows you to configure a separate temporary file directory for online ALTER TABLE operations. This option was introduced to help avoid tmpdir overflows that could occur as a result of large temporary files created during online ALTER TABLE operations. innodb_tmpdir is a SESSION variable and can be configured dynamically using a SET statement. * yaSSL was upgraded to version 2.3.9. This upgrade corrects an issue in which yaSSL handled only cases of zero or one leading zeros for the key agreement instead of potentially any number, which in rare cases could cause connections to fail when using DHE cipher suites. * The Valgrind function signature in mysql-test/valgrind.supp was upgraded for Valgrind 3.11. * Bugs Fixed
2016-02-28 09:58:03 +01:00
share/mysql/test/suite/auth_sec/r/cert_verify.result
Changes 5.6.11: 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. 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. mysql_config_editor now supports --port and --socket options for specifying TCP/IP port number and Unix socket file name. 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. The only supported value for the innodb_mirrored_log_groups system variable is 1, so this variable is now deprecated. Setting it to 1 at startup results in a warning. Setting it to a value other than 1 at startup results in an error and the server exits. This variable will be removed in a future release.
2013-04-20 10:06:01 +02:00
share/mysql/test/suite/auth_sec/r/have_mysql_upgrade.result
share/mysql/test/suite/auth_sec/r/have_ssl.require
share/mysql/test/suite/auth_sec/r/key_value_auth.result
share/mysql/test/suite/auth_sec/r/mysql_native_plugin.result
Changes 5.6.24: * CMake support was updated to handle CMake version 3.1. * The server now includes its version number when it writes the initial “starting” message to the error log, to make it easier to tell which server instance error log output applies to. This value is the same as that available from the version system variable. * ALTER TABLE did not take advantage of fast alterations that might otherwise apply to the operation to be performed, if the table contained temporal columns found to be in pre-5.6.4 format (TIME, DATETIME, and TIMESTAMP columns without support for fractional seconds precision). * Statement digesting as done previously by the Performance Schema is now done at the SQL level regardless of whether the Performance Schema is compiled in and is available to other aspects of server operation that could benefit from it. The default space available for digesting is 1024 bytes, but can be changed at server startup using the max_digest_length system variable. * Bug fixes.
2015-04-08 12:38:48 +02:00
share/mysql/test/suite/auth_sec/r/mysql_no_login.result
Changes 5.6.11: 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. 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. mysql_config_editor now supports --port and --socket options for specifying TCP/IP port number and Unix socket file name. 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. The only supported value for the innodb_mirrored_log_groups system variable is 1, so this variable is now deprecated. Setting it to 1 at startup results in a warning. Setting it to a value other than 1 at startup results in an error and the server exits. This variable will be removed in a future release.
2013-04-20 10:06:01 +02:00
share/mysql/test/suite/auth_sec/r/mysql_old_passwords.result
share/mysql/test/suite/auth_sec/r/mysql_old_plugin.result
share/mysql/test/suite/auth_sec/r/mysql_sha256_plugin.result
share/mysql/test/suite/auth_sec/r/not_embedded.require
share/mysql/test/suite/auth_sec/r/not_openssl.require
share/mysql/test/suite/auth_sec/r/not_ssl.require
share/mysql/test/suite/auth_sec/r/openssl.require
share/mysql/test/suite/auth_sec/r/password_expired.result
share/mysql/test/suite/auth_sec/r/server_withoutssl_client_withoutssl.result
share/mysql/test/suite/auth_sec/r/server_withoutssl_client_withssl.result
share/mysql/test/suite/auth_sec/r/server_withssl_client_withoutssl.result
share/mysql/test/suite/auth_sec/r/server_withssl_client_withssl.result
share/mysql/test/suite/auth_sec/t/access_credential_control-master.opt
share/mysql/test/suite/auth_sec/t/access_credential_control.test
Changes 5.6.29: * InnoDB: A new InnoDB configuration option, innodb_tmpdir, allows you to configure a separate temporary file directory for online ALTER TABLE operations. This option was introduced to help avoid tmpdir overflows that could occur as a result of large temporary files created during online ALTER TABLE operations. innodb_tmpdir is a SESSION variable and can be configured dynamically using a SET statement. * yaSSL was upgraded to version 2.3.9. This upgrade corrects an issue in which yaSSL handled only cases of zero or one leading zeros for the key agreement instead of potentially any number, which in rare cases could cause connections to fail when using DHE cipher suites. * The Valgrind function signature in mysql-test/valgrind.supp was upgraded for Valgrind 3.11. * Bugs Fixed
2016-02-28 09:58:03 +01:00
share/mysql/test/suite/auth_sec/t/cert_verify.test
Changes 5.6.11: 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. 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. mysql_config_editor now supports --port and --socket options for specifying TCP/IP port number and Unix socket file name. 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. The only supported value for the innodb_mirrored_log_groups system variable is 1, so this variable is now deprecated. Setting it to 1 at startup results in a warning. Setting it to a value other than 1 at startup results in an error and the server exits. This variable will be removed in a future release.
2013-04-20 10:06:01 +02:00
share/mysql/test/suite/auth_sec/t/key_value_auth-master.opt
share/mysql/test/suite/auth_sec/t/key_value_auth.test
share/mysql/test/suite/auth_sec/t/key_value_auth.test_old
share/mysql/test/suite/auth_sec/t/mysql_native_plugin.test
Changes 5.6.24: * CMake support was updated to handle CMake version 3.1. * The server now includes its version number when it writes the initial “starting” message to the error log, to make it easier to tell which server instance error log output applies to. This value is the same as that available from the version system variable. * ALTER TABLE did not take advantage of fast alterations that might otherwise apply to the operation to be performed, if the table contained temporal columns found to be in pre-5.6.4 format (TIME, DATETIME, and TIMESTAMP columns without support for fractional seconds precision). * Statement digesting as done previously by the Performance Schema is now done at the SQL level regardless of whether the Performance Schema is compiled in and is available to other aspects of server operation that could benefit from it. The default space available for digesting is 1024 bytes, but can be changed at server startup using the max_digest_length system variable. * Bug fixes.
2015-04-08 12:38:48 +02:00
share/mysql/test/suite/auth_sec/t/mysql_no_login-master.opt
share/mysql/test/suite/auth_sec/t/mysql_no_login.test
Changes 5.6.11: 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. 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. mysql_config_editor now supports --port and --socket options for specifying TCP/IP port number and Unix socket file name. 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. The only supported value for the innodb_mirrored_log_groups system variable is 1, so this variable is now deprecated. Setting it to 1 at startup results in a warning. Setting it to a value other than 1 at startup results in an error and the server exits. This variable will be removed in a future release.
2013-04-20 10:06:01 +02:00
share/mysql/test/suite/auth_sec/t/mysql_old_passwords-master.opt
share/mysql/test/suite/auth_sec/t/mysql_old_passwords.test
share/mysql/test/suite/auth_sec/t/mysql_old_plugin.test
share/mysql/test/suite/auth_sec/t/mysql_old_plugin.test_old
share/mysql/test/suite/auth_sec/t/mysql_sha256_plugin-master.opt
share/mysql/test/suite/auth_sec/t/mysql_sha256_plugin.test
share/mysql/test/suite/auth_sec/t/password_expired-master.opt
share/mysql/test/suite/auth_sec/t/password_expired.test
share/mysql/test/suite/auth_sec/t/server_withoutssl_client_withoutssl.test
share/mysql/test/suite/auth_sec/t/server_withoutssl_client_withssl.test
share/mysql/test/suite/auth_sec/t/server_withssl_client_withoutssl-master.opt
share/mysql/test/suite/auth_sec/t/server_withssl_client_withoutssl.test
share/mysql/test/suite/auth_sec/t/server_withssl_client_withssl-master.opt
share/mysql/test/suite/auth_sec/t/server_withssl_client_withssl.test
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/binlog/combinations
share/mysql/test/suite/binlog/r/binlog_base64_flag.result
share/mysql/test/suite/binlog/r/binlog_bug23533.result
share/mysql/test/suite/binlog/r/binlog_bug36391.result
share/mysql/test/suite/binlog/r/binlog_checksum.result
share/mysql/test/suite/binlog/r/binlog_crash_safe_master_checksum.result
share/mysql/test/suite/binlog/r/binlog_database.result
share/mysql/test/suite/binlog/r/binlog_delete_and_flush_index.result
share/mysql/test/suite/binlog/r/binlog_drop_if_exists.result
share/mysql/test/suite/binlog/r/binlog_enforce_gtid_consistency.result
Changes 5.6.22: * Noisy compiler warnings on FreeBSD 10 were silenced. * CMake workarounds for older Mac OS X and XCode versions were removed. On Mac OS X, compilation always uses Clang, even for 32-bit builds. * Previously, the MYSQL_MAINTAINER_MODE CMake option was turned on by default for debug builds and off for release builds, and MYSQL_MAINTAINER_MODE caused -Werror to be enabled when building with GCC. This made it cumbersome to enable -Werror under certain conditions, such as when compiling with Clang. * Build support was modified to produce the same warnings for Clang as for gcc. * CMake configuration for the Clang compiler sets more appropriate flags for building on Linux. Specifically, -g -fno-omit-frame-pointer -fno-strict-aliasing is now added. * Bugs fixed.
2014-12-02 13:40:09 +01:00
share/mysql/test/suite/binlog/r/binlog_error_action.result
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/binlog/r/binlog_format_switch_in_tmp_table.result
share/mysql/test/suite/binlog/r/binlog_grant.result
share/mysql/test/suite/binlog/r/binlog_gtid_cache.result
share/mysql/test/suite/binlog/r/binlog_gtid_errors.result
Changes 5.6.29: * InnoDB: A new InnoDB configuration option, innodb_tmpdir, allows you to configure a separate temporary file directory for online ALTER TABLE operations. This option was introduced to help avoid tmpdir overflows that could occur as a result of large temporary files created during online ALTER TABLE operations. innodb_tmpdir is a SESSION variable and can be configured dynamically using a SET statement. * yaSSL was upgraded to version 2.3.9. This upgrade corrects an issue in which yaSSL handled only cases of zero or one leading zeros for the key agreement instead of potentially any number, which in rare cases could cause connections to fail when using DHE cipher suites. * The Valgrind function signature in mysql-test/valgrind.supp was upgraded for Valgrind 3.11. * Bugs Fixed
2016-02-28 09:58:03 +01:00
share/mysql/test/suite/binlog/r/binlog_gtid_exhausted.result
Changes 5.6.11: 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. 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. mysql_config_editor now supports --port and --socket options for specifying TCP/IP port number and Unix socket file name. 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. The only supported value for the innodb_mirrored_log_groups system variable is 1, so this variable is now deprecated. Setting it to 1 at startup results in a warning. Setting it to a value other than 1 at startup results in an error and the server exits. This variable will be removed in a future release.
2013-04-20 10:06:01 +02:00
share/mysql/test/suite/binlog/r/binlog_gtid_implicit_commit.result
share/mysql/test/suite/binlog/r/binlog_gtid_innodb.result
share/mysql/test/suite/binlog/r/binlog_gtid_mysqlbinlog_row.result
share/mysql/test/suite/binlog/r/binlog_gtid_mysqlbinlog_row_innodb.result
share/mysql/test/suite/binlog/r/binlog_gtid_mysqlbinlog_row_myisam.result
share/mysql/test/suite/binlog/r/binlog_gtid_mysqlbinlog_start_stop.result
share/mysql/test/suite/binlog/r/binlog_gtid_row_ctype_ucs.result
Changes 5.6.23: * The linked OpenSSL library for the MySQL Commercial Server has been updated from version 1.0.1j to version 1.0.1k. * Support for the SSL 2.0 and SSL 3.0 protocols has been disabled because they provide weak encryption. * yaSSL was upgraded to version 2.3.7. * The valid date range of the SSL certificates in mysql-test/std_data has been extended to the year 2029. * Bugs Fixed
2015-02-07 20:23:40 +01:00
share/mysql/test/suite/binlog/r/binlog_gtid_simple_recovery.result
Changes 5.6.11: 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. 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. mysql_config_editor now supports --port and --socket options for specifying TCP/IP port number and Unix socket file name. 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. The only supported value for the innodb_mirrored_log_groups system variable is 1, so this variable is now deprecated. Setting it to 1 at startup results in a warning. Setting it to a value other than 1 at startup results in an error and the server exits. This variable will be removed in a future release.
2013-04-20 10:06:01 +02:00
share/mysql/test/suite/binlog/r/binlog_gtid_stm_ctype_ucs.result
Changes 5.6.19: Functionality Added or Changed The obsolete and unmaintained charset2html utility has been removed from MySQL distributions. The mysqlbug, mysql_waitpid, and mysql_zap utilities have been deprecated and will be removed in MySQL 5.7. Bugs Fixed InnoDB: After upgrading from 5.6.10 to MySQL versions up to and including MySQL 5.6.18, InnoDB would attempt to rename obsolete full-text search auxiliary tables on server startup, resulting in an assertion failure. InnoDB: For each insert, memset would be called three times to allocate memory for system fields. To reduce CPU usage, the three memset calls are now combined into a single call. InnoDB: Enabling the InnoDB Table Monitor would result in a ib_table->stat_initialized assertion failure. InnoDB: Setting innodb_max_dirty_pages_pct=0 would leave 1% of dirty pages unflushed. Buffer pool flushing is initiated when the percentage of dirty pages is greater innodb_max_dirty_pages_pct. The internal variables that store the innodb_max_dirty_pages_pct value and the percentage of dirty pages (buf_get_modified_ratio_pct and srv_max_buf_pool_modified_pct) were defined as unsigned integer data types, which meant that a innodb_max_dirty_pages_pct value of 0 required a dirty pages percentage of 1 or greater to initiate buffer pool flushing. To address this problem, the buf_get_modified_ratio_pct and srv_max_buf_pool_modified_pct internal variables are redefined as double data types, which changes the range value for innodb_max_dirty_pages_pct and innodb_max_dirty_pages_pct_lwm from 0 .. 99 to 0 .. 99.99. Additionally, buffer pool flushing is now initiated when the percentage of dirty pages is “greater than or equal to” innodb_max_dirty_pages_pct. Replication: Log rotation events could cause group_relay_log_pos to be moved forward incorrectly within a group. This meant that, when the transaction was retried, or if the SQL thread was stopped in the middle of a transaction following one or more log rotations (such that the transaction or group spanned multiple relay log files), part or all of the group was silently skipped. This issue has been addressed by correcting a problem in the logic used to avoid touching the coordinates of the SQL thread when updating the log position as part of a relay log rotation whereby it was possible to update the SQL thread's coordinates when not using a multi-threaded slave, even in the middle of a group. Replication: When running the server with --gtid-mode=ON, STOP SLAVE followed by START SLAVE resulted in a mismatch between the information provided by INFORMATION_SCHEMA.INNODB_TEMP_TABLE_INFO and the Slave_open_temp_tables status variable: the INNODB_TEMP_TABLE_INFO table showed that no temporary tables existed, but Slave_open_temp_tables had a nonzero value. Replication: In certain cases, the server mishandled triggers and stored procedures that tried to modify other tables when called by CREATE TABLE ... SELECT. This is now handled correctly as an error. Replication: When used on a table employing a transactional storage engine, a failed TRUNCATE TABLE was still written to the binary log and thus replayed on the slave. This could lead to inconsistency when the master retained data that was removed on the slave. Now in such cases TRUNCATE TABLE is logged only when it executes successfully. Replication: The server did not always handle the auto.cnf file correctly in cases where this file's permissions were incorrect. Replication: When the binary log was rotated due to receipt of a SIGHUP signal, the new binary log did not contain the Previous_gtid_event required for subsequent processing of that binary log's GTID events. Now when SIGHUP is received, steps are taken to insure that the server writes the necessary Previous_gtid_event to the new log before writing any GTID events to the new log.
2014-06-02 09:30:38 +02:00
share/mysql/test/suite/binlog/r/binlog_gtid_utils.result
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/binlog/r/binlog_hexdump.result
share/mysql/test/suite/binlog/r/binlog_implicit_commit.result
share/mysql/test/suite/binlog/r/binlog_incident.result
share/mysql/test/suite/binlog/r/binlog_incident_ignore.result
share/mysql/test/suite/binlog/r/binlog_index.result
share/mysql/test/suite/binlog/r/binlog_innodb.result
share/mysql/test/suite/binlog/r/binlog_innodb_row.result
share/mysql/test/suite/binlog/r/binlog_killed.result
share/mysql/test/suite/binlog/r/binlog_killed_simulate.result
share/mysql/test/suite/binlog/r/binlog_max_extension.result
share/mysql/test/suite/binlog/r/binlog_mixed_cache_stat.result
share/mysql/test/suite/binlog/r/binlog_mixed_load_data.result
share/mysql/test/suite/binlog/r/binlog_multi_engine.result
share/mysql/test/suite/binlog/r/binlog_mysqlbinlog-cp932.result
share/mysql/test/suite/binlog/r/binlog_mysqlbinlog_base64.result
Changes 5.6.21: The --skip-innodb option is now deprecated and its use results in a warning. It will be removed in a future MySQL release. This also applies to its synonyms (--innodb=OFF, --disable-innodb, and so forth). MySQL Enterprise Edition now includes a set of encryption functions based on the OpenSSL library that expose OpenSSL capabilities at the SQL level. Replication: The new variable simplified_binlog_gtid_recovery can be used to change the way binary log files are searched for previous GTIDs during recovery, speeding up the process when a large number of binary log files exist. Internally, spatial data types such as Geometry are represented as BLOB values, so when invoked with the --hex-blob option, mysqldump now displays spatial values in hex. Bugs Fixed...
2014-10-01 10:34:23 +02:00
share/mysql/test/suite/binlog/r/binlog_mysqlbinlog_concat.result
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/binlog/r/binlog_mysqlbinlog_filter.result
share/mysql/test/suite/binlog/r/binlog_mysqlbinlog_row.result
share/mysql/test/suite/binlog/r/binlog_mysqlbinlog_row_innodb.result
share/mysql/test/suite/binlog/r/binlog_mysqlbinlog_row_myisam.result
share/mysql/test/suite/binlog/r/binlog_mysqlbinlog_row_trans.result
share/mysql/test/suite/binlog/r/binlog_mysqlbinlog_start_stop.result
Changes 5.6.20: Security Fix: The linked OpenSSL library for the MySQL 5.6 Commercial Server has been updated from version 1.0.1g to version 1.0.1h. Versions of OpenSSL prior to and including 1.0.1g are reported to be vulnerable to CVE-2014-0224. This change does not affect the Oracle-produced MySQL Community build of MySQL Server 5.6, which uses the yaSSL library instead. DTrace Support MySQL now includes DTrace support on Oracle Linux 6 or higher with UEK kernel. If DTrace is present, server builds will detect it with no special CMake options required. For information about using DTrace on MySQL, see Tracing mysqld Using DTrace. InnoDB Notes Important Change: Redo log writes for large, externally stored BLOB fields could overwrite the most recent checkpoint. The 5.6.20 patch limits the size of redo log BLOB writes to 10% of the redo log file size. The 5.7.5 patch addresses the bug without imposing a limitation. For MySQL 5.5, the bug remains a known limitation. As a result of the redo log BLOB write limit introduced for MySQL 5.6, innodb_log_file_size should be set to a value greater than 10 times the largest BLOB data size found in the rows of your tables plus the length of other variable length fields (VARCHAR, VARBINARY, and TEXT type fields). Failing to do so could result in “Row size too large” errors. No action is required if your innodb_log_file_size setting is already sufficiently large or your tables contain no BLOB data. Functionality Added or Changed Replication: The new system variable binlog_impossible_mode controls what happens if the server cannot write to the binary log, for example, due to a file error. For backward compatibility, the default for binlog_impossible_mode is IGNORE_ERROR, meaning the server logs the error, halts logging, and continues updates to the database. Setting this variable to ABORT_SERVER makes the server halt logging and shut down if it cannot write to the binary log. CMake support was updated to handle CMake version 3. New Debian7, Ubuntu12.04, and Ubuntu14.04 distribution support that was introduced with 5.6.17 now comes with the platform-specific packaging source placed under the packaging directory, in the deb-precise, deb-wheezy, and deb-trusty directories. Support for LinuxThreads has been removed from the source code. LinuxThreads was superseded by NPTL in Linux 2.6. By default, mysql_install_db creates a my.cnf file in the installation base directory using a template. This may be undesireable for some deployments. To enable this behavior to be suppressed, mysql_install_db now supports a --keep-my-cnf option to preserve any existing my.cnf file and not create a new my.cnf file. The mysqlhotcopy utility is now deprecated and will be removed in a future version of MySQL. Among the reasons for this: It works only for the MyISAM and ARCHIVE storage engines; it works on Unix but not Windows. Alternatives include mysqldump and MySQL Enterprise Backup. The timed_mutexes system variable has no effect and is deprecated. Bugs Fixed
2014-08-10 17:11:57 +02:00
share/mysql/test/suite/binlog/r/binlog_mysqlbinlog_start_stop_slave_server_id.result
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/binlog/r/binlog_old_versions.result
share/mysql/test/suite/binlog/r/binlog_query_filter_rules.result
share/mysql/test/suite/binlog/r/binlog_reset_master.result
share/mysql/test/suite/binlog/r/binlog_rewrite.result
Changes 5.6.29: * InnoDB: A new InnoDB configuration option, innodb_tmpdir, allows you to configure a separate temporary file directory for online ALTER TABLE operations. This option was introduced to help avoid tmpdir overflows that could occur as a result of large temporary files created during online ALTER TABLE operations. innodb_tmpdir is a SESSION variable and can be configured dynamically using a SET statement. * yaSSL was upgraded to version 2.3.9. This upgrade corrects an issue in which yaSSL handled only cases of zero or one leading zeros for the key agreement instead of potentially any number, which in rare cases could cause connections to fail when using DHE cipher suites. * The Valgrind function signature in mysql-test/valgrind.supp was upgraded for Valgrind 3.11. * Bugs Fixed
2016-02-28 09:58:03 +01:00
share/mysql/test/suite/binlog/r/binlog_rotate_bgc_sync.result
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/binlog/r/binlog_row_binlog.result
share/mysql/test/suite/binlog/r/binlog_row_cache_stat.result
share/mysql/test/suite/binlog/r/binlog_row_ctype_cp932.result
share/mysql/test/suite/binlog/r/binlog_row_ctype_ucs.result
share/mysql/test/suite/binlog/r/binlog_row_drop_tbl.result
share/mysql/test/suite/binlog/r/binlog_row_drop_tmp_tbl.result
share/mysql/test/suite/binlog/r/binlog_row_insert_select.result
share/mysql/test/suite/binlog/r/binlog_row_mix_innodb_myisam.result
share/mysql/test/suite/binlog/r/binlog_row_mysqlbinlog_db_filter.result
share/mysql/test/suite/binlog/r/binlog_row_mysqlbinlog_verbose.result
share/mysql/test/suite/binlog/r/binlog_row_query_log_events.result
share/mysql/test/suite/binlog/r/binlog_server_id.result
share/mysql/test/suite/binlog/r/binlog_server_start_options.result
share/mysql/test/suite/binlog/r/binlog_sf.result
share/mysql/test/suite/binlog/r/binlog_spurious_ddl_errors.result
share/mysql/test/suite/binlog/r/binlog_sql_mode.result
share/mysql/test/suite/binlog/r/binlog_start_comment.result
share/mysql/test/suite/binlog/r/binlog_statement_insert_delayed.result
share/mysql/test/suite/binlog/r/binlog_stm_binlog.result
share/mysql/test/suite/binlog/r/binlog_stm_blackhole.result
share/mysql/test/suite/binlog/r/binlog_stm_cache_stat.result
share/mysql/test/suite/binlog/r/binlog_stm_ctype_cp932.result
share/mysql/test/suite/binlog/r/binlog_stm_ctype_ucs.result
share/mysql/test/suite/binlog/r/binlog_stm_do_db.result
share/mysql/test/suite/binlog/r/binlog_stm_drop_tbl.result
share/mysql/test/suite/binlog/r/binlog_stm_drop_tmp_tbl.result
share/mysql/test/suite/binlog/r/binlog_stm_insert_select.result
share/mysql/test/suite/binlog/r/binlog_stm_mix_innodb_myisam.result
share/mysql/test/suite/binlog/r/binlog_stm_ps.result
share/mysql/test/suite/binlog/r/binlog_stm_row.result
share/mysql/test/suite/binlog/r/binlog_stm_unsafe_warning.result
share/mysql/test/suite/binlog/r/binlog_stm_user_variables.result
share/mysql/test/suite/binlog/r/binlog_switch_inside_trans.result
share/mysql/test/suite/binlog/r/binlog_tmp_table.result
Changes 5.6.19: Functionality Added or Changed The obsolete and unmaintained charset2html utility has been removed from MySQL distributions. The mysqlbug, mysql_waitpid, and mysql_zap utilities have been deprecated and will be removed in MySQL 5.7. Bugs Fixed InnoDB: After upgrading from 5.6.10 to MySQL versions up to and including MySQL 5.6.18, InnoDB would attempt to rename obsolete full-text search auxiliary tables on server startup, resulting in an assertion failure. InnoDB: For each insert, memset would be called three times to allocate memory for system fields. To reduce CPU usage, the three memset calls are now combined into a single call. InnoDB: Enabling the InnoDB Table Monitor would result in a ib_table->stat_initialized assertion failure. InnoDB: Setting innodb_max_dirty_pages_pct=0 would leave 1% of dirty pages unflushed. Buffer pool flushing is initiated when the percentage of dirty pages is greater innodb_max_dirty_pages_pct. The internal variables that store the innodb_max_dirty_pages_pct value and the percentage of dirty pages (buf_get_modified_ratio_pct and srv_max_buf_pool_modified_pct) were defined as unsigned integer data types, which meant that a innodb_max_dirty_pages_pct value of 0 required a dirty pages percentage of 1 or greater to initiate buffer pool flushing. To address this problem, the buf_get_modified_ratio_pct and srv_max_buf_pool_modified_pct internal variables are redefined as double data types, which changes the range value for innodb_max_dirty_pages_pct and innodb_max_dirty_pages_pct_lwm from 0 .. 99 to 0 .. 99.99. Additionally, buffer pool flushing is now initiated when the percentage of dirty pages is “greater than or equal to” innodb_max_dirty_pages_pct. Replication: Log rotation events could cause group_relay_log_pos to be moved forward incorrectly within a group. This meant that, when the transaction was retried, or if the SQL thread was stopped in the middle of a transaction following one or more log rotations (such that the transaction or group spanned multiple relay log files), part or all of the group was silently skipped. This issue has been addressed by correcting a problem in the logic used to avoid touching the coordinates of the SQL thread when updating the log position as part of a relay log rotation whereby it was possible to update the SQL thread's coordinates when not using a multi-threaded slave, even in the middle of a group. Replication: When running the server with --gtid-mode=ON, STOP SLAVE followed by START SLAVE resulted in a mismatch between the information provided by INFORMATION_SCHEMA.INNODB_TEMP_TABLE_INFO and the Slave_open_temp_tables status variable: the INNODB_TEMP_TABLE_INFO table showed that no temporary tables existed, but Slave_open_temp_tables had a nonzero value. Replication: In certain cases, the server mishandled triggers and stored procedures that tried to modify other tables when called by CREATE TABLE ... SELECT. This is now handled correctly as an error. Replication: When used on a table employing a transactional storage engine, a failed TRUNCATE TABLE was still written to the binary log and thus replayed on the slave. This could lead to inconsistency when the master retained data that was removed on the slave. Now in such cases TRUNCATE TABLE is logged only when it executes successfully. Replication: The server did not always handle the auto.cnf file correctly in cases where this file's permissions were incorrect. Replication: When the binary log was rotated due to receipt of a SIGHUP signal, the new binary log did not contain the Previous_gtid_event required for subsequent processing of that binary log's GTID events. Now when SIGHUP is received, steps are taken to insure that the server writes the necessary Previous_gtid_event to the new log before writing any GTID events to the new log.
2014-06-02 09:30:38 +02:00
share/mysql/test/suite/binlog/r/binlog_truncate_kill.result
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/binlog/r/binlog_truncate_myisam.result
share/mysql/test/suite/binlog/r/binlog_trx_empty_assertions.result
share/mysql/test/suite/binlog/r/binlog_unsafe.result
share/mysql/test/suite/binlog/r/binlog_variables_log_bin.result
share/mysql/test/suite/binlog/r/binlog_variables_log_bin_index.result
share/mysql/test/suite/binlog/r/binlog_variables_relay_log.result
share/mysql/test/suite/binlog/r/binlog_variables_relay_log_index.result
share/mysql/test/suite/binlog/r/binlog_write_error.result
Changes 5.6.23: * The linked OpenSSL library for the MySQL Commercial Server has been updated from version 1.0.1j to version 1.0.1k. * Support for the SSL 2.0 and SSL 3.0 protocols has been disabled because they provide weak encryption. * yaSSL was upgraded to version 2.3.7. * The valid date range of the SSL certificates in mysql-test/std_data has been extended to the year 2029. * Bugs Fixed
2015-02-07 20:23:40 +01:00
share/mysql/test/suite/binlog/r/binlog_xa_handling.result
Changes 5.6.27: * InnoDB: The new innodb_numa_interleave read-only configuration option allows you to enable the NUMA interleave memory policy for allocation of the InnoDB buffer pool. When innodb_numa_interleave is enabled, the NUMA memory policy is set to MPOL_INTERLEAVE for the mysqld process. After the InnoDB buffer pool is allocated, the NUMA memory policy is set back to MPOL_DEFAULT. This option is only available on NUMA-enabled systems. * yaSSL was upgraded to version 2.3.8. * RPM .spec files were updated so that MySQL Server builds from source RPM packages will include the proper files to take advantage of operating system NUMA capabilities. This introduces a runtime dependency on libnuma.so.1. RPM and yum detect this and refuse to install if that library is not installed. * InnoDB: Reloading a table that was evicted while empty caused an AUTO_INCREMENT value to be reset. * InnoDB: Memory allocation sanity checks were added to the memcached code. * InnoDB: A memcached flush_all command raised an assertion. A function that starts a transaction was called from within assertion code. * InnoDB: A data corruption occurred on ARM64. GCC builtins did not issue the correct fences when setting or unsetting the lock word. * InnoDB: Server shutdown was delayed waiting for the purge thread to exit. To avoid this problem, the number of calls to trx_purge() was reduced, and the trx_purge() batch size was reduced to 20. * InnoDB: In READ COMMITTED mode, a REPLACE operation on a unique secondary index resulted in a constraint violation. * InnoDB: The IBUF_BITMAP_FREE bit indicated that there was more free space in the leaf page than was actually available. * InnoDB: Setting lower_case_table_names=0 on a case-insensitive file system could result in a hang condition when running an INSERT INTO ... SELECT ... FROM tbl_name operation with the wrong tbl_name letter case. An error message is now printed and the server exits when attempting to start the server with --lower_case_table_names=0 on a case-insensitive file system. * InnoDB: The server failed to start with an innodb_force_recovery setting greater than 3. InnoDB was set to read-only mode before redo logs were applied. * InnoDB: The trx_sys_read_pertable_file_format_id() function reported the wrong file format. * Partitioning: CREATE TABLE statements that used an invalid function in a subpartitioning expression did not always fail gracefully as expected. * Partitioning: Error handling for failed partitioning-related ALTER TABLE operations against non-partitioned tables was not performed correctly * Partitioning: ALTER TABLE when executed from a stored procedure did not always work correctly with tables partitioned by RANGE. * Replication: Repeatedly checking for ERR_LOCK_WAIT_TIMEOUT (as done, for example by repeatedly executing SHOW SLAVE STATUS) during a prolonged write lock on a table led to an assert. * Replication: If statement based logging was in use, when updating multiple tables in a single statement, a single transaction could be logged as two different transactions. This was due to the binary logging process not properly identifying statements which were operating over transactional tables. The fix ensures that they are correctly identified, even if such statements do not change the contents of the tables.
2015-10-03 14:46:13 +02:00
share/mysql/test/suite/binlog/r/show_binlog_events_no_lock.result
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/binlog/std_data/binlog_old_version_4_1.000001
share/mysql/test/suite/binlog/std_data/bug11747887-bin.000003
share/mysql/test/suite/binlog/std_data/bug32407.001
share/mysql/test/suite/binlog/std_data/update-full-row.binlog
share/mysql/test/suite/binlog/std_data/update-partial-row.binlog
share/mysql/test/suite/binlog/std_data/ver_5_1-telco.001
share/mysql/test/suite/binlog/std_data/ver_5_1-wl2325_r.001
share/mysql/test/suite/binlog/std_data/ver_5_1-wl2325_s.001
share/mysql/test/suite/binlog/std_data/ver_5_1_17.001
share/mysql/test/suite/binlog/std_data/ver_5_1_23.001
share/mysql/test/suite/binlog/std_data/ver_trunk_row_v2.001
share/mysql/test/suite/binlog/std_data/write-full-row.binlog
share/mysql/test/suite/binlog/std_data/write-partial-row.binlog
share/mysql/test/suite/binlog/t/binlog_base64_flag.test
share/mysql/test/suite/binlog/t/binlog_bug23533.test
share/mysql/test/suite/binlog/t/binlog_bug36391-master.opt
share/mysql/test/suite/binlog/t/binlog_bug36391.test
share/mysql/test/suite/binlog/t/binlog_checksum.test
share/mysql/test/suite/binlog/t/binlog_crash_safe_master_checksum-master.opt
share/mysql/test/suite/binlog/t/binlog_crash_safe_master_checksum.test
share/mysql/test/suite/binlog/t/binlog_database.test
share/mysql/test/suite/binlog/t/binlog_delete_and_flush_index.test
share/mysql/test/suite/binlog/t/binlog_drop_if_exists.test
share/mysql/test/suite/binlog/t/binlog_enforce_gtid_consistency.test
Changes 5.6.28: MySQL Server RPM packages now contain a conflict indicator for MySQL Connector C, such that an error occurs when installing MySQL Server if MySQL Connector C is also installed. To install MySQL Server, remove any MySQL Connector C packages first. mysql_upgrade now attempts to print more informative errors than FATAL ERROR: Upgrade failed. These client programs now support the --enable-cleartext-plugin option: mysqlcheck, mysqldump, mysqlimport, mysqlshow. This option enables the mysql_clear_password cleartext authentication plugin. (See The Cleartext Client-Side Authentication Plugin.) Support for building with Solaris Studio 5.13 was added. Performance Schema digests in DIGEST_TEXT columns have ... appended to the end to indicate when statements exceed the maximum statement size and were truncated. This is also now done for statement text values in SQL_TEXT columns. Bugs Fixed
2015-12-08 09:49:50 +01:00
share/mysql/test/suite/binlog/t/binlog_error_action-master.opt
Changes 5.6.22: * Noisy compiler warnings on FreeBSD 10 were silenced. * CMake workarounds for older Mac OS X and XCode versions were removed. On Mac OS X, compilation always uses Clang, even for 32-bit builds. * Previously, the MYSQL_MAINTAINER_MODE CMake option was turned on by default for debug builds and off for release builds, and MYSQL_MAINTAINER_MODE caused -Werror to be enabled when building with GCC. This made it cumbersome to enable -Werror under certain conditions, such as when compiling with Clang. * Build support was modified to produce the same warnings for Clang as for gcc. * CMake configuration for the Clang compiler sets more appropriate flags for building on Linux. Specifically, -g -fno-omit-frame-pointer -fno-strict-aliasing is now added. * Bugs fixed.
2014-12-02 13:40:09 +01:00
share/mysql/test/suite/binlog/t/binlog_error_action.test
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/binlog/t/binlog_format_switch_in_tmp_table.test
share/mysql/test/suite/binlog/t/binlog_grant.test
share/mysql/test/suite/binlog/t/binlog_gtid_cache-master.opt
share/mysql/test/suite/binlog/t/binlog_gtid_cache.test
share/mysql/test/suite/binlog/t/binlog_gtid_errors-master.opt
share/mysql/test/suite/binlog/t/binlog_gtid_errors.test
Changes 5.6.29: * InnoDB: A new InnoDB configuration option, innodb_tmpdir, allows you to configure a separate temporary file directory for online ALTER TABLE operations. This option was introduced to help avoid tmpdir overflows that could occur as a result of large temporary files created during online ALTER TABLE operations. innodb_tmpdir is a SESSION variable and can be configured dynamically using a SET statement. * yaSSL was upgraded to version 2.3.9. This upgrade corrects an issue in which yaSSL handled only cases of zero or one leading zeros for the key agreement instead of potentially any number, which in rare cases could cause connections to fail when using DHE cipher suites. * The Valgrind function signature in mysql-test/valgrind.supp was upgraded for Valgrind 3.11. * Bugs Fixed
2016-02-28 09:58:03 +01:00
share/mysql/test/suite/binlog/t/binlog_gtid_exhausted-master.opt
share/mysql/test/suite/binlog/t/binlog_gtid_exhausted.test
Changes 5.6.11: 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. 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. mysql_config_editor now supports --port and --socket options for specifying TCP/IP port number and Unix socket file name. 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. The only supported value for the innodb_mirrored_log_groups system variable is 1, so this variable is now deprecated. Setting it to 1 at startup results in a warning. Setting it to a value other than 1 at startup results in an error and the server exits. This variable will be removed in a future release.
2013-04-20 10:06:01 +02:00
share/mysql/test/suite/binlog/t/binlog_gtid_implicit_commit.test
share/mysql/test/suite/binlog/t/binlog_gtid_innodb.test
share/mysql/test/suite/binlog/t/binlog_gtid_mysqlbinlog_row.test
share/mysql/test/suite/binlog/t/binlog_gtid_mysqlbinlog_row_innodb.test
share/mysql/test/suite/binlog/t/binlog_gtid_mysqlbinlog_row_myisam.test
share/mysql/test/suite/binlog/t/binlog_gtid_mysqlbinlog_start_stop.test
share/mysql/test/suite/binlog/t/binlog_gtid_row_ctype_ucs.test
Changes 5.6.23: * The linked OpenSSL library for the MySQL Commercial Server has been updated from version 1.0.1j to version 1.0.1k. * Support for the SSL 2.0 and SSL 3.0 protocols has been disabled because they provide weak encryption. * yaSSL was upgraded to version 2.3.7. * The valid date range of the SSL certificates in mysql-test/std_data has been extended to the year 2029. * Bugs Fixed
2015-02-07 20:23:40 +01:00
share/mysql/test/suite/binlog/t/binlog_gtid_simple_recovery.test
Changes 5.6.11: 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. 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. mysql_config_editor now supports --port and --socket options for specifying TCP/IP port number and Unix socket file name. 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. The only supported value for the innodb_mirrored_log_groups system variable is 1, so this variable is now deprecated. Setting it to 1 at startup results in a warning. Setting it to a value other than 1 at startup results in an error and the server exits. This variable will be removed in a future release.
2013-04-20 10:06:01 +02:00
share/mysql/test/suite/binlog/t/binlog_gtid_stm_ctype_ucs.test
Changes 5.6.19: Functionality Added or Changed The obsolete and unmaintained charset2html utility has been removed from MySQL distributions. The mysqlbug, mysql_waitpid, and mysql_zap utilities have been deprecated and will be removed in MySQL 5.7. Bugs Fixed InnoDB: After upgrading from 5.6.10 to MySQL versions up to and including MySQL 5.6.18, InnoDB would attempt to rename obsolete full-text search auxiliary tables on server startup, resulting in an assertion failure. InnoDB: For each insert, memset would be called three times to allocate memory for system fields. To reduce CPU usage, the three memset calls are now combined into a single call. InnoDB: Enabling the InnoDB Table Monitor would result in a ib_table->stat_initialized assertion failure. InnoDB: Setting innodb_max_dirty_pages_pct=0 would leave 1% of dirty pages unflushed. Buffer pool flushing is initiated when the percentage of dirty pages is greater innodb_max_dirty_pages_pct. The internal variables that store the innodb_max_dirty_pages_pct value and the percentage of dirty pages (buf_get_modified_ratio_pct and srv_max_buf_pool_modified_pct) were defined as unsigned integer data types, which meant that a innodb_max_dirty_pages_pct value of 0 required a dirty pages percentage of 1 or greater to initiate buffer pool flushing. To address this problem, the buf_get_modified_ratio_pct and srv_max_buf_pool_modified_pct internal variables are redefined as double data types, which changes the range value for innodb_max_dirty_pages_pct and innodb_max_dirty_pages_pct_lwm from 0 .. 99 to 0 .. 99.99. Additionally, buffer pool flushing is now initiated when the percentage of dirty pages is “greater than or equal to” innodb_max_dirty_pages_pct. Replication: Log rotation events could cause group_relay_log_pos to be moved forward incorrectly within a group. This meant that, when the transaction was retried, or if the SQL thread was stopped in the middle of a transaction following one or more log rotations (such that the transaction or group spanned multiple relay log files), part or all of the group was silently skipped. This issue has been addressed by correcting a problem in the logic used to avoid touching the coordinates of the SQL thread when updating the log position as part of a relay log rotation whereby it was possible to update the SQL thread's coordinates when not using a multi-threaded slave, even in the middle of a group. Replication: When running the server with --gtid-mode=ON, STOP SLAVE followed by START SLAVE resulted in a mismatch between the information provided by INFORMATION_SCHEMA.INNODB_TEMP_TABLE_INFO and the Slave_open_temp_tables status variable: the INNODB_TEMP_TABLE_INFO table showed that no temporary tables existed, but Slave_open_temp_tables had a nonzero value. Replication: In certain cases, the server mishandled triggers and stored procedures that tried to modify other tables when called by CREATE TABLE ... SELECT. This is now handled correctly as an error. Replication: When used on a table employing a transactional storage engine, a failed TRUNCATE TABLE was still written to the binary log and thus replayed on the slave. This could lead to inconsistency when the master retained data that was removed on the slave. Now in such cases TRUNCATE TABLE is logged only when it executes successfully. Replication: The server did not always handle the auto.cnf file correctly in cases where this file's permissions were incorrect. Replication: When the binary log was rotated due to receipt of a SIGHUP signal, the new binary log did not contain the Previous_gtid_event required for subsequent processing of that binary log's GTID events. Now when SIGHUP is received, steps are taken to insure that the server writes the necessary Previous_gtid_event to the new log before writing any GTID events to the new log.
2014-06-02 09:30:38 +02:00
share/mysql/test/suite/binlog/t/binlog_gtid_utils.test
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/binlog/t/binlog_hexdump.test
share/mysql/test/suite/binlog/t/binlog_implicit_commit.test
share/mysql/test/suite/binlog/t/binlog_incident-master.opt
share/mysql/test/suite/binlog/t/binlog_incident.test
share/mysql/test/suite/binlog/t/binlog_incident_ignore-master.opt
share/mysql/test/suite/binlog/t/binlog_incident_ignore.test
share/mysql/test/suite/binlog/t/binlog_index-master.opt
share/mysql/test/suite/binlog/t/binlog_index.test
share/mysql/test/suite/binlog/t/binlog_innodb.test
share/mysql/test/suite/binlog/t/binlog_innodb_row.test
share/mysql/test/suite/binlog/t/binlog_killed.test
share/mysql/test/suite/binlog/t/binlog_killed_simulate-master.opt
share/mysql/test/suite/binlog/t/binlog_killed_simulate.test
share/mysql/test/suite/binlog/t/binlog_max_extension.test
share/mysql/test/suite/binlog/t/binlog_mixed_cache_stat.test
share/mysql/test/suite/binlog/t/binlog_mixed_load_data.test
share/mysql/test/suite/binlog/t/binlog_multi_engine.test
share/mysql/test/suite/binlog/t/binlog_mysqlbinlog-cp932-master.opt
share/mysql/test/suite/binlog/t/binlog_mysqlbinlog-cp932.test
share/mysql/test/suite/binlog/t/binlog_mysqlbinlog_base64.test
Changes 5.6.21: The --skip-innodb option is now deprecated and its use results in a warning. It will be removed in a future MySQL release. This also applies to its synonyms (--innodb=OFF, --disable-innodb, and so forth). MySQL Enterprise Edition now includes a set of encryption functions based on the OpenSSL library that expose OpenSSL capabilities at the SQL level. Replication: The new variable simplified_binlog_gtid_recovery can be used to change the way binary log files are searched for previous GTIDs during recovery, speeding up the process when a large number of binary log files exist. Internally, spatial data types such as Geometry are represented as BLOB values, so when invoked with the --hex-blob option, mysqldump now displays spatial values in hex. Bugs Fixed...
2014-10-01 10:34:23 +02:00
share/mysql/test/suite/binlog/t/binlog_mysqlbinlog_concat.test
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/binlog/t/binlog_mysqlbinlog_filter.test
share/mysql/test/suite/binlog/t/binlog_mysqlbinlog_row.test
share/mysql/test/suite/binlog/t/binlog_mysqlbinlog_row_innodb.test
share/mysql/test/suite/binlog/t/binlog_mysqlbinlog_row_myisam.test
share/mysql/test/suite/binlog/t/binlog_mysqlbinlog_row_trans.test
share/mysql/test/suite/binlog/t/binlog_mysqlbinlog_start_stop.test
Changes 5.6.20: Security Fix: The linked OpenSSL library for the MySQL 5.6 Commercial Server has been updated from version 1.0.1g to version 1.0.1h. Versions of OpenSSL prior to and including 1.0.1g are reported to be vulnerable to CVE-2014-0224. This change does not affect the Oracle-produced MySQL Community build of MySQL Server 5.6, which uses the yaSSL library instead. DTrace Support MySQL now includes DTrace support on Oracle Linux 6 or higher with UEK kernel. If DTrace is present, server builds will detect it with no special CMake options required. For information about using DTrace on MySQL, see Tracing mysqld Using DTrace. InnoDB Notes Important Change: Redo log writes for large, externally stored BLOB fields could overwrite the most recent checkpoint. The 5.6.20 patch limits the size of redo log BLOB writes to 10% of the redo log file size. The 5.7.5 patch addresses the bug without imposing a limitation. For MySQL 5.5, the bug remains a known limitation. As a result of the redo log BLOB write limit introduced for MySQL 5.6, innodb_log_file_size should be set to a value greater than 10 times the largest BLOB data size found in the rows of your tables plus the length of other variable length fields (VARCHAR, VARBINARY, and TEXT type fields). Failing to do so could result in “Row size too large” errors. No action is required if your innodb_log_file_size setting is already sufficiently large or your tables contain no BLOB data. Functionality Added or Changed Replication: The new system variable binlog_impossible_mode controls what happens if the server cannot write to the binary log, for example, due to a file error. For backward compatibility, the default for binlog_impossible_mode is IGNORE_ERROR, meaning the server logs the error, halts logging, and continues updates to the database. Setting this variable to ABORT_SERVER makes the server halt logging and shut down if it cannot write to the binary log. CMake support was updated to handle CMake version 3. New Debian7, Ubuntu12.04, and Ubuntu14.04 distribution support that was introduced with 5.6.17 now comes with the platform-specific packaging source placed under the packaging directory, in the deb-precise, deb-wheezy, and deb-trusty directories. Support for LinuxThreads has been removed from the source code. LinuxThreads was superseded by NPTL in Linux 2.6. By default, mysql_install_db creates a my.cnf file in the installation base directory using a template. This may be undesireable for some deployments. To enable this behavior to be suppressed, mysql_install_db now supports a --keep-my-cnf option to preserve any existing my.cnf file and not create a new my.cnf file. The mysqlhotcopy utility is now deprecated and will be removed in a future version of MySQL. Among the reasons for this: It works only for the MyISAM and ARCHIVE storage engines; it works on Unix but not Windows. Alternatives include mysqldump and MySQL Enterprise Backup. The timed_mutexes system variable has no effect and is deprecated. Bugs Fixed
2014-08-10 17:11:57 +02:00
share/mysql/test/suite/binlog/t/binlog_mysqlbinlog_start_stop_slave_server_id.test
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/binlog/t/binlog_old_versions.test
share/mysql/test/suite/binlog/t/binlog_query_filter_rules-master.opt
share/mysql/test/suite/binlog/t/binlog_query_filter_rules.test
share/mysql/test/suite/binlog/t/binlog_reset_master.test
share/mysql/test/suite/binlog/t/binlog_rewrite.test
Changes 5.6.29: * InnoDB: A new InnoDB configuration option, innodb_tmpdir, allows you to configure a separate temporary file directory for online ALTER TABLE operations. This option was introduced to help avoid tmpdir overflows that could occur as a result of large temporary files created during online ALTER TABLE operations. innodb_tmpdir is a SESSION variable and can be configured dynamically using a SET statement. * yaSSL was upgraded to version 2.3.9. This upgrade corrects an issue in which yaSSL handled only cases of zero or one leading zeros for the key agreement instead of potentially any number, which in rare cases could cause connections to fail when using DHE cipher suites. * The Valgrind function signature in mysql-test/valgrind.supp was upgraded for Valgrind 3.11. * Bugs Fixed
2016-02-28 09:58:03 +01:00
share/mysql/test/suite/binlog/t/binlog_rotate_bgc_sync.test
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/binlog/t/binlog_row_binlog-master.opt
share/mysql/test/suite/binlog/t/binlog_row_binlog.test
share/mysql/test/suite/binlog/t/binlog_row_cache_stat.test
share/mysql/test/suite/binlog/t/binlog_row_ctype_cp932.test
share/mysql/test/suite/binlog/t/binlog_row_ctype_ucs.test
share/mysql/test/suite/binlog/t/binlog_row_drop_tbl.test
share/mysql/test/suite/binlog/t/binlog_row_drop_tmp_tbl.test
share/mysql/test/suite/binlog/t/binlog_row_innodb_stat-master.opt
share/mysql/test/suite/binlog/t/binlog_row_insert_select.test
share/mysql/test/suite/binlog/t/binlog_row_mix_innodb_myisam-master.opt
share/mysql/test/suite/binlog/t/binlog_row_mix_innodb_myisam.test
share/mysql/test/suite/binlog/t/binlog_row_mysqlbinlog_db_filter.test
share/mysql/test/suite/binlog/t/binlog_row_mysqlbinlog_verbose.test
share/mysql/test/suite/binlog/t/binlog_row_query_log_events.test
share/mysql/test/suite/binlog/t/binlog_server_id.test
share/mysql/test/suite/binlog/t/binlog_server_start_options.test
share/mysql/test/suite/binlog/t/binlog_sf.test
Changes 5.6.21: The --skip-innodb option is now deprecated and its use results in a warning. It will be removed in a future MySQL release. This also applies to its synonyms (--innodb=OFF, --disable-innodb, and so forth). MySQL Enterprise Edition now includes a set of encryption functions based on the OpenSSL library that expose OpenSSL capabilities at the SQL level. Replication: The new variable simplified_binlog_gtid_recovery can be used to change the way binary log files are searched for previous GTIDs during recovery, speeding up the process when a large number of binary log files exist. Internally, spatial data types such as Geometry are represented as BLOB values, so when invoked with the --hex-blob option, mysqldump now displays spatial values in hex. Bugs Fixed...
2014-10-01 10:34:23 +02:00
share/mysql/test/suite/binlog/t/binlog_simplified_binlog_gtid_recovery-master.opt
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/binlog/t/binlog_spurious_ddl_errors-master.opt
share/mysql/test/suite/binlog/t/binlog_spurious_ddl_errors.test
share/mysql/test/suite/binlog/t/binlog_sql_mode.test
share/mysql/test/suite/binlog/t/binlog_start_comment.test
share/mysql/test/suite/binlog/t/binlog_statement_insert_delayed.test
share/mysql/test/suite/binlog/t/binlog_stm_binlog-master.opt
share/mysql/test/suite/binlog/t/binlog_stm_binlog.test
share/mysql/test/suite/binlog/t/binlog_stm_blackhole.test
share/mysql/test/suite/binlog/t/binlog_stm_cache_stat.test
share/mysql/test/suite/binlog/t/binlog_stm_ctype_cp932.test
share/mysql/test/suite/binlog/t/binlog_stm_ctype_ucs.test
share/mysql/test/suite/binlog/t/binlog_stm_do_db-master.opt
share/mysql/test/suite/binlog/t/binlog_stm_do_db.test
share/mysql/test/suite/binlog/t/binlog_stm_drop_tbl.test
share/mysql/test/suite/binlog/t/binlog_stm_drop_tmp_tbl.test
share/mysql/test/suite/binlog/t/binlog_stm_innodb_stat-master.opt
share/mysql/test/suite/binlog/t/binlog_stm_insert_select.test
share/mysql/test/suite/binlog/t/binlog_stm_mix_innodb_myisam-master.opt
share/mysql/test/suite/binlog/t/binlog_stm_mix_innodb_myisam.test
share/mysql/test/suite/binlog/t/binlog_stm_ps.test
share/mysql/test/suite/binlog/t/binlog_stm_row.test
share/mysql/test/suite/binlog/t/binlog_stm_unsafe_warning-master.opt
share/mysql/test/suite/binlog/t/binlog_stm_unsafe_warning.test
share/mysql/test/suite/binlog/t/binlog_stm_user_variables.test
share/mysql/test/suite/binlog/t/binlog_switch_inside_trans.test
share/mysql/test/suite/binlog/t/binlog_tmp_table.test
share/mysql/test/suite/binlog/t/binlog_truncate_innodb-master.opt
Changes 5.6.19: Functionality Added or Changed The obsolete and unmaintained charset2html utility has been removed from MySQL distributions. The mysqlbug, mysql_waitpid, and mysql_zap utilities have been deprecated and will be removed in MySQL 5.7. Bugs Fixed InnoDB: After upgrading from 5.6.10 to MySQL versions up to and including MySQL 5.6.18, InnoDB would attempt to rename obsolete full-text search auxiliary tables on server startup, resulting in an assertion failure. InnoDB: For each insert, memset would be called three times to allocate memory for system fields. To reduce CPU usage, the three memset calls are now combined into a single call. InnoDB: Enabling the InnoDB Table Monitor would result in a ib_table->stat_initialized assertion failure. InnoDB: Setting innodb_max_dirty_pages_pct=0 would leave 1% of dirty pages unflushed. Buffer pool flushing is initiated when the percentage of dirty pages is greater innodb_max_dirty_pages_pct. The internal variables that store the innodb_max_dirty_pages_pct value and the percentage of dirty pages (buf_get_modified_ratio_pct and srv_max_buf_pool_modified_pct) were defined as unsigned integer data types, which meant that a innodb_max_dirty_pages_pct value of 0 required a dirty pages percentage of 1 or greater to initiate buffer pool flushing. To address this problem, the buf_get_modified_ratio_pct and srv_max_buf_pool_modified_pct internal variables are redefined as double data types, which changes the range value for innodb_max_dirty_pages_pct and innodb_max_dirty_pages_pct_lwm from 0 .. 99 to 0 .. 99.99. Additionally, buffer pool flushing is now initiated when the percentage of dirty pages is “greater than or equal to” innodb_max_dirty_pages_pct. Replication: Log rotation events could cause group_relay_log_pos to be moved forward incorrectly within a group. This meant that, when the transaction was retried, or if the SQL thread was stopped in the middle of a transaction following one or more log rotations (such that the transaction or group spanned multiple relay log files), part or all of the group was silently skipped. This issue has been addressed by correcting a problem in the logic used to avoid touching the coordinates of the SQL thread when updating the log position as part of a relay log rotation whereby it was possible to update the SQL thread's coordinates when not using a multi-threaded slave, even in the middle of a group. Replication: When running the server with --gtid-mode=ON, STOP SLAVE followed by START SLAVE resulted in a mismatch between the information provided by INFORMATION_SCHEMA.INNODB_TEMP_TABLE_INFO and the Slave_open_temp_tables status variable: the INNODB_TEMP_TABLE_INFO table showed that no temporary tables existed, but Slave_open_temp_tables had a nonzero value. Replication: In certain cases, the server mishandled triggers and stored procedures that tried to modify other tables when called by CREATE TABLE ... SELECT. This is now handled correctly as an error. Replication: When used on a table employing a transactional storage engine, a failed TRUNCATE TABLE was still written to the binary log and thus replayed on the slave. This could lead to inconsistency when the master retained data that was removed on the slave. Now in such cases TRUNCATE TABLE is logged only when it executes successfully. Replication: The server did not always handle the auto.cnf file correctly in cases where this file's permissions were incorrect. Replication: When the binary log was rotated due to receipt of a SIGHUP signal, the new binary log did not contain the Previous_gtid_event required for subsequent processing of that binary log's GTID events. Now when SIGHUP is received, steps are taken to insure that the server writes the necessary Previous_gtid_event to the new log before writing any GTID events to the new log.
2014-06-02 09:30:38 +02:00
share/mysql/test/suite/binlog/t/binlog_truncate_kill.test
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/binlog/t/binlog_truncate_myisam.test
share/mysql/test/suite/binlog/t/binlog_unsafe-master.opt
share/mysql/test/suite/binlog/t/binlog_unsafe.test
share/mysql/test/suite/binlog/t/binlog_variables_log_bin-master.opt
share/mysql/test/suite/binlog/t/binlog_variables_log_bin.test
share/mysql/test/suite/binlog/t/binlog_variables_log_bin_index-master.opt
share/mysql/test/suite/binlog/t/binlog_variables_log_bin_index.test
share/mysql/test/suite/binlog/t/binlog_variables_relay_log-master.opt
share/mysql/test/suite/binlog/t/binlog_variables_relay_log.test
share/mysql/test/suite/binlog/t/binlog_variables_relay_log_index-master.opt
share/mysql/test/suite/binlog/t/binlog_variables_relay_log_index.test
share/mysql/test/suite/binlog/t/binlog_write_error.test
Changes 5.6.23: * The linked OpenSSL library for the MySQL Commercial Server has been updated from version 1.0.1j to version 1.0.1k. * Support for the SSL 2.0 and SSL 3.0 protocols has been disabled because they provide weak encryption. * yaSSL was upgraded to version 2.3.7. * The valid date range of the SSL certificates in mysql-test/std_data has been extended to the year 2029. * Bugs Fixed
2015-02-07 20:23:40 +01:00
share/mysql/test/suite/binlog/t/binlog_xa_handling.test
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/binlog/t/disabled.def
Changes 5.6.27: * InnoDB: The new innodb_numa_interleave read-only configuration option allows you to enable the NUMA interleave memory policy for allocation of the InnoDB buffer pool. When innodb_numa_interleave is enabled, the NUMA memory policy is set to MPOL_INTERLEAVE for the mysqld process. After the InnoDB buffer pool is allocated, the NUMA memory policy is set back to MPOL_DEFAULT. This option is only available on NUMA-enabled systems. * yaSSL was upgraded to version 2.3.8. * RPM .spec files were updated so that MySQL Server builds from source RPM packages will include the proper files to take advantage of operating system NUMA capabilities. This introduces a runtime dependency on libnuma.so.1. RPM and yum detect this and refuse to install if that library is not installed. * InnoDB: Reloading a table that was evicted while empty caused an AUTO_INCREMENT value to be reset. * InnoDB: Memory allocation sanity checks were added to the memcached code. * InnoDB: A memcached flush_all command raised an assertion. A function that starts a transaction was called from within assertion code. * InnoDB: A data corruption occurred on ARM64. GCC builtins did not issue the correct fences when setting or unsetting the lock word. * InnoDB: Server shutdown was delayed waiting for the purge thread to exit. To avoid this problem, the number of calls to trx_purge() was reduced, and the trx_purge() batch size was reduced to 20. * InnoDB: In READ COMMITTED mode, a REPLACE operation on a unique secondary index resulted in a constraint violation. * InnoDB: The IBUF_BITMAP_FREE bit indicated that there was more free space in the leaf page than was actually available. * InnoDB: Setting lower_case_table_names=0 on a case-insensitive file system could result in a hang condition when running an INSERT INTO ... SELECT ... FROM tbl_name operation with the wrong tbl_name letter case. An error message is now printed and the server exits when attempting to start the server with --lower_case_table_names=0 on a case-insensitive file system. * InnoDB: The server failed to start with an innodb_force_recovery setting greater than 3. InnoDB was set to read-only mode before redo logs were applied. * InnoDB: The trx_sys_read_pertable_file_format_id() function reported the wrong file format. * Partitioning: CREATE TABLE statements that used an invalid function in a subpartitioning expression did not always fail gracefully as expected. * Partitioning: Error handling for failed partitioning-related ALTER TABLE operations against non-partitioned tables was not performed correctly * Partitioning: ALTER TABLE when executed from a stored procedure did not always work correctly with tables partitioned by RANGE. * Replication: Repeatedly checking for ERR_LOCK_WAIT_TIMEOUT (as done, for example by repeatedly executing SHOW SLAVE STATUS) during a prolonged write lock on a table led to an assert. * Replication: If statement based logging was in use, when updating multiple tables in a single statement, a single transaction could be logged as two different transactions. This was due to the binary logging process not properly identifying statements which were operating over transactional tables. The fix ensures that they are correctly identified, even if such statements do not change the contents of the tables.
2015-10-03 14:46:13 +02:00
share/mysql/test/suite/binlog/t/show_binlog_events_no_lock.test
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/engines/README
share/mysql/test/suite/engines/funcs/r/ai_init_alter_table.result
share/mysql/test/suite/engines/funcs/r/ai_init_create_table.result
share/mysql/test/suite/engines/funcs/r/ai_init_insert.result
share/mysql/test/suite/engines/funcs/r/ai_init_insert_id.result
share/mysql/test/suite/engines/funcs/r/ai_overflow_error.result
share/mysql/test/suite/engines/funcs/r/ai_reset_by_truncate.result
share/mysql/test/suite/engines/funcs/r/ai_sql_auto_is_null.result
share/mysql/test/suite/engines/funcs/r/an_calendar.result
share/mysql/test/suite/engines/funcs/r/an_number.result
share/mysql/test/suite/engines/funcs/r/an_string.result
share/mysql/test/suite/engines/funcs/r/comment_column.result
share/mysql/test/suite/engines/funcs/r/comment_column2.result
share/mysql/test/suite/engines/funcs/r/comment_index.result
share/mysql/test/suite/engines/funcs/r/comment_table.result
share/mysql/test/suite/engines/funcs/r/crash_manycolumns_number.result
share/mysql/test/suite/engines/funcs/r/crash_manycolumns_string.result
share/mysql/test/suite/engines/funcs/r/crash_manyindexes_number.result
share/mysql/test/suite/engines/funcs/r/crash_manyindexes_string.result
share/mysql/test/suite/engines/funcs/r/crash_manytables_number.result
share/mysql/test/suite/engines/funcs/r/crash_manytables_string.result
share/mysql/test/suite/engines/funcs/r/date_function.result
share/mysql/test/suite/engines/funcs/r/datetime_function.result
share/mysql/test/suite/engines/funcs/r/db_alter_character_set.result
share/mysql/test/suite/engines/funcs/r/db_alter_character_set_collate.result
share/mysql/test/suite/engines/funcs/r/db_alter_collate_ascii.result
share/mysql/test/suite/engines/funcs/r/db_alter_collate_utf8.result
share/mysql/test/suite/engines/funcs/r/db_create_character_set.result
share/mysql/test/suite/engines/funcs/r/db_create_character_set_collate.result
share/mysql/test/suite/engines/funcs/r/db_create_drop.result
share/mysql/test/suite/engines/funcs/r/db_create_error.result
share/mysql/test/suite/engines/funcs/r/db_create_error_reserved.result
share/mysql/test/suite/engines/funcs/r/db_create_if_not_exists.result
share/mysql/test/suite/engines/funcs/r/db_drop_error.result
share/mysql/test/suite/engines/funcs/r/db_use_error.result
share/mysql/test/suite/engines/funcs/r/de_autoinc.result
share/mysql/test/suite/engines/funcs/r/de_calendar_range.result
share/mysql/test/suite/engines/funcs/r/de_ignore.result
share/mysql/test/suite/engines/funcs/r/de_limit.result
share/mysql/test/suite/engines/funcs/r/de_multi_db_table.result
share/mysql/test/suite/engines/funcs/r/de_multi_db_table_using.result
share/mysql/test/suite/engines/funcs/r/de_multi_table.result
share/mysql/test/suite/engines/funcs/r/de_multi_table_using.result
share/mysql/test/suite/engines/funcs/r/de_number_range.result
share/mysql/test/suite/engines/funcs/r/de_quick.result
share/mysql/test/suite/engines/funcs/r/de_string_range.result
share/mysql/test/suite/engines/funcs/r/de_truncate.result
share/mysql/test/suite/engines/funcs/r/de_truncate_autoinc.result
share/mysql/test/suite/engines/funcs/r/fu_aggregate_avg_number.result
share/mysql/test/suite/engines/funcs/r/fu_aggregate_count_number.result
share/mysql/test/suite/engines/funcs/r/fu_aggregate_max_number.result
share/mysql/test/suite/engines/funcs/r/fu_aggregate_max_subquery.result
share/mysql/test/suite/engines/funcs/r/fu_aggregate_min_number.result
share/mysql/test/suite/engines/funcs/r/fu_aggregate_sum_number.result
share/mysql/test/suite/engines/funcs/r/general_no_data.result
share/mysql/test/suite/engines/funcs/r/general_not_null.result
share/mysql/test/suite/engines/funcs/r/general_null.result
share/mysql/test/suite/engines/funcs/r/in_calendar_2_unique_constraints_duplicate_update.result
share/mysql/test/suite/engines/funcs/r/in_calendar_pk_constraint_duplicate_update.result
share/mysql/test/suite/engines/funcs/r/in_calendar_pk_constraint_error.result
share/mysql/test/suite/engines/funcs/r/in_calendar_pk_constraint_ignore.result
share/mysql/test/suite/engines/funcs/r/in_calendar_unique_constraint_duplicate_update.result
share/mysql/test/suite/engines/funcs/r/in_calendar_unique_constraint_error.result
share/mysql/test/suite/engines/funcs/r/in_calendar_unique_constraint_ignore.result
share/mysql/test/suite/engines/funcs/r/in_enum_null.result
share/mysql/test/suite/engines/funcs/r/in_enum_null_boundary_error.result
share/mysql/test/suite/engines/funcs/r/in_enum_null_large_error.result
share/mysql/test/suite/engines/funcs/r/in_insert_select.result
share/mysql/test/suite/engines/funcs/r/in_insert_select_autoinc.result
share/mysql/test/suite/engines/funcs/r/in_insert_select_unique_violation.result
share/mysql/test/suite/engines/funcs/r/in_lob_boundary_error.result
share/mysql/test/suite/engines/funcs/r/in_multicolumn_calendar_pk_constraint_duplicate_update.result
share/mysql/test/suite/engines/funcs/r/in_multicolumn_calendar_pk_constraint_error.result
share/mysql/test/suite/engines/funcs/r/in_multicolumn_calendar_pk_constraint_ignore.result
share/mysql/test/suite/engines/funcs/r/in_multicolumn_calendar_unique_constraint_duplicate_update.result
share/mysql/test/suite/engines/funcs/r/in_multicolumn_calendar_unique_constraint_error.result
share/mysql/test/suite/engines/funcs/r/in_multicolumn_calendar_unique_constraint_ignore.result
share/mysql/test/suite/engines/funcs/r/in_multicolumn_number_pk_constraint_duplicate_update.result
share/mysql/test/suite/engines/funcs/r/in_multicolumn_number_pk_constraint_error.result
share/mysql/test/suite/engines/funcs/r/in_multicolumn_number_pk_constraint_ignore.result
share/mysql/test/suite/engines/funcs/r/in_multicolumn_number_unique_constraint_duplicate_update.result
share/mysql/test/suite/engines/funcs/r/in_multicolumn_number_unique_constraint_error.result
share/mysql/test/suite/engines/funcs/r/in_multicolumn_number_unique_constraint_ignore.result
share/mysql/test/suite/engines/funcs/r/in_multicolumn_string_pk_constraint_duplicate_update.result
share/mysql/test/suite/engines/funcs/r/in_multicolumn_string_pk_constraint_error.result
share/mysql/test/suite/engines/funcs/r/in_multicolumn_string_pk_constraint_ignore.result
share/mysql/test/suite/engines/funcs/r/in_multicolumn_string_unique_constraint_duplicate_update.result
share/mysql/test/suite/engines/funcs/r/in_multicolumn_string_unique_constraint_error.result
share/mysql/test/suite/engines/funcs/r/in_multicolumn_string_unique_constraint_ignore.result
share/mysql/test/suite/engines/funcs/r/in_number_2_unique_constraints_duplicate_update.result
share/mysql/test/suite/engines/funcs/r/in_number_boundary_error.result
share/mysql/test/suite/engines/funcs/r/in_number_decimal_boundary_error.result
share/mysql/test/suite/engines/funcs/r/in_number_length.result
share/mysql/test/suite/engines/funcs/r/in_number_null.result
share/mysql/test/suite/engines/funcs/r/in_number_pk_constraint_duplicate_update.result
share/mysql/test/suite/engines/funcs/r/in_number_pk_constraint_error.result
share/mysql/test/suite/engines/funcs/r/in_number_pk_constraint_ignore.result
share/mysql/test/suite/engines/funcs/r/in_number_unique_constraint_duplicate_update.result
share/mysql/test/suite/engines/funcs/r/in_number_unique_constraint_error.result
share/mysql/test/suite/engines/funcs/r/in_number_unique_constraint_ignore.result
share/mysql/test/suite/engines/funcs/r/in_set_null.result
share/mysql/test/suite/engines/funcs/r/in_set_null_boundary_error.result
share/mysql/test/suite/engines/funcs/r/in_set_null_large.result
share/mysql/test/suite/engines/funcs/r/in_string_2_unique_constraints_duplicate_update.result
share/mysql/test/suite/engines/funcs/r/in_string_boundary_error.result
share/mysql/test/suite/engines/funcs/r/in_string_not_null.result
share/mysql/test/suite/engines/funcs/r/in_string_null.result
share/mysql/test/suite/engines/funcs/r/in_string_pk_constraint_duplicate_update.result
share/mysql/test/suite/engines/funcs/r/in_string_pk_constraint_error.result
share/mysql/test/suite/engines/funcs/r/in_string_pk_constraint_ignore.result
share/mysql/test/suite/engines/funcs/r/in_string_set_enum_fail.result
share/mysql/test/suite/engines/funcs/r/in_string_unique_constraint_duplicate_update.result
share/mysql/test/suite/engines/funcs/r/in_string_unique_constraint_error.result
share/mysql/test/suite/engines/funcs/r/in_string_unique_constraint_ignore.result
share/mysql/test/suite/engines/funcs/r/ix_drop.result
share/mysql/test/suite/engines/funcs/r/ix_drop_error.result
share/mysql/test/suite/engines/funcs/r/ix_index_decimals.result
share/mysql/test/suite/engines/funcs/r/ix_index_lob.result
share/mysql/test/suite/engines/funcs/r/ix_index_non_string.result
share/mysql/test/suite/engines/funcs/r/ix_index_string.result
share/mysql/test/suite/engines/funcs/r/ix_index_string_length.result
share/mysql/test/suite/engines/funcs/r/ix_unique_decimals.result
share/mysql/test/suite/engines/funcs/r/ix_unique_lob.result
share/mysql/test/suite/engines/funcs/r/ix_unique_non_string.result
share/mysql/test/suite/engines/funcs/r/ix_unique_string.result
share/mysql/test/suite/engines/funcs/r/ix_unique_string_length.result
share/mysql/test/suite/engines/funcs/r/ix_using_order.result
share/mysql/test/suite/engines/funcs/r/jp_comment_column.result
share/mysql/test/suite/engines/funcs/r/jp_comment_index.result
share/mysql/test/suite/engines/funcs/r/jp_comment_older_compatibility1.result
share/mysql/test/suite/engines/funcs/r/jp_comment_table.result
share/mysql/test/suite/engines/funcs/r/ld_all_number_string_calendar_types.result
share/mysql/test/suite/engines/funcs/r/ld_bit.result
share/mysql/test/suite/engines/funcs/r/ld_enum_set.result
share/mysql/test/suite/engines/funcs/r/ld_less_columns.result
share/mysql/test/suite/engines/funcs/r/ld_more_columns_truncated.result
share/mysql/test/suite/engines/funcs/r/ld_null.result
share/mysql/test/suite/engines/funcs/r/ld_quote.result
share/mysql/test/suite/engines/funcs/r/ld_simple.result
share/mysql/test/suite/engines/funcs/r/ld_starting.result
share/mysql/test/suite/engines/funcs/r/ld_unique_error1.result
share/mysql/test/suite/engines/funcs/r/ld_unique_error1_local.result
share/mysql/test/suite/engines/funcs/r/ld_unique_error2.result
share/mysql/test/suite/engines/funcs/r/ld_unique_error2_local.result
share/mysql/test/suite/engines/funcs/r/ld_unique_error3.result
share/mysql/test/suite/engines/funcs/r/ld_unique_error3_local.result
share/mysql/test/suite/engines/funcs/r/ps_number_length.result
share/mysql/test/suite/engines/funcs/r/ps_number_null.result
share/mysql/test/suite/engines/funcs/r/ps_string_not_null.result
share/mysql/test/suite/engines/funcs/r/ps_string_null.result
share/mysql/test/suite/engines/funcs/r/re_number_range.result
share/mysql/test/suite/engines/funcs/r/re_number_range_set.result
share/mysql/test/suite/engines/funcs/r/re_number_select.result
share/mysql/test/suite/engines/funcs/r/re_string_range.result
share/mysql/test/suite/engines/funcs/r/re_string_range_set.result
share/mysql/test/suite/engines/funcs/r/rpl000010.result
share/mysql/test/suite/engines/funcs/r/rpl000011.result
share/mysql/test/suite/engines/funcs/r/rpl000013.result
share/mysql/test/suite/engines/funcs/r/rpl000017.result
share/mysql/test/suite/engines/funcs/r/rpl_000015.result
share/mysql/test/suite/engines/funcs/r/rpl_LD_INFILE.result
share/mysql/test/suite/engines/funcs/r/rpl_REDIRECT.result
share/mysql/test/suite/engines/funcs/r/rpl_alter.result
share/mysql/test/suite/engines/funcs/r/rpl_alter_db.result
share/mysql/test/suite/engines/funcs/r/rpl_bit.result
share/mysql/test/suite/engines/funcs/r/rpl_bit_npk.result
share/mysql/test/suite/engines/funcs/r/rpl_change_master.result
share/mysql/test/suite/engines/funcs/r/rpl_create_database.result
share/mysql/test/suite/engines/funcs/r/rpl_do_grant.result
share/mysql/test/suite/engines/funcs/r/rpl_drop.result
share/mysql/test/suite/engines/funcs/r/rpl_drop_db.result
share/mysql/test/suite/engines/funcs/r/rpl_dual_pos_advance.result
share/mysql/test/suite/engines/funcs/r/rpl_empty_master_crash.result
share/mysql/test/suite/engines/funcs/r/rpl_err_ignoredtable.result
share/mysql/test/suite/engines/funcs/r/rpl_flushlog_loop.result
share/mysql/test/suite/engines/funcs/r/rpl_free_items.result
share/mysql/test/suite/engines/funcs/r/rpl_get_lock.result
share/mysql/test/suite/engines/funcs/r/rpl_ignore_grant.result
share/mysql/test/suite/engines/funcs/r/rpl_ignore_revoke.result
share/mysql/test/suite/engines/funcs/r/rpl_ignore_table_update.result
share/mysql/test/suite/engines/funcs/r/rpl_init_slave.result
share/mysql/test/suite/engines/funcs/r/rpl_insert.result
share/mysql/test/suite/engines/funcs/r/rpl_insert_select.result
share/mysql/test/suite/engines/funcs/r/rpl_loaddata2.result
share/mysql/test/suite/engines/funcs/r/rpl_loaddata_m.result
share/mysql/test/suite/engines/funcs/r/rpl_loaddata_s.result
share/mysql/test/suite/engines/funcs/r/rpl_loaddatalocal.result
share/mysql/test/suite/engines/funcs/r/rpl_loadfile.result
share/mysql/test/suite/engines/funcs/r/rpl_log_pos.result
share/mysql/test/suite/engines/funcs/r/rpl_many_optimize.result
share/mysql/test/suite/engines/funcs/r/rpl_master_pos_wait.result
share/mysql/test/suite/engines/funcs/r/rpl_misc_functions.result
share/mysql/test/suite/engines/funcs/r/rpl_multi_delete.result
share/mysql/test/suite/engines/funcs/r/rpl_multi_delete2.result
share/mysql/test/suite/engines/funcs/r/rpl_multi_update4.result
share/mysql/test/suite/engines/funcs/r/rpl_ps.result
share/mysql/test/suite/engines/funcs/r/rpl_rbr_to_sbr.result
share/mysql/test/suite/engines/funcs/r/rpl_relayspace.result
share/mysql/test/suite/engines/funcs/r/rpl_replicate_ignore_db.result
share/mysql/test/suite/engines/funcs/r/rpl_row_NOW.result
share/mysql/test/suite/engines/funcs/r/rpl_row_USER.result
share/mysql/test/suite/engines/funcs/r/rpl_row_drop.result
share/mysql/test/suite/engines/funcs/r/rpl_row_func001.result
share/mysql/test/suite/engines/funcs/r/rpl_row_inexist_tbl.result
share/mysql/test/suite/engines/funcs/r/rpl_row_max_relay_size.result
share/mysql/test/suite/engines/funcs/r/rpl_row_reset_slave.result
share/mysql/test/suite/engines/funcs/r/rpl_row_sp001.result
share/mysql/test/suite/engines/funcs/r/rpl_row_sp005.result
share/mysql/test/suite/engines/funcs/r/rpl_row_sp008.result
share/mysql/test/suite/engines/funcs/r/rpl_row_sp009.result
share/mysql/test/suite/engines/funcs/r/rpl_row_sp010.result
share/mysql/test/suite/engines/funcs/r/rpl_row_sp011.result
share/mysql/test/suite/engines/funcs/r/rpl_row_sp012.result
share/mysql/test/suite/engines/funcs/r/rpl_row_stop_middle.result
share/mysql/test/suite/engines/funcs/r/rpl_row_trig001.result
share/mysql/test/suite/engines/funcs/r/rpl_row_trig002.result
share/mysql/test/suite/engines/funcs/r/rpl_row_trig003.result
share/mysql/test/suite/engines/funcs/r/rpl_row_until.result
share/mysql/test/suite/engines/funcs/r/rpl_row_view01.result
share/mysql/test/suite/engines/funcs/r/rpl_server_id1.result
share/mysql/test/suite/engines/funcs/r/rpl_server_id2.result
share/mysql/test/suite/engines/funcs/r/rpl_session_var.result
share/mysql/test/suite/engines/funcs/r/rpl_sf.result
share/mysql/test/suite/engines/funcs/r/rpl_skip_error.result
share/mysql/test/suite/engines/funcs/r/rpl_slave_status.result
share/mysql/test/suite/engines/funcs/r/rpl_sp.result
share/mysql/test/suite/engines/funcs/r/rpl_sp004.result
share/mysql/test/suite/engines/funcs/r/rpl_sp_effects.result
share/mysql/test/suite/engines/funcs/r/rpl_start_stop_slave.result
share/mysql/test/suite/engines/funcs/r/rpl_stm_max_relay_size.result
share/mysql/test/suite/engines/funcs/r/rpl_stm_mystery22.result
share/mysql/test/suite/engines/funcs/r/rpl_stm_no_op.result
share/mysql/test/suite/engines/funcs/r/rpl_stm_reset_slave.result
share/mysql/test/suite/engines/funcs/r/rpl_switch_stm_row_mixed.result
share/mysql/test/suite/engines/funcs/r/rpl_temp_table.result
share/mysql/test/suite/engines/funcs/r/rpl_temporary.result
share/mysql/test/suite/engines/funcs/r/rpl_trigger.result
share/mysql/test/suite/engines/funcs/r/rpl_trunc_temp.result
share/mysql/test/suite/engines/funcs/r/rpl_user_variables.result
share/mysql/test/suite/engines/funcs/r/rpl_variables.result
share/mysql/test/suite/engines/funcs/r/rpl_view.result
share/mysql/test/suite/engines/funcs/r/se_join_cross.result
share/mysql/test/suite/engines/funcs/r/se_join_default.result
share/mysql/test/suite/engines/funcs/r/se_join_inner.result
share/mysql/test/suite/engines/funcs/r/se_join_left.result
share/mysql/test/suite/engines/funcs/r/se_join_left_outer.result
share/mysql/test/suite/engines/funcs/r/se_join_natural_left.result
share/mysql/test/suite/engines/funcs/r/se_join_natural_left_outer.result
share/mysql/test/suite/engines/funcs/r/se_join_natural_right.result
share/mysql/test/suite/engines/funcs/r/se_join_natural_right_outer.result
share/mysql/test/suite/engines/funcs/r/se_join_right.result
share/mysql/test/suite/engines/funcs/r/se_join_right_outer.result
share/mysql/test/suite/engines/funcs/r/se_join_straight.result
share/mysql/test/suite/engines/funcs/r/se_rowid.result
share/mysql/test/suite/engines/funcs/r/se_string_distinct.result
share/mysql/test/suite/engines/funcs/r/se_string_from.result
share/mysql/test/suite/engines/funcs/r/se_string_groupby.result
share/mysql/test/suite/engines/funcs/r/se_string_having.result
share/mysql/test/suite/engines/funcs/r/se_string_limit.result
share/mysql/test/suite/engines/funcs/r/se_string_orderby.result
share/mysql/test/suite/engines/funcs/r/se_string_union.result
share/mysql/test/suite/engines/funcs/r/se_string_where.result
share/mysql/test/suite/engines/funcs/r/se_string_where_and.result
share/mysql/test/suite/engines/funcs/r/se_string_where_or.result
share/mysql/test/suite/engines/funcs/r/sf_alter.result
share/mysql/test/suite/engines/funcs/r/sf_cursor.result
share/mysql/test/suite/engines/funcs/r/sf_simple1.result
share/mysql/test/suite/engines/funcs/r/sp_alter.result
share/mysql/test/suite/engines/funcs/r/sp_cursor.result
share/mysql/test/suite/engines/funcs/r/sp_simple1.result
share/mysql/test/suite/engines/funcs/r/sq_all.result
share/mysql/test/suite/engines/funcs/r/sq_any.result
share/mysql/test/suite/engines/funcs/r/sq_corr.result
share/mysql/test/suite/engines/funcs/r/sq_error.result
share/mysql/test/suite/engines/funcs/r/sq_exists.result
share/mysql/test/suite/engines/funcs/r/sq_from.result
share/mysql/test/suite/engines/funcs/r/sq_in.result
share/mysql/test/suite/engines/funcs/r/sq_row.result
share/mysql/test/suite/engines/funcs/r/sq_scalar.result
share/mysql/test/suite/engines/funcs/r/sq_some.result
share/mysql/test/suite/engines/funcs/r/ta_2part_column_to_pk.result
share/mysql/test/suite/engines/funcs/r/ta_2part_diff_string_to_pk.result
share/mysql/test/suite/engines/funcs/r/ta_2part_diff_to_pk.result
share/mysql/test/suite/engines/funcs/r/ta_2part_string_to_pk.result
share/mysql/test/suite/engines/funcs/r/ta_3part_column_to_pk.result
share/mysql/test/suite/engines/funcs/r/ta_3part_string_to_pk.result
share/mysql/test/suite/engines/funcs/r/ta_add_column.result
share/mysql/test/suite/engines/funcs/r/ta_add_column2.result
share/mysql/test/suite/engines/funcs/r/ta_add_column_first.result
share/mysql/test/suite/engines/funcs/r/ta_add_column_first2.result
share/mysql/test/suite/engines/funcs/r/ta_add_column_middle.result
share/mysql/test/suite/engines/funcs/r/ta_add_column_middle2.result
share/mysql/test/suite/engines/funcs/r/ta_add_string.result
share/mysql/test/suite/engines/funcs/r/ta_add_string2.result
share/mysql/test/suite/engines/funcs/r/ta_add_string_first.result
share/mysql/test/suite/engines/funcs/r/ta_add_string_first2.result
share/mysql/test/suite/engines/funcs/r/ta_add_string_middle.result
share/mysql/test/suite/engines/funcs/r/ta_add_string_middle2.result
share/mysql/test/suite/engines/funcs/r/ta_add_string_unique_index.result
share/mysql/test/suite/engines/funcs/r/ta_add_unique_index.result
share/mysql/test/suite/engines/funcs/r/ta_column_from_unsigned.result
share/mysql/test/suite/engines/funcs/r/ta_column_from_zerofill.result
share/mysql/test/suite/engines/funcs/r/ta_column_to_index.result
share/mysql/test/suite/engines/funcs/r/ta_column_to_not_null.result
share/mysql/test/suite/engines/funcs/r/ta_column_to_null.result
share/mysql/test/suite/engines/funcs/r/ta_column_to_pk.result
share/mysql/test/suite/engines/funcs/r/ta_column_to_unsigned.result
share/mysql/test/suite/engines/funcs/r/ta_column_to_zerofill.result
share/mysql/test/suite/engines/funcs/r/ta_drop_column.result
share/mysql/test/suite/engines/funcs/r/ta_drop_index.result
share/mysql/test/suite/engines/funcs/r/ta_drop_pk_autoincrement.result
share/mysql/test/suite/engines/funcs/r/ta_drop_pk_number.result
share/mysql/test/suite/engines/funcs/r/ta_drop_pk_string.result
share/mysql/test/suite/engines/funcs/r/ta_drop_string_index.result
share/mysql/test/suite/engines/funcs/r/ta_orderby.result
share/mysql/test/suite/engines/funcs/r/ta_rename.result
share/mysql/test/suite/engines/funcs/r/ta_set_drop_default.result
share/mysql/test/suite/engines/funcs/r/ta_string_drop_column.result
share/mysql/test/suite/engines/funcs/r/ta_string_to_index.result
share/mysql/test/suite/engines/funcs/r/ta_string_to_not_null.result
share/mysql/test/suite/engines/funcs/r/ta_string_to_null.result
share/mysql/test/suite/engines/funcs/r/ta_string_to_pk.result
share/mysql/test/suite/engines/funcs/r/tc_column_autoincrement.result
share/mysql/test/suite/engines/funcs/r/tc_column_comment.result
share/mysql/test/suite/engines/funcs/r/tc_column_comment_string.result
share/mysql/test/suite/engines/funcs/r/tc_column_default_decimal.result
share/mysql/test/suite/engines/funcs/r/tc_column_default_number.result
share/mysql/test/suite/engines/funcs/r/tc_column_default_string.result
share/mysql/test/suite/engines/funcs/r/tc_column_enum.result
share/mysql/test/suite/engines/funcs/r/tc_column_enum_long.result
share/mysql/test/suite/engines/funcs/r/tc_column_key.result
share/mysql/test/suite/engines/funcs/r/tc_column_key_length.result
share/mysql/test/suite/engines/funcs/r/tc_column_length.result
share/mysql/test/suite/engines/funcs/r/tc_column_length_decimals.result
share/mysql/test/suite/engines/funcs/r/tc_column_length_zero.result
share/mysql/test/suite/engines/funcs/r/tc_column_not_null.result
share/mysql/test/suite/engines/funcs/r/tc_column_null.result
share/mysql/test/suite/engines/funcs/r/tc_column_primary_key_number.result
share/mysql/test/suite/engines/funcs/r/tc_column_primary_key_string.result
share/mysql/test/suite/engines/funcs/r/tc_column_serial.result
share/mysql/test/suite/engines/funcs/r/tc_column_set.result
share/mysql/test/suite/engines/funcs/r/tc_column_set_long.result
share/mysql/test/suite/engines/funcs/r/tc_column_unique_key.result
share/mysql/test/suite/engines/funcs/r/tc_column_unique_key_string.result
share/mysql/test/suite/engines/funcs/r/tc_column_unsigned.result
share/mysql/test/suite/engines/funcs/r/tc_column_zerofill.result
share/mysql/test/suite/engines/funcs/r/tc_drop_table.result
share/mysql/test/suite/engines/funcs/r/tc_multicolumn_different.result
share/mysql/test/suite/engines/funcs/r/tc_multicolumn_same.result
share/mysql/test/suite/engines/funcs/r/tc_multicolumn_same_string.result
share/mysql/test/suite/engines/funcs/r/tc_partition_analyze.result
share/mysql/test/suite/engines/funcs/r/tc_partition_change_from_range_to_hash_key.result
share/mysql/test/suite/engines/funcs/r/tc_partition_check.result
share/mysql/test/suite/engines/funcs/r/tc_partition_hash.result
share/mysql/test/suite/engines/funcs/r/tc_partition_hash_date_function.result
share/mysql/test/suite/engines/funcs/r/tc_partition_key.result
share/mysql/test/suite/engines/funcs/r/tc_partition_linear_key.result
share/mysql/test/suite/engines/funcs/r/tc_partition_list_directory.result
share/mysql/test/suite/engines/funcs/r/tc_partition_list_error.result
share/mysql/test/suite/engines/funcs/r/tc_partition_optimize.result
share/mysql/test/suite/engines/funcs/r/tc_partition_rebuild.result
share/mysql/test/suite/engines/funcs/r/tc_partition_remove.result
share/mysql/test/suite/engines/funcs/r/tc_partition_reorg_divide.result
share/mysql/test/suite/engines/funcs/r/tc_partition_reorg_hash_key.result
share/mysql/test/suite/engines/funcs/r/tc_partition_reorg_merge.result
share/mysql/test/suite/engines/funcs/r/tc_partition_repair.result
share/mysql/test/suite/engines/funcs/r/tc_partition_sub1.result
share/mysql/test/suite/engines/funcs/r/tc_partition_sub2.result
share/mysql/test/suite/engines/funcs/r/tc_partition_value.result
share/mysql/test/suite/engines/funcs/r/tc_partition_value_error.result
share/mysql/test/suite/engines/funcs/r/tc_partition_value_specific.result
share/mysql/test/suite/engines/funcs/r/tc_rename.result
share/mysql/test/suite/engines/funcs/r/tc_rename_across_database.result
share/mysql/test/suite/engines/funcs/r/tc_rename_error.result
share/mysql/test/suite/engines/funcs/r/tc_structure_comment.result
share/mysql/test/suite/engines/funcs/r/tc_structure_create_like.result
share/mysql/test/suite/engines/funcs/r/tc_structure_create_like_string.result
share/mysql/test/suite/engines/funcs/r/tc_structure_create_select.result
share/mysql/test/suite/engines/funcs/r/tc_structure_create_select_string.result
share/mysql/test/suite/engines/funcs/r/tc_structure_string_comment.result
share/mysql/test/suite/engines/funcs/r/tc_temporary_column.result
share/mysql/test/suite/engines/funcs/r/tc_temporary_column_length.result
share/mysql/test/suite/engines/funcs/r/time_function.result
share/mysql/test/suite/engines/funcs/r/tr_all_type_triggers.result
share/mysql/test/suite/engines/funcs/r/tr_delete.result
share/mysql/test/suite/engines/funcs/r/tr_delete_new_error.result
share/mysql/test/suite/engines/funcs/r/tr_insert.result
share/mysql/test/suite/engines/funcs/r/tr_insert_after_error.result
share/mysql/test/suite/engines/funcs/r/tr_insert_old_error.result
share/mysql/test/suite/engines/funcs/r/tr_update.result
share/mysql/test/suite/engines/funcs/r/tr_update_after_error.result
share/mysql/test/suite/engines/funcs/r/up_calendar_range.result
share/mysql/test/suite/engines/funcs/r/up_ignore.result
share/mysql/test/suite/engines/funcs/r/up_limit.result
share/mysql/test/suite/engines/funcs/r/up_multi_db_table.result
share/mysql/test/suite/engines/funcs/r/up_multi_table.result
share/mysql/test/suite/engines/funcs/r/up_nullcheck.result
share/mysql/test/suite/engines/funcs/r/up_number_range.result
share/mysql/test/suite/engines/funcs/r/up_string_range.result
share/mysql/test/suite/engines/funcs/t/ai_init_alter_table.test
share/mysql/test/suite/engines/funcs/t/ai_init_create_table.test
share/mysql/test/suite/engines/funcs/t/ai_init_insert.test
share/mysql/test/suite/engines/funcs/t/ai_init_insert_id.test
share/mysql/test/suite/engines/funcs/t/ai_overflow_error.test
share/mysql/test/suite/engines/funcs/t/ai_reset_by_truncate.test
share/mysql/test/suite/engines/funcs/t/ai_sql_auto_is_null.test
share/mysql/test/suite/engines/funcs/t/an_calendar.test
share/mysql/test/suite/engines/funcs/t/an_number.test
share/mysql/test/suite/engines/funcs/t/an_string.test
share/mysql/test/suite/engines/funcs/t/comment_column.test
share/mysql/test/suite/engines/funcs/t/comment_column2.test
share/mysql/test/suite/engines/funcs/t/comment_index.test
share/mysql/test/suite/engines/funcs/t/comment_table.test
share/mysql/test/suite/engines/funcs/t/crash_manycolumns_number.test
share/mysql/test/suite/engines/funcs/t/crash_manycolumns_string.test
share/mysql/test/suite/engines/funcs/t/crash_manyindexes_number.test
share/mysql/test/suite/engines/funcs/t/crash_manyindexes_string.test
share/mysql/test/suite/engines/funcs/t/crash_manytables_number.cnf
share/mysql/test/suite/engines/funcs/t/crash_manytables_number.test
share/mysql/test/suite/engines/funcs/t/crash_manytables_string.cnf
share/mysql/test/suite/engines/funcs/t/crash_manytables_string.test
share/mysql/test/suite/engines/funcs/t/data1.inc
share/mysql/test/suite/engines/funcs/t/data2.inc
share/mysql/test/suite/engines/funcs/t/date_function.test
share/mysql/test/suite/engines/funcs/t/datetime_function.test
share/mysql/test/suite/engines/funcs/t/db_alter_character_set.test
share/mysql/test/suite/engines/funcs/t/db_alter_character_set_collate.test
share/mysql/test/suite/engines/funcs/t/db_alter_collate_ascii.test
share/mysql/test/suite/engines/funcs/t/db_alter_collate_utf8.test
share/mysql/test/suite/engines/funcs/t/db_create_character_set.test
share/mysql/test/suite/engines/funcs/t/db_create_character_set_collate.test
share/mysql/test/suite/engines/funcs/t/db_create_drop.test
share/mysql/test/suite/engines/funcs/t/db_create_error.test
share/mysql/test/suite/engines/funcs/t/db_create_error_reserved.test
share/mysql/test/suite/engines/funcs/t/db_create_if_not_exists.test
share/mysql/test/suite/engines/funcs/t/db_drop_error.test
share/mysql/test/suite/engines/funcs/t/db_use_error.test
share/mysql/test/suite/engines/funcs/t/de_autoinc.test
share/mysql/test/suite/engines/funcs/t/de_calendar_range.test
share/mysql/test/suite/engines/funcs/t/de_ignore.test
share/mysql/test/suite/engines/funcs/t/de_limit.test
share/mysql/test/suite/engines/funcs/t/de_multi_db_table.test
share/mysql/test/suite/engines/funcs/t/de_multi_db_table_using.test
share/mysql/test/suite/engines/funcs/t/de_multi_table.test
share/mysql/test/suite/engines/funcs/t/de_multi_table_using.test
share/mysql/test/suite/engines/funcs/t/de_number_range.test
share/mysql/test/suite/engines/funcs/t/de_quick.test
share/mysql/test/suite/engines/funcs/t/de_string_range.test
share/mysql/test/suite/engines/funcs/t/de_truncate.test
share/mysql/test/suite/engines/funcs/t/de_truncate_autoinc.test
share/mysql/test/suite/engines/funcs/t/disabled.def
share/mysql/test/suite/engines/funcs/t/fu_aggregate_avg_number.test
share/mysql/test/suite/engines/funcs/t/fu_aggregate_count_number.test
share/mysql/test/suite/engines/funcs/t/fu_aggregate_max_number.test
share/mysql/test/suite/engines/funcs/t/fu_aggregate_max_subquery.test
share/mysql/test/suite/engines/funcs/t/fu_aggregate_min_number.test
share/mysql/test/suite/engines/funcs/t/fu_aggregate_sum_number.test
share/mysql/test/suite/engines/funcs/t/general_no_data.test
share/mysql/test/suite/engines/funcs/t/general_not_null.test
share/mysql/test/suite/engines/funcs/t/general_null.test
share/mysql/test/suite/engines/funcs/t/in_calendar_2_unique_constraints_duplicate_update.test
share/mysql/test/suite/engines/funcs/t/in_calendar_pk_constraint_duplicate_update.test
share/mysql/test/suite/engines/funcs/t/in_calendar_pk_constraint_error.test
share/mysql/test/suite/engines/funcs/t/in_calendar_pk_constraint_ignore.test
share/mysql/test/suite/engines/funcs/t/in_calendar_unique_constraint_duplicate_update.test
share/mysql/test/suite/engines/funcs/t/in_calendar_unique_constraint_error.test
share/mysql/test/suite/engines/funcs/t/in_calendar_unique_constraint_ignore.test
share/mysql/test/suite/engines/funcs/t/in_enum_null.test
share/mysql/test/suite/engines/funcs/t/in_enum_null_boundary_error.test
share/mysql/test/suite/engines/funcs/t/in_enum_null_large_error.test
share/mysql/test/suite/engines/funcs/t/in_insert_select.test
share/mysql/test/suite/engines/funcs/t/in_insert_select_autoinc.test
share/mysql/test/suite/engines/funcs/t/in_insert_select_unique_violation.test
share/mysql/test/suite/engines/funcs/t/in_lob_boundary_error.test
share/mysql/test/suite/engines/funcs/t/in_multicolumn_calendar_pk_constraint_duplicate_update.test
share/mysql/test/suite/engines/funcs/t/in_multicolumn_calendar_pk_constraint_error.test
share/mysql/test/suite/engines/funcs/t/in_multicolumn_calendar_pk_constraint_ignore.test
share/mysql/test/suite/engines/funcs/t/in_multicolumn_calendar_unique_constraint_duplicate_update.test
share/mysql/test/suite/engines/funcs/t/in_multicolumn_calendar_unique_constraint_error.test
share/mysql/test/suite/engines/funcs/t/in_multicolumn_calendar_unique_constraint_ignore.test
share/mysql/test/suite/engines/funcs/t/in_multicolumn_number_pk_constraint_duplicate_update.test
share/mysql/test/suite/engines/funcs/t/in_multicolumn_number_pk_constraint_error.test
share/mysql/test/suite/engines/funcs/t/in_multicolumn_number_pk_constraint_ignore.test
share/mysql/test/suite/engines/funcs/t/in_multicolumn_number_unique_constraint_duplicate_update.test
share/mysql/test/suite/engines/funcs/t/in_multicolumn_number_unique_constraint_error.test
share/mysql/test/suite/engines/funcs/t/in_multicolumn_number_unique_constraint_ignore.test
share/mysql/test/suite/engines/funcs/t/in_multicolumn_string_pk_constraint_duplicate_update.test
share/mysql/test/suite/engines/funcs/t/in_multicolumn_string_pk_constraint_error.test
share/mysql/test/suite/engines/funcs/t/in_multicolumn_string_pk_constraint_ignore.test
share/mysql/test/suite/engines/funcs/t/in_multicolumn_string_unique_constraint_duplicate_update.test
share/mysql/test/suite/engines/funcs/t/in_multicolumn_string_unique_constraint_error.test
share/mysql/test/suite/engines/funcs/t/in_multicolumn_string_unique_constraint_ignore.test
share/mysql/test/suite/engines/funcs/t/in_number_2_unique_constraints_duplicate_update.test
share/mysql/test/suite/engines/funcs/t/in_number_boundary_error.test
share/mysql/test/suite/engines/funcs/t/in_number_decimal_boundary_error.test
share/mysql/test/suite/engines/funcs/t/in_number_length.test
share/mysql/test/suite/engines/funcs/t/in_number_null.test
share/mysql/test/suite/engines/funcs/t/in_number_pk_constraint_duplicate_update.test
share/mysql/test/suite/engines/funcs/t/in_number_pk_constraint_error.test
share/mysql/test/suite/engines/funcs/t/in_number_pk_constraint_ignore.test
share/mysql/test/suite/engines/funcs/t/in_number_unique_constraint_duplicate_update.test
share/mysql/test/suite/engines/funcs/t/in_number_unique_constraint_error.test
share/mysql/test/suite/engines/funcs/t/in_number_unique_constraint_ignore.test
share/mysql/test/suite/engines/funcs/t/in_set_null.test
share/mysql/test/suite/engines/funcs/t/in_set_null_boundary_error.test
share/mysql/test/suite/engines/funcs/t/in_set_null_large.test
share/mysql/test/suite/engines/funcs/t/in_string_2_unique_constraints_duplicate_update.test
share/mysql/test/suite/engines/funcs/t/in_string_boundary_error.test
share/mysql/test/suite/engines/funcs/t/in_string_not_null.test
share/mysql/test/suite/engines/funcs/t/in_string_null.test
share/mysql/test/suite/engines/funcs/t/in_string_pk_constraint_duplicate_update.test
share/mysql/test/suite/engines/funcs/t/in_string_pk_constraint_error.test
share/mysql/test/suite/engines/funcs/t/in_string_pk_constraint_ignore.test
share/mysql/test/suite/engines/funcs/t/in_string_set_enum_fail.test
share/mysql/test/suite/engines/funcs/t/in_string_unique_constraint_duplicate_update.test
share/mysql/test/suite/engines/funcs/t/in_string_unique_constraint_error.test
share/mysql/test/suite/engines/funcs/t/in_string_unique_constraint_ignore.test
share/mysql/test/suite/engines/funcs/t/ix_drop.test
share/mysql/test/suite/engines/funcs/t/ix_drop_error.test
share/mysql/test/suite/engines/funcs/t/ix_index_decimals.test
share/mysql/test/suite/engines/funcs/t/ix_index_lob.test
share/mysql/test/suite/engines/funcs/t/ix_index_non_string.test
share/mysql/test/suite/engines/funcs/t/ix_index_string.test
share/mysql/test/suite/engines/funcs/t/ix_index_string_length.test
share/mysql/test/suite/engines/funcs/t/ix_unique_decimals.test
share/mysql/test/suite/engines/funcs/t/ix_unique_lob.test
share/mysql/test/suite/engines/funcs/t/ix_unique_non_string.test
share/mysql/test/suite/engines/funcs/t/ix_unique_string.test
share/mysql/test/suite/engines/funcs/t/ix_unique_string_length.test
share/mysql/test/suite/engines/funcs/t/ix_using_order.test
share/mysql/test/suite/engines/funcs/t/jp_comment_column.test
share/mysql/test/suite/engines/funcs/t/jp_comment_index.test
share/mysql/test/suite/engines/funcs/t/jp_comment_older_compatibility1.test
share/mysql/test/suite/engines/funcs/t/jp_comment_table.test
share/mysql/test/suite/engines/funcs/t/ld_all_number_string_calendar_types.test
share/mysql/test/suite/engines/funcs/t/ld_bit.test
share/mysql/test/suite/engines/funcs/t/ld_enum_set.test
share/mysql/test/suite/engines/funcs/t/ld_less_columns.test
share/mysql/test/suite/engines/funcs/t/ld_more_columns_truncated.test
share/mysql/test/suite/engines/funcs/t/ld_null.test
share/mysql/test/suite/engines/funcs/t/ld_quote.test
share/mysql/test/suite/engines/funcs/t/ld_simple.test
share/mysql/test/suite/engines/funcs/t/ld_starting.test
share/mysql/test/suite/engines/funcs/t/ld_unique_error1.test
share/mysql/test/suite/engines/funcs/t/ld_unique_error1_local.test
share/mysql/test/suite/engines/funcs/t/ld_unique_error2.test
share/mysql/test/suite/engines/funcs/t/ld_unique_error2_local.test
share/mysql/test/suite/engines/funcs/t/ld_unique_error3.test
share/mysql/test/suite/engines/funcs/t/ld_unique_error3_local.test
share/mysql/test/suite/engines/funcs/t/load_bit.inc
share/mysql/test/suite/engines/funcs/t/load_enum_set.inc
share/mysql/test/suite/engines/funcs/t/load_less_columns.inc
share/mysql/test/suite/engines/funcs/t/load_more_columns.inc
share/mysql/test/suite/engines/funcs/t/load_null.inc
share/mysql/test/suite/engines/funcs/t/load_null2.inc
share/mysql/test/suite/engines/funcs/t/load_quote.inc
share/mysql/test/suite/engines/funcs/t/load_simple.inc
share/mysql/test/suite/engines/funcs/t/load_starting.inc
share/mysql/test/suite/engines/funcs/t/load_unique_error1.inc
share/mysql/test/suite/engines/funcs/t/load_unique_error2.inc
share/mysql/test/suite/engines/funcs/t/load_unique_error3.inc
share/mysql/test/suite/engines/funcs/t/ps_number_length.test
share/mysql/test/suite/engines/funcs/t/ps_number_null.test
share/mysql/test/suite/engines/funcs/t/ps_string_not_null.test
share/mysql/test/suite/engines/funcs/t/ps_string_null.test
share/mysql/test/suite/engines/funcs/t/re_number_range.test
share/mysql/test/suite/engines/funcs/t/re_number_range_set.test
share/mysql/test/suite/engines/funcs/t/re_number_select.test
share/mysql/test/suite/engines/funcs/t/re_string_range.test
share/mysql/test/suite/engines/funcs/t/re_string_range_set.test
share/mysql/test/suite/engines/funcs/t/rpl000010-slave.opt
share/mysql/test/suite/engines/funcs/t/rpl000010.test
share/mysql/test/suite/engines/funcs/t/rpl000011.test
share/mysql/test/suite/engines/funcs/t/rpl000013.test
share/mysql/test/suite/engines/funcs/t/rpl000017-slave.opt
share/mysql/test/suite/engines/funcs/t/rpl000017.test
share/mysql/test/suite/engines/funcs/t/rpl_000015.test
share/mysql/test/suite/engines/funcs/t/rpl_LD_INFILE.test
share/mysql/test/suite/engines/funcs/t/rpl_REDIRECT.test
share/mysql/test/suite/engines/funcs/t/rpl_alter.test
share/mysql/test/suite/engines/funcs/t/rpl_alter_db.test
share/mysql/test/suite/engines/funcs/t/rpl_bit.test
share/mysql/test/suite/engines/funcs/t/rpl_bit_npk.test
share/mysql/test/suite/engines/funcs/t/rpl_change_master.test
share/mysql/test/suite/engines/funcs/t/rpl_create_database-master.opt
share/mysql/test/suite/engines/funcs/t/rpl_create_database-slave.opt
share/mysql/test/suite/engines/funcs/t/rpl_create_database.test
share/mysql/test/suite/engines/funcs/t/rpl_do_grant.test
share/mysql/test/suite/engines/funcs/t/rpl_drop.test
share/mysql/test/suite/engines/funcs/t/rpl_drop_db.test
share/mysql/test/suite/engines/funcs/t/rpl_dual_pos_advance-master.opt
share/mysql/test/suite/engines/funcs/t/rpl_dual_pos_advance.test
share/mysql/test/suite/engines/funcs/t/rpl_empty_master_crash-master.opt
share/mysql/test/suite/engines/funcs/t/rpl_empty_master_crash.test
share/mysql/test/suite/engines/funcs/t/rpl_err_ignoredtable-slave.opt
share/mysql/test/suite/engines/funcs/t/rpl_err_ignoredtable.test
share/mysql/test/suite/engines/funcs/t/rpl_flushlog_loop.test
share/mysql/test/suite/engines/funcs/t/rpl_free_items-slave.opt
share/mysql/test/suite/engines/funcs/t/rpl_free_items.test
share/mysql/test/suite/engines/funcs/t/rpl_get_lock.test
share/mysql/test/suite/engines/funcs/t/rpl_ignore_grant-slave.opt
share/mysql/test/suite/engines/funcs/t/rpl_ignore_grant.test
share/mysql/test/suite/engines/funcs/t/rpl_ignore_revoke-slave.opt
share/mysql/test/suite/engines/funcs/t/rpl_ignore_revoke.test
share/mysql/test/suite/engines/funcs/t/rpl_ignore_table_update-slave.opt
share/mysql/test/suite/engines/funcs/t/rpl_ignore_table_update.test
share/mysql/test/suite/engines/funcs/t/rpl_init_slave-slave.opt
share/mysql/test/suite/engines/funcs/t/rpl_init_slave.test
share/mysql/test/suite/engines/funcs/t/rpl_insert.test
share/mysql/test/suite/engines/funcs/t/rpl_insert_select.test
share/mysql/test/suite/engines/funcs/t/rpl_loaddata2.test
share/mysql/test/suite/engines/funcs/t/rpl_loaddata_m-master.opt
share/mysql/test/suite/engines/funcs/t/rpl_loaddata_m.test
share/mysql/test/suite/engines/funcs/t/rpl_loaddata_s-slave.opt
share/mysql/test/suite/engines/funcs/t/rpl_loaddata_s.test
share/mysql/test/suite/engines/funcs/t/rpl_loaddatalocal.test
share/mysql/test/suite/engines/funcs/t/rpl_loadfile.test
share/mysql/test/suite/engines/funcs/t/rpl_log_pos.test
share/mysql/test/suite/engines/funcs/t/rpl_many_optimize.test
share/mysql/test/suite/engines/funcs/t/rpl_master_pos_wait.test
share/mysql/test/suite/engines/funcs/t/rpl_misc_functions.test
share/mysql/test/suite/engines/funcs/t/rpl_multi_delete-slave.opt
share/mysql/test/suite/engines/funcs/t/rpl_multi_delete.test
share/mysql/test/suite/engines/funcs/t/rpl_multi_delete2-slave.opt
share/mysql/test/suite/engines/funcs/t/rpl_multi_delete2.test
share/mysql/test/suite/engines/funcs/t/rpl_multi_update4-slave.opt
share/mysql/test/suite/engines/funcs/t/rpl_multi_update4.test
share/mysql/test/suite/engines/funcs/t/rpl_ps.test
share/mysql/test/suite/engines/funcs/t/rpl_rbr_to_sbr.test
share/mysql/test/suite/engines/funcs/t/rpl_relayspace-slave.opt
share/mysql/test/suite/engines/funcs/t/rpl_relayspace.test
share/mysql/test/suite/engines/funcs/t/rpl_replicate_ignore_db-slave.opt
share/mysql/test/suite/engines/funcs/t/rpl_replicate_ignore_db.test
share/mysql/test/suite/engines/funcs/t/rpl_row_NOW.test
share/mysql/test/suite/engines/funcs/t/rpl_row_USER.test
share/mysql/test/suite/engines/funcs/t/rpl_row_drop.test
share/mysql/test/suite/engines/funcs/t/rpl_row_func001.test
share/mysql/test/suite/engines/funcs/t/rpl_row_inexist_tbl-slave.opt
share/mysql/test/suite/engines/funcs/t/rpl_row_inexist_tbl.test
share/mysql/test/suite/engines/funcs/t/rpl_row_max_relay_size.test
share/mysql/test/suite/engines/funcs/t/rpl_row_reset_slave.test
share/mysql/test/suite/engines/funcs/t/rpl_row_sp001.test
share/mysql/test/suite/engines/funcs/t/rpl_row_sp005.test
share/mysql/test/suite/engines/funcs/t/rpl_row_sp008.test
share/mysql/test/suite/engines/funcs/t/rpl_row_sp009.test
share/mysql/test/suite/engines/funcs/t/rpl_row_sp010.test
share/mysql/test/suite/engines/funcs/t/rpl_row_sp011.test
share/mysql/test/suite/engines/funcs/t/rpl_row_sp012.test
share/mysql/test/suite/engines/funcs/t/rpl_row_stop_middle.test
share/mysql/test/suite/engines/funcs/t/rpl_row_trig001.test
share/mysql/test/suite/engines/funcs/t/rpl_row_trig002.test
share/mysql/test/suite/engines/funcs/t/rpl_row_trig003.test
share/mysql/test/suite/engines/funcs/t/rpl_row_until.test
share/mysql/test/suite/engines/funcs/t/rpl_row_view01.test
share/mysql/test/suite/engines/funcs/t/rpl_server_id1.test
share/mysql/test/suite/engines/funcs/t/rpl_server_id2-slave.opt
share/mysql/test/suite/engines/funcs/t/rpl_server_id2.test
share/mysql/test/suite/engines/funcs/t/rpl_session_var.test
share/mysql/test/suite/engines/funcs/t/rpl_sf.test
share/mysql/test/suite/engines/funcs/t/rpl_skip_error-slave.opt
share/mysql/test/suite/engines/funcs/t/rpl_skip_error.test
share/mysql/test/suite/engines/funcs/t/rpl_slave_status.test
share/mysql/test/suite/engines/funcs/t/rpl_sp-master.opt
share/mysql/test/suite/engines/funcs/t/rpl_sp-slave.opt
share/mysql/test/suite/engines/funcs/t/rpl_sp.test
share/mysql/test/suite/engines/funcs/t/rpl_sp004.test
share/mysql/test/suite/engines/funcs/t/rpl_sp_effects-master.opt
share/mysql/test/suite/engines/funcs/t/rpl_sp_effects-slave.opt
share/mysql/test/suite/engines/funcs/t/rpl_sp_effects.test
share/mysql/test/suite/engines/funcs/t/rpl_start_stop_slave.test
share/mysql/test/suite/engines/funcs/t/rpl_stm_max_relay_size.test
share/mysql/test/suite/engines/funcs/t/rpl_stm_mystery22.test
share/mysql/test/suite/engines/funcs/t/rpl_stm_no_op.test
share/mysql/test/suite/engines/funcs/t/rpl_stm_reset_slave.test
share/mysql/test/suite/engines/funcs/t/rpl_switch_stm_row_mixed.test
share/mysql/test/suite/engines/funcs/t/rpl_temp_table.test
share/mysql/test/suite/engines/funcs/t/rpl_temporary.test
share/mysql/test/suite/engines/funcs/t/rpl_trigger.test
share/mysql/test/suite/engines/funcs/t/rpl_trunc_temp.test
share/mysql/test/suite/engines/funcs/t/rpl_user_variables.test
share/mysql/test/suite/engines/funcs/t/rpl_variables-master.opt
share/mysql/test/suite/engines/funcs/t/rpl_variables.test
share/mysql/test/suite/engines/funcs/t/rpl_view-slave.opt
share/mysql/test/suite/engines/funcs/t/rpl_view.test
share/mysql/test/suite/engines/funcs/t/se_join_cross.test
share/mysql/test/suite/engines/funcs/t/se_join_default.test
share/mysql/test/suite/engines/funcs/t/se_join_inner.test
share/mysql/test/suite/engines/funcs/t/se_join_left.test
share/mysql/test/suite/engines/funcs/t/se_join_left_outer.test
share/mysql/test/suite/engines/funcs/t/se_join_natural_left.test
share/mysql/test/suite/engines/funcs/t/se_join_natural_left_outer.test
share/mysql/test/suite/engines/funcs/t/se_join_natural_right.test
share/mysql/test/suite/engines/funcs/t/se_join_natural_right_outer.test
share/mysql/test/suite/engines/funcs/t/se_join_right.test
share/mysql/test/suite/engines/funcs/t/se_join_right_outer.test
share/mysql/test/suite/engines/funcs/t/se_join_straight.test
share/mysql/test/suite/engines/funcs/t/se_rowid.test
share/mysql/test/suite/engines/funcs/t/se_string_distinct.test
share/mysql/test/suite/engines/funcs/t/se_string_from.test
share/mysql/test/suite/engines/funcs/t/se_string_groupby.test
share/mysql/test/suite/engines/funcs/t/se_string_having.test
share/mysql/test/suite/engines/funcs/t/se_string_limit.test
share/mysql/test/suite/engines/funcs/t/se_string_orderby.test
share/mysql/test/suite/engines/funcs/t/se_string_union.test
share/mysql/test/suite/engines/funcs/t/se_string_where.test
share/mysql/test/suite/engines/funcs/t/se_string_where_and.test
share/mysql/test/suite/engines/funcs/t/se_string_where_or.test
share/mysql/test/suite/engines/funcs/t/sf_alter.test
share/mysql/test/suite/engines/funcs/t/sf_cursor.test
share/mysql/test/suite/engines/funcs/t/sf_simple1.test
share/mysql/test/suite/engines/funcs/t/sp_alter.test
share/mysql/test/suite/engines/funcs/t/sp_cursor.test
share/mysql/test/suite/engines/funcs/t/sp_simple1.test
share/mysql/test/suite/engines/funcs/t/sq_all.test
share/mysql/test/suite/engines/funcs/t/sq_any.test
share/mysql/test/suite/engines/funcs/t/sq_corr.test
share/mysql/test/suite/engines/funcs/t/sq_error.test
share/mysql/test/suite/engines/funcs/t/sq_exists.test
share/mysql/test/suite/engines/funcs/t/sq_from.test
share/mysql/test/suite/engines/funcs/t/sq_in.test
share/mysql/test/suite/engines/funcs/t/sq_row.test
share/mysql/test/suite/engines/funcs/t/sq_scalar.test
share/mysql/test/suite/engines/funcs/t/sq_some.test
share/mysql/test/suite/engines/funcs/t/ta_2part_column_to_pk.test
share/mysql/test/suite/engines/funcs/t/ta_2part_diff_string_to_pk.test
share/mysql/test/suite/engines/funcs/t/ta_2part_diff_to_pk.test
share/mysql/test/suite/engines/funcs/t/ta_2part_string_to_pk.test
share/mysql/test/suite/engines/funcs/t/ta_3part_column_to_pk.test
share/mysql/test/suite/engines/funcs/t/ta_3part_string_to_pk.test
share/mysql/test/suite/engines/funcs/t/ta_add_column.test
share/mysql/test/suite/engines/funcs/t/ta_add_column2.test
share/mysql/test/suite/engines/funcs/t/ta_add_column_first.test
share/mysql/test/suite/engines/funcs/t/ta_add_column_first2.test
share/mysql/test/suite/engines/funcs/t/ta_add_column_middle.test
share/mysql/test/suite/engines/funcs/t/ta_add_column_middle2.test
share/mysql/test/suite/engines/funcs/t/ta_add_string.test
share/mysql/test/suite/engines/funcs/t/ta_add_string2.test
share/mysql/test/suite/engines/funcs/t/ta_add_string_first.test
share/mysql/test/suite/engines/funcs/t/ta_add_string_first2.test
share/mysql/test/suite/engines/funcs/t/ta_add_string_middle.test
share/mysql/test/suite/engines/funcs/t/ta_add_string_middle2.test
share/mysql/test/suite/engines/funcs/t/ta_add_string_unique_index.test
share/mysql/test/suite/engines/funcs/t/ta_add_unique_index.test
share/mysql/test/suite/engines/funcs/t/ta_column_from_unsigned.test
share/mysql/test/suite/engines/funcs/t/ta_column_from_zerofill.test
share/mysql/test/suite/engines/funcs/t/ta_column_to_index.test
share/mysql/test/suite/engines/funcs/t/ta_column_to_not_null.test
share/mysql/test/suite/engines/funcs/t/ta_column_to_null.test
share/mysql/test/suite/engines/funcs/t/ta_column_to_pk.test
share/mysql/test/suite/engines/funcs/t/ta_column_to_unsigned.test
share/mysql/test/suite/engines/funcs/t/ta_column_to_zerofill.test
share/mysql/test/suite/engines/funcs/t/ta_drop_column.test
share/mysql/test/suite/engines/funcs/t/ta_drop_index.test
share/mysql/test/suite/engines/funcs/t/ta_drop_pk_autoincrement.test
share/mysql/test/suite/engines/funcs/t/ta_drop_pk_number.test
share/mysql/test/suite/engines/funcs/t/ta_drop_pk_string.test
share/mysql/test/suite/engines/funcs/t/ta_drop_string_index.test
share/mysql/test/suite/engines/funcs/t/ta_orderby.test
share/mysql/test/suite/engines/funcs/t/ta_rename.test
share/mysql/test/suite/engines/funcs/t/ta_set_drop_default.test
share/mysql/test/suite/engines/funcs/t/ta_string_drop_column.test
share/mysql/test/suite/engines/funcs/t/ta_string_to_index.test
share/mysql/test/suite/engines/funcs/t/ta_string_to_not_null.test
share/mysql/test/suite/engines/funcs/t/ta_string_to_null.test
share/mysql/test/suite/engines/funcs/t/ta_string_to_pk.test
share/mysql/test/suite/engines/funcs/t/tc_column_autoincrement.test
share/mysql/test/suite/engines/funcs/t/tc_column_comment.test
share/mysql/test/suite/engines/funcs/t/tc_column_comment_string.test
share/mysql/test/suite/engines/funcs/t/tc_column_default_decimal.test
share/mysql/test/suite/engines/funcs/t/tc_column_default_number.test
share/mysql/test/suite/engines/funcs/t/tc_column_default_string.test
share/mysql/test/suite/engines/funcs/t/tc_column_enum.test
share/mysql/test/suite/engines/funcs/t/tc_column_enum_long.test
share/mysql/test/suite/engines/funcs/t/tc_column_key.test
share/mysql/test/suite/engines/funcs/t/tc_column_key_length.test
share/mysql/test/suite/engines/funcs/t/tc_column_length.test
share/mysql/test/suite/engines/funcs/t/tc_column_length_decimals.test
share/mysql/test/suite/engines/funcs/t/tc_column_length_zero.test
share/mysql/test/suite/engines/funcs/t/tc_column_not_null.test
share/mysql/test/suite/engines/funcs/t/tc_column_null.test
share/mysql/test/suite/engines/funcs/t/tc_column_primary_key_number.test
share/mysql/test/suite/engines/funcs/t/tc_column_primary_key_string.test
share/mysql/test/suite/engines/funcs/t/tc_column_serial.test
share/mysql/test/suite/engines/funcs/t/tc_column_set.test
share/mysql/test/suite/engines/funcs/t/tc_column_set_long.test
share/mysql/test/suite/engines/funcs/t/tc_column_unique_key.test
share/mysql/test/suite/engines/funcs/t/tc_column_unique_key_string.test
share/mysql/test/suite/engines/funcs/t/tc_column_unsigned.test
share/mysql/test/suite/engines/funcs/t/tc_column_zerofill.test
share/mysql/test/suite/engines/funcs/t/tc_drop_table.test
share/mysql/test/suite/engines/funcs/t/tc_multicolumn_different.test
share/mysql/test/suite/engines/funcs/t/tc_multicolumn_same.test
share/mysql/test/suite/engines/funcs/t/tc_multicolumn_same_string.test
share/mysql/test/suite/engines/funcs/t/tc_partition_analyze.test
share/mysql/test/suite/engines/funcs/t/tc_partition_change_from_range_to_hash_key.test
share/mysql/test/suite/engines/funcs/t/tc_partition_check.test
share/mysql/test/suite/engines/funcs/t/tc_partition_hash.test
share/mysql/test/suite/engines/funcs/t/tc_partition_hash_date_function.test
share/mysql/test/suite/engines/funcs/t/tc_partition_key.test
share/mysql/test/suite/engines/funcs/t/tc_partition_linear_key.test
share/mysql/test/suite/engines/funcs/t/tc_partition_list_directory.test
share/mysql/test/suite/engines/funcs/t/tc_partition_list_error.test
share/mysql/test/suite/engines/funcs/t/tc_partition_optimize.test
share/mysql/test/suite/engines/funcs/t/tc_partition_rebuild.test
share/mysql/test/suite/engines/funcs/t/tc_partition_remove.test
share/mysql/test/suite/engines/funcs/t/tc_partition_reorg_divide.test
share/mysql/test/suite/engines/funcs/t/tc_partition_reorg_hash_key.test
share/mysql/test/suite/engines/funcs/t/tc_partition_reorg_merge.test
share/mysql/test/suite/engines/funcs/t/tc_partition_repair.test
share/mysql/test/suite/engines/funcs/t/tc_partition_sub1.test
share/mysql/test/suite/engines/funcs/t/tc_partition_sub2.test
share/mysql/test/suite/engines/funcs/t/tc_partition_value.test
share/mysql/test/suite/engines/funcs/t/tc_partition_value_error.test
share/mysql/test/suite/engines/funcs/t/tc_partition_value_specific.test
share/mysql/test/suite/engines/funcs/t/tc_rename.test
share/mysql/test/suite/engines/funcs/t/tc_rename_across_database.test
share/mysql/test/suite/engines/funcs/t/tc_rename_error.test
share/mysql/test/suite/engines/funcs/t/tc_structure_comment.test
share/mysql/test/suite/engines/funcs/t/tc_structure_create_like.test
share/mysql/test/suite/engines/funcs/t/tc_structure_create_like_string.test
share/mysql/test/suite/engines/funcs/t/tc_structure_create_select.test
share/mysql/test/suite/engines/funcs/t/tc_structure_create_select_string.test
share/mysql/test/suite/engines/funcs/t/tc_structure_string_comment.test
share/mysql/test/suite/engines/funcs/t/tc_temporary_column.test
share/mysql/test/suite/engines/funcs/t/tc_temporary_column_length.test
share/mysql/test/suite/engines/funcs/t/time_function.test
share/mysql/test/suite/engines/funcs/t/tr_all_type_triggers.test
share/mysql/test/suite/engines/funcs/t/tr_delete.test
share/mysql/test/suite/engines/funcs/t/tr_delete_new_error.test
share/mysql/test/suite/engines/funcs/t/tr_insert.test
share/mysql/test/suite/engines/funcs/t/tr_insert_after_error.test
share/mysql/test/suite/engines/funcs/t/tr_insert_old_error.test
share/mysql/test/suite/engines/funcs/t/tr_update.test
share/mysql/test/suite/engines/funcs/t/tr_update_after_error.test
share/mysql/test/suite/engines/funcs/t/up_calendar_range.test
share/mysql/test/suite/engines/funcs/t/up_ignore.test
share/mysql/test/suite/engines/funcs/t/up_limit.test
share/mysql/test/suite/engines/funcs/t/up_multi_db_table.test
share/mysql/test/suite/engines/funcs/t/up_multi_table.test
share/mysql/test/suite/engines/funcs/t/up_nullcheck.test
share/mysql/test/suite/engines/funcs/t/up_number_range.test
share/mysql/test/suite/engines/funcs/t/up_string_range.test
share/mysql/test/suite/engines/funcs/t/wait_show_pattern.inc
share/mysql/test/suite/engines/funcs/t/wait_slave_status.inc
share/mysql/test/suite/engines/iuds/r/delete_decimal.result
share/mysql/test/suite/engines/iuds/r/delete_time.result
share/mysql/test/suite/engines/iuds/r/delete_year.result
share/mysql/test/suite/engines/iuds/r/insert_calendar.result
share/mysql/test/suite/engines/iuds/r/insert_decimal.result
share/mysql/test/suite/engines/iuds/r/insert_number.result
share/mysql/test/suite/engines/iuds/r/insert_time.result
share/mysql/test/suite/engines/iuds/r/insert_year.result
share/mysql/test/suite/engines/iuds/r/strings_charsets_update_delete.result
share/mysql/test/suite/engines/iuds/r/strings_update_delete.result
share/mysql/test/suite/engines/iuds/r/type_bit_iuds.result
share/mysql/test/suite/engines/iuds/r/update_decimal.result
share/mysql/test/suite/engines/iuds/r/update_delete_calendar.result
share/mysql/test/suite/engines/iuds/r/update_delete_number.result
share/mysql/test/suite/engines/iuds/r/update_time.result
share/mysql/test/suite/engines/iuds/r/update_year.result
share/mysql/test/suite/engines/iuds/t/delete_decimal.test
share/mysql/test/suite/engines/iuds/t/delete_time.test
share/mysql/test/suite/engines/iuds/t/delete_year.test
share/mysql/test/suite/engines/iuds/t/disabled.def
share/mysql/test/suite/engines/iuds/t/hindi.txt
share/mysql/test/suite/engines/iuds/t/insert_calendar.test
share/mysql/test/suite/engines/iuds/t/insert_decimal.test
share/mysql/test/suite/engines/iuds/t/insert_number.test
share/mysql/test/suite/engines/iuds/t/insert_time.test
share/mysql/test/suite/engines/iuds/t/insert_year.test
share/mysql/test/suite/engines/iuds/t/sample.txt
share/mysql/test/suite/engines/iuds/t/strings_charsets_update_delete.test
share/mysql/test/suite/engines/iuds/t/strings_update_delete.test
share/mysql/test/suite/engines/iuds/t/type_bit_iuds.test
share/mysql/test/suite/engines/iuds/t/update_decimal.test
share/mysql/test/suite/engines/iuds/t/update_delete_calendar.test
share/mysql/test/suite/engines/iuds/t/update_delete_number.test
share/mysql/test/suite/engines/iuds/t/update_time.test
share/mysql/test/suite/engines/iuds/t/update_year.test
share/mysql/test/suite/engines/rr_trx/check_consistency.sql
share/mysql/test/suite/engines/rr_trx/include/check_for_error_rollback.inc
share/mysql/test/suite/engines/rr_trx/include/check_for_error_rollback_skip.inc
share/mysql/test/suite/engines/rr_trx/include/check_repeatable_read_all_columns.inc
share/mysql/test/suite/engines/rr_trx/include/record_query_all_columns.inc
share/mysql/test/suite/engines/rr_trx/include/rr_init.test
share/mysql/test/suite/engines/rr_trx/init_innodb.txt
share/mysql/test/suite/engines/rr_trx/r/init_innodb.result
share/mysql/test/suite/engines/rr_trx/r/rr_c_count_not_zero.result
share/mysql/test/suite/engines/rr_trx/r/rr_c_stats.result
share/mysql/test/suite/engines/rr_trx/r/rr_i_40-44.result
share/mysql/test/suite/engines/rr_trx/r/rr_id_3.result
share/mysql/test/suite/engines/rr_trx/r/rr_id_900.result
share/mysql/test/suite/engines/rr_trx/r/rr_insert_select_2.result
share/mysql/test/suite/engines/rr_trx/r/rr_iud_rollback-multi-50.result
share/mysql/test/suite/engines/rr_trx/r/rr_replace_7-8.result
share/mysql/test/suite/engines/rr_trx/r/rr_s_select-uncommitted.result
share/mysql/test/suite/engines/rr_trx/r/rr_sc_select-limit-nolimit_4.result
share/mysql/test/suite/engines/rr_trx/r/rr_sc_select-same_2.result
share/mysql/test/suite/engines/rr_trx/r/rr_sc_sum_total.result
share/mysql/test/suite/engines/rr_trx/r/rr_u_10-19.result
share/mysql/test/suite/engines/rr_trx/r/rr_u_10-19_nolimit.result
share/mysql/test/suite/engines/rr_trx/r/rr_u_4.result
share/mysql/test/suite/engines/rr_trx/run.txt
share/mysql/test/suite/engines/rr_trx/run_stress_tx_rr.pl
share/mysql/test/suite/engines/rr_trx/t/init_innodb.test
share/mysql/test/suite/engines/rr_trx/t/rr_c_count_not_zero.test
share/mysql/test/suite/engines/rr_trx/t/rr_c_stats.test
share/mysql/test/suite/engines/rr_trx/t/rr_i_40-44.test
share/mysql/test/suite/engines/rr_trx/t/rr_id_3.test
share/mysql/test/suite/engines/rr_trx/t/rr_id_900.test
share/mysql/test/suite/engines/rr_trx/t/rr_insert_select_2.test
share/mysql/test/suite/engines/rr_trx/t/rr_iud_rollback-multi-50.test
share/mysql/test/suite/engines/rr_trx/t/rr_replace_7-8.test
share/mysql/test/suite/engines/rr_trx/t/rr_s_select-uncommitted.test
share/mysql/test/suite/engines/rr_trx/t/rr_sc_select-limit-nolimit_4.test
share/mysql/test/suite/engines/rr_trx/t/rr_sc_select-same_2.test
share/mysql/test/suite/engines/rr_trx/t/rr_sc_sum_total.test
share/mysql/test/suite/engines/rr_trx/t/rr_u_10-19.test
share/mysql/test/suite/engines/rr_trx/t/rr_u_10-19_nolimit.test
share/mysql/test/suite/engines/rr_trx/t/rr_u_4.test
share/mysql/test/suite/federated/disabled.def
share/mysql/test/suite/federated/federated.result
share/mysql/test/suite/federated/federated.test
share/mysql/test/suite/federated/federated_archive.result
share/mysql/test/suite/federated/federated_archive.test
share/mysql/test/suite/federated/federated_bug_13118.result
share/mysql/test/suite/federated/federated_bug_13118.test
share/mysql/test/suite/federated/federated_bug_25714.result
share/mysql/test/suite/federated/federated_bug_25714.test
share/mysql/test/suite/federated/federated_bug_35333.result
share/mysql/test/suite/federated/federated_bug_35333.test
share/mysql/test/suite/federated/federated_debug-master.opt
share/mysql/test/suite/federated/federated_debug.result
share/mysql/test/suite/federated/federated_debug.test
share/mysql/test/suite/federated/federated_innodb-slave.opt
share/mysql/test/suite/federated/federated_innodb.result
share/mysql/test/suite/federated/federated_innodb.test
share/mysql/test/suite/federated/federated_plugin-master.opt
share/mysql/test/suite/federated/federated_plugin.result
share/mysql/test/suite/federated/federated_plugin.test
share/mysql/test/suite/federated/federated_server.result
share/mysql/test/suite/federated/federated_server.test
share/mysql/test/suite/federated/federated_transactions-slave.opt
share/mysql/test/suite/federated/federated_transactions.result
share/mysql/test/suite/federated/federated_transactions.test
share/mysql/test/suite/federated/include/federated.inc
share/mysql/test/suite/federated/include/federated_cleanup.inc
share/mysql/test/suite/federated/include/have_federated_db.inc
share/mysql/test/suite/federated/my.cnf
share/mysql/test/suite/funcs_1/README.txt
share/mysql/test/suite/funcs_1/bitdata/bitdata_master.test
share/mysql/test/suite/funcs_1/cursors/cursors_master.test
share/mysql/test/suite/funcs_1/datadict/basics_mixed1.inc
share/mysql/test/suite/funcs_1/datadict/basics_mixed2.inc
share/mysql/test/suite/funcs_1/datadict/basics_mixed3.inc
share/mysql/test/suite/funcs_1/datadict/columns.inc
share/mysql/test/suite/funcs_1/datadict/datadict.pre
share/mysql/test/suite/funcs_1/datadict/datadict_bug_12777.inc
share/mysql/test/suite/funcs_1/datadict/datadict_load.inc
share/mysql/test/suite/funcs_1/datadict/datadict_priv.inc
share/mysql/test/suite/funcs_1/datadict/is_key_column_usage.inc
share/mysql/test/suite/funcs_1/datadict/is_routines.inc
share/mysql/test/suite/funcs_1/datadict/is_schemata.inc
share/mysql/test/suite/funcs_1/datadict/is_table_query.inc
share/mysql/test/suite/funcs_1/datadict/is_tables.inc
share/mysql/test/suite/funcs_1/datadict/is_triggers.inc
share/mysql/test/suite/funcs_1/datadict/is_views.inc
share/mysql/test/suite/funcs_1/datadict/processlist_priv.inc
share/mysql/test/suite/funcs_1/datadict/processlist_val.inc
share/mysql/test/suite/funcs_1/datadict/statistics.inc
share/mysql/test/suite/funcs_1/datadict/table_constraints.inc
share/mysql/test/suite/funcs_1/datadict/tables.inc
share/mysql/test/suite/funcs_1/datadict/tables1.inc
share/mysql/test/suite/funcs_1/datadict/tables2.inc
share/mysql/test/suite/funcs_1/include/bug28309_skip.inc
share/mysql/test/suite/funcs_1/include/cleanup.inc
share/mysql/test/suite/funcs_1/include/innodb_tb1.inc
share/mysql/test/suite/funcs_1/include/innodb_tb2.inc
share/mysql/test/suite/funcs_1/include/innodb_tb3.inc
share/mysql/test/suite/funcs_1/include/innodb_tb4.inc
share/mysql/test/suite/funcs_1/include/memory_tb1.inc
share/mysql/test/suite/funcs_1/include/memory_tb2.inc
share/mysql/test/suite/funcs_1/include/memory_tb3.inc
share/mysql/test/suite/funcs_1/include/memory_tb4.inc
share/mysql/test/suite/funcs_1/include/myisam_tb1.inc
share/mysql/test/suite/funcs_1/include/myisam_tb2.inc
share/mysql/test/suite/funcs_1/include/myisam_tb3.inc
share/mysql/test/suite/funcs_1/include/myisam_tb4.inc
share/mysql/test/suite/funcs_1/include/ndb_tb1.inc
share/mysql/test/suite/funcs_1/include/ndb_tb2.inc
share/mysql/test/suite/funcs_1/include/ndb_tb3.inc
share/mysql/test/suite/funcs_1/include/ndb_tb4.inc
share/mysql/test/suite/funcs_1/include/show_connection.inc
share/mysql/test/suite/funcs_1/include/sp_tb.inc
share/mysql/test/suite/funcs_1/include/tb3.inc
share/mysql/test/suite/funcs_1/lib/DataGen_local.pl
share/mysql/test/suite/funcs_1/lib/DataGen_modify.pl
share/mysql/test/suite/funcs_1/r/charset_collation.result
share/mysql/test/suite/funcs_1/r/innodb_bitdata.result
share/mysql/test/suite/funcs_1/r/innodb_cursors.result
share/mysql/test/suite/funcs_1/r/innodb_func_view.result
share/mysql/test/suite/funcs_1/r/innodb_storedproc_02.result
share/mysql/test/suite/funcs_1/r/innodb_storedproc_03.result
share/mysql/test/suite/funcs_1/r/innodb_storedproc_06.result
share/mysql/test/suite/funcs_1/r/innodb_storedproc_07.result
share/mysql/test/suite/funcs_1/r/innodb_storedproc_08.result
share/mysql/test/suite/funcs_1/r/innodb_storedproc_10.result
share/mysql/test/suite/funcs_1/r/innodb_trig_0102.result
share/mysql/test/suite/funcs_1/r/innodb_trig_03.result
share/mysql/test/suite/funcs_1/r/innodb_trig_03e.result
share/mysql/test/suite/funcs_1/r/innodb_trig_0407.result
share/mysql/test/suite/funcs_1/r/innodb_trig_08.result
share/mysql/test/suite/funcs_1/r/innodb_trig_09.result
share/mysql/test/suite/funcs_1/r/innodb_trig_1011ext.result
share/mysql/test/suite/funcs_1/r/innodb_trig_frkey.result
share/mysql/test/suite/funcs_1/r/innodb_views.result
share/mysql/test/suite/funcs_1/r/is_basics_mixed.result
share/mysql/test/suite/funcs_1/r/is_character_sets.result
share/mysql/test/suite/funcs_1/r/is_cml_innodb.result
share/mysql/test/suite/funcs_1/r/is_cml_memory.result
share/mysql/test/suite/funcs_1/r/is_cml_myisam.result
share/mysql/test/suite/funcs_1/r/is_coll_char_set_appl.result
share/mysql/test/suite/funcs_1/r/is_collations.result
share/mysql/test/suite/funcs_1/r/is_column_privileges.result
share/mysql/test/suite/funcs_1/r/is_column_privileges_is_mysql_test.result
share/mysql/test/suite/funcs_1/r/is_columns.result
share/mysql/test/suite/funcs_1/r/is_columns_innodb.result
share/mysql/test/suite/funcs_1/r/is_columns_is.result
share/mysql/test/suite/funcs_1/r/is_columns_is_embedded.result
share/mysql/test/suite/funcs_1/r/is_columns_memory.result
share/mysql/test/suite/funcs_1/r/is_columns_myisam.result
share/mysql/test/suite/funcs_1/r/is_columns_myisam_embedded.result
share/mysql/test/suite/funcs_1/r/is_columns_mysql.result
share/mysql/test/suite/funcs_1/r/is_columns_mysql_embedded.result
share/mysql/test/suite/funcs_1/r/is_engines.result
share/mysql/test/suite/funcs_1/r/is_engines_archive.result
share/mysql/test/suite/funcs_1/r/is_engines_blackhole.result
share/mysql/test/suite/funcs_1/r/is_engines_csv.result
share/mysql/test/suite/funcs_1/r/is_engines_federated.result
share/mysql/test/suite/funcs_1/r/is_engines_innodb.result
share/mysql/test/suite/funcs_1/r/is_engines_memory.result
share/mysql/test/suite/funcs_1/r/is_engines_merge.result
share/mysql/test/suite/funcs_1/r/is_engines_myisam.result
share/mysql/test/suite/funcs_1/r/is_events.result
share/mysql/test/suite/funcs_1/r/is_key_column_usage.result
share/mysql/test/suite/funcs_1/r/is_key_column_usage_embedded.result
share/mysql/test/suite/funcs_1/r/is_routines.result
share/mysql/test/suite/funcs_1/r/is_routines_embedded.result
share/mysql/test/suite/funcs_1/r/is_schema_privileges.result
share/mysql/test/suite/funcs_1/r/is_schema_privileges_is_mysql_test.result
share/mysql/test/suite/funcs_1/r/is_schemata.result
share/mysql/test/suite/funcs_1/r/is_schemata_embedded.result
share/mysql/test/suite/funcs_1/r/is_schemata_is_mysql_test.result
share/mysql/test/suite/funcs_1/r/is_statistics.result
share/mysql/test/suite/funcs_1/r/is_statistics_is.result
share/mysql/test/suite/funcs_1/r/is_statistics_mysql.result
share/mysql/test/suite/funcs_1/r/is_statistics_mysql_embedded.result
share/mysql/test/suite/funcs_1/r/is_table_constraints.result
share/mysql/test/suite/funcs_1/r/is_table_constraints_is.result
share/mysql/test/suite/funcs_1/r/is_table_constraints_mysql.result
share/mysql/test/suite/funcs_1/r/is_table_constraints_mysql_embedded.result
share/mysql/test/suite/funcs_1/r/is_table_privileges.result
share/mysql/test/suite/funcs_1/r/is_tables.result
share/mysql/test/suite/funcs_1/r/is_tables_embedded.result
share/mysql/test/suite/funcs_1/r/is_tables_innodb.result
share/mysql/test/suite/funcs_1/r/is_tables_is.result
share/mysql/test/suite/funcs_1/r/is_tables_memory.result
share/mysql/test/suite/funcs_1/r/is_tables_myisam.result
share/mysql/test/suite/funcs_1/r/is_tables_myisam_embedded.result
share/mysql/test/suite/funcs_1/r/is_tables_mysql.result
share/mysql/test/suite/funcs_1/r/is_tables_mysql_embedded.result
share/mysql/test/suite/funcs_1/r/is_triggers.result
share/mysql/test/suite/funcs_1/r/is_triggers_embedded.result
share/mysql/test/suite/funcs_1/r/is_user_privileges.result
share/mysql/test/suite/funcs_1/r/is_views.result
share/mysql/test/suite/funcs_1/r/is_views_embedded.result
share/mysql/test/suite/funcs_1/r/memory_bitdata.result
share/mysql/test/suite/funcs_1/r/memory_cursors.result
share/mysql/test/suite/funcs_1/r/memory_func_view.result
share/mysql/test/suite/funcs_1/r/memory_storedproc_02.result
share/mysql/test/suite/funcs_1/r/memory_storedproc_03.result
share/mysql/test/suite/funcs_1/r/memory_storedproc_06.result
share/mysql/test/suite/funcs_1/r/memory_storedproc_07.result
share/mysql/test/suite/funcs_1/r/memory_storedproc_08.result
share/mysql/test/suite/funcs_1/r/memory_storedproc_10.result
share/mysql/test/suite/funcs_1/r/memory_trig_0102.result
share/mysql/test/suite/funcs_1/r/memory_trig_03.result
share/mysql/test/suite/funcs_1/r/memory_trig_03e.result
share/mysql/test/suite/funcs_1/r/memory_trig_0407.result
share/mysql/test/suite/funcs_1/r/memory_trig_08.result
share/mysql/test/suite/funcs_1/r/memory_trig_09.result
share/mysql/test/suite/funcs_1/r/memory_trig_1011ext.result
share/mysql/test/suite/funcs_1/r/memory_views.result
share/mysql/test/suite/funcs_1/r/myisam_bitdata.result
share/mysql/test/suite/funcs_1/r/myisam_cursors.result
share/mysql/test/suite/funcs_1/r/myisam_func_view.result
share/mysql/test/suite/funcs_1/r/myisam_storedproc_02.result
share/mysql/test/suite/funcs_1/r/myisam_storedproc_03.result
share/mysql/test/suite/funcs_1/r/myisam_storedproc_06.result
share/mysql/test/suite/funcs_1/r/myisam_storedproc_07.result
share/mysql/test/suite/funcs_1/r/myisam_storedproc_08.result
share/mysql/test/suite/funcs_1/r/myisam_storedproc_10.result
share/mysql/test/suite/funcs_1/r/myisam_trig_0102.result
share/mysql/test/suite/funcs_1/r/myisam_trig_03.result
share/mysql/test/suite/funcs_1/r/myisam_trig_03e.result
share/mysql/test/suite/funcs_1/r/myisam_trig_0407.result
share/mysql/test/suite/funcs_1/r/myisam_trig_08.result
share/mysql/test/suite/funcs_1/r/myisam_trig_09.result
share/mysql/test/suite/funcs_1/r/myisam_trig_1011ext.result
share/mysql/test/suite/funcs_1/r/myisam_views-big.result
share/mysql/test/suite/funcs_1/r/processlist_priv_no_prot.result
share/mysql/test/suite/funcs_1/r/processlist_priv_ps.result
share/mysql/test/suite/funcs_1/r/processlist_val_no_prot.result
share/mysql/test/suite/funcs_1/r/processlist_val_ps.result
share/mysql/test/suite/funcs_1/r/row_count_func.result
share/mysql/test/suite/funcs_1/r/storedproc.result
share/mysql/test/suite/funcs_1/storedproc/cleanup_sp_tb.inc
share/mysql/test/suite/funcs_1/storedproc/load_sp_tb.inc
share/mysql/test/suite/funcs_1/storedproc/param_check.inc
share/mysql/test/suite/funcs_1/storedproc/storedproc_02.inc
share/mysql/test/suite/funcs_1/storedproc/storedproc_03.inc
share/mysql/test/suite/funcs_1/storedproc/storedproc_06.inc
share/mysql/test/suite/funcs_1/storedproc/storedproc_07.inc
share/mysql/test/suite/funcs_1/storedproc/storedproc_08.inc
share/mysql/test/suite/funcs_1/storedproc/storedproc_08_show.inc
share/mysql/test/suite/funcs_1/storedproc/storedproc_10.inc
share/mysql/test/suite/funcs_1/t/charset_collation.test
share/mysql/test/suite/funcs_1/t/disabled.def
share/mysql/test/suite/funcs_1/t/innodb_bitdata.test
share/mysql/test/suite/funcs_1/t/innodb_cursors.test
share/mysql/test/suite/funcs_1/t/innodb_func_view.test
share/mysql/test/suite/funcs_1/t/innodb_storedproc_02.test
share/mysql/test/suite/funcs_1/t/innodb_storedproc_03.test
share/mysql/test/suite/funcs_1/t/innodb_storedproc_06.test
share/mysql/test/suite/funcs_1/t/innodb_storedproc_07.test
share/mysql/test/suite/funcs_1/t/innodb_storedproc_08.test
share/mysql/test/suite/funcs_1/t/innodb_storedproc_10.test
share/mysql/test/suite/funcs_1/t/innodb_trig_0102.test
share/mysql/test/suite/funcs_1/t/innodb_trig_03.test
share/mysql/test/suite/funcs_1/t/innodb_trig_03e.test
share/mysql/test/suite/funcs_1/t/innodb_trig_0407.test
share/mysql/test/suite/funcs_1/t/innodb_trig_08.test
share/mysql/test/suite/funcs_1/t/innodb_trig_09.test
share/mysql/test/suite/funcs_1/t/innodb_trig_1011ext-master.opt
share/mysql/test/suite/funcs_1/t/innodb_trig_1011ext.test
share/mysql/test/suite/funcs_1/t/innodb_trig_frkey.test
share/mysql/test/suite/funcs_1/t/innodb_views.test
share/mysql/test/suite/funcs_1/t/is_basics_mixed.test
share/mysql/test/suite/funcs_1/t/is_character_sets.test
share/mysql/test/suite/funcs_1/t/is_cml_innodb.test
share/mysql/test/suite/funcs_1/t/is_cml_memory.test
share/mysql/test/suite/funcs_1/t/is_cml_myisam.test
share/mysql/test/suite/funcs_1/t/is_coll_char_set_appl.test
share/mysql/test/suite/funcs_1/t/is_collations.test
share/mysql/test/suite/funcs_1/t/is_column_privileges.test
share/mysql/test/suite/funcs_1/t/is_column_privileges_is_mysql_test.test
share/mysql/test/suite/funcs_1/t/is_columns.test
share/mysql/test/suite/funcs_1/t/is_columns_innodb.test
share/mysql/test/suite/funcs_1/t/is_columns_is.test
share/mysql/test/suite/funcs_1/t/is_columns_is_embedded.test
share/mysql/test/suite/funcs_1/t/is_columns_memory.test
share/mysql/test/suite/funcs_1/t/is_columns_myisam.test
share/mysql/test/suite/funcs_1/t/is_columns_myisam_embedded.test
share/mysql/test/suite/funcs_1/t/is_columns_mysql.test
share/mysql/test/suite/funcs_1/t/is_columns_mysql_embedded.test
share/mysql/test/suite/funcs_1/t/is_engines.test
share/mysql/test/suite/funcs_1/t/is_engines_archive.test
share/mysql/test/suite/funcs_1/t/is_engines_blackhole.test
share/mysql/test/suite/funcs_1/t/is_engines_csv.test
share/mysql/test/suite/funcs_1/t/is_engines_federated.test
share/mysql/test/suite/funcs_1/t/is_engines_innodb.test
share/mysql/test/suite/funcs_1/t/is_engines_memory.test
share/mysql/test/suite/funcs_1/t/is_engines_merge.test
share/mysql/test/suite/funcs_1/t/is_engines_myisam.test
share/mysql/test/suite/funcs_1/t/is_events.test
share/mysql/test/suite/funcs_1/t/is_key_column_usage.test
share/mysql/test/suite/funcs_1/t/is_key_column_usage_embedded.test
share/mysql/test/suite/funcs_1/t/is_routines.test
share/mysql/test/suite/funcs_1/t/is_routines_embedded.test
share/mysql/test/suite/funcs_1/t/is_schema_privileges.test
share/mysql/test/suite/funcs_1/t/is_schema_privileges_is_mysql_test.test
share/mysql/test/suite/funcs_1/t/is_schemata.test
share/mysql/test/suite/funcs_1/t/is_schemata_embedded.test
share/mysql/test/suite/funcs_1/t/is_schemata_is_mysql_test.test
share/mysql/test/suite/funcs_1/t/is_statistics.test
share/mysql/test/suite/funcs_1/t/is_statistics_is.test
share/mysql/test/suite/funcs_1/t/is_statistics_mysql.test
share/mysql/test/suite/funcs_1/t/is_statistics_mysql_embedded.test
share/mysql/test/suite/funcs_1/t/is_table_constraints.test
share/mysql/test/suite/funcs_1/t/is_table_constraints_is.test
share/mysql/test/suite/funcs_1/t/is_table_constraints_mysql.test
share/mysql/test/suite/funcs_1/t/is_table_constraints_mysql_embedded.test
share/mysql/test/suite/funcs_1/t/is_table_privileges.test
share/mysql/test/suite/funcs_1/t/is_tables.test
share/mysql/test/suite/funcs_1/t/is_tables_embedded.test
share/mysql/test/suite/funcs_1/t/is_tables_innodb.test
share/mysql/test/suite/funcs_1/t/is_tables_is.test
share/mysql/test/suite/funcs_1/t/is_tables_memory.test
share/mysql/test/suite/funcs_1/t/is_tables_myisam.test
share/mysql/test/suite/funcs_1/t/is_tables_myisam_embedded.test
share/mysql/test/suite/funcs_1/t/is_tables_mysql.test
share/mysql/test/suite/funcs_1/t/is_tables_mysql_embedded.test
share/mysql/test/suite/funcs_1/t/is_triggers.test
share/mysql/test/suite/funcs_1/t/is_triggers_embedded.test
share/mysql/test/suite/funcs_1/t/is_user_privileges.test
share/mysql/test/suite/funcs_1/t/is_views.test
share/mysql/test/suite/funcs_1/t/is_views_embedded.test
share/mysql/test/suite/funcs_1/t/memory_bitdata.test
share/mysql/test/suite/funcs_1/t/memory_cursors.test
share/mysql/test/suite/funcs_1/t/memory_func_view.test
share/mysql/test/suite/funcs_1/t/memory_storedproc_02.test
share/mysql/test/suite/funcs_1/t/memory_storedproc_03.test
share/mysql/test/suite/funcs_1/t/memory_storedproc_06.test
share/mysql/test/suite/funcs_1/t/memory_storedproc_07.test
share/mysql/test/suite/funcs_1/t/memory_storedproc_08.test
share/mysql/test/suite/funcs_1/t/memory_storedproc_10.test
share/mysql/test/suite/funcs_1/t/memory_trig_0102.test
share/mysql/test/suite/funcs_1/t/memory_trig_03.test
share/mysql/test/suite/funcs_1/t/memory_trig_03e.test
share/mysql/test/suite/funcs_1/t/memory_trig_0407.test
share/mysql/test/suite/funcs_1/t/memory_trig_08.test
share/mysql/test/suite/funcs_1/t/memory_trig_09.test
share/mysql/test/suite/funcs_1/t/memory_trig_1011ext-master.opt
share/mysql/test/suite/funcs_1/t/memory_trig_1011ext.test
share/mysql/test/suite/funcs_1/t/memory_views.test
share/mysql/test/suite/funcs_1/t/myisam_bitdata.test
share/mysql/test/suite/funcs_1/t/myisam_cursors.test
share/mysql/test/suite/funcs_1/t/myisam_func_view.test
share/mysql/test/suite/funcs_1/t/myisam_storedproc_02.test
share/mysql/test/suite/funcs_1/t/myisam_storedproc_03.test
share/mysql/test/suite/funcs_1/t/myisam_storedproc_06.test
share/mysql/test/suite/funcs_1/t/myisam_storedproc_07.test
share/mysql/test/suite/funcs_1/t/myisam_storedproc_08.test
share/mysql/test/suite/funcs_1/t/myisam_storedproc_10.test
share/mysql/test/suite/funcs_1/t/myisam_trig_0102.test
share/mysql/test/suite/funcs_1/t/myisam_trig_03.test
share/mysql/test/suite/funcs_1/t/myisam_trig_03e.test
share/mysql/test/suite/funcs_1/t/myisam_trig_0407.test
share/mysql/test/suite/funcs_1/t/myisam_trig_08.test
share/mysql/test/suite/funcs_1/t/myisam_trig_09.test
share/mysql/test/suite/funcs_1/t/myisam_trig_1011ext-master.opt
share/mysql/test/suite/funcs_1/t/myisam_trig_1011ext.test
share/mysql/test/suite/funcs_1/t/myisam_views-big.test
share/mysql/test/suite/funcs_1/t/processlist_priv_no_prot.test
share/mysql/test/suite/funcs_1/t/processlist_priv_ps.test
share/mysql/test/suite/funcs_1/t/processlist_val_no_prot.test
share/mysql/test/suite/funcs_1/t/processlist_val_ps.test
share/mysql/test/suite/funcs_1/t/row_count_func-master.opt
share/mysql/test/suite/funcs_1/t/row_count_func.test
share/mysql/test/suite/funcs_1/t/storedproc.test
share/mysql/test/suite/funcs_1/t/suite.opt
share/mysql/test/suite/funcs_1/triggers/trig_frkey.inc
share/mysql/test/suite/funcs_1/triggers/trig_frkey2.inc
share/mysql/test/suite/funcs_1/triggers/triggers_0102.inc
share/mysql/test/suite/funcs_1/triggers/triggers_03.inc
share/mysql/test/suite/funcs_1/triggers/triggers_03e_columns.inc
share/mysql/test/suite/funcs_1/triggers/triggers_03e_db_level.inc
share/mysql/test/suite/funcs_1/triggers/triggers_03e_db_table_mix.inc
share/mysql/test/suite/funcs_1/triggers/triggers_03e_definer.inc
share/mysql/test/suite/funcs_1/triggers/triggers_03e_global_db_mix.inc
share/mysql/test/suite/funcs_1/triggers/triggers_03e_prepare.inc
share/mysql/test/suite/funcs_1/triggers/triggers_03e_table_level.inc
share/mysql/test/suite/funcs_1/triggers/triggers_03e_transaction.inc
share/mysql/test/suite/funcs_1/triggers/triggers_0407.inc
share/mysql/test/suite/funcs_1/triggers/triggers_08.inc
share/mysql/test/suite/funcs_1/triggers/triggers_09.inc
share/mysql/test/suite/funcs_1/triggers/triggers_1011ext.inc
share/mysql/test/suite/funcs_1/views/func_view.inc
share/mysql/test/suite/funcs_1/views/fv1.inc
share/mysql/test/suite/funcs_1/views/fv2.inc
share/mysql/test/suite/funcs_1/views/fv_cast.inc
share/mysql/test/suite/funcs_1/views/fv_if1.inc
share/mysql/test/suite/funcs_1/views/fv_if2.inc
share/mysql/test/suite/funcs_1/views/fv_ifnull.inc
share/mysql/test/suite/funcs_1/views/views_master.inc
share/mysql/test/suite/funcs_2/charset/charset_master.test
share/mysql/test/suite/funcs_2/data/charset_utf8.txt
share/mysql/test/suite/funcs_2/include/check_charset.inc
share/mysql/test/suite/funcs_2/include/check_charset_ucs2.inc
share/mysql/test/suite/funcs_2/include/check_charset_utf8.inc
share/mysql/test/suite/funcs_2/lib/gen_charset_utf8.pl
share/mysql/test/suite/funcs_2/r/innodb_charset.result
share/mysql/test/suite/funcs_2/r/memory_charset.result
share/mysql/test/suite/funcs_2/r/myisam_charset.result
share/mysql/test/suite/funcs_2/readme.txt
share/mysql/test/suite/funcs_2/t/disabled.def
share/mysql/test/suite/funcs_2/t/innodb_charset.test
share/mysql/test/suite/funcs_2/t/memory_charset.test
share/mysql/test/suite/funcs_2/t/myisam_charset.test
share/mysql/test/suite/funcs_2/t/suite.opt
Changes 5.6.22: * Noisy compiler warnings on FreeBSD 10 were silenced. * CMake workarounds for older Mac OS X and XCode versions were removed. On Mac OS X, compilation always uses Clang, even for 32-bit builds. * Previously, the MYSQL_MAINTAINER_MODE CMake option was turned on by default for debug builds and off for release builds, and MYSQL_MAINTAINER_MODE caused -Werror to be enabled when building with GCC. This made it cumbersome to enable -Werror under certain conditions, such as when compiling with Clang. * Build support was modified to produce the same warnings for Clang as for gcc. * CMake configuration for the Clang compiler sets more appropriate flags for building on Linux. Specifically, -g -fno-omit-frame-pointer -fno-strict-aliasing is now added. * Bugs fixed.
2014-12-02 13:40:09 +01:00
share/mysql/test/suite/innodb/include/checksum_not_strict.inc
Changes 5.6.26: * Security Fix: Due to the LogJam issue (https://weakdh.org/), OpenSSL has changed the Diffie-Hellman key length parameters for openssl-1.0.1n and up. * Replication: When using a multi-threaded slave, each worker thread has its own queue of transactions to process. In previous MySQL versions, STOP SLAVE waited for all workers to process their entire queue. This logic has been changed so that STOP SLAVE first finds the newest transaction that was committed by any worker thread. Then, it waits for all workers to complete transactions older than that. Newer transactions are not processed. The new logic allows STOP SLAVE to complete faster in case some worker queues contain multiple transactions. * Previously, the max_digest_length system variable controlled the maximum digest length for all server functions that computed statement digests. However, whereas the Performance Schema may need to maintain many digest values, other server functions such as MySQL Enterprise Firewall need only one digest per session. Increasing the max_digest_length value has little impact on total memory requirements for those functions, but can increase Performance Schema memory requirements significantly. To enable configuring digest length separately for the Performance Schema, its digest length is now controlled by the new performance_schema_max_digest_length system variable. * Previously, changes to the validate_password plugin dictionary file (named by the validate_password_dictionary_file system variable) while the server was running required a restart for the server to recognize the changes. Now validate_password_dictionary_file can be set at runtime and assigning a value causes the named file to be read without a restart. In addition, two new status variables are available. validate_password_dictionary_file_last_parsed indicates when the dictionary file was last read, and validate_password_dictionary_file_words_count indicates how many words it contains. * Bugs fixed
2015-07-30 16:39:18 +02:00
share/mysql/test/suite/innodb/include/import.inc
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/innodb/include/innodb_dict.inc
share/mysql/test/suite/innodb/include/innodb_stats.inc
share/mysql/test/suite/innodb/include/innodb_stats_table_flag.inc
share/mysql/test/suite/innodb/include/innodb_stats_table_flag_analyze.inc
Changes 5.6.21: The --skip-innodb option is now deprecated and its use results in a warning. It will be removed in a future MySQL release. This also applies to its synonyms (--innodb=OFF, --disable-innodb, and so forth). MySQL Enterprise Edition now includes a set of encryption functions based on the OpenSSL library that expose OpenSSL capabilities at the SQL level. Replication: The new variable simplified_binlog_gtid_recovery can be used to change the way binary log files are searched for previous GTIDs during recovery, speeding up the process when a large number of binary log files exist. Internally, spatial data types such as Geometry are represented as BLOB values, so when invoked with the --hex-blob option, mysqldump now displays spatial values in hex. Bugs Fixed...
2014-10-01 10:34:23 +02:00
share/mysql/test/suite/innodb/r/add_foreign_key.result
Changes 5.6.28: MySQL Server RPM packages now contain a conflict indicator for MySQL Connector C, such that an error occurs when installing MySQL Server if MySQL Connector C is also installed. To install MySQL Server, remove any MySQL Connector C packages first. mysql_upgrade now attempts to print more informative errors than FATAL ERROR: Upgrade failed. These client programs now support the --enable-cleartext-plugin option: mysqlcheck, mysqldump, mysqlimport, mysqlshow. This option enables the mysql_clear_password cleartext authentication plugin. (See The Cleartext Client-Side Authentication Plugin.) Support for building with Solaris Studio 5.13 was added. Performance Schema digests in DIGEST_TEXT columns have ... appended to the end to indicate when statements exceed the maximum statement size and were truncated. This is also now done for statement text values in SQL_TEXT columns. Bugs Fixed
2015-12-08 09:49:50 +01:00
share/mysql/test/suite/innodb/r/alter_rename_existing.result
Changes 5.6.29: * InnoDB: A new InnoDB configuration option, innodb_tmpdir, allows you to configure a separate temporary file directory for online ALTER TABLE operations. This option was introduced to help avoid tmpdir overflows that could occur as a result of large temporary files created during online ALTER TABLE operations. innodb_tmpdir is a SESSION variable and can be configured dynamically using a SET statement. * yaSSL was upgraded to version 2.3.9. This upgrade corrects an issue in which yaSSL handled only cases of zero or one leading zeros for the key agreement instead of potentially any number, which in rare cases could cause connections to fail when using DHE cipher suites. * The Valgrind function signature in mysql-test/valgrind.supp was upgraded for Valgrind 3.11. * Bugs Fixed
2016-02-28 09:58:03 +01:00
share/mysql/test/suite/innodb/r/analyze_table.result
Changes 5.6.17: Functionality Added or Changed Incompatible Change: The AES_ENCRYPT() and AES_DECRYPT() functions now permit control of the block encryption mode and take an optional initialization vector argument: The new block_encryption_mode system variable controls the mode for block-based encryption algorithms. Its default value is aes-128-ecb, which signifies encryption using a key length of 128 bits and ECB mode. An optional init_vector argument provides an initialization vector for encryption modes that require it: AES_ENCRYPT(str,key_str[,init_vector]) AES_DECRYPT(crypt_str,key_str[,init_vector]) A random string of bytes to use for the initialization vector can be produced by calling the new RANDOM_BYTES() function. For more information, see Encryption and Compression Functions. These changes make statements that use AES_ENCRYPT() or AES_DECRYPT() unsafe for statement-based replication and they cannot be stored in the query cache. Queries that use RANDOM_BYTES() are unsafe for statement-based replication and cannot be stored in the query cache. Incompatible Change: The ERROR_FOR_DIVISION_BY_ZERO, NO_ZERO_DATE, and NO_ZERO_IN_DATE SQL modes now are deprecated and setting the sql_mode value to include any of them generates a warning. In MySQL 5.7, these modes do nothing. Instead, their effects are included in the effects of strict SQL mode (STRICT_ALL_TABLES or STRICT_TRANS_TABLES). The motivation for the change in MySQL 5.7 is to reduce the number of SQL modes with an effect dependent on strict mode and make them part of strict mode itself. To make advance preparation for an upgrade to MySQL 5.7, see SQL Mode Changes in MySQL 5.7. That discussion provides guidelines to assess whether your applications will be affected by the SQL mode changes in MySQL 5.7. InnoDB: MySQL now supports rebuilding regular and partitioned InnoDB tables using online DDL (ALGORITHM=INPLACE) for the following operations: OPTIMIZE TABLE ALTER TABLE ... FORCE ALTER TABLE ... ENGINE=INNODB (when run on an InnoDB table) Online DDL support reduces table rebuild time and permits concurrent DML, which helps reduce user application downtime. For additional information, see Overview of Online DDL. On Solaris, mysql_config --libs now includes -R/path/to/library so that libraries can be found at runtime. mysql_install_db provides a more informative diagnostic message when required Perl modules are missing. The IGNORE clause for ALTER TABLE is now deprecated and will be removed in a future version of MySQL. ALTER IGNORE TABLE causes problems for replication, prevents online ALTER TABLE for unique index creation, and causes problems with foreign keys (rows removed in the parent table). Bugs Fixed
2014-03-31 12:32:13 +02:00
share/mysql/test/suite/innodb/r/blob-update-debug.result
Changes 5.6.22: * Noisy compiler warnings on FreeBSD 10 were silenced. * CMake workarounds for older Mac OS X and XCode versions were removed. On Mac OS X, compilation always uses Clang, even for 32-bit builds. * Previously, the MYSQL_MAINTAINER_MODE CMake option was turned on by default for debug builds and off for release builds, and MYSQL_MAINTAINER_MODE caused -Werror to be enabled when building with GCC. This made it cumbersome to enable -Werror under certain conditions, such as when compiling with Clang. * Build support was modified to produce the same warnings for Clang as for gcc. * CMake configuration for the Clang compiler sets more appropriate flags for building on Linux. Specifically, -g -fno-omit-frame-pointer -fno-strict-aliasing is now added. * Bugs fixed.
2014-12-02 13:40:09 +01:00
share/mysql/test/suite/innodb/r/blob_redo.result
share/mysql/test/suite/innodb/r/checksum.result
Changes 5.6.17: Functionality Added or Changed Incompatible Change: The AES_ENCRYPT() and AES_DECRYPT() functions now permit control of the block encryption mode and take an optional initialization vector argument: The new block_encryption_mode system variable controls the mode for block-based encryption algorithms. Its default value is aes-128-ecb, which signifies encryption using a key length of 128 bits and ECB mode. An optional init_vector argument provides an initialization vector for encryption modes that require it: AES_ENCRYPT(str,key_str[,init_vector]) AES_DECRYPT(crypt_str,key_str[,init_vector]) A random string of bytes to use for the initialization vector can be produced by calling the new RANDOM_BYTES() function. For more information, see Encryption and Compression Functions. These changes make statements that use AES_ENCRYPT() or AES_DECRYPT() unsafe for statement-based replication and they cannot be stored in the query cache. Queries that use RANDOM_BYTES() are unsafe for statement-based replication and cannot be stored in the query cache. Incompatible Change: The ERROR_FOR_DIVISION_BY_ZERO, NO_ZERO_DATE, and NO_ZERO_IN_DATE SQL modes now are deprecated and setting the sql_mode value to include any of them generates a warning. In MySQL 5.7, these modes do nothing. Instead, their effects are included in the effects of strict SQL mode (STRICT_ALL_TABLES or STRICT_TRANS_TABLES). The motivation for the change in MySQL 5.7 is to reduce the number of SQL modes with an effect dependent on strict mode and make them part of strict mode itself. To make advance preparation for an upgrade to MySQL 5.7, see SQL Mode Changes in MySQL 5.7. That discussion provides guidelines to assess whether your applications will be affected by the SQL mode changes in MySQL 5.7. InnoDB: MySQL now supports rebuilding regular and partitioned InnoDB tables using online DDL (ALGORITHM=INPLACE) for the following operations: OPTIMIZE TABLE ALTER TABLE ... FORCE ALTER TABLE ... ENGINE=INNODB (when run on an InnoDB table) Online DDL support reduces table rebuild time and permits concurrent DML, which helps reduce user application downtime. For additional information, see Overview of Online DDL. On Solaris, mysql_config --libs now includes -R/path/to/library so that libraries can be found at runtime. mysql_install_db provides a more informative diagnostic message when required Perl modules are missing. The IGNORE clause for ALTER TABLE is now deprecated and will be removed in a future version of MySQL. ALTER IGNORE TABLE causes problems for replication, prevents online ALTER TABLE for unique index creation, and causes problems with foreign keys (rows removed in the parent table). Bugs Fixed
2014-03-31 12:32:13 +02:00
share/mysql/test/suite/innodb/r/create-index.result
Changes 5.6.26: * Security Fix: Due to the LogJam issue (https://weakdh.org/), OpenSSL has changed the Diffie-Hellman key length parameters for openssl-1.0.1n and up. * Replication: When using a multi-threaded slave, each worker thread has its own queue of transactions to process. In previous MySQL versions, STOP SLAVE waited for all workers to process their entire queue. This logic has been changed so that STOP SLAVE first finds the newest transaction that was committed by any worker thread. Then, it waits for all workers to complete transactions older than that. Newer transactions are not processed. The new logic allows STOP SLAVE to complete faster in case some worker queues contain multiple transactions. * Previously, the max_digest_length system variable controlled the maximum digest length for all server functions that computed statement digests. However, whereas the Performance Schema may need to maintain many digest values, other server functions such as MySQL Enterprise Firewall need only one digest per session. Increasing the max_digest_length value has little impact on total memory requirements for those functions, but can increase Performance Schema memory requirements significantly. To enable configuring digest length separately for the Performance Schema, its digest length is now controlled by the new performance_schema_max_digest_length system variable. * Previously, changes to the validate_password plugin dictionary file (named by the validate_password_dictionary_file system variable) while the server was running required a restart for the server to recognize the changes. Now validate_password_dictionary_file can be set at runtime and assigning a value causes the named file to be read without a restart. In addition, two new status variables are available. validate_password_dictionary_file_last_parsed indicates when the dictionary file was last read, and validate_password_dictionary_file_words_count indicates how many words it contains. * Bugs fixed
2015-07-30 16:39:18 +02:00
share/mysql/test/suite/innodb/r/dropdb.result
Changes 5.6.20: Security Fix: The linked OpenSSL library for the MySQL 5.6 Commercial Server has been updated from version 1.0.1g to version 1.0.1h. Versions of OpenSSL prior to and including 1.0.1g are reported to be vulnerable to CVE-2014-0224. This change does not affect the Oracle-produced MySQL Community build of MySQL Server 5.6, which uses the yaSSL library instead. DTrace Support MySQL now includes DTrace support on Oracle Linux 6 or higher with UEK kernel. If DTrace is present, server builds will detect it with no special CMake options required. For information about using DTrace on MySQL, see Tracing mysqld Using DTrace. InnoDB Notes Important Change: Redo log writes for large, externally stored BLOB fields could overwrite the most recent checkpoint. The 5.6.20 patch limits the size of redo log BLOB writes to 10% of the redo log file size. The 5.7.5 patch addresses the bug without imposing a limitation. For MySQL 5.5, the bug remains a known limitation. As a result of the redo log BLOB write limit introduced for MySQL 5.6, innodb_log_file_size should be set to a value greater than 10 times the largest BLOB data size found in the rows of your tables plus the length of other variable length fields (VARCHAR, VARBINARY, and TEXT type fields). Failing to do so could result in “Row size too large” errors. No action is required if your innodb_log_file_size setting is already sufficiently large or your tables contain no BLOB data. Functionality Added or Changed Replication: The new system variable binlog_impossible_mode controls what happens if the server cannot write to the binary log, for example, due to a file error. For backward compatibility, the default for binlog_impossible_mode is IGNORE_ERROR, meaning the server logs the error, halts logging, and continues updates to the database. Setting this variable to ABORT_SERVER makes the server halt logging and shut down if it cannot write to the binary log. CMake support was updated to handle CMake version 3. New Debian7, Ubuntu12.04, and Ubuntu14.04 distribution support that was introduced with 5.6.17 now comes with the platform-specific packaging source placed under the packaging directory, in the deb-precise, deb-wheezy, and deb-trusty directories. Support for LinuxThreads has been removed from the source code. LinuxThreads was superseded by NPTL in Linux 2.6. By default, mysql_install_db creates a my.cnf file in the installation base directory using a template. This may be undesireable for some deployments. To enable this behavior to be suppressed, mysql_install_db now supports a --keep-my-cnf option to preserve any existing my.cnf file and not create a new my.cnf file. The mysqlhotcopy utility is now deprecated and will be removed in a future version of MySQL. Among the reasons for this: It works only for the MyISAM and ARCHIVE storage engines; it works on Unix but not Windows. Alternatives include mysqldump and MySQL Enterprise Backup. The timed_mutexes system variable has no effect and is deprecated. Bugs Fixed
2014-08-10 17:11:57 +02:00
share/mysql/test/suite/innodb/r/foreign_key.result
Changes 5.6.26: * Security Fix: Due to the LogJam issue (https://weakdh.org/), OpenSSL has changed the Diffie-Hellman key length parameters for openssl-1.0.1n and up. * Replication: When using a multi-threaded slave, each worker thread has its own queue of transactions to process. In previous MySQL versions, STOP SLAVE waited for all workers to process their entire queue. This logic has been changed so that STOP SLAVE first finds the newest transaction that was committed by any worker thread. Then, it waits for all workers to complete transactions older than that. Newer transactions are not processed. The new logic allows STOP SLAVE to complete faster in case some worker queues contain multiple transactions. * Previously, the max_digest_length system variable controlled the maximum digest length for all server functions that computed statement digests. However, whereas the Performance Schema may need to maintain many digest values, other server functions such as MySQL Enterprise Firewall need only one digest per session. Increasing the max_digest_length value has little impact on total memory requirements for those functions, but can increase Performance Schema memory requirements significantly. To enable configuring digest length separately for the Performance Schema, its digest length is now controlled by the new performance_schema_max_digest_length system variable. * Previously, changes to the validate_password plugin dictionary file (named by the validate_password_dictionary_file system variable) while the server was running required a restart for the server to recognize the changes. Now validate_password_dictionary_file can be set at runtime and assigning a value causes the named file to be read without a restart. In addition, two new status variables are available. validate_password_dictionary_file_last_parsed indicates when the dictionary file was last read, and validate_password_dictionary_file_words_count indicates how many words it contains. * Bugs fixed
2015-07-30 16:39:18 +02:00
share/mysql/test/suite/innodb/r/import.result
Changes 5.6.21: The --skip-innodb option is now deprecated and its use results in a warning. It will be removed in a future MySQL release. This also applies to its synonyms (--innodb=OFF, --disable-innodb, and so forth). MySQL Enterprise Edition now includes a set of encryption functions based on the OpenSSL library that expose OpenSSL capabilities at the SQL level. Replication: The new variable simplified_binlog_gtid_recovery can be used to change the way binary log files are searched for previous GTIDs during recovery, speeding up the process when a large number of binary log files exist. Internally, spatial data types such as Geometry are represented as BLOB values, so when invoked with the --hex-blob option, mysqldump now displays spatial values in hex. Bugs Fixed...
2014-10-01 10:34:23 +02:00
share/mysql/test/suite/innodb/r/index_tree_operation.result
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/innodb/r/innodb-2byte-collation.result
share/mysql/test/suite/innodb/r/innodb-ac-non-locking-select.result
share/mysql/test/suite/innodb/r/innodb-alter-autoinc.result
share/mysql/test/suite/innodb/r/innodb-alter-debug.result
share/mysql/test/suite/innodb/r/innodb-alter-discard.result
share/mysql/test/suite/innodb/r/innodb-alter-nullable.result
Changes 5.6.21: The --skip-innodb option is now deprecated and its use results in a warning. It will be removed in a future MySQL release. This also applies to its synonyms (--innodb=OFF, --disable-innodb, and so forth). MySQL Enterprise Edition now includes a set of encryption functions based on the OpenSSL library that expose OpenSSL capabilities at the SQL level. Replication: The new variable simplified_binlog_gtid_recovery can be used to change the way binary log files are searched for previous GTIDs during recovery, speeding up the process when a large number of binary log files exist. Internally, spatial data types such as Geometry are represented as BLOB values, so when invoked with the --hex-blob option, mysqldump now displays spatial values in hex. Bugs Fixed...
2014-10-01 10:34:23 +02:00
share/mysql/test/suite/innodb/r/innodb-alter-tempfile.result
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/innodb/r/innodb-alter.result
share/mysql/test/suite/innodb/r/innodb-analyze.result
share/mysql/test/suite/innodb/r/innodb-autoinc-18274.result
share/mysql/test/suite/innodb/r/innodb-autoinc-44030.result
share/mysql/test/suite/innodb/r/innodb-autoinc-56228.result
share/mysql/test/suite/innodb/r/innodb-autoinc-optimize.result
share/mysql/test/suite/innodb/r/innodb-autoinc.result
share/mysql/test/suite/innodb/r/innodb-blob.result
share/mysql/test/suite/innodb/r/innodb-bug-14068765.result
share/mysql/test/suite/innodb/r/innodb-bug-14084530.result
share/mysql/test/suite/innodb/r/innodb-bug12552164.result
share/mysql/test/suite/innodb/r/innodb-bug14219515.result
Changes 5.6.16: Functionality Added or Changed * InnoDB: New global configuration parameters, innodb_status_output and innodb_status_output_locks, allow you to dynamically enable and disable the standard InnoDB Monitor and InnoDB Lock Monitor for periodic output. Enabling and disabling monitors for periodic output by creating and dropping specially named tables is deprecated and may be removed in a future release. * Previously, ALTER TABLE in MySQL 5.6 could alter a table such that the result had temporal columns in both 5.5 and 5.6 format. Now ALTER TABLE upgrades old temporal columns to 5.6 format for ADD COLUMN, CHANGE COLUMN, MODIFY COLUMN, ADD INDEX, and FORCE operations. This conversion cannot be done using the INPLACE algorithm, so specifying ALGORITHM=INPLACE in these cases results in an error. * CMake now supports a -DTMPDIR=dir_name option to specify the default tmpdir value. If unspecified, the value defaults to P_tmpdir in <stdio.h>. Bugs Fixed * InnoDB; Replication: Using the InnoDB memcached plugin (see InnoDB Integration with memcached) with innodb_api_enable_binlog set to 1 caused the server to leak memory. * InnoDB: A boolean mode full-text search query would result in a memory access violation during parsing. * InnoDB: When new indexes are added by an ALTER TABLE operation, instead of only saving table-level statistics and statistics for the new indexes, InnoDB would save statistics for the entire table, including the table's other indexes. This behavior slowed ALTER TABLE performance. * InnoDB: Due to a parser error, full-text search queries that include a sub-expression could return the wrong result. * InnoDB: The innochecksum tool did not use a Windows-specific API to retrieve file size information, which resulted in an incorrect error message (Error: ibdata1 cannot be found) when the MySQL 5.6 innochecksum 2GB file size limit was exceeded. innochecksum now provides support for files larger than 2GB in both MySQL 5.6 and MySQL 5.7. * InnoDB: Due to a regression introduced by the fix for Bug17371537, memory was not allocated for the default memcached engine when using the default memcached engine as the backstore for data instead of InnoDB. * InnoDB: InnoDB would report an incorrect operating system error code after failing to initialize. * InnoDB: Manipulating a table after discarding its tablespace using ALTER TABLE ... DISCARD TABLESPACE could result in a serious error. * InnoDB: Persistent optimizer statistics would cause stalls due to latch contention. * InnoDB: MATCH() ... AGAINST queries that use a long string as an argument for AGAINST() could result in an error when run on an InnoDB table with a full-text search index. * InnoDB: An InnoDB full-text search failure would occur due to an “unended” token. The string and string length should be passed for string comparison. * InnoDB: In debug builds, a merge insert buffer during a page read would cause a memory access violation. * InnoDB: Truncating a memcached InnoDB table while memcached is performing DML operations would result in a serious error. * InnoDB: In sync0rw.ic, rw_lock_x_lock_func_nowait would needlessly call os_thread_get_curr_id. * InnoDB: Attempting to rename a table to a missing database would result in a serious error. more...
2014-02-13 08:49:56 +01:00
share/mysql/test/suite/innodb/r/innodb-change-buffer-recovery.result
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/innodb/r/innodb-consistent.result
Changes 5.6.17: Functionality Added or Changed Incompatible Change: The AES_ENCRYPT() and AES_DECRYPT() functions now permit control of the block encryption mode and take an optional initialization vector argument: The new block_encryption_mode system variable controls the mode for block-based encryption algorithms. Its default value is aes-128-ecb, which signifies encryption using a key length of 128 bits and ECB mode. An optional init_vector argument provides an initialization vector for encryption modes that require it: AES_ENCRYPT(str,key_str[,init_vector]) AES_DECRYPT(crypt_str,key_str[,init_vector]) A random string of bytes to use for the initialization vector can be produced by calling the new RANDOM_BYTES() function. For more information, see Encryption and Compression Functions. These changes make statements that use AES_ENCRYPT() or AES_DECRYPT() unsafe for statement-based replication and they cannot be stored in the query cache. Queries that use RANDOM_BYTES() are unsafe for statement-based replication and cannot be stored in the query cache. Incompatible Change: The ERROR_FOR_DIVISION_BY_ZERO, NO_ZERO_DATE, and NO_ZERO_IN_DATE SQL modes now are deprecated and setting the sql_mode value to include any of them generates a warning. In MySQL 5.7, these modes do nothing. Instead, their effects are included in the effects of strict SQL mode (STRICT_ALL_TABLES or STRICT_TRANS_TABLES). The motivation for the change in MySQL 5.7 is to reduce the number of SQL modes with an effect dependent on strict mode and make them part of strict mode itself. To make advance preparation for an upgrade to MySQL 5.7, see SQL Mode Changes in MySQL 5.7. That discussion provides guidelines to assess whether your applications will be affected by the SQL mode changes in MySQL 5.7. InnoDB: MySQL now supports rebuilding regular and partitioned InnoDB tables using online DDL (ALGORITHM=INPLACE) for the following operations: OPTIMIZE TABLE ALTER TABLE ... FORCE ALTER TABLE ... ENGINE=INNODB (when run on an InnoDB table) Online DDL support reduces table rebuild time and permits concurrent DML, which helps reduce user application downtime. For additional information, see Overview of Online DDL. On Solaris, mysql_config --libs now includes -R/path/to/library so that libraries can be found at runtime. mysql_install_db provides a more informative diagnostic message when required Perl modules are missing. The IGNORE clause for ALTER TABLE is now deprecated and will be removed in a future version of MySQL. ALTER IGNORE TABLE causes problems for replication, prevents online ALTER TABLE for unique index creation, and causes problems with foreign keys (rows removed in the parent table). Bugs Fixed
2014-03-31 12:32:13 +02:00
share/mysql/test/suite/innodb/r/innodb-double-write.result
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/innodb/r/innodb-index-debug.result
share/mysql/test/suite/innodb/r/innodb-index-online-delete.result
share/mysql/test/suite/innodb/r/innodb-index-online-fk.result
share/mysql/test/suite/innodb/r/innodb-index-online-purge.result
share/mysql/test/suite/innodb/r/innodb-index-online.result
share/mysql/test/suite/innodb/r/innodb-index.result
share/mysql/test/suite/innodb/r/innodb-index_ucs2.result
Changes 5.6.27: * InnoDB: The new innodb_numa_interleave read-only configuration option allows you to enable the NUMA interleave memory policy for allocation of the InnoDB buffer pool. When innodb_numa_interleave is enabled, the NUMA memory policy is set to MPOL_INTERLEAVE for the mysqld process. After the InnoDB buffer pool is allocated, the NUMA memory policy is set back to MPOL_DEFAULT. This option is only available on NUMA-enabled systems. * yaSSL was upgraded to version 2.3.8. * RPM .spec files were updated so that MySQL Server builds from source RPM packages will include the proper files to take advantage of operating system NUMA capabilities. This introduces a runtime dependency on libnuma.so.1. RPM and yum detect this and refuse to install if that library is not installed. * InnoDB: Reloading a table that was evicted while empty caused an AUTO_INCREMENT value to be reset. * InnoDB: Memory allocation sanity checks were added to the memcached code. * InnoDB: A memcached flush_all command raised an assertion. A function that starts a transaction was called from within assertion code. * InnoDB: A data corruption occurred on ARM64. GCC builtins did not issue the correct fences when setting or unsetting the lock word. * InnoDB: Server shutdown was delayed waiting for the purge thread to exit. To avoid this problem, the number of calls to trx_purge() was reduced, and the trx_purge() batch size was reduced to 20. * InnoDB: In READ COMMITTED mode, a REPLACE operation on a unique secondary index resulted in a constraint violation. * InnoDB: The IBUF_BITMAP_FREE bit indicated that there was more free space in the leaf page than was actually available. * InnoDB: Setting lower_case_table_names=0 on a case-insensitive file system could result in a hang condition when running an INSERT INTO ... SELECT ... FROM tbl_name operation with the wrong tbl_name letter case. An error message is now printed and the server exits when attempting to start the server with --lower_case_table_names=0 on a case-insensitive file system. * InnoDB: The server failed to start with an innodb_force_recovery setting greater than 3. InnoDB was set to read-only mode before redo logs were applied. * InnoDB: The trx_sys_read_pertable_file_format_id() function reported the wrong file format. * Partitioning: CREATE TABLE statements that used an invalid function in a subpartitioning expression did not always fail gracefully as expected. * Partitioning: Error handling for failed partitioning-related ALTER TABLE operations against non-partitioned tables was not performed correctly * Partitioning: ALTER TABLE when executed from a stored procedure did not always work correctly with tables partitioned by RANGE. * Replication: Repeatedly checking for ERR_LOCK_WAIT_TIMEOUT (as done, for example by repeatedly executing SHOW SLAVE STATUS) during a prolonged write lock on a table led to an assert. * Replication: If statement based logging was in use, when updating multiple tables in a single statement, a single transaction could be logged as two different transactions. This was due to the binary logging process not properly identifying statements which were operating over transactional tables. The fix ensures that they are correctly identified, even if such statements do not change the contents of the tables.
2015-10-03 14:46:13 +02:00
share/mysql/test/suite/innodb/r/innodb-lock-inherit-read_commited.result
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/innodb/r/innodb-lock.result
share/mysql/test/suite/innodb/r/innodb-log-file-size-1.result
share/mysql/test/suite/innodb/r/innodb-log-file-size.result
share/mysql/test/suite/innodb/r/innodb-multiple-tablespaces.result
share/mysql/test/suite/innodb/r/innodb-read-view.result
share/mysql/test/suite/innodb/r/innodb-replace.result
share/mysql/test/suite/innodb/r/innodb-semi-consistent.result
Changes 5.6.16: Functionality Added or Changed * InnoDB: New global configuration parameters, innodb_status_output and innodb_status_output_locks, allow you to dynamically enable and disable the standard InnoDB Monitor and InnoDB Lock Monitor for periodic output. Enabling and disabling monitors for periodic output by creating and dropping specially named tables is deprecated and may be removed in a future release. * Previously, ALTER TABLE in MySQL 5.6 could alter a table such that the result had temporal columns in both 5.5 and 5.6 format. Now ALTER TABLE upgrades old temporal columns to 5.6 format for ADD COLUMN, CHANGE COLUMN, MODIFY COLUMN, ADD INDEX, and FORCE operations. This conversion cannot be done using the INPLACE algorithm, so specifying ALGORITHM=INPLACE in these cases results in an error. * CMake now supports a -DTMPDIR=dir_name option to specify the default tmpdir value. If unspecified, the value defaults to P_tmpdir in <stdio.h>. Bugs Fixed * InnoDB; Replication: Using the InnoDB memcached plugin (see InnoDB Integration with memcached) with innodb_api_enable_binlog set to 1 caused the server to leak memory. * InnoDB: A boolean mode full-text search query would result in a memory access violation during parsing. * InnoDB: When new indexes are added by an ALTER TABLE operation, instead of only saving table-level statistics and statistics for the new indexes, InnoDB would save statistics for the entire table, including the table's other indexes. This behavior slowed ALTER TABLE performance. * InnoDB: Due to a parser error, full-text search queries that include a sub-expression could return the wrong result. * InnoDB: The innochecksum tool did not use a Windows-specific API to retrieve file size information, which resulted in an incorrect error message (Error: ibdata1 cannot be found) when the MySQL 5.6 innochecksum 2GB file size limit was exceeded. innochecksum now provides support for files larger than 2GB in both MySQL 5.6 and MySQL 5.7. * InnoDB: Due to a regression introduced by the fix for Bug17371537, memory was not allocated for the default memcached engine when using the default memcached engine as the backstore for data instead of InnoDB. * InnoDB: InnoDB would report an incorrect operating system error code after failing to initialize. * InnoDB: Manipulating a table after discarding its tablespace using ALTER TABLE ... DISCARD TABLESPACE could result in a serious error. * InnoDB: Persistent optimizer statistics would cause stalls due to latch contention. * InnoDB: MATCH() ... AGAINST queries that use a long string as an argument for AGAINST() could result in an error when run on an InnoDB table with a full-text search index. * InnoDB: An InnoDB full-text search failure would occur due to an “unended” token. The string and string length should be passed for string comparison. * InnoDB: In debug builds, a merge insert buffer during a page read would cause a memory access violation. * InnoDB: Truncating a memcached InnoDB table while memcached is performing DML operations would result in a serious error. * InnoDB: In sync0rw.ic, rw_lock_x_lock_func_nowait would needlessly call os_thread_get_curr_id. * InnoDB: Attempting to rename a table to a missing database would result in a serious error. more...
2014-02-13 08:49:56 +01:00
share/mysql/test/suite/innodb/r/innodb-status-output.result
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/innodb/r/innodb-system-table-view.result
share/mysql/test/suite/innodb/r/innodb-table-online.result
share/mysql/test/suite/innodb/r/innodb-tablespace.result
share/mysql/test/suite/innodb/r/innodb-timeout.result
share/mysql/test/suite/innodb/r/innodb-truncate.result
share/mysql/test/suite/innodb/r/innodb-ucs2.result
Changes 5.6.17: Functionality Added or Changed Incompatible Change: The AES_ENCRYPT() and AES_DECRYPT() functions now permit control of the block encryption mode and take an optional initialization vector argument: The new block_encryption_mode system variable controls the mode for block-based encryption algorithms. Its default value is aes-128-ecb, which signifies encryption using a key length of 128 bits and ECB mode. An optional init_vector argument provides an initialization vector for encryption modes that require it: AES_ENCRYPT(str,key_str[,init_vector]) AES_DECRYPT(crypt_str,key_str[,init_vector]) A random string of bytes to use for the initialization vector can be produced by calling the new RANDOM_BYTES() function. For more information, see Encryption and Compression Functions. These changes make statements that use AES_ENCRYPT() or AES_DECRYPT() unsafe for statement-based replication and they cannot be stored in the query cache. Queries that use RANDOM_BYTES() are unsafe for statement-based replication and cannot be stored in the query cache. Incompatible Change: The ERROR_FOR_DIVISION_BY_ZERO, NO_ZERO_DATE, and NO_ZERO_IN_DATE SQL modes now are deprecated and setting the sql_mode value to include any of them generates a warning. In MySQL 5.7, these modes do nothing. Instead, their effects are included in the effects of strict SQL mode (STRICT_ALL_TABLES or STRICT_TRANS_TABLES). The motivation for the change in MySQL 5.7 is to reduce the number of SQL modes with an effect dependent on strict mode and make them part of strict mode itself. To make advance preparation for an upgrade to MySQL 5.7, see SQL Mode Changes in MySQL 5.7. That discussion provides guidelines to assess whether your applications will be affected by the SQL mode changes in MySQL 5.7. InnoDB: MySQL now supports rebuilding regular and partitioned InnoDB tables using online DDL (ALGORITHM=INPLACE) for the following operations: OPTIMIZE TABLE ALTER TABLE ... FORCE ALTER TABLE ... ENGINE=INNODB (when run on an InnoDB table) Online DDL support reduces table rebuild time and permits concurrent DML, which helps reduce user application downtime. For additional information, see Overview of Online DDL. On Solaris, mysql_config --libs now includes -R/path/to/library so that libraries can be found at runtime. mysql_install_db provides a more informative diagnostic message when required Perl modules are missing. The IGNORE clause for ALTER TABLE is now deprecated and will be removed in a future version of MySQL. ALTER IGNORE TABLE causes problems for replication, prevents online ALTER TABLE for unique index creation, and causes problems with foreign keys (rows removed in the parent table). Bugs Fixed
2014-03-31 12:32:13 +02:00
share/mysql/test/suite/innodb/r/innodb-update-insert.result
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/innodb/r/innodb-use-sys-malloc.result
share/mysql/test/suite/innodb/r/innodb-wl5522-1.result
share/mysql/test/suite/innodb/r/innodb-wl5522-debug.result
share/mysql/test/suite/innodb/r/innodb-wl5522.result
share/mysql/test/suite/innodb/r/innodb-wl5980-alter.result
share/mysql/test/suite/innodb/r/innodb-wl5980-debug.result
share/mysql/test/suite/innodb/r/innodb-wl5980-discard.result
share/mysql/test/suite/innodb/r/innodb-wl5980-linux.result
share/mysql/test/suite/innodb/r/innodb-wl5980-windows.result
share/mysql/test/suite/innodb/r/innodb-wl6445-1.result
share/mysql/test/suite/innodb/r/innodb-wl6445-2.result
share/mysql/test/suite/innodb/r/innodb-wl6445.result
share/mysql/test/suite/innodb/r/innodb.result
share/mysql/test/suite/innodb/r/innodb_autoinc_lock_mode_zero.result
Changes 5.6.27: * InnoDB: The new innodb_numa_interleave read-only configuration option allows you to enable the NUMA interleave memory policy for allocation of the InnoDB buffer pool. When innodb_numa_interleave is enabled, the NUMA memory policy is set to MPOL_INTERLEAVE for the mysqld process. After the InnoDB buffer pool is allocated, the NUMA memory policy is set back to MPOL_DEFAULT. This option is only available on NUMA-enabled systems. * yaSSL was upgraded to version 2.3.8. * RPM .spec files were updated so that MySQL Server builds from source RPM packages will include the proper files to take advantage of operating system NUMA capabilities. This introduces a runtime dependency on libnuma.so.1. RPM and yum detect this and refuse to install if that library is not installed. * InnoDB: Reloading a table that was evicted while empty caused an AUTO_INCREMENT value to be reset. * InnoDB: Memory allocation sanity checks were added to the memcached code. * InnoDB: A memcached flush_all command raised an assertion. A function that starts a transaction was called from within assertion code. * InnoDB: A data corruption occurred on ARM64. GCC builtins did not issue the correct fences when setting or unsetting the lock word. * InnoDB: Server shutdown was delayed waiting for the purge thread to exit. To avoid this problem, the number of calls to trx_purge() was reduced, and the trx_purge() batch size was reduced to 20. * InnoDB: In READ COMMITTED mode, a REPLACE operation on a unique secondary index resulted in a constraint violation. * InnoDB: The IBUF_BITMAP_FREE bit indicated that there was more free space in the leaf page than was actually available. * InnoDB: Setting lower_case_table_names=0 on a case-insensitive file system could result in a hang condition when running an INSERT INTO ... SELECT ... FROM tbl_name operation with the wrong tbl_name letter case. An error message is now printed and the server exits when attempting to start the server with --lower_case_table_names=0 on a case-insensitive file system. * InnoDB: The server failed to start with an innodb_force_recovery setting greater than 3. InnoDB was set to read-only mode before redo logs were applied. * InnoDB: The trx_sys_read_pertable_file_format_id() function reported the wrong file format. * Partitioning: CREATE TABLE statements that used an invalid function in a subpartitioning expression did not always fail gracefully as expected. * Partitioning: Error handling for failed partitioning-related ALTER TABLE operations against non-partitioned tables was not performed correctly * Partitioning: ALTER TABLE when executed from a stored procedure did not always work correctly with tables partitioned by RANGE. * Replication: Repeatedly checking for ERR_LOCK_WAIT_TIMEOUT (as done, for example by repeatedly executing SHOW SLAVE STATUS) during a prolonged write lock on a table led to an assert. * Replication: If statement based logging was in use, when updating multiple tables in a single statement, a single transaction could be logged as two different transactions. This was due to the binary logging process not properly identifying statements which were operating over transactional tables. The fix ensures that they are correctly identified, even if such statements do not change the contents of the tables.
2015-10-03 14:46:13 +02:00
share/mysql/test/suite/innodb/r/innodb_autoinc_reset.result
Changes 5.6.20: Security Fix: The linked OpenSSL library for the MySQL 5.6 Commercial Server has been updated from version 1.0.1g to version 1.0.1h. Versions of OpenSSL prior to and including 1.0.1g are reported to be vulnerable to CVE-2014-0224. This change does not affect the Oracle-produced MySQL Community build of MySQL Server 5.6, which uses the yaSSL library instead. DTrace Support MySQL now includes DTrace support on Oracle Linux 6 or higher with UEK kernel. If DTrace is present, server builds will detect it with no special CMake options required. For information about using DTrace on MySQL, see Tracing mysqld Using DTrace. InnoDB Notes Important Change: Redo log writes for large, externally stored BLOB fields could overwrite the most recent checkpoint. The 5.6.20 patch limits the size of redo log BLOB writes to 10% of the redo log file size. The 5.7.5 patch addresses the bug without imposing a limitation. For MySQL 5.5, the bug remains a known limitation. As a result of the redo log BLOB write limit introduced for MySQL 5.6, innodb_log_file_size should be set to a value greater than 10 times the largest BLOB data size found in the rows of your tables plus the length of other variable length fields (VARCHAR, VARBINARY, and TEXT type fields). Failing to do so could result in “Row size too large” errors. No action is required if your innodb_log_file_size setting is already sufficiently large or your tables contain no BLOB data. Functionality Added or Changed Replication: The new system variable binlog_impossible_mode controls what happens if the server cannot write to the binary log, for example, due to a file error. For backward compatibility, the default for binlog_impossible_mode is IGNORE_ERROR, meaning the server logs the error, halts logging, and continues updates to the database. Setting this variable to ABORT_SERVER makes the server halt logging and shut down if it cannot write to the binary log. CMake support was updated to handle CMake version 3. New Debian7, Ubuntu12.04, and Ubuntu14.04 distribution support that was introduced with 5.6.17 now comes with the platform-specific packaging source placed under the packaging directory, in the deb-precise, deb-wheezy, and deb-trusty directories. Support for LinuxThreads has been removed from the source code. LinuxThreads was superseded by NPTL in Linux 2.6. By default, mysql_install_db creates a my.cnf file in the installation base directory using a template. This may be undesireable for some deployments. To enable this behavior to be suppressed, mysql_install_db now supports a --keep-my-cnf option to preserve any existing my.cnf file and not create a new my.cnf file. The mysqlhotcopy utility is now deprecated and will be removed in a future version of MySQL. Among the reasons for this: It works only for the MyISAM and ARCHIVE storage engines; it works on Unix but not Windows. Alternatives include mysqldump and MySQL Enterprise Backup. The timed_mutexes system variable has no effect and is deprecated. Bugs Fixed
2014-08-10 17:11:57 +02:00
share/mysql/test/suite/innodb/r/innodb_blob_unrecoverable_crash.result
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/innodb/r/innodb_buffer_pool_load.result
share/mysql/test/suite/innodb/r/innodb_bug-13628249.result
share/mysql/test/suite/innodb/r/innodb_bug11754376.result
share/mysql/test/suite/innodb/r/innodb_bug11766634.result
share/mysql/test/suite/innodb/r/innodb_bug11789106.result
share/mysql/test/suite/innodb/r/innodb_bug11933790.result
share/mysql/test/suite/innodb/r/innodb_bug12400341.result
share/mysql/test/suite/innodb/r/innodb_bug12429573.result
share/mysql/test/suite/innodb/r/innodb_bug12661768.result
share/mysql/test/suite/innodb/r/innodb_bug13635833.result
share/mysql/test/suite/innodb/r/innodb_bug13867871.result
share/mysql/test/suite/innodb/r/innodb_bug14006907.result
share/mysql/test/suite/innodb/r/innodb_bug14007109.result
share/mysql/test/suite/innodb/r/innodb_bug14007649.result
share/mysql/test/suite/innodb/r/innodb_bug14147491.result
share/mysql/test/suite/innodb/r/innodb_bug14169459.result
share/mysql/test/suite/innodb/r/innodb_bug14676111.result
share/mysql/test/suite/innodb/r/innodb_bug14704286.result
share/mysql/test/suite/innodb/r/innodb_bug21704.result
share/mysql/test/suite/innodb/r/innodb_bug30423.result
share/mysql/test/suite/innodb/r/innodb_bug30919.result
share/mysql/test/suite/innodb/r/innodb_bug34053.result
share/mysql/test/suite/innodb/r/innodb_bug34300.result
share/mysql/test/suite/innodb/r/innodb_bug35220.result
share/mysql/test/suite/innodb/r/innodb_bug38231.result
share/mysql/test/suite/innodb/r/innodb_bug39438.result
share/mysql/test/suite/innodb/r/innodb_bug40360.result
share/mysql/test/suite/innodb/r/innodb_bug40565.result
share/mysql/test/suite/innodb/r/innodb_bug41904.result
share/mysql/test/suite/innodb/r/innodb_bug42101-nonzero.result
share/mysql/test/suite/innodb/r/innodb_bug42101.result
share/mysql/test/suite/innodb/r/innodb_bug42419.result
share/mysql/test/suite/innodb/r/innodb_bug44032.result
share/mysql/test/suite/innodb/r/innodb_bug44369.result
share/mysql/test/suite/innodb/r/innodb_bug44571.result
share/mysql/test/suite/innodb/r/innodb_bug45357.result
share/mysql/test/suite/innodb/r/innodb_bug46000.result
share/mysql/test/suite/innodb/r/innodb_bug46676.result
share/mysql/test/suite/innodb/r/innodb_bug47167.result
share/mysql/test/suite/innodb/r/innodb_bug47621.result
share/mysql/test/suite/innodb/r/innodb_bug47622.result
share/mysql/test/suite/innodb/r/innodb_bug47777.result
share/mysql/test/suite/innodb/r/innodb_bug48024.result
share/mysql/test/suite/innodb/r/innodb_bug49164.result
share/mysql/test/suite/innodb/r/innodb_bug51378.result
share/mysql/test/suite/innodb/r/innodb_bug51920.result
share/mysql/test/suite/innodb/r/innodb_bug52199.result
share/mysql/test/suite/innodb/r/innodb_bug52663.result
share/mysql/test/suite/innodb/r/innodb_bug53046.result
share/mysql/test/suite/innodb/r/innodb_bug53290.result
share/mysql/test/suite/innodb/r/innodb_bug53592.result
share/mysql/test/suite/innodb/r/innodb_bug53674.result
share/mysql/test/suite/innodb/r/innodb_bug53756.result
share/mysql/test/suite/innodb/r/innodb_bug54044.result
share/mysql/test/suite/innodb/r/innodb_bug56143.result
share/mysql/test/suite/innodb/r/innodb_bug56716.result
share/mysql/test/suite/innodb/r/innodb_bug56947.result
share/mysql/test/suite/innodb/r/innodb_bug57252.result
share/mysql/test/suite/innodb/r/innodb_bug57255.result
share/mysql/test/suite/innodb/r/innodb_bug57904.result
share/mysql/test/suite/innodb/r/innodb_bug59307.result
share/mysql/test/suite/innodb/r/innodb_bug59410.result
share/mysql/test/suite/innodb/r/innodb_bug59641.result
share/mysql/test/suite/innodb/r/innodb_bug59733.result
share/mysql/test/suite/innodb/r/innodb_bug60049.result
share/mysql/test/suite/innodb/r/innodb_bug60196.result
share/mysql/test/suite/innodb/r/innodb_bug60229.result
Changes 5.6.16: Functionality Added or Changed * InnoDB: New global configuration parameters, innodb_status_output and innodb_status_output_locks, allow you to dynamically enable and disable the standard InnoDB Monitor and InnoDB Lock Monitor for periodic output. Enabling and disabling monitors for periodic output by creating and dropping specially named tables is deprecated and may be removed in a future release. * Previously, ALTER TABLE in MySQL 5.6 could alter a table such that the result had temporal columns in both 5.5 and 5.6 format. Now ALTER TABLE upgrades old temporal columns to 5.6 format for ADD COLUMN, CHANGE COLUMN, MODIFY COLUMN, ADD INDEX, and FORCE operations. This conversion cannot be done using the INPLACE algorithm, so specifying ALGORITHM=INPLACE in these cases results in an error. * CMake now supports a -DTMPDIR=dir_name option to specify the default tmpdir value. If unspecified, the value defaults to P_tmpdir in <stdio.h>. Bugs Fixed * InnoDB; Replication: Using the InnoDB memcached plugin (see InnoDB Integration with memcached) with innodb_api_enable_binlog set to 1 caused the server to leak memory. * InnoDB: A boolean mode full-text search query would result in a memory access violation during parsing. * InnoDB: When new indexes are added by an ALTER TABLE operation, instead of only saving table-level statistics and statistics for the new indexes, InnoDB would save statistics for the entire table, including the table's other indexes. This behavior slowed ALTER TABLE performance. * InnoDB: Due to a parser error, full-text search queries that include a sub-expression could return the wrong result. * InnoDB: The innochecksum tool did not use a Windows-specific API to retrieve file size information, which resulted in an incorrect error message (Error: ibdata1 cannot be found) when the MySQL 5.6 innochecksum 2GB file size limit was exceeded. innochecksum now provides support for files larger than 2GB in both MySQL 5.6 and MySQL 5.7. * InnoDB: Due to a regression introduced by the fix for Bug17371537, memory was not allocated for the default memcached engine when using the default memcached engine as the backstore for data instead of InnoDB. * InnoDB: InnoDB would report an incorrect operating system error code after failing to initialize. * InnoDB: Manipulating a table after discarding its tablespace using ALTER TABLE ... DISCARD TABLESPACE could result in a serious error. * InnoDB: Persistent optimizer statistics would cause stalls due to latch contention. * InnoDB: MATCH() ... AGAINST queries that use a long string as an argument for AGAINST() could result in an error when run on an InnoDB table with a full-text search index. * InnoDB: An InnoDB full-text search failure would occur due to an “unended” token. The string and string length should be passed for string comparison. * InnoDB: In debug builds, a merge insert buffer during a page read would cause a memory access violation. * InnoDB: Truncating a memcached InnoDB table while memcached is performing DML operations would result in a serious error. * InnoDB: In sync0rw.ic, rw_lock_x_lock_func_nowait would needlessly call os_thread_get_curr_id. * InnoDB: Attempting to rename a table to a missing database would result in a serious error. more...
2014-02-13 08:49:56 +01:00
share/mysql/test/suite/innodb/r/innodb_bug70867.result
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/innodb/r/innodb_corrupt_bit.result
share/mysql/test/suite/innodb/r/innodb_ctype_ldml.result
share/mysql/test/suite/innodb/r/innodb_file_format.result
Changes 5.6.27: * InnoDB: The new innodb_numa_interleave read-only configuration option allows you to enable the NUMA interleave memory policy for allocation of the InnoDB buffer pool. When innodb_numa_interleave is enabled, the NUMA memory policy is set to MPOL_INTERLEAVE for the mysqld process. After the InnoDB buffer pool is allocated, the NUMA memory policy is set back to MPOL_DEFAULT. This option is only available on NUMA-enabled systems. * yaSSL was upgraded to version 2.3.8. * RPM .spec files were updated so that MySQL Server builds from source RPM packages will include the proper files to take advantage of operating system NUMA capabilities. This introduces a runtime dependency on libnuma.so.1. RPM and yum detect this and refuse to install if that library is not installed. * InnoDB: Reloading a table that was evicted while empty caused an AUTO_INCREMENT value to be reset. * InnoDB: Memory allocation sanity checks were added to the memcached code. * InnoDB: A memcached flush_all command raised an assertion. A function that starts a transaction was called from within assertion code. * InnoDB: A data corruption occurred on ARM64. GCC builtins did not issue the correct fences when setting or unsetting the lock word. * InnoDB: Server shutdown was delayed waiting for the purge thread to exit. To avoid this problem, the number of calls to trx_purge() was reduced, and the trx_purge() batch size was reduced to 20. * InnoDB: In READ COMMITTED mode, a REPLACE operation on a unique secondary index resulted in a constraint violation. * InnoDB: The IBUF_BITMAP_FREE bit indicated that there was more free space in the leaf page than was actually available. * InnoDB: Setting lower_case_table_names=0 on a case-insensitive file system could result in a hang condition when running an INSERT INTO ... SELECT ... FROM tbl_name operation with the wrong tbl_name letter case. An error message is now printed and the server exits when attempting to start the server with --lower_case_table_names=0 on a case-insensitive file system. * InnoDB: The server failed to start with an innodb_force_recovery setting greater than 3. InnoDB was set to read-only mode before redo logs were applied. * InnoDB: The trx_sys_read_pertable_file_format_id() function reported the wrong file format. * Partitioning: CREATE TABLE statements that used an invalid function in a subpartitioning expression did not always fail gracefully as expected. * Partitioning: Error handling for failed partitioning-related ALTER TABLE operations against non-partitioned tables was not performed correctly * Partitioning: ALTER TABLE when executed from a stored procedure did not always work correctly with tables partitioned by RANGE. * Replication: Repeatedly checking for ERR_LOCK_WAIT_TIMEOUT (as done, for example by repeatedly executing SHOW SLAVE STATUS) during a prolonged write lock on a table led to an assert. * Replication: If statement based logging was in use, when updating multiple tables in a single statement, a single transaction could be logged as two different transactions. This was due to the binary logging process not properly identifying statements which were operating over transactional tables. The fix ensures that they are correctly identified, even if such statements do not change the contents of the tables.
2015-10-03 14:46:13 +02:00
share/mysql/test/suite/innodb/r/innodb_force_recovery.result
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/innodb/r/innodb_gis.result
share/mysql/test/suite/innodb/r/innodb_i_s_innodb_locks.result
share/mysql/test/suite/innodb/r/innodb_i_s_innodb_trx.result
share/mysql/test/suite/innodb/r/innodb_information_schema_buffer.result
share/mysql/test/suite/innodb/r/innodb_lock_wait_timeout_1.result
share/mysql/test/suite/innodb/r/innodb_misc1.result
share/mysql/test/suite/innodb/r/innodb_multi_update.result
share/mysql/test/suite/innodb/r/innodb_mysql.result
share/mysql/test/suite/innodb/r/innodb_mysql_rbk.result
share/mysql/test/suite/innodb/r/innodb_notembedded.result
share/mysql/test/suite/innodb/r/innodb_page_size_func.result
share/mysql/test/suite/innodb/r/innodb_prefix_index_restart_server.result
share/mysql/test/suite/innodb/r/innodb_replace.result
share/mysql/test/suite/innodb/r/innodb_stats.result
share/mysql/test/suite/innodb/r/innodb_stats_auto_recalc.result
share/mysql/test/suite/innodb/r/innodb_stats_auto_recalc_ddl.result
share/mysql/test/suite/innodb/r/innodb_stats_auto_recalc_lots.result
share/mysql/test/suite/innodb/r/innodb_stats_auto_recalc_on_nonexistent.result
share/mysql/test/suite/innodb/r/innodb_stats_create_on_corrupted.result
share/mysql/test/suite/innodb/r/innodb_stats_create_table.result
share/mysql/test/suite/innodb/r/innodb_stats_drop_locked.result
Changes 5.6.19: Functionality Added or Changed The obsolete and unmaintained charset2html utility has been removed from MySQL distributions. The mysqlbug, mysql_waitpid, and mysql_zap utilities have been deprecated and will be removed in MySQL 5.7. Bugs Fixed InnoDB: After upgrading from 5.6.10 to MySQL versions up to and including MySQL 5.6.18, InnoDB would attempt to rename obsolete full-text search auxiliary tables on server startup, resulting in an assertion failure. InnoDB: For each insert, memset would be called three times to allocate memory for system fields. To reduce CPU usage, the three memset calls are now combined into a single call. InnoDB: Enabling the InnoDB Table Monitor would result in a ib_table->stat_initialized assertion failure. InnoDB: Setting innodb_max_dirty_pages_pct=0 would leave 1% of dirty pages unflushed. Buffer pool flushing is initiated when the percentage of dirty pages is greater innodb_max_dirty_pages_pct. The internal variables that store the innodb_max_dirty_pages_pct value and the percentage of dirty pages (buf_get_modified_ratio_pct and srv_max_buf_pool_modified_pct) were defined as unsigned integer data types, which meant that a innodb_max_dirty_pages_pct value of 0 required a dirty pages percentage of 1 or greater to initiate buffer pool flushing. To address this problem, the buf_get_modified_ratio_pct and srv_max_buf_pool_modified_pct internal variables are redefined as double data types, which changes the range value for innodb_max_dirty_pages_pct and innodb_max_dirty_pages_pct_lwm from 0 .. 99 to 0 .. 99.99. Additionally, buffer pool flushing is now initiated when the percentage of dirty pages is “greater than or equal to” innodb_max_dirty_pages_pct. Replication: Log rotation events could cause group_relay_log_pos to be moved forward incorrectly within a group. This meant that, when the transaction was retried, or if the SQL thread was stopped in the middle of a transaction following one or more log rotations (such that the transaction or group spanned multiple relay log files), part or all of the group was silently skipped. This issue has been addressed by correcting a problem in the logic used to avoid touching the coordinates of the SQL thread when updating the log position as part of a relay log rotation whereby it was possible to update the SQL thread's coordinates when not using a multi-threaded slave, even in the middle of a group. Replication: When running the server with --gtid-mode=ON, STOP SLAVE followed by START SLAVE resulted in a mismatch between the information provided by INFORMATION_SCHEMA.INNODB_TEMP_TABLE_INFO and the Slave_open_temp_tables status variable: the INNODB_TEMP_TABLE_INFO table showed that no temporary tables existed, but Slave_open_temp_tables had a nonzero value. Replication: In certain cases, the server mishandled triggers and stored procedures that tried to modify other tables when called by CREATE TABLE ... SELECT. This is now handled correctly as an error. Replication: When used on a table employing a transactional storage engine, a failed TRUNCATE TABLE was still written to the binary log and thus replayed on the slave. This could lead to inconsistency when the master retained data that was removed on the slave. Now in such cases TRUNCATE TABLE is logged only when it executes successfully. Replication: The server did not always handle the auto.cnf file correctly in cases where this file's permissions were incorrect. Replication: When the binary log was rotated due to receipt of a SIGHUP signal, the new binary log did not contain the Previous_gtid_event required for subsequent processing of that binary log's GTID events. Now when SIGHUP is received, steps are taken to insure that the server writes the necessary Previous_gtid_event to the new log before writing any GTID events to the new log.
2014-06-02 09:30:38 +02:00
share/mysql/test/suite/innodb/r/innodb_stats_external_pages.result
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/innodb/r/innodb_stats_fetch.result
share/mysql/test/suite/innodb/r/innodb_stats_fetch_corrupted.result
share/mysql/test/suite/innodb/r/innodb_stats_fetch_nonexistent.result
share/mysql/test/suite/innodb/r/innodb_stats_flag_global_off.result
share/mysql/test/suite/innodb/r/innodb_stats_flag_global_on.result
share/mysql/test/suite/innodb/r/innodb_stats_rename_table.result
share/mysql/test/suite/innodb/r/innodb_stats_rename_table_if_exists.result
share/mysql/test/suite/innodb/r/innodb_stats_sample_pages.result
share/mysql/test/suite/innodb/r/innodb_stats_table_flag_auto_recalc.result
share/mysql/test/suite/innodb/r/innodb_stats_table_flag_sample_pages.result
share/mysql/test/suite/innodb/r/innodb_timeout_rollback.result
share/mysql/test/suite/innodb/r/innodb_trx_weight.result
share/mysql/test/suite/innodb/r/innodb_upd_stats_if_needed_not_inited.result
share/mysql/test/suite/innodb/r/innodb_ut_format_name.result
Changes 5.6.22: * Noisy compiler warnings on FreeBSD 10 were silenced. * CMake workarounds for older Mac OS X and XCode versions were removed. On Mac OS X, compilation always uses Clang, even for 32-bit builds. * Previously, the MYSQL_MAINTAINER_MODE CMake option was turned on by default for debug builds and off for release builds, and MYSQL_MAINTAINER_MODE caused -Werror to be enabled when building with GCC. This made it cumbersome to enable -Werror under certain conditions, such as when compiling with Clang. * Build support was modified to produce the same warnings for Clang as for gcc. * CMake configuration for the Clang compiler sets more appropriate flags for building on Linux. Specifically, -g -fno-omit-frame-pointer -fno-strict-aliasing is now added. * Bugs fixed.
2014-12-02 13:40:09 +01:00
share/mysql/test/suite/innodb/r/insert_debug.result
Changes 5.6.23: * The linked OpenSSL library for the MySQL Commercial Server has been updated from version 1.0.1j to version 1.0.1k. * Support for the SSL 2.0 and SSL 3.0 protocols has been disabled because they provide weak encryption. * yaSSL was upgraded to version 2.3.7. * The valid date range of the SSL certificates in mysql-test/std_data has been extended to the year 2029. * Bugs Fixed
2015-02-07 20:23:40 +01:00
share/mysql/test/suite/innodb/r/monitor.result
share/mysql/test/suite/innodb/r/monitor_debug.result
Changes 5.6.22: * Noisy compiler warnings on FreeBSD 10 were silenced. * CMake workarounds for older Mac OS X and XCode versions were removed. On Mac OS X, compilation always uses Clang, even for 32-bit builds. * Previously, the MYSQL_MAINTAINER_MODE CMake option was turned on by default for debug builds and off for release builds, and MYSQL_MAINTAINER_MODE caused -Werror to be enabled when building with GCC. This made it cumbersome to enable -Werror under certain conditions, such as when compiling with Clang. * Build support was modified to produce the same warnings for Clang as for gcc. * CMake configuration for the Clang compiler sets more appropriate flags for building on Linux. Specifically, -g -fno-omit-frame-pointer -fno-strict-aliasing is now added. * Bugs fixed.
2014-12-02 13:40:09 +01:00
share/mysql/test/suite/innodb/r/sp_temp_table.result
Changes 5.6.25: Functionality Added or Changed * MySQL Enterprise Firewall operates on parser states and does not work well together with the query cache, which circumvents the parser. MySQL Enterprise Firewall now checks whether the query cache is enabled. If so, it displays a message that the query cache must be disabled and does not load. * my_print_defaults now masks passwords. To display passwords in cleartext, use the new --show option. * MySQL distributions now include an innodb_stress suite of test cases. Thanks to Mark Callaghan for the contribution. Bugs Fixed * InnoDB; Partitioning: The CREATE_TIME column of the INFORMATION_SCHEMA.TABLES table now shows the correct table creation time for partitioned InnoDB tables. The CREATE_TIME column of the INFORMATION_SCHEMA.PARTITIONS table now shows the correct partition creation time for a partition of partitioned InnoDB tables. The UPDATE_TIME column of the INFORMATION_SCHEMA.TABLES table now shows when a partitioned InnoDB table was last updated by an INSERT, DELETE, or UPDATE. The UPDATE_TIME column of the INFORMATION_SCHEMA.PARTITIONS table now shows when a partition of a partitioned InnoDB table was last updated. * InnoDB: An assertion was raised on shutdown due to XA PREPARE transactions holding explicit locks. * InnoDB: The strict_* forms of innodb_checksum_algorithm settings (strict_none, strict_innodb, and strict_crc32) caused the server to halt when a non-matching checksum was encountered, even though the non-matching checksum was valid. For example, with innodb_checksum_algorithm=strict_crc32, encountering a valid innodb checksum caused the server to halt. Instead of halting the server, a message is now printed to the error log and the page is accepted as valid if it matches an innodb, crc32 or none checksum. * InnoDB: The memcached set command permitted a negative expire time value. Expire time is stored internally as an unsigned integer. A negative value would be converted to a large number and accepted. The maximum expire time value is now restricted to INT_MAX32 to prevent negative expire time values. * InnoDB: Removal of a foreign key object from the data dictionary cache during error handling caused the server to exit. * InnoDB: SHOW ENGINE INNODB STATUS output showed negative reservation and signal count values due to a counter overflow error. * InnoDB: Failure to check the status of a cursor transaction read-only option before reusing the cursor transaction for a write operation resulted in a server exit during a memcached workload. * InnoDB: MDL locks taken by memcached clients caused a MySQL Enterprise Backup FLUSH TABLES WITH READ LOCK operation to hang. * InnoDB: Estimates that were too low for the size of merge chunks in the result sorting algorithm caused a server exit. * InnoDB: For full-text searches, the optimizer could choose an index that does not produce correct relevancy rankings. * Partitioning: When creating a partitioned table, partition-level DATA DIRECTORY or INDEX DIRECTORY option values that contained an excessive number of characters were handled incorrectly. * Partitioning: Executing an ALTER TABLE on a partitioned table on which a write lock was in effect could cause subsequent SQL statements on this table to fail. * Replication: When binary logging was enabled, using stored functions and triggers resulting in a long running procedure that inserted many records caused the memory use to increase rapidly. This was due to memory being allocated per variable. The fix ensures that in such a situation, memory is allocated once and the same memory is reused. * Replication: If an error was encountered while adding a GTID to the received GTID set, the log lock was not being correctly released. This could cause a deadlock. more...
2015-06-01 10:15:05 +02:00
share/mysql/test/suite/innodb/r/strict_checksum.result
Changes 5.6.22: * Noisy compiler warnings on FreeBSD 10 were silenced. * CMake workarounds for older Mac OS X and XCode versions were removed. On Mac OS X, compilation always uses Clang, even for 32-bit builds. * Previously, the MYSQL_MAINTAINER_MODE CMake option was turned on by default for debug builds and off for release builds, and MYSQL_MAINTAINER_MODE caused -Werror to be enabled when building with GCC. This made it cumbersome to enable -Werror under certain conditions, such as when compiling with Clang. * Build support was modified to produce the same warnings for Clang as for gcc. * CMake configuration for the Clang compiler sets more appropriate flags for building on Linux. Specifically, -g -fno-omit-frame-pointer -fno-strict-aliasing is now added. * Bugs fixed.
2014-12-02 13:40:09 +01:00
share/mysql/test/suite/innodb/r/strict_mode.result
Changes 5.6.29: * InnoDB: A new InnoDB configuration option, innodb_tmpdir, allows you to configure a separate temporary file directory for online ALTER TABLE operations. This option was introduced to help avoid tmpdir overflows that could occur as a result of large temporary files created during online ALTER TABLE operations. innodb_tmpdir is a SESSION variable and can be configured dynamically using a SET statement. * yaSSL was upgraded to version 2.3.9. This upgrade corrects an issue in which yaSSL handled only cases of zero or one leading zeros for the key agreement instead of potentially any number, which in rare cases could cause connections to fail when using DHE cipher suites. * The Valgrind function signature in mysql-test/valgrind.supp was upgraded for Valgrind 3.11. * Bugs Fixed
2016-02-28 09:58:03 +01:00
share/mysql/test/suite/innodb/r/tmpdir.result
Changes 5.6.25: Functionality Added or Changed * MySQL Enterprise Firewall operates on parser states and does not work well together with the query cache, which circumvents the parser. MySQL Enterprise Firewall now checks whether the query cache is enabled. If so, it displays a message that the query cache must be disabled and does not load. * my_print_defaults now masks passwords. To display passwords in cleartext, use the new --show option. * MySQL distributions now include an innodb_stress suite of test cases. Thanks to Mark Callaghan for the contribution. Bugs Fixed * InnoDB; Partitioning: The CREATE_TIME column of the INFORMATION_SCHEMA.TABLES table now shows the correct table creation time for partitioned InnoDB tables. The CREATE_TIME column of the INFORMATION_SCHEMA.PARTITIONS table now shows the correct partition creation time for a partition of partitioned InnoDB tables. The UPDATE_TIME column of the INFORMATION_SCHEMA.TABLES table now shows when a partitioned InnoDB table was last updated by an INSERT, DELETE, or UPDATE. The UPDATE_TIME column of the INFORMATION_SCHEMA.PARTITIONS table now shows when a partition of a partitioned InnoDB table was last updated. * InnoDB: An assertion was raised on shutdown due to XA PREPARE transactions holding explicit locks. * InnoDB: The strict_* forms of innodb_checksum_algorithm settings (strict_none, strict_innodb, and strict_crc32) caused the server to halt when a non-matching checksum was encountered, even though the non-matching checksum was valid. For example, with innodb_checksum_algorithm=strict_crc32, encountering a valid innodb checksum caused the server to halt. Instead of halting the server, a message is now printed to the error log and the page is accepted as valid if it matches an innodb, crc32 or none checksum. * InnoDB: The memcached set command permitted a negative expire time value. Expire time is stored internally as an unsigned integer. A negative value would be converted to a large number and accepted. The maximum expire time value is now restricted to INT_MAX32 to prevent negative expire time values. * InnoDB: Removal of a foreign key object from the data dictionary cache during error handling caused the server to exit. * InnoDB: SHOW ENGINE INNODB STATUS output showed negative reservation and signal count values due to a counter overflow error. * InnoDB: Failure to check the status of a cursor transaction read-only option before reusing the cursor transaction for a write operation resulted in a server exit during a memcached workload. * InnoDB: MDL locks taken by memcached clients caused a MySQL Enterprise Backup FLUSH TABLES WITH READ LOCK operation to hang. * InnoDB: Estimates that were too low for the size of merge chunks in the result sorting algorithm caused a server exit. * InnoDB: For full-text searches, the optimizer could choose an index that does not produce correct relevancy rankings. * Partitioning: When creating a partitioned table, partition-level DATA DIRECTORY or INDEX DIRECTORY option values that contained an excessive number of characters were handled incorrectly. * Partitioning: Executing an ALTER TABLE on a partitioned table on which a write lock was in effect could cause subsequent SQL statements on this table to fail. * Replication: When binary logging was enabled, using stored functions and triggers resulting in a long running procedure that inserted many records caused the memory use to increase rapidly. This was due to memory being allocated per variable. The fix ensures that in such a situation, memory is allocated once and the same memory is reused. * Replication: If an error was encountered while adding a GTID to the received GTID set, the log lock was not being correctly released. This could cause a deadlock. more...
2015-06-01 10:15:05 +02:00
share/mysql/test/suite/innodb/r/xa_recovery.result
Changes 5.6.21: The --skip-innodb option is now deprecated and its use results in a warning. It will be removed in a future MySQL release. This also applies to its synonyms (--innodb=OFF, --disable-innodb, and so forth). MySQL Enterprise Edition now includes a set of encryption functions based on the OpenSSL library that expose OpenSSL capabilities at the SQL level. Replication: The new variable simplified_binlog_gtid_recovery can be used to change the way binary log files are searched for previous GTIDs during recovery, speeding up the process when a large number of binary log files exist. Internally, spatial data types such as Geometry are represented as BLOB values, so when invoked with the --hex-blob option, mysqldump now displays spatial values in hex. Bugs Fixed...
2014-10-01 10:34:23 +02:00
share/mysql/test/suite/innodb/t/add_foreign_key.test
Changes 5.6.28: MySQL Server RPM packages now contain a conflict indicator for MySQL Connector C, such that an error occurs when installing MySQL Server if MySQL Connector C is also installed. To install MySQL Server, remove any MySQL Connector C packages first. mysql_upgrade now attempts to print more informative errors than FATAL ERROR: Upgrade failed. These client programs now support the --enable-cleartext-plugin option: mysqlcheck, mysqldump, mysqlimport, mysqlshow. This option enables the mysql_clear_password cleartext authentication plugin. (See The Cleartext Client-Side Authentication Plugin.) Support for building with Solaris Studio 5.13 was added. Performance Schema digests in DIGEST_TEXT columns have ... appended to the end to indicate when statements exceed the maximum statement size and were truncated. This is also now done for statement text values in SQL_TEXT columns. Bugs Fixed
2015-12-08 09:49:50 +01:00
share/mysql/test/suite/innodb/t/alter_rename_existing.test
Changes 5.6.29: * InnoDB: A new InnoDB configuration option, innodb_tmpdir, allows you to configure a separate temporary file directory for online ALTER TABLE operations. This option was introduced to help avoid tmpdir overflows that could occur as a result of large temporary files created during online ALTER TABLE operations. innodb_tmpdir is a SESSION variable and can be configured dynamically using a SET statement. * yaSSL was upgraded to version 2.3.9. This upgrade corrects an issue in which yaSSL handled only cases of zero or one leading zeros for the key agreement instead of potentially any number, which in rare cases could cause connections to fail when using DHE cipher suites. * The Valgrind function signature in mysql-test/valgrind.supp was upgraded for Valgrind 3.11. * Bugs Fixed
2016-02-28 09:58:03 +01:00
share/mysql/test/suite/innodb/t/analyze_table.test
Changes 5.6.17: Functionality Added or Changed Incompatible Change: The AES_ENCRYPT() and AES_DECRYPT() functions now permit control of the block encryption mode and take an optional initialization vector argument: The new block_encryption_mode system variable controls the mode for block-based encryption algorithms. Its default value is aes-128-ecb, which signifies encryption using a key length of 128 bits and ECB mode. An optional init_vector argument provides an initialization vector for encryption modes that require it: AES_ENCRYPT(str,key_str[,init_vector]) AES_DECRYPT(crypt_str,key_str[,init_vector]) A random string of bytes to use for the initialization vector can be produced by calling the new RANDOM_BYTES() function. For more information, see Encryption and Compression Functions. These changes make statements that use AES_ENCRYPT() or AES_DECRYPT() unsafe for statement-based replication and they cannot be stored in the query cache. Queries that use RANDOM_BYTES() are unsafe for statement-based replication and cannot be stored in the query cache. Incompatible Change: The ERROR_FOR_DIVISION_BY_ZERO, NO_ZERO_DATE, and NO_ZERO_IN_DATE SQL modes now are deprecated and setting the sql_mode value to include any of them generates a warning. In MySQL 5.7, these modes do nothing. Instead, their effects are included in the effects of strict SQL mode (STRICT_ALL_TABLES or STRICT_TRANS_TABLES). The motivation for the change in MySQL 5.7 is to reduce the number of SQL modes with an effect dependent on strict mode and make them part of strict mode itself. To make advance preparation for an upgrade to MySQL 5.7, see SQL Mode Changes in MySQL 5.7. That discussion provides guidelines to assess whether your applications will be affected by the SQL mode changes in MySQL 5.7. InnoDB: MySQL now supports rebuilding regular and partitioned InnoDB tables using online DDL (ALGORITHM=INPLACE) for the following operations: OPTIMIZE TABLE ALTER TABLE ... FORCE ALTER TABLE ... ENGINE=INNODB (when run on an InnoDB table) Online DDL support reduces table rebuild time and permits concurrent DML, which helps reduce user application downtime. For additional information, see Overview of Online DDL. On Solaris, mysql_config --libs now includes -R/path/to/library so that libraries can be found at runtime. mysql_install_db provides a more informative diagnostic message when required Perl modules are missing. The IGNORE clause for ALTER TABLE is now deprecated and will be removed in a future version of MySQL. ALTER IGNORE TABLE causes problems for replication, prevents online ALTER TABLE for unique index creation, and causes problems with foreign keys (rows removed in the parent table). Bugs Fixed
2014-03-31 12:32:13 +02:00
share/mysql/test/suite/innodb/t/blob-update-debug.test
Changes 5.6.22: * Noisy compiler warnings on FreeBSD 10 were silenced. * CMake workarounds for older Mac OS X and XCode versions were removed. On Mac OS X, compilation always uses Clang, even for 32-bit builds. * Previously, the MYSQL_MAINTAINER_MODE CMake option was turned on by default for debug builds and off for release builds, and MYSQL_MAINTAINER_MODE caused -Werror to be enabled when building with GCC. This made it cumbersome to enable -Werror under certain conditions, such as when compiling with Clang. * Build support was modified to produce the same warnings for Clang as for gcc. * CMake configuration for the Clang compiler sets more appropriate flags for building on Linux. Specifically, -g -fno-omit-frame-pointer -fno-strict-aliasing is now added. * Bugs fixed.
2014-12-02 13:40:09 +01:00
share/mysql/test/suite/innodb/t/blob_redo-master.opt
share/mysql/test/suite/innodb/t/blob_redo.test
share/mysql/test/suite/innodb/t/checksum.test
Changes 5.6.17: Functionality Added or Changed Incompatible Change: The AES_ENCRYPT() and AES_DECRYPT() functions now permit control of the block encryption mode and take an optional initialization vector argument: The new block_encryption_mode system variable controls the mode for block-based encryption algorithms. Its default value is aes-128-ecb, which signifies encryption using a key length of 128 bits and ECB mode. An optional init_vector argument provides an initialization vector for encryption modes that require it: AES_ENCRYPT(str,key_str[,init_vector]) AES_DECRYPT(crypt_str,key_str[,init_vector]) A random string of bytes to use for the initialization vector can be produced by calling the new RANDOM_BYTES() function. For more information, see Encryption and Compression Functions. These changes make statements that use AES_ENCRYPT() or AES_DECRYPT() unsafe for statement-based replication and they cannot be stored in the query cache. Queries that use RANDOM_BYTES() are unsafe for statement-based replication and cannot be stored in the query cache. Incompatible Change: The ERROR_FOR_DIVISION_BY_ZERO, NO_ZERO_DATE, and NO_ZERO_IN_DATE SQL modes now are deprecated and setting the sql_mode value to include any of them generates a warning. In MySQL 5.7, these modes do nothing. Instead, their effects are included in the effects of strict SQL mode (STRICT_ALL_TABLES or STRICT_TRANS_TABLES). The motivation for the change in MySQL 5.7 is to reduce the number of SQL modes with an effect dependent on strict mode and make them part of strict mode itself. To make advance preparation for an upgrade to MySQL 5.7, see SQL Mode Changes in MySQL 5.7. That discussion provides guidelines to assess whether your applications will be affected by the SQL mode changes in MySQL 5.7. InnoDB: MySQL now supports rebuilding regular and partitioned InnoDB tables using online DDL (ALGORITHM=INPLACE) for the following operations: OPTIMIZE TABLE ALTER TABLE ... FORCE ALTER TABLE ... ENGINE=INNODB (when run on an InnoDB table) Online DDL support reduces table rebuild time and permits concurrent DML, which helps reduce user application downtime. For additional information, see Overview of Online DDL. On Solaris, mysql_config --libs now includes -R/path/to/library so that libraries can be found at runtime. mysql_install_db provides a more informative diagnostic message when required Perl modules are missing. The IGNORE clause for ALTER TABLE is now deprecated and will be removed in a future version of MySQL. ALTER IGNORE TABLE causes problems for replication, prevents online ALTER TABLE for unique index creation, and causes problems with foreign keys (rows removed in the parent table). Bugs Fixed
2014-03-31 12:32:13 +02:00
share/mysql/test/suite/innodb/t/create-index.test
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/innodb/t/disabled.def
Changes 5.6.26: * Security Fix: Due to the LogJam issue (https://weakdh.org/), OpenSSL has changed the Diffie-Hellman key length parameters for openssl-1.0.1n and up. * Replication: When using a multi-threaded slave, each worker thread has its own queue of transactions to process. In previous MySQL versions, STOP SLAVE waited for all workers to process their entire queue. This logic has been changed so that STOP SLAVE first finds the newest transaction that was committed by any worker thread. Then, it waits for all workers to complete transactions older than that. Newer transactions are not processed. The new logic allows STOP SLAVE to complete faster in case some worker queues contain multiple transactions. * Previously, the max_digest_length system variable controlled the maximum digest length for all server functions that computed statement digests. However, whereas the Performance Schema may need to maintain many digest values, other server functions such as MySQL Enterprise Firewall need only one digest per session. Increasing the max_digest_length value has little impact on total memory requirements for those functions, but can increase Performance Schema memory requirements significantly. To enable configuring digest length separately for the Performance Schema, its digest length is now controlled by the new performance_schema_max_digest_length system variable. * Previously, changes to the validate_password plugin dictionary file (named by the validate_password_dictionary_file system variable) while the server was running required a restart for the server to recognize the changes. Now validate_password_dictionary_file can be set at runtime and assigning a value causes the named file to be read without a restart. In addition, two new status variables are available. validate_password_dictionary_file_last_parsed indicates when the dictionary file was last read, and validate_password_dictionary_file_words_count indicates how many words it contains. * Bugs fixed
2015-07-30 16:39:18 +02:00
share/mysql/test/suite/innodb/t/dropdb.test
Changes 5.6.20: Security Fix: The linked OpenSSL library for the MySQL 5.6 Commercial Server has been updated from version 1.0.1g to version 1.0.1h. Versions of OpenSSL prior to and including 1.0.1g are reported to be vulnerable to CVE-2014-0224. This change does not affect the Oracle-produced MySQL Community build of MySQL Server 5.6, which uses the yaSSL library instead. DTrace Support MySQL now includes DTrace support on Oracle Linux 6 or higher with UEK kernel. If DTrace is present, server builds will detect it with no special CMake options required. For information about using DTrace on MySQL, see Tracing mysqld Using DTrace. InnoDB Notes Important Change: Redo log writes for large, externally stored BLOB fields could overwrite the most recent checkpoint. The 5.6.20 patch limits the size of redo log BLOB writes to 10% of the redo log file size. The 5.7.5 patch addresses the bug without imposing a limitation. For MySQL 5.5, the bug remains a known limitation. As a result of the redo log BLOB write limit introduced for MySQL 5.6, innodb_log_file_size should be set to a value greater than 10 times the largest BLOB data size found in the rows of your tables plus the length of other variable length fields (VARCHAR, VARBINARY, and TEXT type fields). Failing to do so could result in “Row size too large” errors. No action is required if your innodb_log_file_size setting is already sufficiently large or your tables contain no BLOB data. Functionality Added or Changed Replication: The new system variable binlog_impossible_mode controls what happens if the server cannot write to the binary log, for example, due to a file error. For backward compatibility, the default for binlog_impossible_mode is IGNORE_ERROR, meaning the server logs the error, halts logging, and continues updates to the database. Setting this variable to ABORT_SERVER makes the server halt logging and shut down if it cannot write to the binary log. CMake support was updated to handle CMake version 3. New Debian7, Ubuntu12.04, and Ubuntu14.04 distribution support that was introduced with 5.6.17 now comes with the platform-specific packaging source placed under the packaging directory, in the deb-precise, deb-wheezy, and deb-trusty directories. Support for LinuxThreads has been removed from the source code. LinuxThreads was superseded by NPTL in Linux 2.6. By default, mysql_install_db creates a my.cnf file in the installation base directory using a template. This may be undesireable for some deployments. To enable this behavior to be suppressed, mysql_install_db now supports a --keep-my-cnf option to preserve any existing my.cnf file and not create a new my.cnf file. The mysqlhotcopy utility is now deprecated and will be removed in a future version of MySQL. Among the reasons for this: It works only for the MyISAM and ARCHIVE storage engines; it works on Unix but not Windows. Alternatives include mysqldump and MySQL Enterprise Backup. The timed_mutexes system variable has no effect and is deprecated. Bugs Fixed
2014-08-10 17:11:57 +02:00
share/mysql/test/suite/innodb/t/foreign_key.test
Changes 5.6.26: * Security Fix: Due to the LogJam issue (https://weakdh.org/), OpenSSL has changed the Diffie-Hellman key length parameters for openssl-1.0.1n and up. * Replication: When using a multi-threaded slave, each worker thread has its own queue of transactions to process. In previous MySQL versions, STOP SLAVE waited for all workers to process their entire queue. This logic has been changed so that STOP SLAVE first finds the newest transaction that was committed by any worker thread. Then, it waits for all workers to complete transactions older than that. Newer transactions are not processed. The new logic allows STOP SLAVE to complete faster in case some worker queues contain multiple transactions. * Previously, the max_digest_length system variable controlled the maximum digest length for all server functions that computed statement digests. However, whereas the Performance Schema may need to maintain many digest values, other server functions such as MySQL Enterprise Firewall need only one digest per session. Increasing the max_digest_length value has little impact on total memory requirements for those functions, but can increase Performance Schema memory requirements significantly. To enable configuring digest length separately for the Performance Schema, its digest length is now controlled by the new performance_schema_max_digest_length system variable. * Previously, changes to the validate_password plugin dictionary file (named by the validate_password_dictionary_file system variable) while the server was running required a restart for the server to recognize the changes. Now validate_password_dictionary_file can be set at runtime and assigning a value causes the named file to be read without a restart. In addition, two new status variables are available. validate_password_dictionary_file_last_parsed indicates when the dictionary file was last read, and validate_password_dictionary_file_words_count indicates how many words it contains. * Bugs fixed
2015-07-30 16:39:18 +02:00
share/mysql/test/suite/innodb/t/import.test
Changes 5.6.21: The --skip-innodb option is now deprecated and its use results in a warning. It will be removed in a future MySQL release. This also applies to its synonyms (--innodb=OFF, --disable-innodb, and so forth). MySQL Enterprise Edition now includes a set of encryption functions based on the OpenSSL library that expose OpenSSL capabilities at the SQL level. Replication: The new variable simplified_binlog_gtid_recovery can be used to change the way binary log files are searched for previous GTIDs during recovery, speeding up the process when a large number of binary log files exist. Internally, spatial data types such as Geometry are represented as BLOB values, so when invoked with the --hex-blob option, mysqldump now displays spatial values in hex. Bugs Fixed...
2014-10-01 10:34:23 +02:00
share/mysql/test/suite/innodb/t/index_tree_operation.test
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/innodb/t/innodb-2byte-collation-master.opt
share/mysql/test/suite/innodb/t/innodb-2byte-collation.test
share/mysql/test/suite/innodb/t/innodb-ac-non-locking-select.test
share/mysql/test/suite/innodb/t/innodb-alter-autoinc.test
share/mysql/test/suite/innodb/t/innodb-alter-debug.test
share/mysql/test/suite/innodb/t/innodb-alter-discard.test
share/mysql/test/suite/innodb/t/innodb-alter-nullable.test
Changes 5.6.21: The --skip-innodb option is now deprecated and its use results in a warning. It will be removed in a future MySQL release. This also applies to its synonyms (--innodb=OFF, --disable-innodb, and so forth). MySQL Enterprise Edition now includes a set of encryption functions based on the OpenSSL library that expose OpenSSL capabilities at the SQL level. Replication: The new variable simplified_binlog_gtid_recovery can be used to change the way binary log files are searched for previous GTIDs during recovery, speeding up the process when a large number of binary log files exist. Internally, spatial data types such as Geometry are represented as BLOB values, so when invoked with the --hex-blob option, mysqldump now displays spatial values in hex. Bugs Fixed...
2014-10-01 10:34:23 +02:00
share/mysql/test/suite/innodb/t/innodb-alter-tempfile.test
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/innodb/t/innodb-alter.test
share/mysql/test/suite/innodb/t/innodb-analyze.test
share/mysql/test/suite/innodb/t/innodb-autoinc-18274.test
share/mysql/test/suite/innodb/t/innodb-autoinc-44030-master.opt
share/mysql/test/suite/innodb/t/innodb-autoinc-44030.test
share/mysql/test/suite/innodb/t/innodb-autoinc-56228-master.opt
share/mysql/test/suite/innodb/t/innodb-autoinc-56228.test
share/mysql/test/suite/innodb/t/innodb-autoinc-master.opt
share/mysql/test/suite/innodb/t/innodb-autoinc-optimize.test
share/mysql/test/suite/innodb/t/innodb-autoinc.test
share/mysql/test/suite/innodb/t/innodb-blob.test
share/mysql/test/suite/innodb/t/innodb-bug-14068765.test
share/mysql/test/suite/innodb/t/innodb-bug-14084530.test
share/mysql/test/suite/innodb/t/innodb-bug12552164.test
share/mysql/test/suite/innodb/t/innodb-bug14219515.test
Changes 5.6.16: Functionality Added or Changed * InnoDB: New global configuration parameters, innodb_status_output and innodb_status_output_locks, allow you to dynamically enable and disable the standard InnoDB Monitor and InnoDB Lock Monitor for periodic output. Enabling and disabling monitors for periodic output by creating and dropping specially named tables is deprecated and may be removed in a future release. * Previously, ALTER TABLE in MySQL 5.6 could alter a table such that the result had temporal columns in both 5.5 and 5.6 format. Now ALTER TABLE upgrades old temporal columns to 5.6 format for ADD COLUMN, CHANGE COLUMN, MODIFY COLUMN, ADD INDEX, and FORCE operations. This conversion cannot be done using the INPLACE algorithm, so specifying ALGORITHM=INPLACE in these cases results in an error. * CMake now supports a -DTMPDIR=dir_name option to specify the default tmpdir value. If unspecified, the value defaults to P_tmpdir in <stdio.h>. Bugs Fixed * InnoDB; Replication: Using the InnoDB memcached plugin (see InnoDB Integration with memcached) with innodb_api_enable_binlog set to 1 caused the server to leak memory. * InnoDB: A boolean mode full-text search query would result in a memory access violation during parsing. * InnoDB: When new indexes are added by an ALTER TABLE operation, instead of only saving table-level statistics and statistics for the new indexes, InnoDB would save statistics for the entire table, including the table's other indexes. This behavior slowed ALTER TABLE performance. * InnoDB: Due to a parser error, full-text search queries that include a sub-expression could return the wrong result. * InnoDB: The innochecksum tool did not use a Windows-specific API to retrieve file size information, which resulted in an incorrect error message (Error: ibdata1 cannot be found) when the MySQL 5.6 innochecksum 2GB file size limit was exceeded. innochecksum now provides support for files larger than 2GB in both MySQL 5.6 and MySQL 5.7. * InnoDB: Due to a regression introduced by the fix for Bug17371537, memory was not allocated for the default memcached engine when using the default memcached engine as the backstore for data instead of InnoDB. * InnoDB: InnoDB would report an incorrect operating system error code after failing to initialize. * InnoDB: Manipulating a table after discarding its tablespace using ALTER TABLE ... DISCARD TABLESPACE could result in a serious error. * InnoDB: Persistent optimizer statistics would cause stalls due to latch contention. * InnoDB: MATCH() ... AGAINST queries that use a long string as an argument for AGAINST() could result in an error when run on an InnoDB table with a full-text search index. * InnoDB: An InnoDB full-text search failure would occur due to an “unended” token. The string and string length should be passed for string comparison. * InnoDB: In debug builds, a merge insert buffer during a page read would cause a memory access violation. * InnoDB: Truncating a memcached InnoDB table while memcached is performing DML operations would result in a serious error. * InnoDB: In sync0rw.ic, rw_lock_x_lock_func_nowait would needlessly call os_thread_get_curr_id. * InnoDB: Attempting to rename a table to a missing database would result in a serious error. more...
2014-02-13 08:49:56 +01:00
share/mysql/test/suite/innodb/t/innodb-change-buffer-recovery-master.opt
share/mysql/test/suite/innodb/t/innodb-change-buffer-recovery.test
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/innodb/t/innodb-consistent-master.opt
share/mysql/test/suite/innodb/t/innodb-consistent.test
Changes 5.6.17: Functionality Added or Changed Incompatible Change: The AES_ENCRYPT() and AES_DECRYPT() functions now permit control of the block encryption mode and take an optional initialization vector argument: The new block_encryption_mode system variable controls the mode for block-based encryption algorithms. Its default value is aes-128-ecb, which signifies encryption using a key length of 128 bits and ECB mode. An optional init_vector argument provides an initialization vector for encryption modes that require it: AES_ENCRYPT(str,key_str[,init_vector]) AES_DECRYPT(crypt_str,key_str[,init_vector]) A random string of bytes to use for the initialization vector can be produced by calling the new RANDOM_BYTES() function. For more information, see Encryption and Compression Functions. These changes make statements that use AES_ENCRYPT() or AES_DECRYPT() unsafe for statement-based replication and they cannot be stored in the query cache. Queries that use RANDOM_BYTES() are unsafe for statement-based replication and cannot be stored in the query cache. Incompatible Change: The ERROR_FOR_DIVISION_BY_ZERO, NO_ZERO_DATE, and NO_ZERO_IN_DATE SQL modes now are deprecated and setting the sql_mode value to include any of them generates a warning. In MySQL 5.7, these modes do nothing. Instead, their effects are included in the effects of strict SQL mode (STRICT_ALL_TABLES or STRICT_TRANS_TABLES). The motivation for the change in MySQL 5.7 is to reduce the number of SQL modes with an effect dependent on strict mode and make them part of strict mode itself. To make advance preparation for an upgrade to MySQL 5.7, see SQL Mode Changes in MySQL 5.7. That discussion provides guidelines to assess whether your applications will be affected by the SQL mode changes in MySQL 5.7. InnoDB: MySQL now supports rebuilding regular and partitioned InnoDB tables using online DDL (ALGORITHM=INPLACE) for the following operations: OPTIMIZE TABLE ALTER TABLE ... FORCE ALTER TABLE ... ENGINE=INNODB (when run on an InnoDB table) Online DDL support reduces table rebuild time and permits concurrent DML, which helps reduce user application downtime. For additional information, see Overview of Online DDL. On Solaris, mysql_config --libs now includes -R/path/to/library so that libraries can be found at runtime. mysql_install_db provides a more informative diagnostic message when required Perl modules are missing. The IGNORE clause for ALTER TABLE is now deprecated and will be removed in a future version of MySQL. ALTER IGNORE TABLE causes problems for replication, prevents online ALTER TABLE for unique index creation, and causes problems with foreign keys (rows removed in the parent table). Bugs Fixed
2014-03-31 12:32:13 +02:00
share/mysql/test/suite/innodb/t/innodb-double-write.test
Changes 5.6.29: * InnoDB: A new InnoDB configuration option, innodb_tmpdir, allows you to configure a separate temporary file directory for online ALTER TABLE operations. This option was introduced to help avoid tmpdir overflows that could occur as a result of large temporary files created during online ALTER TABLE operations. innodb_tmpdir is a SESSION variable and can be configured dynamically using a SET statement. * yaSSL was upgraded to version 2.3.9. This upgrade corrects an issue in which yaSSL handled only cases of zero or one leading zeros for the key agreement instead of potentially any number, which in rare cases could cause connections to fail when using DHE cipher suites. * The Valgrind function signature in mysql-test/valgrind.supp was upgraded for Valgrind 3.11. * Bugs Fixed
2016-02-28 09:58:03 +01:00
share/mysql/test/suite/innodb/t/innodb-index-debug-master.opt
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/innodb/t/innodb-index-debug.test
share/mysql/test/suite/innodb/t/innodb-index-online-delete.test
share/mysql/test/suite/innodb/t/innodb-index-online-fk.test
share/mysql/test/suite/innodb/t/innodb-index-online-master.opt
share/mysql/test/suite/innodb/t/innodb-index-online-purge.test
share/mysql/test/suite/innodb/t/innodb-index-online.test
share/mysql/test/suite/innodb/t/innodb-index.test
share/mysql/test/suite/innodb/t/innodb-index_ucs2.test
Changes 5.6.27: * InnoDB: The new innodb_numa_interleave read-only configuration option allows you to enable the NUMA interleave memory policy for allocation of the InnoDB buffer pool. When innodb_numa_interleave is enabled, the NUMA memory policy is set to MPOL_INTERLEAVE for the mysqld process. After the InnoDB buffer pool is allocated, the NUMA memory policy is set back to MPOL_DEFAULT. This option is only available on NUMA-enabled systems. * yaSSL was upgraded to version 2.3.8. * RPM .spec files were updated so that MySQL Server builds from source RPM packages will include the proper files to take advantage of operating system NUMA capabilities. This introduces a runtime dependency on libnuma.so.1. RPM and yum detect this and refuse to install if that library is not installed. * InnoDB: Reloading a table that was evicted while empty caused an AUTO_INCREMENT value to be reset. * InnoDB: Memory allocation sanity checks were added to the memcached code. * InnoDB: A memcached flush_all command raised an assertion. A function that starts a transaction was called from within assertion code. * InnoDB: A data corruption occurred on ARM64. GCC builtins did not issue the correct fences when setting or unsetting the lock word. * InnoDB: Server shutdown was delayed waiting for the purge thread to exit. To avoid this problem, the number of calls to trx_purge() was reduced, and the trx_purge() batch size was reduced to 20. * InnoDB: In READ COMMITTED mode, a REPLACE operation on a unique secondary index resulted in a constraint violation. * InnoDB: The IBUF_BITMAP_FREE bit indicated that there was more free space in the leaf page than was actually available. * InnoDB: Setting lower_case_table_names=0 on a case-insensitive file system could result in a hang condition when running an INSERT INTO ... SELECT ... FROM tbl_name operation with the wrong tbl_name letter case. An error message is now printed and the server exits when attempting to start the server with --lower_case_table_names=0 on a case-insensitive file system. * InnoDB: The server failed to start with an innodb_force_recovery setting greater than 3. InnoDB was set to read-only mode before redo logs were applied. * InnoDB: The trx_sys_read_pertable_file_format_id() function reported the wrong file format. * Partitioning: CREATE TABLE statements that used an invalid function in a subpartitioning expression did not always fail gracefully as expected. * Partitioning: Error handling for failed partitioning-related ALTER TABLE operations against non-partitioned tables was not performed correctly * Partitioning: ALTER TABLE when executed from a stored procedure did not always work correctly with tables partitioned by RANGE. * Replication: Repeatedly checking for ERR_LOCK_WAIT_TIMEOUT (as done, for example by repeatedly executing SHOW SLAVE STATUS) during a prolonged write lock on a table led to an assert. * Replication: If statement based logging was in use, when updating multiple tables in a single statement, a single transaction could be logged as two different transactions. This was due to the binary logging process not properly identifying statements which were operating over transactional tables. The fix ensures that they are correctly identified, even if such statements do not change the contents of the tables.
2015-10-03 14:46:13 +02:00
share/mysql/test/suite/innodb/t/innodb-lock-inherit-read_commited.test
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/innodb/t/innodb-lock.test
share/mysql/test/suite/innodb/t/innodb-log-file-size-1.test
share/mysql/test/suite/innodb/t/innodb-log-file-size.test
share/mysql/test/suite/innodb/t/innodb-master.opt
share/mysql/test/suite/innodb/t/innodb-multiple-tablespaces.test
share/mysql/test/suite/innodb/t/innodb-read-view.test
share/mysql/test/suite/innodb/t/innodb-replace.test
share/mysql/test/suite/innodb/t/innodb-semi-consistent-master.opt
share/mysql/test/suite/innodb/t/innodb-semi-consistent.test
Changes 5.6.16: Functionality Added or Changed * InnoDB: New global configuration parameters, innodb_status_output and innodb_status_output_locks, allow you to dynamically enable and disable the standard InnoDB Monitor and InnoDB Lock Monitor for periodic output. Enabling and disabling monitors for periodic output by creating and dropping specially named tables is deprecated and may be removed in a future release. * Previously, ALTER TABLE in MySQL 5.6 could alter a table such that the result had temporal columns in both 5.5 and 5.6 format. Now ALTER TABLE upgrades old temporal columns to 5.6 format for ADD COLUMN, CHANGE COLUMN, MODIFY COLUMN, ADD INDEX, and FORCE operations. This conversion cannot be done using the INPLACE algorithm, so specifying ALGORITHM=INPLACE in these cases results in an error. * CMake now supports a -DTMPDIR=dir_name option to specify the default tmpdir value. If unspecified, the value defaults to P_tmpdir in <stdio.h>. Bugs Fixed * InnoDB; Replication: Using the InnoDB memcached plugin (see InnoDB Integration with memcached) with innodb_api_enable_binlog set to 1 caused the server to leak memory. * InnoDB: A boolean mode full-text search query would result in a memory access violation during parsing. * InnoDB: When new indexes are added by an ALTER TABLE operation, instead of only saving table-level statistics and statistics for the new indexes, InnoDB would save statistics for the entire table, including the table's other indexes. This behavior slowed ALTER TABLE performance. * InnoDB: Due to a parser error, full-text search queries that include a sub-expression could return the wrong result. * InnoDB: The innochecksum tool did not use a Windows-specific API to retrieve file size information, which resulted in an incorrect error message (Error: ibdata1 cannot be found) when the MySQL 5.6 innochecksum 2GB file size limit was exceeded. innochecksum now provides support for files larger than 2GB in both MySQL 5.6 and MySQL 5.7. * InnoDB: Due to a regression introduced by the fix for Bug17371537, memory was not allocated for the default memcached engine when using the default memcached engine as the backstore for data instead of InnoDB. * InnoDB: InnoDB would report an incorrect operating system error code after failing to initialize. * InnoDB: Manipulating a table after discarding its tablespace using ALTER TABLE ... DISCARD TABLESPACE could result in a serious error. * InnoDB: Persistent optimizer statistics would cause stalls due to latch contention. * InnoDB: MATCH() ... AGAINST queries that use a long string as an argument for AGAINST() could result in an error when run on an InnoDB table with a full-text search index. * InnoDB: An InnoDB full-text search failure would occur due to an “unended” token. The string and string length should be passed for string comparison. * InnoDB: In debug builds, a merge insert buffer during a page read would cause a memory access violation. * InnoDB: Truncating a memcached InnoDB table while memcached is performing DML operations would result in a serious error. * InnoDB: In sync0rw.ic, rw_lock_x_lock_func_nowait would needlessly call os_thread_get_curr_id. * InnoDB: Attempting to rename a table to a missing database would result in a serious error. more...
2014-02-13 08:49:56 +01:00
share/mysql/test/suite/innodb/t/innodb-status-output.test
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/innodb/t/innodb-system-table-view.test
share/mysql/test/suite/innodb/t/innodb-table-online-master.opt
share/mysql/test/suite/innodb/t/innodb-table-online.test
share/mysql/test/suite/innodb/t/innodb-tablespace.test
share/mysql/test/suite/innodb/t/innodb-timeout.test
share/mysql/test/suite/innodb/t/innodb-truncate.test
share/mysql/test/suite/innodb/t/innodb-ucs2.test
Changes 5.6.17: Functionality Added or Changed Incompatible Change: The AES_ENCRYPT() and AES_DECRYPT() functions now permit control of the block encryption mode and take an optional initialization vector argument: The new block_encryption_mode system variable controls the mode for block-based encryption algorithms. Its default value is aes-128-ecb, which signifies encryption using a key length of 128 bits and ECB mode. An optional init_vector argument provides an initialization vector for encryption modes that require it: AES_ENCRYPT(str,key_str[,init_vector]) AES_DECRYPT(crypt_str,key_str[,init_vector]) A random string of bytes to use for the initialization vector can be produced by calling the new RANDOM_BYTES() function. For more information, see Encryption and Compression Functions. These changes make statements that use AES_ENCRYPT() or AES_DECRYPT() unsafe for statement-based replication and they cannot be stored in the query cache. Queries that use RANDOM_BYTES() are unsafe for statement-based replication and cannot be stored in the query cache. Incompatible Change: The ERROR_FOR_DIVISION_BY_ZERO, NO_ZERO_DATE, and NO_ZERO_IN_DATE SQL modes now are deprecated and setting the sql_mode value to include any of them generates a warning. In MySQL 5.7, these modes do nothing. Instead, their effects are included in the effects of strict SQL mode (STRICT_ALL_TABLES or STRICT_TRANS_TABLES). The motivation for the change in MySQL 5.7 is to reduce the number of SQL modes with an effect dependent on strict mode and make them part of strict mode itself. To make advance preparation for an upgrade to MySQL 5.7, see SQL Mode Changes in MySQL 5.7. That discussion provides guidelines to assess whether your applications will be affected by the SQL mode changes in MySQL 5.7. InnoDB: MySQL now supports rebuilding regular and partitioned InnoDB tables using online DDL (ALGORITHM=INPLACE) for the following operations: OPTIMIZE TABLE ALTER TABLE ... FORCE ALTER TABLE ... ENGINE=INNODB (when run on an InnoDB table) Online DDL support reduces table rebuild time and permits concurrent DML, which helps reduce user application downtime. For additional information, see Overview of Online DDL. On Solaris, mysql_config --libs now includes -R/path/to/library so that libraries can be found at runtime. mysql_install_db provides a more informative diagnostic message when required Perl modules are missing. The IGNORE clause for ALTER TABLE is now deprecated and will be removed in a future version of MySQL. ALTER IGNORE TABLE causes problems for replication, prevents online ALTER TABLE for unique index creation, and causes problems with foreign keys (rows removed in the parent table). Bugs Fixed
2014-03-31 12:32:13 +02:00
share/mysql/test/suite/innodb/t/innodb-update-insert.test
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/innodb/t/innodb-use-sys-malloc-master.opt
share/mysql/test/suite/innodb/t/innodb-use-sys-malloc.test
share/mysql/test/suite/innodb/t/innodb-wl5522-1.test
share/mysql/test/suite/innodb/t/innodb-wl5522-debug.test
share/mysql/test/suite/innodb/t/innodb-wl5522.test
share/mysql/test/suite/innodb/t/innodb-wl5980-alter.test
share/mysql/test/suite/innodb/t/innodb-wl5980-debug.test
share/mysql/test/suite/innodb/t/innodb-wl5980-discard.test
share/mysql/test/suite/innodb/t/innodb-wl5980-linux.test
share/mysql/test/suite/innodb/t/innodb-wl5980-windows.test
share/mysql/test/suite/innodb/t/innodb-wl6445-1.test
share/mysql/test/suite/innodb/t/innodb-wl6445-2.test
share/mysql/test/suite/innodb/t/innodb-wl6445.test
share/mysql/test/suite/innodb/t/innodb.test
share/mysql/test/suite/innodb/t/innodb_autoinc_lock_mode_zero-master.opt
share/mysql/test/suite/innodb/t/innodb_autoinc_lock_mode_zero.test
Changes 5.6.27: * InnoDB: The new innodb_numa_interleave read-only configuration option allows you to enable the NUMA interleave memory policy for allocation of the InnoDB buffer pool. When innodb_numa_interleave is enabled, the NUMA memory policy is set to MPOL_INTERLEAVE for the mysqld process. After the InnoDB buffer pool is allocated, the NUMA memory policy is set back to MPOL_DEFAULT. This option is only available on NUMA-enabled systems. * yaSSL was upgraded to version 2.3.8. * RPM .spec files were updated so that MySQL Server builds from source RPM packages will include the proper files to take advantage of operating system NUMA capabilities. This introduces a runtime dependency on libnuma.so.1. RPM and yum detect this and refuse to install if that library is not installed. * InnoDB: Reloading a table that was evicted while empty caused an AUTO_INCREMENT value to be reset. * InnoDB: Memory allocation sanity checks were added to the memcached code. * InnoDB: A memcached flush_all command raised an assertion. A function that starts a transaction was called from within assertion code. * InnoDB: A data corruption occurred on ARM64. GCC builtins did not issue the correct fences when setting or unsetting the lock word. * InnoDB: Server shutdown was delayed waiting for the purge thread to exit. To avoid this problem, the number of calls to trx_purge() was reduced, and the trx_purge() batch size was reduced to 20. * InnoDB: In READ COMMITTED mode, a REPLACE operation on a unique secondary index resulted in a constraint violation. * InnoDB: The IBUF_BITMAP_FREE bit indicated that there was more free space in the leaf page than was actually available. * InnoDB: Setting lower_case_table_names=0 on a case-insensitive file system could result in a hang condition when running an INSERT INTO ... SELECT ... FROM tbl_name operation with the wrong tbl_name letter case. An error message is now printed and the server exits when attempting to start the server with --lower_case_table_names=0 on a case-insensitive file system. * InnoDB: The server failed to start with an innodb_force_recovery setting greater than 3. InnoDB was set to read-only mode before redo logs were applied. * InnoDB: The trx_sys_read_pertable_file_format_id() function reported the wrong file format. * Partitioning: CREATE TABLE statements that used an invalid function in a subpartitioning expression did not always fail gracefully as expected. * Partitioning: Error handling for failed partitioning-related ALTER TABLE operations against non-partitioned tables was not performed correctly * Partitioning: ALTER TABLE when executed from a stored procedure did not always work correctly with tables partitioned by RANGE. * Replication: Repeatedly checking for ERR_LOCK_WAIT_TIMEOUT (as done, for example by repeatedly executing SHOW SLAVE STATUS) during a prolonged write lock on a table led to an assert. * Replication: If statement based logging was in use, when updating multiple tables in a single statement, a single transaction could be logged as two different transactions. This was due to the binary logging process not properly identifying statements which were operating over transactional tables. The fix ensures that they are correctly identified, even if such statements do not change the contents of the tables.
2015-10-03 14:46:13 +02:00
share/mysql/test/suite/innodb/t/innodb_autoinc_reset.test
Changes 5.6.20: Security Fix: The linked OpenSSL library for the MySQL 5.6 Commercial Server has been updated from version 1.0.1g to version 1.0.1h. Versions of OpenSSL prior to and including 1.0.1g are reported to be vulnerable to CVE-2014-0224. This change does not affect the Oracle-produced MySQL Community build of MySQL Server 5.6, which uses the yaSSL library instead. DTrace Support MySQL now includes DTrace support on Oracle Linux 6 or higher with UEK kernel. If DTrace is present, server builds will detect it with no special CMake options required. For information about using DTrace on MySQL, see Tracing mysqld Using DTrace. InnoDB Notes Important Change: Redo log writes for large, externally stored BLOB fields could overwrite the most recent checkpoint. The 5.6.20 patch limits the size of redo log BLOB writes to 10% of the redo log file size. The 5.7.5 patch addresses the bug without imposing a limitation. For MySQL 5.5, the bug remains a known limitation. As a result of the redo log BLOB write limit introduced for MySQL 5.6, innodb_log_file_size should be set to a value greater than 10 times the largest BLOB data size found in the rows of your tables plus the length of other variable length fields (VARCHAR, VARBINARY, and TEXT type fields). Failing to do so could result in “Row size too large” errors. No action is required if your innodb_log_file_size setting is already sufficiently large or your tables contain no BLOB data. Functionality Added or Changed Replication: The new system variable binlog_impossible_mode controls what happens if the server cannot write to the binary log, for example, due to a file error. For backward compatibility, the default for binlog_impossible_mode is IGNORE_ERROR, meaning the server logs the error, halts logging, and continues updates to the database. Setting this variable to ABORT_SERVER makes the server halt logging and shut down if it cannot write to the binary log. CMake support was updated to handle CMake version 3. New Debian7, Ubuntu12.04, and Ubuntu14.04 distribution support that was introduced with 5.6.17 now comes with the platform-specific packaging source placed under the packaging directory, in the deb-precise, deb-wheezy, and deb-trusty directories. Support for LinuxThreads has been removed from the source code. LinuxThreads was superseded by NPTL in Linux 2.6. By default, mysql_install_db creates a my.cnf file in the installation base directory using a template. This may be undesireable for some deployments. To enable this behavior to be suppressed, mysql_install_db now supports a --keep-my-cnf option to preserve any existing my.cnf file and not create a new my.cnf file. The mysqlhotcopy utility is now deprecated and will be removed in a future version of MySQL. Among the reasons for this: It works only for the MyISAM and ARCHIVE storage engines; it works on Unix but not Windows. Alternatives include mysqldump and MySQL Enterprise Backup. The timed_mutexes system variable has no effect and is deprecated. Bugs Fixed
2014-08-10 17:11:57 +02:00
share/mysql/test/suite/innodb/t/innodb_blob_unrecoverable_crash.test
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/innodb/t/innodb_buffer_pool_load-master.opt
share/mysql/test/suite/innodb/t/innodb_buffer_pool_load.test
share/mysql/test/suite/innodb/t/innodb_bug-13628249.test
share/mysql/test/suite/innodb/t/innodb_bug11754376.test
share/mysql/test/suite/innodb/t/innodb_bug11766634-master.opt
share/mysql/test/suite/innodb/t/innodb_bug11766634.test
share/mysql/test/suite/innodb/t/innodb_bug11789106.test
share/mysql/test/suite/innodb/t/innodb_bug11933790.test
share/mysql/test/suite/innodb/t/innodb_bug12400341-master.opt
share/mysql/test/suite/innodb/t/innodb_bug12400341.test
share/mysql/test/suite/innodb/t/innodb_bug12429573.test
share/mysql/test/suite/innodb/t/innodb_bug12661768.test
share/mysql/test/suite/innodb/t/innodb_bug13635833.test
share/mysql/test/suite/innodb/t/innodb_bug13867871.test
share/mysql/test/suite/innodb/t/innodb_bug14006907.test
share/mysql/test/suite/innodb/t/innodb_bug14007109.test
share/mysql/test/suite/innodb/t/innodb_bug14007649.test
share/mysql/test/suite/innodb/t/innodb_bug14147491-master.opt
share/mysql/test/suite/innodb/t/innodb_bug14147491.test
share/mysql/test/suite/innodb/t/innodb_bug14169459.test
share/mysql/test/suite/innodb/t/innodb_bug14676111.test
share/mysql/test/suite/innodb/t/innodb_bug14704286.test
share/mysql/test/suite/innodb/t/innodb_bug21704.test
share/mysql/test/suite/innodb/t/innodb_bug30423.test
share/mysql/test/suite/innodb/t/innodb_bug30919-master.opt
share/mysql/test/suite/innodb/t/innodb_bug30919.test
share/mysql/test/suite/innodb/t/innodb_bug34053.test
share/mysql/test/suite/innodb/t/innodb_bug34300.test
share/mysql/test/suite/innodb/t/innodb_bug35220.test
share/mysql/test/suite/innodb/t/innodb_bug38231.test
share/mysql/test/suite/innodb/t/innodb_bug39438-master.opt
share/mysql/test/suite/innodb/t/innodb_bug39438.test
share/mysql/test/suite/innodb/t/innodb_bug40360.test
share/mysql/test/suite/innodb/t/innodb_bug40565.test
share/mysql/test/suite/innodb/t/innodb_bug41904.test
share/mysql/test/suite/innodb/t/innodb_bug42101-nonzero-master.opt
share/mysql/test/suite/innodb/t/innodb_bug42101-nonzero.test
share/mysql/test/suite/innodb/t/innodb_bug42101.test
share/mysql/test/suite/innodb/t/innodb_bug42419.test
share/mysql/test/suite/innodb/t/innodb_bug44032.test
share/mysql/test/suite/innodb/t/innodb_bug44369.test
share/mysql/test/suite/innodb/t/innodb_bug44571.test
share/mysql/test/suite/innodb/t/innodb_bug45357.test
share/mysql/test/suite/innodb/t/innodb_bug46000.test
share/mysql/test/suite/innodb/t/innodb_bug46676.test
share/mysql/test/suite/innodb/t/innodb_bug47167-master.opt
share/mysql/test/suite/innodb/t/innodb_bug47167.test
share/mysql/test/suite/innodb/t/innodb_bug47621.test
share/mysql/test/suite/innodb/t/innodb_bug47622.test
share/mysql/test/suite/innodb/t/innodb_bug47777.test
share/mysql/test/suite/innodb/t/innodb_bug48024.test
share/mysql/test/suite/innodb/t/innodb_bug49164.test
share/mysql/test/suite/innodb/t/innodb_bug51378.test
share/mysql/test/suite/innodb/t/innodb_bug51920.test
share/mysql/test/suite/innodb/t/innodb_bug52199.test
share/mysql/test/suite/innodb/t/innodb_bug52663.test
share/mysql/test/suite/innodb/t/innodb_bug53046.test
share/mysql/test/suite/innodb/t/innodb_bug53290.test
share/mysql/test/suite/innodb/t/innodb_bug53592.test
share/mysql/test/suite/innodb/t/innodb_bug53674-master.opt
share/mysql/test/suite/innodb/t/innodb_bug53674.test
share/mysql/test/suite/innodb/t/innodb_bug53756-master.opt
share/mysql/test/suite/innodb/t/innodb_bug53756.test
share/mysql/test/suite/innodb/t/innodb_bug54044.test
share/mysql/test/suite/innodb/t/innodb_bug56143.test
share/mysql/test/suite/innodb/t/innodb_bug56716.test
share/mysql/test/suite/innodb/t/innodb_bug56947.test
share/mysql/test/suite/innodb/t/innodb_bug57252.test
share/mysql/test/suite/innodb/t/innodb_bug57255.test
share/mysql/test/suite/innodb/t/innodb_bug57904.test
share/mysql/test/suite/innodb/t/innodb_bug59307.test
share/mysql/test/suite/innodb/t/innodb_bug59410.test
share/mysql/test/suite/innodb/t/innodb_bug59641.test
share/mysql/test/suite/innodb/t/innodb_bug59733.test
share/mysql/test/suite/innodb/t/innodb_bug60049-master.opt
share/mysql/test/suite/innodb/t/innodb_bug60049.test
share/mysql/test/suite/innodb/t/innodb_bug60196-master.opt
share/mysql/test/suite/innodb/t/innodb_bug60196.test
share/mysql/test/suite/innodb/t/innodb_bug60229.test
Changes 5.6.16: Functionality Added or Changed * InnoDB: New global configuration parameters, innodb_status_output and innodb_status_output_locks, allow you to dynamically enable and disable the standard InnoDB Monitor and InnoDB Lock Monitor for periodic output. Enabling and disabling monitors for periodic output by creating and dropping specially named tables is deprecated and may be removed in a future release. * Previously, ALTER TABLE in MySQL 5.6 could alter a table such that the result had temporal columns in both 5.5 and 5.6 format. Now ALTER TABLE upgrades old temporal columns to 5.6 format for ADD COLUMN, CHANGE COLUMN, MODIFY COLUMN, ADD INDEX, and FORCE operations. This conversion cannot be done using the INPLACE algorithm, so specifying ALGORITHM=INPLACE in these cases results in an error. * CMake now supports a -DTMPDIR=dir_name option to specify the default tmpdir value. If unspecified, the value defaults to P_tmpdir in <stdio.h>. Bugs Fixed * InnoDB; Replication: Using the InnoDB memcached plugin (see InnoDB Integration with memcached) with innodb_api_enable_binlog set to 1 caused the server to leak memory. * InnoDB: A boolean mode full-text search query would result in a memory access violation during parsing. * InnoDB: When new indexes are added by an ALTER TABLE operation, instead of only saving table-level statistics and statistics for the new indexes, InnoDB would save statistics for the entire table, including the table's other indexes. This behavior slowed ALTER TABLE performance. * InnoDB: Due to a parser error, full-text search queries that include a sub-expression could return the wrong result. * InnoDB: The innochecksum tool did not use a Windows-specific API to retrieve file size information, which resulted in an incorrect error message (Error: ibdata1 cannot be found) when the MySQL 5.6 innochecksum 2GB file size limit was exceeded. innochecksum now provides support for files larger than 2GB in both MySQL 5.6 and MySQL 5.7. * InnoDB: Due to a regression introduced by the fix for Bug17371537, memory was not allocated for the default memcached engine when using the default memcached engine as the backstore for data instead of InnoDB. * InnoDB: InnoDB would report an incorrect operating system error code after failing to initialize. * InnoDB: Manipulating a table after discarding its tablespace using ALTER TABLE ... DISCARD TABLESPACE could result in a serious error. * InnoDB: Persistent optimizer statistics would cause stalls due to latch contention. * InnoDB: MATCH() ... AGAINST queries that use a long string as an argument for AGAINST() could result in an error when run on an InnoDB table with a full-text search index. * InnoDB: An InnoDB full-text search failure would occur due to an “unended” token. The string and string length should be passed for string comparison. * InnoDB: In debug builds, a merge insert buffer during a page read would cause a memory access violation. * InnoDB: Truncating a memcached InnoDB table while memcached is performing DML operations would result in a serious error. * InnoDB: In sync0rw.ic, rw_lock_x_lock_func_nowait would needlessly call os_thread_get_curr_id. * InnoDB: Attempting to rename a table to a missing database would result in a serious error. more...
2014-02-13 08:49:56 +01:00
share/mysql/test/suite/innodb/t/innodb_bug70867.test
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/innodb/t/innodb_corrupt_bit.test
share/mysql/test/suite/innodb/t/innodb_ctype_ldml-master.opt
share/mysql/test/suite/innodb/t/innodb_ctype_ldml.test
share/mysql/test/suite/innodb/t/innodb_file_format-master.opt
share/mysql/test/suite/innodb/t/innodb_file_format.test
Changes 5.6.27: * InnoDB: The new innodb_numa_interleave read-only configuration option allows you to enable the NUMA interleave memory policy for allocation of the InnoDB buffer pool. When innodb_numa_interleave is enabled, the NUMA memory policy is set to MPOL_INTERLEAVE for the mysqld process. After the InnoDB buffer pool is allocated, the NUMA memory policy is set back to MPOL_DEFAULT. This option is only available on NUMA-enabled systems. * yaSSL was upgraded to version 2.3.8. * RPM .spec files were updated so that MySQL Server builds from source RPM packages will include the proper files to take advantage of operating system NUMA capabilities. This introduces a runtime dependency on libnuma.so.1. RPM and yum detect this and refuse to install if that library is not installed. * InnoDB: Reloading a table that was evicted while empty caused an AUTO_INCREMENT value to be reset. * InnoDB: Memory allocation sanity checks were added to the memcached code. * InnoDB: A memcached flush_all command raised an assertion. A function that starts a transaction was called from within assertion code. * InnoDB: A data corruption occurred on ARM64. GCC builtins did not issue the correct fences when setting or unsetting the lock word. * InnoDB: Server shutdown was delayed waiting for the purge thread to exit. To avoid this problem, the number of calls to trx_purge() was reduced, and the trx_purge() batch size was reduced to 20. * InnoDB: In READ COMMITTED mode, a REPLACE operation on a unique secondary index resulted in a constraint violation. * InnoDB: The IBUF_BITMAP_FREE bit indicated that there was more free space in the leaf page than was actually available. * InnoDB: Setting lower_case_table_names=0 on a case-insensitive file system could result in a hang condition when running an INSERT INTO ... SELECT ... FROM tbl_name operation with the wrong tbl_name letter case. An error message is now printed and the server exits when attempting to start the server with --lower_case_table_names=0 on a case-insensitive file system. * InnoDB: The server failed to start with an innodb_force_recovery setting greater than 3. InnoDB was set to read-only mode before redo logs were applied. * InnoDB: The trx_sys_read_pertable_file_format_id() function reported the wrong file format. * Partitioning: CREATE TABLE statements that used an invalid function in a subpartitioning expression did not always fail gracefully as expected. * Partitioning: Error handling for failed partitioning-related ALTER TABLE operations against non-partitioned tables was not performed correctly * Partitioning: ALTER TABLE when executed from a stored procedure did not always work correctly with tables partitioned by RANGE. * Replication: Repeatedly checking for ERR_LOCK_WAIT_TIMEOUT (as done, for example by repeatedly executing SHOW SLAVE STATUS) during a prolonged write lock on a table led to an assert. * Replication: If statement based logging was in use, when updating multiple tables in a single statement, a single transaction could be logged as two different transactions. This was due to the binary logging process not properly identifying statements which were operating over transactional tables. The fix ensures that they are correctly identified, even if such statements do not change the contents of the tables.
2015-10-03 14:46:13 +02:00
share/mysql/test/suite/innodb/t/innodb_force_recovery.test
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/innodb/t/innodb_gis.test
share/mysql/test/suite/innodb/t/innodb_i_s_innodb_locks.test
share/mysql/test/suite/innodb/t/innodb_i_s_innodb_trx.test
share/mysql/test/suite/innodb/t/innodb_information_schema_buffer.test
share/mysql/test/suite/innodb/t/innodb_lock_wait_timeout_1-master.opt
share/mysql/test/suite/innodb/t/innodb_lock_wait_timeout_1.test
share/mysql/test/suite/innodb/t/innodb_misc1-master.opt
share/mysql/test/suite/innodb/t/innodb_misc1.test
share/mysql/test/suite/innodb/t/innodb_multi_update.test
share/mysql/test/suite/innodb/t/innodb_mysql-master.opt
share/mysql/test/suite/innodb/t/innodb_mysql.test
share/mysql/test/suite/innodb/t/innodb_mysql_rbk-master.opt
share/mysql/test/suite/innodb/t/innodb_mysql_rbk.test
share/mysql/test/suite/innodb/t/innodb_notembedded.test
share/mysql/test/suite/innodb/t/innodb_page_size_func.test
share/mysql/test/suite/innodb/t/innodb_prefix_index_restart_server.test
share/mysql/test/suite/innodb/t/innodb_replace.test
share/mysql/test/suite/innodb/t/innodb_stats.test
share/mysql/test/suite/innodb/t/innodb_stats_auto_recalc.test
share/mysql/test/suite/innodb/t/innodb_stats_auto_recalc_ddl.test
share/mysql/test/suite/innodb/t/innodb_stats_auto_recalc_lots.test
share/mysql/test/suite/innodb/t/innodb_stats_auto_recalc_on_nonexistent.test
share/mysql/test/suite/innodb/t/innodb_stats_create_on_corrupted.test
share/mysql/test/suite/innodb/t/innodb_stats_create_table.test
share/mysql/test/suite/innodb/t/innodb_stats_drop_locked.test
Changes 5.6.19: Functionality Added or Changed The obsolete and unmaintained charset2html utility has been removed from MySQL distributions. The mysqlbug, mysql_waitpid, and mysql_zap utilities have been deprecated and will be removed in MySQL 5.7. Bugs Fixed InnoDB: After upgrading from 5.6.10 to MySQL versions up to and including MySQL 5.6.18, InnoDB would attempt to rename obsolete full-text search auxiliary tables on server startup, resulting in an assertion failure. InnoDB: For each insert, memset would be called three times to allocate memory for system fields. To reduce CPU usage, the three memset calls are now combined into a single call. InnoDB: Enabling the InnoDB Table Monitor would result in a ib_table->stat_initialized assertion failure. InnoDB: Setting innodb_max_dirty_pages_pct=0 would leave 1% of dirty pages unflushed. Buffer pool flushing is initiated when the percentage of dirty pages is greater innodb_max_dirty_pages_pct. The internal variables that store the innodb_max_dirty_pages_pct value and the percentage of dirty pages (buf_get_modified_ratio_pct and srv_max_buf_pool_modified_pct) were defined as unsigned integer data types, which meant that a innodb_max_dirty_pages_pct value of 0 required a dirty pages percentage of 1 or greater to initiate buffer pool flushing. To address this problem, the buf_get_modified_ratio_pct and srv_max_buf_pool_modified_pct internal variables are redefined as double data types, which changes the range value for innodb_max_dirty_pages_pct and innodb_max_dirty_pages_pct_lwm from 0 .. 99 to 0 .. 99.99. Additionally, buffer pool flushing is now initiated when the percentage of dirty pages is “greater than or equal to” innodb_max_dirty_pages_pct. Replication: Log rotation events could cause group_relay_log_pos to be moved forward incorrectly within a group. This meant that, when the transaction was retried, or if the SQL thread was stopped in the middle of a transaction following one or more log rotations (such that the transaction or group spanned multiple relay log files), part or all of the group was silently skipped. This issue has been addressed by correcting a problem in the logic used to avoid touching the coordinates of the SQL thread when updating the log position as part of a relay log rotation whereby it was possible to update the SQL thread's coordinates when not using a multi-threaded slave, even in the middle of a group. Replication: When running the server with --gtid-mode=ON, STOP SLAVE followed by START SLAVE resulted in a mismatch between the information provided by INFORMATION_SCHEMA.INNODB_TEMP_TABLE_INFO and the Slave_open_temp_tables status variable: the INNODB_TEMP_TABLE_INFO table showed that no temporary tables existed, but Slave_open_temp_tables had a nonzero value. Replication: In certain cases, the server mishandled triggers and stored procedures that tried to modify other tables when called by CREATE TABLE ... SELECT. This is now handled correctly as an error. Replication: When used on a table employing a transactional storage engine, a failed TRUNCATE TABLE was still written to the binary log and thus replayed on the slave. This could lead to inconsistency when the master retained data that was removed on the slave. Now in such cases TRUNCATE TABLE is logged only when it executes successfully. Replication: The server did not always handle the auto.cnf file correctly in cases where this file's permissions were incorrect. Replication: When the binary log was rotated due to receipt of a SIGHUP signal, the new binary log did not contain the Previous_gtid_event required for subsequent processing of that binary log's GTID events. Now when SIGHUP is received, steps are taken to insure that the server writes the necessary Previous_gtid_event to the new log before writing any GTID events to the new log.
2014-06-02 09:30:38 +02:00
share/mysql/test/suite/innodb/t/innodb_stats_external_pages.test
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/innodb/t/innodb_stats_fetch.test
share/mysql/test/suite/innodb/t/innodb_stats_fetch_corrupted.test
share/mysql/test/suite/innodb/t/innodb_stats_fetch_nonexistent.test
share/mysql/test/suite/innodb/t/innodb_stats_flag_global_off-master.opt
share/mysql/test/suite/innodb/t/innodb_stats_flag_global_off.test
share/mysql/test/suite/innodb/t/innodb_stats_flag_global_on-master.opt
share/mysql/test/suite/innodb/t/innodb_stats_flag_global_on.test
share/mysql/test/suite/innodb/t/innodb_stats_rename_table.test
share/mysql/test/suite/innodb/t/innodb_stats_rename_table_if_exists.test
share/mysql/test/suite/innodb/t/innodb_stats_sample_pages.test
share/mysql/test/suite/innodb/t/innodb_stats_table_flag_auto_recalc.test
share/mysql/test/suite/innodb/t/innodb_stats_table_flag_sample_pages.test
share/mysql/test/suite/innodb/t/innodb_timeout_rollback-master.opt
share/mysql/test/suite/innodb/t/innodb_timeout_rollback.test
share/mysql/test/suite/innodb/t/innodb_trx_weight.test
share/mysql/test/suite/innodb/t/innodb_upd_stats_if_needed_not_inited.test
share/mysql/test/suite/innodb/t/innodb_ut_format_name.test
Changes 5.6.22: * Noisy compiler warnings on FreeBSD 10 were silenced. * CMake workarounds for older Mac OS X and XCode versions were removed. On Mac OS X, compilation always uses Clang, even for 32-bit builds. * Previously, the MYSQL_MAINTAINER_MODE CMake option was turned on by default for debug builds and off for release builds, and MYSQL_MAINTAINER_MODE caused -Werror to be enabled when building with GCC. This made it cumbersome to enable -Werror under certain conditions, such as when compiling with Clang. * Build support was modified to produce the same warnings for Clang as for gcc. * CMake configuration for the Clang compiler sets more appropriate flags for building on Linux. Specifically, -g -fno-omit-frame-pointer -fno-strict-aliasing is now added. * Bugs fixed.
2014-12-02 13:40:09 +01:00
share/mysql/test/suite/innodb/t/insert_debug.test
Changes 5.6.23: * The linked OpenSSL library for the MySQL Commercial Server has been updated from version 1.0.1j to version 1.0.1k. * Support for the SSL 2.0 and SSL 3.0 protocols has been disabled because they provide weak encryption. * yaSSL was upgraded to version 2.3.7. * The valid date range of the SSL certificates in mysql-test/std_data has been extended to the year 2029. * Bugs Fixed
2015-02-07 20:23:40 +01:00
share/mysql/test/suite/innodb/t/monitor.test
share/mysql/test/suite/innodb/t/monitor_debug.test
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/innodb/t/portability_wl5980_linux.zip
share/mysql/test/suite/innodb/t/portability_wl5980_windows.zip
Changes 5.6.22: * Noisy compiler warnings on FreeBSD 10 were silenced. * CMake workarounds for older Mac OS X and XCode versions were removed. On Mac OS X, compilation always uses Clang, even for 32-bit builds. * Previously, the MYSQL_MAINTAINER_MODE CMake option was turned on by default for debug builds and off for release builds, and MYSQL_MAINTAINER_MODE caused -Werror to be enabled when building with GCC. This made it cumbersome to enable -Werror under certain conditions, such as when compiling with Clang. * Build support was modified to produce the same warnings for Clang as for gcc. * CMake configuration for the Clang compiler sets more appropriate flags for building on Linux. Specifically, -g -fno-omit-frame-pointer -fno-strict-aliasing is now added. * Bugs fixed.
2014-12-02 13:40:09 +01:00
share/mysql/test/suite/innodb/t/sp_temp_table.test
Changes 5.6.25: Functionality Added or Changed * MySQL Enterprise Firewall operates on parser states and does not work well together with the query cache, which circumvents the parser. MySQL Enterprise Firewall now checks whether the query cache is enabled. If so, it displays a message that the query cache must be disabled and does not load. * my_print_defaults now masks passwords. To display passwords in cleartext, use the new --show option. * MySQL distributions now include an innodb_stress suite of test cases. Thanks to Mark Callaghan for the contribution. Bugs Fixed * InnoDB; Partitioning: The CREATE_TIME column of the INFORMATION_SCHEMA.TABLES table now shows the correct table creation time for partitioned InnoDB tables. The CREATE_TIME column of the INFORMATION_SCHEMA.PARTITIONS table now shows the correct partition creation time for a partition of partitioned InnoDB tables. The UPDATE_TIME column of the INFORMATION_SCHEMA.TABLES table now shows when a partitioned InnoDB table was last updated by an INSERT, DELETE, or UPDATE. The UPDATE_TIME column of the INFORMATION_SCHEMA.PARTITIONS table now shows when a partition of a partitioned InnoDB table was last updated. * InnoDB: An assertion was raised on shutdown due to XA PREPARE transactions holding explicit locks. * InnoDB: The strict_* forms of innodb_checksum_algorithm settings (strict_none, strict_innodb, and strict_crc32) caused the server to halt when a non-matching checksum was encountered, even though the non-matching checksum was valid. For example, with innodb_checksum_algorithm=strict_crc32, encountering a valid innodb checksum caused the server to halt. Instead of halting the server, a message is now printed to the error log and the page is accepted as valid if it matches an innodb, crc32 or none checksum. * InnoDB: The memcached set command permitted a negative expire time value. Expire time is stored internally as an unsigned integer. A negative value would be converted to a large number and accepted. The maximum expire time value is now restricted to INT_MAX32 to prevent negative expire time values. * InnoDB: Removal of a foreign key object from the data dictionary cache during error handling caused the server to exit. * InnoDB: SHOW ENGINE INNODB STATUS output showed negative reservation and signal count values due to a counter overflow error. * InnoDB: Failure to check the status of a cursor transaction read-only option before reusing the cursor transaction for a write operation resulted in a server exit during a memcached workload. * InnoDB: MDL locks taken by memcached clients caused a MySQL Enterprise Backup FLUSH TABLES WITH READ LOCK operation to hang. * InnoDB: Estimates that were too low for the size of merge chunks in the result sorting algorithm caused a server exit. * InnoDB: For full-text searches, the optimizer could choose an index that does not produce correct relevancy rankings. * Partitioning: When creating a partitioned table, partition-level DATA DIRECTORY or INDEX DIRECTORY option values that contained an excessive number of characters were handled incorrectly. * Partitioning: Executing an ALTER TABLE on a partitioned table on which a write lock was in effect could cause subsequent SQL statements on this table to fail. * Replication: When binary logging was enabled, using stored functions and triggers resulting in a long running procedure that inserted many records caused the memory use to increase rapidly. This was due to memory being allocated per variable. The fix ensures that in such a situation, memory is allocated once and the same memory is reused. * Replication: If an error was encountered while adding a GTID to the received GTID set, the log lock was not being correctly released. This could cause a deadlock. more...
2015-06-01 10:15:05 +02:00
share/mysql/test/suite/innodb/t/strict_checksum.test
Changes 5.6.22: * Noisy compiler warnings on FreeBSD 10 were silenced. * CMake workarounds for older Mac OS X and XCode versions were removed. On Mac OS X, compilation always uses Clang, even for 32-bit builds. * Previously, the MYSQL_MAINTAINER_MODE CMake option was turned on by default for debug builds and off for release builds, and MYSQL_MAINTAINER_MODE caused -Werror to be enabled when building with GCC. This made it cumbersome to enable -Werror under certain conditions, such as when compiling with Clang. * Build support was modified to produce the same warnings for Clang as for gcc. * CMake configuration for the Clang compiler sets more appropriate flags for building on Linux. Specifically, -g -fno-omit-frame-pointer -fno-strict-aliasing is now added. * Bugs fixed.
2014-12-02 13:40:09 +01:00
share/mysql/test/suite/innodb/t/strict_mode.test
Changes 5.6.29: * InnoDB: A new InnoDB configuration option, innodb_tmpdir, allows you to configure a separate temporary file directory for online ALTER TABLE operations. This option was introduced to help avoid tmpdir overflows that could occur as a result of large temporary files created during online ALTER TABLE operations. innodb_tmpdir is a SESSION variable and can be configured dynamically using a SET statement. * yaSSL was upgraded to version 2.3.9. This upgrade corrects an issue in which yaSSL handled only cases of zero or one leading zeros for the key agreement instead of potentially any number, which in rare cases could cause connections to fail when using DHE cipher suites. * The Valgrind function signature in mysql-test/valgrind.supp was upgraded for Valgrind 3.11. * Bugs Fixed
2016-02-28 09:58:03 +01:00
share/mysql/test/suite/innodb/t/tmpdir.test
Changes 5.6.25: Functionality Added or Changed * MySQL Enterprise Firewall operates on parser states and does not work well together with the query cache, which circumvents the parser. MySQL Enterprise Firewall now checks whether the query cache is enabled. If so, it displays a message that the query cache must be disabled and does not load. * my_print_defaults now masks passwords. To display passwords in cleartext, use the new --show option. * MySQL distributions now include an innodb_stress suite of test cases. Thanks to Mark Callaghan for the contribution. Bugs Fixed * InnoDB; Partitioning: The CREATE_TIME column of the INFORMATION_SCHEMA.TABLES table now shows the correct table creation time for partitioned InnoDB tables. The CREATE_TIME column of the INFORMATION_SCHEMA.PARTITIONS table now shows the correct partition creation time for a partition of partitioned InnoDB tables. The UPDATE_TIME column of the INFORMATION_SCHEMA.TABLES table now shows when a partitioned InnoDB table was last updated by an INSERT, DELETE, or UPDATE. The UPDATE_TIME column of the INFORMATION_SCHEMA.PARTITIONS table now shows when a partition of a partitioned InnoDB table was last updated. * InnoDB: An assertion was raised on shutdown due to XA PREPARE transactions holding explicit locks. * InnoDB: The strict_* forms of innodb_checksum_algorithm settings (strict_none, strict_innodb, and strict_crc32) caused the server to halt when a non-matching checksum was encountered, even though the non-matching checksum was valid. For example, with innodb_checksum_algorithm=strict_crc32, encountering a valid innodb checksum caused the server to halt. Instead of halting the server, a message is now printed to the error log and the page is accepted as valid if it matches an innodb, crc32 or none checksum. * InnoDB: The memcached set command permitted a negative expire time value. Expire time is stored internally as an unsigned integer. A negative value would be converted to a large number and accepted. The maximum expire time value is now restricted to INT_MAX32 to prevent negative expire time values. * InnoDB: Removal of a foreign key object from the data dictionary cache during error handling caused the server to exit. * InnoDB: SHOW ENGINE INNODB STATUS output showed negative reservation and signal count values due to a counter overflow error. * InnoDB: Failure to check the status of a cursor transaction read-only option before reusing the cursor transaction for a write operation resulted in a server exit during a memcached workload. * InnoDB: MDL locks taken by memcached clients caused a MySQL Enterprise Backup FLUSH TABLES WITH READ LOCK operation to hang. * InnoDB: Estimates that were too low for the size of merge chunks in the result sorting algorithm caused a server exit. * InnoDB: For full-text searches, the optimizer could choose an index that does not produce correct relevancy rankings. * Partitioning: When creating a partitioned table, partition-level DATA DIRECTORY or INDEX DIRECTORY option values that contained an excessive number of characters were handled incorrectly. * Partitioning: Executing an ALTER TABLE on a partitioned table on which a write lock was in effect could cause subsequent SQL statements on this table to fail. * Replication: When binary logging was enabled, using stored functions and triggers resulting in a long running procedure that inserted many records caused the memory use to increase rapidly. This was due to memory being allocated per variable. The fix ensures that in such a situation, memory is allocated once and the same memory is reused. * Replication: If an error was encountered while adding a GTID to the received GTID set, the log lock was not being correctly released. This could cause a deadlock. more...
2015-06-01 10:15:05 +02:00
share/mysql/test/suite/innodb/t/xa_recovery.test
Changes 5.6.22: * Noisy compiler warnings on FreeBSD 10 were silenced. * CMake workarounds for older Mac OS X and XCode versions were removed. On Mac OS X, compilation always uses Clang, even for 32-bit builds. * Previously, the MYSQL_MAINTAINER_MODE CMake option was turned on by default for debug builds and off for release builds, and MYSQL_MAINTAINER_MODE caused -Werror to be enabled when building with GCC. This made it cumbersome to enable -Werror under certain conditions, such as when compiling with Clang. * Build support was modified to produce the same warnings for Clang as for gcc. * CMake configuration for the Clang compiler sets more appropriate flags for building on Linux. Specifically, -g -fno-omit-frame-pointer -fno-strict-aliasing is now added. * Bugs fixed.
2014-12-02 13:40:09 +01:00
share/mysql/test/suite/innodb_fts/r/fts_compatibility.result
share/mysql/test/suite/innodb_fts/r/fts_compatibility_win.result
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/innodb_fts/r/fulltext.result
share/mysql/test/suite/innodb_fts/r/fulltext2.result
share/mysql/test/suite/innodb_fts/r/fulltext3.result
share/mysql/test/suite/innodb_fts/r/fulltext_cache.result
share/mysql/test/suite/innodb_fts/r/fulltext_distinct.result
share/mysql/test/suite/innodb_fts/r/fulltext_left_join.result
share/mysql/test/suite/innodb_fts/r/fulltext_misc.result
share/mysql/test/suite/innodb_fts/r/fulltext_multi.result
share/mysql/test/suite/innodb_fts/r/fulltext_order_by.result
share/mysql/test/suite/innodb_fts/r/fulltext_update.result
share/mysql/test/suite/innodb_fts/r/fulltext_var.result
share/mysql/test/suite/innodb_fts/r/innobase_drop_fts_index_table.result
share/mysql/test/suite/innodb_fts/r/innodb-fts-basic.result
share/mysql/test/suite/innodb_fts/r/innodb-fts-ddl.result
share/mysql/test/suite/innodb_fts/r/innodb-fts-fic.result
share/mysql/test/suite/innodb_fts/r/innodb-fts-stopword.result
Changes 5.6.15: * Previously, MySQL Server distributions included the MySQL Reference Manual in Info format (the Docs/mysql.info file). Because the license for the manual restricts redistribution, its inclusion in Community packages caused problems for downstream redistributors, such as those who create Linux distributions. Community distributions of MySQL Server no longer include the mysql.info file, to make the repackaging and redistribution process easier (for example, the source tarball and its checksum can be used directly). This change applies to all source and binary Community packaging formats. Commercial (Enterprise) distributions are unchanged. * Incompatible Change: Several statement instruments in the setup_instruments table are used by the Performance Schema during the early stages of statement classification before the exact statement type is known. * The Performance Schema now instruments the read/write lock Delegate::lock * A new CMake option, WITH_ASAN, permits enabling address sanitization for compilers that support it. * The hash function used for metadata locking was modified to reduce overhead. * Bugs Fixed
2013-12-03 21:02:41 +01:00
share/mysql/test/suite/innodb_fts/r/innodb_fts_index_table.result
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/innodb_fts/r/innodb_fts_large_records.result
share/mysql/test/suite/innodb_fts/r/innodb_fts_misc.result
share/mysql/test/suite/innodb_fts/r/innodb_fts_misc_1.result
share/mysql/test/suite/innodb_fts/r/innodb_fts_misc_debug.result
share/mysql/test/suite/innodb_fts/r/innodb_fts_multiple_index.result
share/mysql/test/suite/innodb_fts/r/innodb_fts_opt.result
Changes 5.6.12: * mysql_upgrade now verifies that the server version matches the version against which it was compiled, and exits if there is a mismatch. In addiion, a --version-check option permits specifying whether to enable version checking (the default), or disable checking if given as --skip-version-checking. * Bugs Fixed
2013-06-04 20:17:25 +02:00
share/mysql/test/suite/innodb_fts/r/innodb_fts_plugin.result
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/innodb_fts/r/innodb_fts_proximity.result
Changes 5.6.13: * Important Change; Replication: By default, when promoting integers from a smaller type on the master to a larger type on the slave (for example, from a SMALLINT column on the master to a BIGINT column on the slave), the promoted values are treated as though they are signed. Now in such cases it is possible to modify or override this behavior using one or both of ALL_SIGNED, ALL_UNSIGNED in the set of values specified for the slave_type_conversions server system variable. For more information, see Row-based replication: attribute promotion and demotion, as well as the description of the variable. * Previously, program options could be specified in full or as any unambiguous prefix. For example, the --compress option could be given to mysqldump as --compr, but not as --comp because the latter is ambiguous. Option prefixes now are deprecated. They can cause problems when new options are implemented for programs. A prefix that is currently unambiguous might become ambiguous in the future. If an unambiguous prefix is given, a warning now occurs to provide feedback. For example: Warning: Using unique option prefix compr instead of compress is deprecated and will be removed in a future release. Please use the full name instead. Option prefixes are no longer supported in MySQL 5.7; only full options are accepted. * The C API libmysqlclient shared-library .so files now have version 18.1.0 (up from version 18.0.0 used in MySQL 5.5). * In batch mode, mysql formatted result status messages such as “"Query OK, 1 row affected"” but did not print them. Now these messages are not formatted. * Bugs Fixed
2013-07-31 11:51:38 +02:00
share/mysql/test/suite/innodb_fts/r/innodb_fts_result_cache_limit.result
Changes 5.6.15: * Previously, MySQL Server distributions included the MySQL Reference Manual in Info format (the Docs/mysql.info file). Because the license for the manual restricts redistribution, its inclusion in Community packages caused problems for downstream redistributors, such as those who create Linux distributions. Community distributions of MySQL Server no longer include the mysql.info file, to make the repackaging and redistribution process easier (for example, the source tarball and its checksum can be used directly). This change applies to all source and binary Community packaging formats. Commercial (Enterprise) distributions are unchanged. * Incompatible Change: Several statement instruments in the setup_instruments table are used by the Performance Schema during the early stages of statement classification before the exact statement type is known. * The Performance Schema now instruments the read/write lock Delegate::lock * A new CMake option, WITH_ASAN, permits enabling address sanitization for compilers that support it. * The hash function used for metadata locking was modified to reduce overhead. * Bugs Fixed
2013-12-03 21:02:41 +01:00
share/mysql/test/suite/innodb_fts/r/innodb_fts_savepoint.result
Changes 5.6.11: 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. 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. mysql_config_editor now supports --port and --socket options for specifying TCP/IP port number and Unix socket file name. 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. The only supported value for the innodb_mirrored_log_groups system variable is 1, so this variable is now deprecated. Setting it to 1 at startup results in a warning. Setting it to a value other than 1 at startup results in an error and the server exits. This variable will be removed in a future release.
2013-04-20 10:06:01 +02:00
share/mysql/test/suite/innodb_fts/r/innodb_fts_stopword_charset.result
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/innodb_fts/r/innodb_fts_transaction.result
Changes 5.6.24: * CMake support was updated to handle CMake version 3.1. * The server now includes its version number when it writes the initial “starting” message to the error log, to make it easier to tell which server instance error log output applies to. This value is the same as that available from the version system variable. * ALTER TABLE did not take advantage of fast alterations that might otherwise apply to the operation to be performed, if the table contained temporal columns found to be in pre-5.6.4 format (TIME, DATETIME, and TIMESTAMP columns without support for fractional seconds precision). * Statement digesting as done previously by the Performance Schema is now done at the SQL level regardless of whether the Performance Schema is compiled in and is available to other aspects of server operation that could benefit from it. The default space available for digesting is 1024 bytes, but can be changed at server startup using the max_digest_length system variable. * Bug fixes.
2015-04-08 12:38:48 +02:00
share/mysql/test/suite/innodb_fts/r/phrase.result
Changes 5.6.23: * The linked OpenSSL library for the MySQL Commercial Server has been updated from version 1.0.1j to version 1.0.1k. * Support for the SSL 2.0 and SSL 3.0 protocols has been disabled because they provide weak encryption. * yaSSL was upgraded to version 2.3.7. * The valid date range of the SSL certificates in mysql-test/std_data has been extended to the year 2029. * Bugs Fixed
2015-02-07 20:23:40 +01:00
share/mysql/test/suite/innodb_fts/r/subexpr.result
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/innodb_fts/t/disabled.def
Changes 5.6.22: * Noisy compiler warnings on FreeBSD 10 were silenced. * CMake workarounds for older Mac OS X and XCode versions were removed. On Mac OS X, compilation always uses Clang, even for 32-bit builds. * Previously, the MYSQL_MAINTAINER_MODE CMake option was turned on by default for debug builds and off for release builds, and MYSQL_MAINTAINER_MODE caused -Werror to be enabled when building with GCC. This made it cumbersome to enable -Werror under certain conditions, such as when compiling with Clang. * Build support was modified to produce the same warnings for Clang as for gcc. * CMake configuration for the Clang compiler sets more appropriate flags for building on Linux. Specifically, -g -fno-omit-frame-pointer -fno-strict-aliasing is now added. * Bugs fixed.
2014-12-02 13:40:09 +01:00
share/mysql/test/suite/innodb_fts/t/fts_compatibility.test
share/mysql/test/suite/innodb_fts/t/fts_compatibility_win.test
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/innodb_fts/t/fulltext.test
share/mysql/test/suite/innodb_fts/t/fulltext2.test
share/mysql/test/suite/innodb_fts/t/fulltext3.test
share/mysql/test/suite/innodb_fts/t/fulltext_cache.test
share/mysql/test/suite/innodb_fts/t/fulltext_distinct.test
share/mysql/test/suite/innodb_fts/t/fulltext_left_join.test
share/mysql/test/suite/innodb_fts/t/fulltext_misc.test
share/mysql/test/suite/innodb_fts/t/fulltext_multi.test
share/mysql/test/suite/innodb_fts/t/fulltext_order_by.test
share/mysql/test/suite/innodb_fts/t/fulltext_plugin-master.opt
share/mysql/test/suite/innodb_fts/t/fulltext_update.test
share/mysql/test/suite/innodb_fts/t/fulltext_var.test
share/mysql/test/suite/innodb_fts/t/innobase_drop_fts_index_table.test
share/mysql/test/suite/innodb_fts/t/innodb-fts-basic.test
share/mysql/test/suite/innodb_fts/t/innodb-fts-ddl.test
share/mysql/test/suite/innodb_fts/t/innodb-fts-fic.test
share/mysql/test/suite/innodb_fts/t/innodb-fts-stopword.test
Changes 5.6.15: * Previously, MySQL Server distributions included the MySQL Reference Manual in Info format (the Docs/mysql.info file). Because the license for the manual restricts redistribution, its inclusion in Community packages caused problems for downstream redistributors, such as those who create Linux distributions. Community distributions of MySQL Server no longer include the mysql.info file, to make the repackaging and redistribution process easier (for example, the source tarball and its checksum can be used directly). This change applies to all source and binary Community packaging formats. Commercial (Enterprise) distributions are unchanged. * Incompatible Change: Several statement instruments in the setup_instruments table are used by the Performance Schema during the early stages of statement classification before the exact statement type is known. * The Performance Schema now instruments the read/write lock Delegate::lock * A new CMake option, WITH_ASAN, permits enabling address sanitization for compilers that support it. * The hash function used for metadata locking was modified to reduce overhead. * Bugs Fixed
2013-12-03 21:02:41 +01:00
share/mysql/test/suite/innodb_fts/t/innodb_fts_index_table.test
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/innodb_fts/t/innodb_fts_large_records.test
share/mysql/test/suite/innodb_fts/t/innodb_fts_misc.test
share/mysql/test/suite/innodb_fts/t/innodb_fts_misc_1.test
share/mysql/test/suite/innodb_fts/t/innodb_fts_misc_debug.test
share/mysql/test/suite/innodb_fts/t/innodb_fts_multiple_index.test
share/mysql/test/suite/innodb_fts/t/innodb_fts_opt.test
Changes 5.6.12: * mysql_upgrade now verifies that the server version matches the version against which it was compiled, and exits if there is a mismatch. In addiion, a --version-check option permits specifying whether to enable version checking (the default), or disable checking if given as --skip-version-checking. * Bugs Fixed
2013-06-04 20:17:25 +02:00
share/mysql/test/suite/innodb_fts/t/innodb_fts_plugin.test
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/innodb_fts/t/innodb_fts_proximity.test
Changes 5.6.13: * Important Change; Replication: By default, when promoting integers from a smaller type on the master to a larger type on the slave (for example, from a SMALLINT column on the master to a BIGINT column on the slave), the promoted values are treated as though they are signed. Now in such cases it is possible to modify or override this behavior using one or both of ALL_SIGNED, ALL_UNSIGNED in the set of values specified for the slave_type_conversions server system variable. For more information, see Row-based replication: attribute promotion and demotion, as well as the description of the variable. * Previously, program options could be specified in full or as any unambiguous prefix. For example, the --compress option could be given to mysqldump as --compr, but not as --comp because the latter is ambiguous. Option prefixes now are deprecated. They can cause problems when new options are implemented for programs. A prefix that is currently unambiguous might become ambiguous in the future. If an unambiguous prefix is given, a warning now occurs to provide feedback. For example: Warning: Using unique option prefix compr instead of compress is deprecated and will be removed in a future release. Please use the full name instead. Option prefixes are no longer supported in MySQL 5.7; only full options are accepted. * The C API libmysqlclient shared-library .so files now have version 18.1.0 (up from version 18.0.0 used in MySQL 5.5). * In batch mode, mysql formatted result status messages such as “"Query OK, 1 row affected"” but did not print them. Now these messages are not formatted. * Bugs Fixed
2013-07-31 11:51:38 +02:00
share/mysql/test/suite/innodb_fts/t/innodb_fts_result_cache_limit.test
Changes 5.6.15: * Previously, MySQL Server distributions included the MySQL Reference Manual in Info format (the Docs/mysql.info file). Because the license for the manual restricts redistribution, its inclusion in Community packages caused problems for downstream redistributors, such as those who create Linux distributions. Community distributions of MySQL Server no longer include the mysql.info file, to make the repackaging and redistribution process easier (for example, the source tarball and its checksum can be used directly). This change applies to all source and binary Community packaging formats. Commercial (Enterprise) distributions are unchanged. * Incompatible Change: Several statement instruments in the setup_instruments table are used by the Performance Schema during the early stages of statement classification before the exact statement type is known. * The Performance Schema now instruments the read/write lock Delegate::lock * A new CMake option, WITH_ASAN, permits enabling address sanitization for compilers that support it. * The hash function used for metadata locking was modified to reduce overhead. * Bugs Fixed
2013-12-03 21:02:41 +01:00
share/mysql/test/suite/innodb_fts/t/innodb_fts_savepoint.test
Changes 5.6.11: 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. 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. mysql_config_editor now supports --port and --socket options for specifying TCP/IP port number and Unix socket file name. 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. The only supported value for the innodb_mirrored_log_groups system variable is 1, so this variable is now deprecated. Setting it to 1 at startup results in a warning. Setting it to a value other than 1 at startup results in an error and the server exits. This variable will be removed in a future release.
2013-04-20 10:06:01 +02:00
share/mysql/test/suite/innodb_fts/t/innodb_fts_stopword_charset.test
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/innodb_fts/t/innodb_fts_transaction.test
Changes 5.6.24: * CMake support was updated to handle CMake version 3.1. * The server now includes its version number when it writes the initial “starting” message to the error log, to make it easier to tell which server instance error log output applies to. This value is the same as that available from the version system variable. * ALTER TABLE did not take advantage of fast alterations that might otherwise apply to the operation to be performed, if the table contained temporal columns found to be in pre-5.6.4 format (TIME, DATETIME, and TIMESTAMP columns without support for fractional seconds precision). * Statement digesting as done previously by the Performance Schema is now done at the SQL level regardless of whether the Performance Schema is compiled in and is available to other aspects of server operation that could benefit from it. The default space available for digesting is 1024 bytes, but can be changed at server startup using the max_digest_length system variable. * Bug fixes.
2015-04-08 12:38:48 +02:00
share/mysql/test/suite/innodb_fts/t/phrase.test
Changes 5.6.23: * The linked OpenSSL library for the MySQL Commercial Server has been updated from version 1.0.1j to version 1.0.1k. * Support for the SSL 2.0 and SSL 3.0 protocols has been disabled because they provide weak encryption. * yaSSL was upgraded to version 2.3.7. * The valid date range of the SSL certificates in mysql-test/std_data has been extended to the year 2029. * Bugs Fixed
2015-02-07 20:23:40 +01:00
share/mysql/test/suite/innodb_fts/t/subexpr.test
Changes 5.6.25: Functionality Added or Changed * MySQL Enterprise Firewall operates on parser states and does not work well together with the query cache, which circumvents the parser. MySQL Enterprise Firewall now checks whether the query cache is enabled. If so, it displays a message that the query cache must be disabled and does not load. * my_print_defaults now masks passwords. To display passwords in cleartext, use the new --show option. * MySQL distributions now include an innodb_stress suite of test cases. Thanks to Mark Callaghan for the contribution. Bugs Fixed * InnoDB; Partitioning: The CREATE_TIME column of the INFORMATION_SCHEMA.TABLES table now shows the correct table creation time for partitioned InnoDB tables. The CREATE_TIME column of the INFORMATION_SCHEMA.PARTITIONS table now shows the correct partition creation time for a partition of partitioned InnoDB tables. The UPDATE_TIME column of the INFORMATION_SCHEMA.TABLES table now shows when a partitioned InnoDB table was last updated by an INSERT, DELETE, or UPDATE. The UPDATE_TIME column of the INFORMATION_SCHEMA.PARTITIONS table now shows when a partition of a partitioned InnoDB table was last updated. * InnoDB: An assertion was raised on shutdown due to XA PREPARE transactions holding explicit locks. * InnoDB: The strict_* forms of innodb_checksum_algorithm settings (strict_none, strict_innodb, and strict_crc32) caused the server to halt when a non-matching checksum was encountered, even though the non-matching checksum was valid. For example, with innodb_checksum_algorithm=strict_crc32, encountering a valid innodb checksum caused the server to halt. Instead of halting the server, a message is now printed to the error log and the page is accepted as valid if it matches an innodb, crc32 or none checksum. * InnoDB: The memcached set command permitted a negative expire time value. Expire time is stored internally as an unsigned integer. A negative value would be converted to a large number and accepted. The maximum expire time value is now restricted to INT_MAX32 to prevent negative expire time values. * InnoDB: Removal of a foreign key object from the data dictionary cache during error handling caused the server to exit. * InnoDB: SHOW ENGINE INNODB STATUS output showed negative reservation and signal count values due to a counter overflow error. * InnoDB: Failure to check the status of a cursor transaction read-only option before reusing the cursor transaction for a write operation resulted in a server exit during a memcached workload. * InnoDB: MDL locks taken by memcached clients caused a MySQL Enterprise Backup FLUSH TABLES WITH READ LOCK operation to hang. * InnoDB: Estimates that were too low for the size of merge chunks in the result sorting algorithm caused a server exit. * InnoDB: For full-text searches, the optimizer could choose an index that does not produce correct relevancy rankings. * Partitioning: When creating a partitioned table, partition-level DATA DIRECTORY or INDEX DIRECTORY option values that contained an excessive number of characters were handled incorrectly. * Partitioning: Executing an ALTER TABLE on a partitioned table on which a write lock was in effect could cause subsequent SQL statements on this table to fail. * Replication: When binary logging was enabled, using stored functions and triggers resulting in a long running procedure that inserted many records caused the memory use to increase rapidly. This was due to memory being allocated per variable. The fix ensures that in such a situation, memory is allocated once and the same memory is reused. * Replication: If an error was encountered while adding a GTID to the received GTID set, the log lock was not being correctly released. This could cause a deadlock. more...
2015-06-01 10:15:05 +02:00
share/mysql/test/suite/innodb_stress/include/innodb_stress.inc
share/mysql/test/suite/innodb_stress/r/innodb_bigstress.result
share/mysql/test/suite/innodb_stress/r/innodb_bigstress_blob.result
share/mysql/test/suite/innodb_stress/r/innodb_bigstress_blob_nocompress.result
share/mysql/test/suite/innodb_stress/r/innodb_bigstress_crash.result
share/mysql/test/suite/innodb_stress/r/innodb_bigstress_crash_blob.result
share/mysql/test/suite/innodb_stress/r/innodb_bigstress_crash_blob_nocompress.result
share/mysql/test/suite/innodb_stress/r/innodb_bigstress_crash_nocompress.result
share/mysql/test/suite/innodb_stress/r/innodb_bigstress_nocompress.result
share/mysql/test/suite/innodb_stress/r/innodb_hugestress.result
share/mysql/test/suite/innodb_stress/r/innodb_hugestress_blob.result
share/mysql/test/suite/innodb_stress/r/innodb_hugestress_blob_nocompress.result
share/mysql/test/suite/innodb_stress/r/innodb_hugestress_crash.result
share/mysql/test/suite/innodb_stress/r/innodb_hugestress_crash_blob.result
share/mysql/test/suite/innodb_stress/r/innodb_hugestress_crash_blob_nocompress.result
share/mysql/test/suite/innodb_stress/r/innodb_hugestress_crash_nocompress.result
share/mysql/test/suite/innodb_stress/r/innodb_hugestress_nocompress.result
share/mysql/test/suite/innodb_stress/r/innodb_stress.result
share/mysql/test/suite/innodb_stress/r/innodb_stress_blob.result
share/mysql/test/suite/innodb_stress/r/innodb_stress_blob_nocompress.result
share/mysql/test/suite/innodb_stress/r/innodb_stress_crash.result
share/mysql/test/suite/innodb_stress/r/innodb_stress_crash_blob.result
share/mysql/test/suite/innodb_stress/r/innodb_stress_crash_blob_nocompress.result
share/mysql/test/suite/innodb_stress/r/innodb_stress_crash_nocompress.result
share/mysql/test/suite/innodb_stress/r/innodb_stress_nocompress.result
share/mysql/test/suite/innodb_stress/t/Readme
share/mysql/test/suite/innodb_stress/t/innodb_bigstress-master.opt
share/mysql/test/suite/innodb_stress/t/innodb_bigstress-slave.opt
share/mysql/test/suite/innodb_stress/t/innodb_bigstress.test
share/mysql/test/suite/innodb_stress/t/innodb_bigstress_blob-master.opt
share/mysql/test/suite/innodb_stress/t/innodb_bigstress_blob-slave.opt
share/mysql/test/suite/innodb_stress/t/innodb_bigstress_blob.test
share/mysql/test/suite/innodb_stress/t/innodb_bigstress_blob_nocompress-master.opt
share/mysql/test/suite/innodb_stress/t/innodb_bigstress_blob_nocompress-slave.opt
share/mysql/test/suite/innodb_stress/t/innodb_bigstress_blob_nocompress.test
share/mysql/test/suite/innodb_stress/t/innodb_bigstress_crash-master.opt
share/mysql/test/suite/innodb_stress/t/innodb_bigstress_crash-slave.opt
share/mysql/test/suite/innodb_stress/t/innodb_bigstress_crash.test
share/mysql/test/suite/innodb_stress/t/innodb_bigstress_crash_blob-master.opt
share/mysql/test/suite/innodb_stress/t/innodb_bigstress_crash_blob-slave.opt
share/mysql/test/suite/innodb_stress/t/innodb_bigstress_crash_blob.test
share/mysql/test/suite/innodb_stress/t/innodb_bigstress_crash_blob_nocompress-master.opt
share/mysql/test/suite/innodb_stress/t/innodb_bigstress_crash_blob_nocompress-slave.opt
share/mysql/test/suite/innodb_stress/t/innodb_bigstress_crash_blob_nocompress.test
share/mysql/test/suite/innodb_stress/t/innodb_bigstress_crash_nocompress-master.opt
share/mysql/test/suite/innodb_stress/t/innodb_bigstress_crash_nocompress-slave.opt
share/mysql/test/suite/innodb_stress/t/innodb_bigstress_crash_nocompress.test
share/mysql/test/suite/innodb_stress/t/innodb_bigstress_nocompress-master.opt
share/mysql/test/suite/innodb_stress/t/innodb_bigstress_nocompress-slave.opt
share/mysql/test/suite/innodb_stress/t/innodb_bigstress_nocompress.test
share/mysql/test/suite/innodb_stress/t/innodb_hugestress-master.opt
share/mysql/test/suite/innodb_stress/t/innodb_hugestress-slave.opt
share/mysql/test/suite/innodb_stress/t/innodb_hugestress.test
share/mysql/test/suite/innodb_stress/t/innodb_hugestress_blob-master.opt
share/mysql/test/suite/innodb_stress/t/innodb_hugestress_blob-slave.opt
share/mysql/test/suite/innodb_stress/t/innodb_hugestress_blob.test
share/mysql/test/suite/innodb_stress/t/innodb_hugestress_blob_nocompress-master.opt
share/mysql/test/suite/innodb_stress/t/innodb_hugestress_blob_nocompress-slave.opt
share/mysql/test/suite/innodb_stress/t/innodb_hugestress_blob_nocompress.test
share/mysql/test/suite/innodb_stress/t/innodb_hugestress_crash-master.opt
share/mysql/test/suite/innodb_stress/t/innodb_hugestress_crash-slave.opt
share/mysql/test/suite/innodb_stress/t/innodb_hugestress_crash.test
share/mysql/test/suite/innodb_stress/t/innodb_hugestress_crash_blob-master.opt
share/mysql/test/suite/innodb_stress/t/innodb_hugestress_crash_blob-slave.opt
share/mysql/test/suite/innodb_stress/t/innodb_hugestress_crash_blob.test
share/mysql/test/suite/innodb_stress/t/innodb_hugestress_crash_blob_nocompress-master.opt
share/mysql/test/suite/innodb_stress/t/innodb_hugestress_crash_blob_nocompress-slave.opt
share/mysql/test/suite/innodb_stress/t/innodb_hugestress_crash_blob_nocompress.test
share/mysql/test/suite/innodb_stress/t/innodb_hugestress_crash_nocompress-master.opt
share/mysql/test/suite/innodb_stress/t/innodb_hugestress_crash_nocompress-slave.opt
share/mysql/test/suite/innodb_stress/t/innodb_hugestress_crash_nocompress.test
share/mysql/test/suite/innodb_stress/t/innodb_hugestress_nocompress-master.opt
share/mysql/test/suite/innodb_stress/t/innodb_hugestress_nocompress-slave.opt
share/mysql/test/suite/innodb_stress/t/innodb_hugestress_nocompress.test
share/mysql/test/suite/innodb_stress/t/innodb_stress-master.opt
share/mysql/test/suite/innodb_stress/t/innodb_stress-slave.opt
share/mysql/test/suite/innodb_stress/t/innodb_stress.test
share/mysql/test/suite/innodb_stress/t/innodb_stress_blob-master.opt
share/mysql/test/suite/innodb_stress/t/innodb_stress_blob-slave.opt
share/mysql/test/suite/innodb_stress/t/innodb_stress_blob.test
share/mysql/test/suite/innodb_stress/t/innodb_stress_blob_nocompress-master.opt
share/mysql/test/suite/innodb_stress/t/innodb_stress_blob_nocompress-slave.opt
share/mysql/test/suite/innodb_stress/t/innodb_stress_blob_nocompress.test
share/mysql/test/suite/innodb_stress/t/innodb_stress_crash-master.opt
share/mysql/test/suite/innodb_stress/t/innodb_stress_crash-slave.opt
share/mysql/test/suite/innodb_stress/t/innodb_stress_crash.test
share/mysql/test/suite/innodb_stress/t/innodb_stress_crash_blob-master.opt
share/mysql/test/suite/innodb_stress/t/innodb_stress_crash_blob-slave.opt
share/mysql/test/suite/innodb_stress/t/innodb_stress_crash_blob.test
share/mysql/test/suite/innodb_stress/t/innodb_stress_crash_blob_nocompress-master.opt
share/mysql/test/suite/innodb_stress/t/innodb_stress_crash_blob_nocompress-slave.opt
share/mysql/test/suite/innodb_stress/t/innodb_stress_crash_blob_nocompress.test
share/mysql/test/suite/innodb_stress/t/innodb_stress_crash_nocompress-master.opt
share/mysql/test/suite/innodb_stress/t/innodb_stress_crash_nocompress-slave.opt
share/mysql/test/suite/innodb_stress/t/innodb_stress_crash_nocompress.test
share/mysql/test/suite/innodb_stress/t/innodb_stress_nocompress-master.opt
share/mysql/test/suite/innodb_stress/t/innodb_stress_nocompress-slave.opt
share/mysql/test/suite/innodb_stress/t/innodb_stress_nocompress.test
share/mysql/test/suite/innodb_stress/t/load_generator.py
Changes 5.6.16: Functionality Added or Changed * InnoDB: New global configuration parameters, innodb_status_output and innodb_status_output_locks, allow you to dynamically enable and disable the standard InnoDB Monitor and InnoDB Lock Monitor for periodic output. Enabling and disabling monitors for periodic output by creating and dropping specially named tables is deprecated and may be removed in a future release. * Previously, ALTER TABLE in MySQL 5.6 could alter a table such that the result had temporal columns in both 5.5 and 5.6 format. Now ALTER TABLE upgrades old temporal columns to 5.6 format for ADD COLUMN, CHANGE COLUMN, MODIFY COLUMN, ADD INDEX, and FORCE operations. This conversion cannot be done using the INPLACE algorithm, so specifying ALGORITHM=INPLACE in these cases results in an error. * CMake now supports a -DTMPDIR=dir_name option to specify the default tmpdir value. If unspecified, the value defaults to P_tmpdir in <stdio.h>. Bugs Fixed * InnoDB; Replication: Using the InnoDB memcached plugin (see InnoDB Integration with memcached) with innodb_api_enable_binlog set to 1 caused the server to leak memory. * InnoDB: A boolean mode full-text search query would result in a memory access violation during parsing. * InnoDB: When new indexes are added by an ALTER TABLE operation, instead of only saving table-level statistics and statistics for the new indexes, InnoDB would save statistics for the entire table, including the table's other indexes. This behavior slowed ALTER TABLE performance. * InnoDB: Due to a parser error, full-text search queries that include a sub-expression could return the wrong result. * InnoDB: The innochecksum tool did not use a Windows-specific API to retrieve file size information, which resulted in an incorrect error message (Error: ibdata1 cannot be found) when the MySQL 5.6 innochecksum 2GB file size limit was exceeded. innochecksum now provides support for files larger than 2GB in both MySQL 5.6 and MySQL 5.7. * InnoDB: Due to a regression introduced by the fix for Bug17371537, memory was not allocated for the default memcached engine when using the default memcached engine as the backstore for data instead of InnoDB. * InnoDB: InnoDB would report an incorrect operating system error code after failing to initialize. * InnoDB: Manipulating a table after discarding its tablespace using ALTER TABLE ... DISCARD TABLESPACE could result in a serious error. * InnoDB: Persistent optimizer statistics would cause stalls due to latch contention. * InnoDB: MATCH() ... AGAINST queries that use a long string as an argument for AGAINST() could result in an error when run on an InnoDB table with a full-text search index. * InnoDB: An InnoDB full-text search failure would occur due to an “unended” token. The string and string length should be passed for string comparison. * InnoDB: In debug builds, a merge insert buffer during a page read would cause a memory access violation. * InnoDB: Truncating a memcached InnoDB table while memcached is performing DML operations would result in a serious error. * InnoDB: In sync0rw.ic, rw_lock_x_lock_func_nowait would needlessly call os_thread_get_curr_id. * InnoDB: Attempting to rename a table to a missing database would result in a serious error. more...
2014-02-13 08:49:56 +01:00
share/mysql/test/suite/innodb_zip/include/innodb_create_tab_indx.inc
share/mysql/test/suite/innodb_zip/include/innodb_fetch_records.inc
share/mysql/test/suite/innodb_zip/include/innodb_load_data.inc
share/mysql/test/suite/innodb_zip/include/innodb_stats_comp_index.inc
share/mysql/test/suite/innodb_zip/include/innodb_stats_restart.inc
share/mysql/test/suite/innodb_zip/r/innodb-create-options.result
share/mysql/test/suite/innodb_zip/r/innodb-restart.result
share/mysql/test/suite/innodb_zip/r/innodb-wl5522-debug-zip.result
share/mysql/test/suite/innodb_zip/r/innodb-wl5522-zip.result
share/mysql/test/suite/innodb_zip/r/innodb-zip.result
share/mysql/test/suite/innodb_zip/r/innodb_16k.result
share/mysql/test/suite/innodb_zip/r/innodb_4k.result
share/mysql/test/suite/innodb_zip/r/innodb_8k.result
share/mysql/test/suite/innodb_zip/r/innodb_bug36169.result
share/mysql/test/suite/innodb_zip/r/innodb_bug36172.result
share/mysql/test/suite/innodb_zip/r/innodb_bug52745.result
share/mysql/test/suite/innodb_zip/r/innodb_bug53591.result
share/mysql/test/suite/innodb_zip/r/innodb_bug56680.result
share/mysql/test/suite/innodb_zip/r/innodb_cmp_drop_table.result
share/mysql/test/suite/innodb_zip/r/innodb_cmp_per_index.result
share/mysql/test/suite/innodb_zip/r/innodb_index_large_prefix.result
share/mysql/test/suite/innodb_zip/r/innodb_index_large_prefix_4k.result
share/mysql/test/suite/innodb_zip/r/innodb_index_large_prefix_8k.result
share/mysql/test/suite/innodb_zip/r/innodb_prefix_index_liftedlimit.result
share/mysql/test/suite/innodb_zip/r/innodb_wl6347_comp_indx_stat.result
share/mysql/test/suite/innodb_zip/t/innodb-create-options.test
share/mysql/test/suite/innodb_zip/t/innodb-restart.test
share/mysql/test/suite/innodb_zip/t/innodb-wl5522-debug-zip.test
share/mysql/test/suite/innodb_zip/t/innodb-wl5522-zip.test
share/mysql/test/suite/innodb_zip/t/innodb-zip.test
share/mysql/test/suite/innodb_zip/t/innodb_16k.test
share/mysql/test/suite/innodb_zip/t/innodb_4k.test
share/mysql/test/suite/innodb_zip/t/innodb_8k.test
share/mysql/test/suite/innodb_zip/t/innodb_bug36169.test
share/mysql/test/suite/innodb_zip/t/innodb_bug36172.test
share/mysql/test/suite/innodb_zip/t/innodb_bug52745.test
share/mysql/test/suite/innodb_zip/t/innodb_bug53591.test
share/mysql/test/suite/innodb_zip/t/innodb_bug56680.test
share/mysql/test/suite/innodb_zip/t/innodb_cmp_drop_table-master.opt
share/mysql/test/suite/innodb_zip/t/innodb_cmp_drop_table.test
share/mysql/test/suite/innodb_zip/t/innodb_cmp_per_index.test
share/mysql/test/suite/innodb_zip/t/innodb_index_large_prefix.test
share/mysql/test/suite/innodb_zip/t/innodb_index_large_prefix_4k.test
share/mysql/test/suite/innodb_zip/t/innodb_index_large_prefix_8k.test
share/mysql/test/suite/innodb_zip/t/innodb_prefix_index_liftedlimit.test
share/mysql/test/suite/innodb_zip/t/innodb_wl6347_comp_indx_stat.test
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/jp/include/trim_sjis.inc
share/mysql/test/suite/jp/r/jp_alter_sjis.result
share/mysql/test/suite/jp/r/jp_alter_ucs2.result
share/mysql/test/suite/jp/r/jp_alter_ujis.result
share/mysql/test/suite/jp/r/jp_alter_utf8.result
share/mysql/test/suite/jp/r/jp_charlength_sjis.result
share/mysql/test/suite/jp/r/jp_charlength_ucs2.result
share/mysql/test/suite/jp/r/jp_charlength_ujis.result
share/mysql/test/suite/jp/r/jp_charlength_utf8.result
share/mysql/test/suite/jp/r/jp_charset_sjis.result
share/mysql/test/suite/jp/r/jp_charset_ucs2.result
share/mysql/test/suite/jp/r/jp_charset_ujis.result
share/mysql/test/suite/jp/r/jp_charset_utf8.result
share/mysql/test/suite/jp/r/jp_convert_sjis.result
share/mysql/test/suite/jp/r/jp_convert_ucs2.result
share/mysql/test/suite/jp/r/jp_convert_ujis.result
share/mysql/test/suite/jp/r/jp_convert_utf8.result
share/mysql/test/suite/jp/r/jp_create_db_sjis.result
share/mysql/test/suite/jp/r/jp_create_db_ucs2.result
share/mysql/test/suite/jp/r/jp_create_db_ujis.result
share/mysql/test/suite/jp/r/jp_create_db_utf8.result
share/mysql/test/suite/jp/r/jp_create_tbl_sjis.result
share/mysql/test/suite/jp/r/jp_create_tbl_ucs2.result
share/mysql/test/suite/jp/r/jp_create_tbl_ujis.result
share/mysql/test/suite/jp/r/jp_create_tbl_utf8.result
share/mysql/test/suite/jp/r/jp_enum_sjis.result
share/mysql/test/suite/jp/r/jp_enum_ucs2.result
share/mysql/test/suite/jp/r/jp_enum_ujis.result
share/mysql/test/suite/jp/r/jp_enum_utf8.result
share/mysql/test/suite/jp/r/jp_insert_sjis.result
share/mysql/test/suite/jp/r/jp_insert_ucs2.result
share/mysql/test/suite/jp/r/jp_insert_ujis.result
share/mysql/test/suite/jp/r/jp_insert_utf8.result
share/mysql/test/suite/jp/r/jp_instr_sjis.result
share/mysql/test/suite/jp/r/jp_instr_ucs2.result
share/mysql/test/suite/jp/r/jp_instr_ujis.result
share/mysql/test/suite/jp/r/jp_instr_utf8.result
share/mysql/test/suite/jp/r/jp_join_sjis.result
share/mysql/test/suite/jp/r/jp_join_ucs2.result
share/mysql/test/suite/jp/r/jp_join_ujis.result
share/mysql/test/suite/jp/r/jp_join_utf8.result
share/mysql/test/suite/jp/r/jp_left_sjis.result
share/mysql/test/suite/jp/r/jp_left_ucs2.result
share/mysql/test/suite/jp/r/jp_left_ujis.result
share/mysql/test/suite/jp/r/jp_left_utf8.result
share/mysql/test/suite/jp/r/jp_length_sjis.result
share/mysql/test/suite/jp/r/jp_length_ucs2.result
share/mysql/test/suite/jp/r/jp_length_ujis.result
share/mysql/test/suite/jp/r/jp_length_utf8.result
share/mysql/test/suite/jp/r/jp_like_sjis.result
share/mysql/test/suite/jp/r/jp_like_ucs2.result
share/mysql/test/suite/jp/r/jp_like_ujis.result
share/mysql/test/suite/jp/r/jp_like_utf8.result
share/mysql/test/suite/jp/r/jp_locate_sjis.result
share/mysql/test/suite/jp/r/jp_locate_ucs2.result
share/mysql/test/suite/jp/r/jp_locate_ujis.result
share/mysql/test/suite/jp/r/jp_locate_utf8.result
share/mysql/test/suite/jp/r/jp_lpad_sjis.result
share/mysql/test/suite/jp/r/jp_lpad_ucs2.result
share/mysql/test/suite/jp/r/jp_lpad_ujis.result
share/mysql/test/suite/jp/r/jp_lpad_utf8.result
share/mysql/test/suite/jp/r/jp_ltrim_sjis.result
share/mysql/test/suite/jp/r/jp_ltrim_ucs2.result
share/mysql/test/suite/jp/r/jp_ltrim_ujis.result
share/mysql/test/suite/jp/r/jp_ltrim_utf8.result
share/mysql/test/suite/jp/r/jp_ps_sjis.result
share/mysql/test/suite/jp/r/jp_ps_ujis.result
share/mysql/test/suite/jp/r/jp_replace_sjis.result
share/mysql/test/suite/jp/r/jp_replace_ucs2.result
share/mysql/test/suite/jp/r/jp_replace_ujis.result
share/mysql/test/suite/jp/r/jp_replace_utf8.result
share/mysql/test/suite/jp/r/jp_reverse_sjis.result
share/mysql/test/suite/jp/r/jp_reverse_ucs2.result
share/mysql/test/suite/jp/r/jp_reverse_ujis.result
share/mysql/test/suite/jp/r/jp_reverse_utf8.result
share/mysql/test/suite/jp/r/jp_right_sjis.result
share/mysql/test/suite/jp/r/jp_right_ucs2.result
share/mysql/test/suite/jp/r/jp_right_ujis.result
share/mysql/test/suite/jp/r/jp_right_utf8.result
share/mysql/test/suite/jp/r/jp_rpad_sjis.result
share/mysql/test/suite/jp/r/jp_rpad_ucs2.result
share/mysql/test/suite/jp/r/jp_rpad_ujis.result
share/mysql/test/suite/jp/r/jp_rpad_utf8.result
share/mysql/test/suite/jp/r/jp_rtrim_sjis.result
share/mysql/test/suite/jp/r/jp_rtrim_ucs2.result
share/mysql/test/suite/jp/r/jp_rtrim_ujis.result
share/mysql/test/suite/jp/r/jp_rtrim_utf8.result
share/mysql/test/suite/jp/r/jp_select_sjis.result
share/mysql/test/suite/jp/r/jp_select_ucs2.result
share/mysql/test/suite/jp/r/jp_select_ujis.result
share/mysql/test/suite/jp/r/jp_select_utf8.result
share/mysql/test/suite/jp/r/jp_subquery_sjis.result
share/mysql/test/suite/jp/r/jp_subquery_ucs2.result
share/mysql/test/suite/jp/r/jp_subquery_ujis.result
share/mysql/test/suite/jp/r/jp_subquery_utf8.result
share/mysql/test/suite/jp/r/jp_substring_sjis.result
share/mysql/test/suite/jp/r/jp_substring_ucs2.result
share/mysql/test/suite/jp/r/jp_substring_ujis.result
share/mysql/test/suite/jp/r/jp_substring_utf8.result
share/mysql/test/suite/jp/r/jp_trim_sjis.result
share/mysql/test/suite/jp/r/jp_trim_ucs2.result
share/mysql/test/suite/jp/r/jp_trim_ujis.result
share/mysql/test/suite/jp/r/jp_trim_utf8.result
share/mysql/test/suite/jp/r/jp_union_ujis.result
share/mysql/test/suite/jp/r/jp_update_sjis.result
share/mysql/test/suite/jp/r/jp_update_ucs2.result
share/mysql/test/suite/jp/r/jp_update_ujis.result
share/mysql/test/suite/jp/r/jp_update_utf8.result
share/mysql/test/suite/jp/r/jp_where_sjis.result
share/mysql/test/suite/jp/r/jp_where_ucs2.result
share/mysql/test/suite/jp/r/jp_where_ujis.result
share/mysql/test/suite/jp/r/jp_where_utf8.result
share/mysql/test/suite/jp/std_data/jisx0201_sjis.dat
share/mysql/test/suite/jp/std_data/jisx0201_ucs2.dat
share/mysql/test/suite/jp/std_data/jisx0201_ujis.dat
share/mysql/test/suite/jp/std_data/jisx0201_utf8.dat
share/mysql/test/suite/jp/std_data/jisx0208_sjis.dat
share/mysql/test/suite/jp/std_data/jisx0208_sjis2.dat
share/mysql/test/suite/jp/std_data/jisx0208_sjis3.dat
share/mysql/test/suite/jp/std_data/jisx0208_ucs2.dat
share/mysql/test/suite/jp/std_data/jisx0208_ujis.dat
share/mysql/test/suite/jp/std_data/jisx0208_utf8.dat
share/mysql/test/suite/jp/std_data/jisx0212_ucs2.dat
share/mysql/test/suite/jp/std_data/jisx0212_ujis.dat
share/mysql/test/suite/jp/std_data/jisx0212_utf8.dat
share/mysql/test/suite/jp/t/disabled.def
share/mysql/test/suite/jp/t/jp_alter_sjis.test
share/mysql/test/suite/jp/t/jp_alter_ucs2.test
share/mysql/test/suite/jp/t/jp_alter_ujis.test
share/mysql/test/suite/jp/t/jp_alter_utf8.test
share/mysql/test/suite/jp/t/jp_charlength_sjis.test
share/mysql/test/suite/jp/t/jp_charlength_ucs2.test
share/mysql/test/suite/jp/t/jp_charlength_ujis.test
share/mysql/test/suite/jp/t/jp_charlength_utf8.test
share/mysql/test/suite/jp/t/jp_charset_sjis.test
share/mysql/test/suite/jp/t/jp_charset_ucs2.test
share/mysql/test/suite/jp/t/jp_charset_ujis.test
share/mysql/test/suite/jp/t/jp_charset_utf8.test
share/mysql/test/suite/jp/t/jp_convert_sjis.test
share/mysql/test/suite/jp/t/jp_convert_ucs2.test
share/mysql/test/suite/jp/t/jp_convert_ujis.test
share/mysql/test/suite/jp/t/jp_convert_utf8.test
share/mysql/test/suite/jp/t/jp_create_db_sjis.test
share/mysql/test/suite/jp/t/jp_create_db_ucs2.test
share/mysql/test/suite/jp/t/jp_create_db_ujis.test
share/mysql/test/suite/jp/t/jp_create_db_utf8.test
share/mysql/test/suite/jp/t/jp_create_tbl_sjis.test
share/mysql/test/suite/jp/t/jp_create_tbl_ucs2.test
share/mysql/test/suite/jp/t/jp_create_tbl_ujis.test
share/mysql/test/suite/jp/t/jp_create_tbl_utf8.test
share/mysql/test/suite/jp/t/jp_enum_sjis.test
share/mysql/test/suite/jp/t/jp_enum_ucs2.test
share/mysql/test/suite/jp/t/jp_enum_ujis.test
share/mysql/test/suite/jp/t/jp_enum_utf8.test
share/mysql/test/suite/jp/t/jp_insert_sjis.test
share/mysql/test/suite/jp/t/jp_insert_ucs2.test
share/mysql/test/suite/jp/t/jp_insert_ujis.test
share/mysql/test/suite/jp/t/jp_insert_utf8.test
share/mysql/test/suite/jp/t/jp_instr_sjis.test
share/mysql/test/suite/jp/t/jp_instr_ucs2.test
share/mysql/test/suite/jp/t/jp_instr_ujis.test
share/mysql/test/suite/jp/t/jp_instr_utf8.test
share/mysql/test/suite/jp/t/jp_join_sjis.test
share/mysql/test/suite/jp/t/jp_join_ucs2.test
share/mysql/test/suite/jp/t/jp_join_ujis.test
share/mysql/test/suite/jp/t/jp_join_utf8.test
share/mysql/test/suite/jp/t/jp_left_sjis.test
share/mysql/test/suite/jp/t/jp_left_ucs2.test
share/mysql/test/suite/jp/t/jp_left_ujis.test
share/mysql/test/suite/jp/t/jp_left_utf8.test
share/mysql/test/suite/jp/t/jp_length_sjis.test
share/mysql/test/suite/jp/t/jp_length_ucs2.test
share/mysql/test/suite/jp/t/jp_length_ujis.test
share/mysql/test/suite/jp/t/jp_length_utf8.test
share/mysql/test/suite/jp/t/jp_like_sjis.test
share/mysql/test/suite/jp/t/jp_like_ucs2.test
share/mysql/test/suite/jp/t/jp_like_ujis.test
share/mysql/test/suite/jp/t/jp_like_utf8.test
share/mysql/test/suite/jp/t/jp_locate_sjis.test
share/mysql/test/suite/jp/t/jp_locate_ucs2.test
share/mysql/test/suite/jp/t/jp_locate_ujis.test
share/mysql/test/suite/jp/t/jp_locate_utf8.test
share/mysql/test/suite/jp/t/jp_lpad_sjis.test
share/mysql/test/suite/jp/t/jp_lpad_ucs2.test
share/mysql/test/suite/jp/t/jp_lpad_ujis.test
share/mysql/test/suite/jp/t/jp_lpad_utf8.test
share/mysql/test/suite/jp/t/jp_ltrim_sjis.test
share/mysql/test/suite/jp/t/jp_ltrim_ucs2.test
share/mysql/test/suite/jp/t/jp_ltrim_ujis.test
share/mysql/test/suite/jp/t/jp_ltrim_utf8.test
share/mysql/test/suite/jp/t/jp_ps_sjis.test
share/mysql/test/suite/jp/t/jp_ps_ujis.test
share/mysql/test/suite/jp/t/jp_replace_sjis.test
share/mysql/test/suite/jp/t/jp_replace_ucs2.test
share/mysql/test/suite/jp/t/jp_replace_ujis.test
share/mysql/test/suite/jp/t/jp_replace_utf8.test
share/mysql/test/suite/jp/t/jp_reverse_sjis.test
share/mysql/test/suite/jp/t/jp_reverse_ucs2.test
share/mysql/test/suite/jp/t/jp_reverse_ujis.test
share/mysql/test/suite/jp/t/jp_reverse_utf8.test
share/mysql/test/suite/jp/t/jp_right_sjis.test
share/mysql/test/suite/jp/t/jp_right_ucs2.test
share/mysql/test/suite/jp/t/jp_right_ujis.test
share/mysql/test/suite/jp/t/jp_right_utf8.test
share/mysql/test/suite/jp/t/jp_rpad_sjis.test
share/mysql/test/suite/jp/t/jp_rpad_ucs2.test
share/mysql/test/suite/jp/t/jp_rpad_ujis.test
share/mysql/test/suite/jp/t/jp_rpad_utf8.test
share/mysql/test/suite/jp/t/jp_rtrim_sjis.test
share/mysql/test/suite/jp/t/jp_rtrim_ucs2.test
share/mysql/test/suite/jp/t/jp_rtrim_ujis.test
share/mysql/test/suite/jp/t/jp_rtrim_utf8.test
share/mysql/test/suite/jp/t/jp_select_sjis.test
share/mysql/test/suite/jp/t/jp_select_ucs2.test
share/mysql/test/suite/jp/t/jp_select_ujis.test
share/mysql/test/suite/jp/t/jp_select_utf8.test
share/mysql/test/suite/jp/t/jp_subquery_sjis.test
share/mysql/test/suite/jp/t/jp_subquery_ucs2.test
share/mysql/test/suite/jp/t/jp_subquery_ujis.test
share/mysql/test/suite/jp/t/jp_subquery_utf8.test
share/mysql/test/suite/jp/t/jp_substring_sjis.test
share/mysql/test/suite/jp/t/jp_substring_ucs2.test
share/mysql/test/suite/jp/t/jp_substring_ujis.test
share/mysql/test/suite/jp/t/jp_substring_utf8.test
share/mysql/test/suite/jp/t/jp_trim_sjis.test
share/mysql/test/suite/jp/t/jp_trim_ucs2.test
share/mysql/test/suite/jp/t/jp_trim_ujis.test
share/mysql/test/suite/jp/t/jp_trim_utf8.test
share/mysql/test/suite/jp/t/jp_union_ujis.test
share/mysql/test/suite/jp/t/jp_update_sjis.test
share/mysql/test/suite/jp/t/jp_update_ucs2.test
share/mysql/test/suite/jp/t/jp_update_ujis.test
share/mysql/test/suite/jp/t/jp_update_utf8.test
share/mysql/test/suite/jp/t/jp_where_sjis.test
share/mysql/test/suite/jp/t/jp_where_ucs2.test
share/mysql/test/suite/jp/t/jp_where_ujis.test
share/mysql/test/suite/jp/t/jp_where_utf8.test
share/mysql/test/suite/large_tests/README.TXT
share/mysql/test/suite/large_tests/r/alter_table.result
share/mysql/test/suite/large_tests/r/lock_tables_big.result
share/mysql/test/suite/large_tests/r/rpl_slave_net_timeout.result
share/mysql/test/suite/large_tests/t/alter_table.test
share/mysql/test/suite/large_tests/t/lock_tables_big.test
share/mysql/test/suite/large_tests/t/rpl_slave_net_timeout-slave.opt
share/mysql/test/suite/large_tests/t/rpl_slave_net_timeout.test
share/mysql/test/suite/ndb/backups/50/BACKUP-1-0.1.Data
share/mysql/test/suite/ndb/backups/50/BACKUP-1-0.2.Data
share/mysql/test/suite/ndb/backups/50/BACKUP-1.1.ctl
share/mysql/test/suite/ndb/backups/50/BACKUP-1.1.log
share/mysql/test/suite/ndb/backups/50/BACKUP-1.2.ctl
share/mysql/test/suite/ndb/backups/50/BACKUP-1.2.log
share/mysql/test/suite/ndb/backups/50/BACKUP-2-0.1.Data
share/mysql/test/suite/ndb/backups/50/BACKUP-2-0.2.Data
share/mysql/test/suite/ndb/backups/50/BACKUP-2.1.ctl
share/mysql/test/suite/ndb/backups/50/BACKUP-2.1.log
share/mysql/test/suite/ndb/backups/50/BACKUP-2.2.ctl
share/mysql/test/suite/ndb/backups/50/BACKUP-2.2.log
share/mysql/test/suite/ndb/backups/51/BACKUP-1-0.1.Data
share/mysql/test/suite/ndb/backups/51/BACKUP-1-0.2.Data
share/mysql/test/suite/ndb/backups/51/BACKUP-1.1.ctl
share/mysql/test/suite/ndb/backups/51/BACKUP-1.1.log
share/mysql/test/suite/ndb/backups/51/BACKUP-1.2.ctl
share/mysql/test/suite/ndb/backups/51/BACKUP-1.2.log
share/mysql/test/suite/ndb/backups/51_d2_be/BACKUP-1-0.1.Data
share/mysql/test/suite/ndb/backups/51_d2_be/BACKUP-1-0.2.Data
share/mysql/test/suite/ndb/backups/51_d2_be/BACKUP-1.1.ctl
share/mysql/test/suite/ndb/backups/51_d2_be/BACKUP-1.1.log
share/mysql/test/suite/ndb/backups/51_d2_be/BACKUP-1.2.ctl
share/mysql/test/suite/ndb/backups/51_d2_be/BACKUP-1.2.log
share/mysql/test/suite/ndb/backups/51_d2_le/BACKUP-1-0.1.Data
share/mysql/test/suite/ndb/backups/51_d2_le/BACKUP-1-0.2.Data
share/mysql/test/suite/ndb/backups/51_d2_le/BACKUP-1.1.ctl
share/mysql/test/suite/ndb/backups/51_d2_le/BACKUP-1.1.log
share/mysql/test/suite/ndb/backups/51_d2_le/BACKUP-1.2.ctl
share/mysql/test/suite/ndb/backups/51_d2_le/BACKUP-1.2.log
share/mysql/test/suite/ndb/backups/51_data_be/BACKUP-1-0.1.Data
share/mysql/test/suite/ndb/backups/51_data_be/BACKUP-1-0.2.Data
share/mysql/test/suite/ndb/backups/51_data_be/BACKUP-1.1.ctl
share/mysql/test/suite/ndb/backups/51_data_be/BACKUP-1.1.log
share/mysql/test/suite/ndb/backups/51_data_be/BACKUP-1.2.ctl
share/mysql/test/suite/ndb/backups/51_data_be/BACKUP-1.2.log
share/mysql/test/suite/ndb/backups/51_data_le/BACKUP-1-0.1.Data
share/mysql/test/suite/ndb/backups/51_data_le/BACKUP-1-0.2.Data
share/mysql/test/suite/ndb/backups/51_data_le/BACKUP-1.1.ctl
share/mysql/test/suite/ndb/backups/51_data_le/BACKUP-1.1.log
share/mysql/test/suite/ndb/backups/51_data_le/BACKUP-1.2.ctl
share/mysql/test/suite/ndb/backups/51_data_le/BACKUP-1.2.log
share/mysql/test/suite/ndb/backups/51_dd/BACKUP-1-0.1.Data
share/mysql/test/suite/ndb/backups/51_dd/BACKUP-1-0.2.Data
share/mysql/test/suite/ndb/backups/51_dd/BACKUP-1.1.ctl
share/mysql/test/suite/ndb/backups/51_dd/BACKUP-1.1.log
share/mysql/test/suite/ndb/backups/51_dd/BACKUP-1.2.ctl
share/mysql/test/suite/ndb/backups/51_dd/BACKUP-1.2.log
share/mysql/test/suite/ndb/backups/51_undolog_be/BACKUP-1-0.1.Data
share/mysql/test/suite/ndb/backups/51_undolog_be/BACKUP-1-0.2.Data
share/mysql/test/suite/ndb/backups/51_undolog_be/BACKUP-1.1.ctl
share/mysql/test/suite/ndb/backups/51_undolog_be/BACKUP-1.1.log
share/mysql/test/suite/ndb/backups/51_undolog_be/BACKUP-1.2.ctl
share/mysql/test/suite/ndb/backups/51_undolog_be/BACKUP-1.2.log
share/mysql/test/suite/ndb/backups/51_undolog_le/BACKUP-1-0.1.Data
share/mysql/test/suite/ndb/backups/51_undolog_le/BACKUP-1-0.2.Data
share/mysql/test/suite/ndb/backups/51_undolog_le/BACKUP-1.1.ctl
share/mysql/test/suite/ndb/backups/51_undolog_le/BACKUP-1.1.log
share/mysql/test/suite/ndb/backups/51_undolog_le/BACKUP-1.2.ctl
share/mysql/test/suite/ndb/backups/51_undolog_le/BACKUP-1.2.log
share/mysql/test/suite/ndb/backups/before_native_default/BACKUP-1-0.1.Data
share/mysql/test/suite/ndb/backups/before_native_default/BACKUP-1-0.2.Data
share/mysql/test/suite/ndb/backups/before_native_default/BACKUP-1.1.ctl
share/mysql/test/suite/ndb/backups/before_native_default/BACKUP-1.1.log
share/mysql/test/suite/ndb/backups/before_native_default/BACKUP-1.2.ctl
share/mysql/test/suite/ndb/backups/before_native_default/BACKUP-1.2.log
share/mysql/test/suite/ndb/backups/bug54613/BACKUP-2.2.ctl
share/mysql/test/suite/ndb/backups/hashmap/BACKUP-1.2.ctl
share/mysql/test/suite/ndb/backups/packed/BACKUP-1-0.2.Data
share/mysql/test/suite/ndb/backups/packed/BACKUP-1.2.ctl
share/mysql/test/suite/ndb/backups/packed/BACKUP-1.2.log
share/mysql/test/suite/ndb/bug12712109.ini
share/mysql/test/suite/ndb/bug49400.ini
share/mysql/test/suite/ndb/bug56185.ini
share/mysql/test/suite/ndb/data/table_data10000.dat
share/mysql/test/suite/ndb/data/table_data100000.dat
share/mysql/test/suite/ndb/include/have_clusterj.inc
share/mysql/test/suite/ndb/include/have_clusterj_jpa.inc
share/mysql/test/suite/ndb/include/have_connectorj.inc
share/mysql/test/suite/ndb/include/have_java.inc
share/mysql/test/suite/ndb/include/have_junit.inc
share/mysql/test/suite/ndb/include/have_ndbjtie_junit.inc
share/mysql/test/suite/ndb/include/have_openjpa.inc
share/mysql/test/suite/ndb/include/memory_usage.inc
share/mysql/test/suite/ndb/include/ndb_add_node.cnf
share/mysql/test/suite/ndb/include/ndb_add_node_mysqld.cnf
share/mysql/test/suite/ndb/include/ndb_desc_print.inc
share/mysql/test/suite/ndb/include/ndb_execute_count.inc
share/mysql/test/suite/ndb/include/ndb_info.inc
share/mysql/test/suite/ndb/include/ndb_init_execute_count.inc
share/mysql/test/suite/ndb/include/ndb_init_scan_counts.inc
share/mysql/test/suite/ndb/include/ndb_scan_counts.inc
share/mysql/test/suite/ndb/include/ndb_share_check_shares.inc
share/mysql/test/suite/ndb/include/restart_cluster.inc
share/mysql/test/suite/ndb/include/restart_cluster_rolling.inc
share/mysql/test/suite/ndb/include/restart_node.inc
share/mysql/test/suite/ndb/include/restart_random_node.inc
share/mysql/test/suite/ndb/include/run_java.inc
share/mysql/test/suite/ndb/include/run_ndbapitest.inc
share/mysql/test/suite/ndb/my.cnf
share/mysql/test/suite/ndb/ndb_config_config.ini
share/mysql/test/suite/ndb/ndb_config_mycnf1.cnf
share/mysql/test/suite/ndb/ndb_config_mycnf2.cnf
share/mysql/test/suite/ndb/ndb_config_threadconfig.ini
share/mysql/test/suite/ndb/r/bug36547.result
share/mysql/test/suite/ndb/r/loaddata_autocom_ndb.result
share/mysql/test/suite/ndb/r/ndb_add_partition.result
share/mysql/test/suite/ndb/r/ndb_alter_table.result
share/mysql/test/suite/ndb/r/ndb_alter_table2.result
share/mysql/test/suite/ndb/r/ndb_alter_table3.result
share/mysql/test/suite/ndb/r/ndb_alter_table_backup.result
share/mysql/test/suite/ndb/r/ndb_alter_table_error.result
share/mysql/test/suite/ndb/r/ndb_alter_table_online.result
share/mysql/test/suite/ndb/r/ndb_alter_table_online2.result
share/mysql/test/suite/ndb/r/ndb_alter_table_online_multi.result
share/mysql/test/suite/ndb/r/ndb_auto_increment.result
share/mysql/test/suite/ndb/r/ndb_autoinc.result
share/mysql/test/suite/ndb/r/ndb_basic.result
share/mysql/test/suite/ndb/r/ndb_bitfield.result
share/mysql/test/suite/ndb/r/ndb_blob.result
share/mysql/test/suite/ndb/r/ndb_blob_big.result
share/mysql/test/suite/ndb/r/ndb_blob_partition.result
share/mysql/test/suite/ndb/r/ndb_bug26793.result
share/mysql/test/suite/ndb/r/ndb_bug31477.result
share/mysql/test/suite/ndb/r/ndb_bug31754.result
share/mysql/test/suite/ndb/r/ndb_bulk_delete.result
share/mysql/test/suite/ndb/r/ndb_cache.result
share/mysql/test/suite/ndb/r/ndb_cache2.result
share/mysql/test/suite/ndb/r/ndb_cache_multi.result
share/mysql/test/suite/ndb/r/ndb_cache_multi2.result
share/mysql/test/suite/ndb/r/ndb_cache_trans.result
share/mysql/test/suite/ndb/r/ndb_charset.result
share/mysql/test/suite/ndb/r/ndb_column_properties.result
share/mysql/test/suite/ndb/r/ndb_condition_pushdown.result
share/mysql/test/suite/ndb/r/ndb_config.result
share/mysql/test/suite/ndb/r/ndb_config2.result
share/mysql/test/suite/ndb/r/ndb_create_table.result
share/mysql/test/suite/ndb/r/ndb_cursor.result
share/mysql/test/suite/ndb/r/ndb_database.result
share/mysql/test/suite/ndb/r/ndb_dbug_lock.result
share/mysql/test/suite/ndb/r/ndb_dbug_tc_select.result
share/mysql/test/suite/ndb/r/ndb_dd_alter.result
share/mysql/test/suite/ndb/r/ndb_dd_basic.result
share/mysql/test/suite/ndb/r/ndb_dd_bug12581213.result
share/mysql/test/suite/ndb/r/ndb_dd_ddl.result
share/mysql/test/suite/ndb/r/ndb_dd_disk2memory.result
share/mysql/test/suite/ndb/r/ndb_dd_dump.result
share/mysql/test/suite/ndb/r/ndb_dd_restore_compat.result
share/mysql/test/suite/ndb/r/ndb_dd_sql_features.result
share/mysql/test/suite/ndb/r/ndb_ddl_open_trans.result
share/mysql/test/suite/ndb/r/ndb_disconnect_ddl.result
share/mysql/test/suite/ndb/r/ndb_discover_db.result
share/mysql/test/suite/ndb/r/ndb_dist_priv.result
share/mysql/test/suite/ndb/r/ndb_gis.result
share/mysql/test/suite/ndb/r/ndb_global_schema_lock.result
share/mysql/test/suite/ndb/r/ndb_global_schema_lock_error.result
share/mysql/test/suite/ndb/r/ndb_grant.result
share/mysql/test/suite/ndb/r/ndb_hidden_pk.result
share/mysql/test/suite/ndb/r/ndb_index.result
share/mysql/test/suite/ndb/r/ndb_index_ordered.result
share/mysql/test/suite/ndb/r/ndb_index_stat.result
share/mysql/test/suite/ndb/r/ndb_index_unique.result
share/mysql/test/suite/ndb/r/ndb_insert.result
share/mysql/test/suite/ndb/r/ndb_join_pushdown.result
share/mysql/test/suite/ndb/r/ndb_limit.result
share/mysql/test/suite/ndb/r/ndb_load.result
share/mysql/test/suite/ndb/r/ndb_loaddatalocal.result
share/mysql/test/suite/ndb/r/ndb_lock.result
share/mysql/test/suite/ndb/r/ndb_lock_table.result
share/mysql/test/suite/ndb/r/ndb_mgm.result
share/mysql/test/suite/ndb/r/ndb_minmax.result
share/mysql/test/suite/ndb/r/ndb_multi.result
share/mysql/test/suite/ndb/r/ndb_multi_row.result
share/mysql/test/suite/ndb/r/ndb_native_default_support.result
share/mysql/test/suite/ndb/r/ndb_optimize_table.result
share/mysql/test/suite/ndb/r/ndb_optimized_node_selection.result
share/mysql/test/suite/ndb/r/ndb_partition_error.result
share/mysql/test/suite/ndb/r/ndb_partition_error2.result
share/mysql/test/suite/ndb/r/ndb_partition_hash.result
share/mysql/test/suite/ndb/r/ndb_partition_key.result
share/mysql/test/suite/ndb/r/ndb_partition_list.result
share/mysql/test/suite/ndb/r/ndb_partition_range.result
share/mysql/test/suite/ndb/r/ndb_read_multi_range.result
share/mysql/test/suite/ndb/r/ndb_reconnect.result
share/mysql/test/suite/ndb/r/ndb_rename.result
share/mysql/test/suite/ndb/r/ndb_replace.result
share/mysql/test/suite/ndb/r/ndb_restore_compat_downward.result
share/mysql/test/suite/ndb/r/ndb_restore_compat_endianness.result
share/mysql/test/suite/ndb/r/ndb_restore_conv_lossy_charbinary.result
share/mysql/test/suite/ndb/r/ndb_restore_conv_lossy_integral.result
share/mysql/test/suite/ndb/r/ndb_restore_conv_padding.result
share/mysql/test/suite/ndb/r/ndb_restore_conv_promotion.result
Changes 5.6.26: * Security Fix: Due to the LogJam issue (https://weakdh.org/), OpenSSL has changed the Diffie-Hellman key length parameters for openssl-1.0.1n and up. * Replication: When using a multi-threaded slave, each worker thread has its own queue of transactions to process. In previous MySQL versions, STOP SLAVE waited for all workers to process their entire queue. This logic has been changed so that STOP SLAVE first finds the newest transaction that was committed by any worker thread. Then, it waits for all workers to complete transactions older than that. Newer transactions are not processed. The new logic allows STOP SLAVE to complete faster in case some worker queues contain multiple transactions. * Previously, the max_digest_length system variable controlled the maximum digest length for all server functions that computed statement digests. However, whereas the Performance Schema may need to maintain many digest values, other server functions such as MySQL Enterprise Firewall need only one digest per session. Increasing the max_digest_length value has little impact on total memory requirements for those functions, but can increase Performance Schema memory requirements significantly. To enable configuring digest length separately for the Performance Schema, its digest length is now controlled by the new performance_schema_max_digest_length system variable. * Previously, changes to the validate_password plugin dictionary file (named by the validate_password_dictionary_file system variable) while the server was running required a restart for the server to recognize the changes. Now validate_password_dictionary_file can be set at runtime and assigning a value causes the named file to be read without a restart. In addition, two new status variables are available. validate_password_dictionary_file_last_parsed indicates when the dictionary file was last read, and validate_password_dictionary_file_words_count indicates how many words it contains. * Bugs fixed
2015-07-30 16:39:18 +02:00
share/mysql/test/suite/ndb/r/ndb_restore_discover.result
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/ndb/r/ndb_restore_misc.result
share/mysql/test/suite/ndb/r/ndb_restore_print.result
share/mysql/test/suite/ndb/r/ndb_restore_schema_blobs.result
share/mysql/test/suite/ndb/r/ndb_restore_schema_partitions.result
share/mysql/test/suite/ndb/r/ndb_restore_schema_rewrites.result
share/mysql/test/suite/ndb/r/ndb_restore_schema_subsets.result
share/mysql/test/suite/ndb/r/ndb_restore_schema_tolerance.result
share/mysql/test/suite/ndb/r/ndb_restore_undolog.result
share/mysql/test/suite/ndb/r/ndb_row_count.result
share/mysql/test/suite/ndb/r/ndb_row_format.result
share/mysql/test/suite/ndb/r/ndb_select_count.result
share/mysql/test/suite/ndb/r/ndb_share.result
share/mysql/test/suite/ndb/r/ndb_short_sigs.result
share/mysql/test/suite/ndb/r/ndb_single_user.result
share/mysql/test/suite/ndb/r/ndb_sp.result
share/mysql/test/suite/ndb/r/ndb_sql_allow_batching.result
share/mysql/test/suite/ndb/r/ndb_statistics0.result
share/mysql/test/suite/ndb/r/ndb_statistics1.result
share/mysql/test/suite/ndb/r/ndb_subquery.result
share/mysql/test/suite/ndb/r/ndb_temporary.result
share/mysql/test/suite/ndb/r/ndb_tmp_table_and_DDL.result
share/mysql/test/suite/ndb/r/ndb_transaction.result
share/mysql/test/suite/ndb/r/ndb_trigger.result
share/mysql/test/suite/ndb/r/ndb_truncate.result
share/mysql/test/suite/ndb/r/ndb_types.result
share/mysql/test/suite/ndb/r/ndb_update.result
share/mysql/test/suite/ndb/r/ndb_update_no_read.result
share/mysql/test/suite/ndb/r/ndb_view.result
share/mysql/test/suite/ndb/r/ndbapi.result
share/mysql/test/suite/ndb/r/ndbinfo.result
share/mysql/test/suite/ndb/r/ndbinfo_cache.result
share/mysql/test/suite/ndb/r/ndbinfo_dump.result
share/mysql/test/suite/ndb/r/ps_7ndb.result
share/mysql/test/suite/ndb/r/strict_autoinc_5ndb.result
share/mysql/test/suite/ndb/t/bug36547.test
share/mysql/test/suite/ndb/t/clusterj.test
share/mysql/test/suite/ndb/t/clusterj_jpa.test
share/mysql/test/suite/ndb/t/disabled.def
share/mysql/test/suite/ndb/t/have_ndb_dist_priv.inc
share/mysql/test/suite/ndb/t/have_ndb_error_insert.inc
share/mysql/test/suite/ndb/t/have_ndbinfo.inc
share/mysql/test/suite/ndb/t/loaddata_autocom_ndb.test
share/mysql/test/suite/ndb/t/ndb_add_partition.test
share/mysql/test/suite/ndb/t/ndb_addnode.cnf
share/mysql/test/suite/ndb/t/ndb_addnode.test
share/mysql/test/suite/ndb/t/ndb_alter_table.test
share/mysql/test/suite/ndb/t/ndb_alter_table2.test
share/mysql/test/suite/ndb/t/ndb_alter_table3.test
share/mysql/test/suite/ndb/t/ndb_alter_table_backup.test
share/mysql/test/suite/ndb/t/ndb_alter_table_error.test
share/mysql/test/suite/ndb/t/ndb_alter_table_online.test
share/mysql/test/suite/ndb/t/ndb_alter_table_online2.test
share/mysql/test/suite/ndb/t/ndb_alter_table_online_multi.test
share/mysql/test/suite/ndb/t/ndb_auto_increment.test
share/mysql/test/suite/ndb/t/ndb_autoinc.test
share/mysql/test/suite/ndb/t/ndb_basic.test
share/mysql/test/suite/ndb/t/ndb_bitfield.test
share/mysql/test/suite/ndb/t/ndb_blob.test
share/mysql/test/suite/ndb/t/ndb_blob_big.cnf
share/mysql/test/suite/ndb/t/ndb_blob_big.test
share/mysql/test/suite/ndb/t/ndb_blob_partition.test
share/mysql/test/suite/ndb/t/ndb_bug26793.test
share/mysql/test/suite/ndb/t/ndb_bug31477.test
share/mysql/test/suite/ndb/t/ndb_bug31754.test
share/mysql/test/suite/ndb/t/ndb_bulk_delete.test
share/mysql/test/suite/ndb/t/ndb_cache.test
share/mysql/test/suite/ndb/t/ndb_cache2.test
share/mysql/test/suite/ndb/t/ndb_cache_multi.test
share/mysql/test/suite/ndb/t/ndb_cache_multi2.test
share/mysql/test/suite/ndb/t/ndb_cache_trans.test
share/mysql/test/suite/ndb/t/ndb_charset.test
share/mysql/test/suite/ndb/t/ndb_column_properties.test
share/mysql/test/suite/ndb/t/ndb_condition_pushdown.test
share/mysql/test/suite/ndb/t/ndb_config.test
share/mysql/test/suite/ndb/t/ndb_config2.test
share/mysql/test/suite/ndb/t/ndb_create_table.test
share/mysql/test/suite/ndb/t/ndb_cursor.test
share/mysql/test/suite/ndb/t/ndb_database.test
share/mysql/test/suite/ndb/t/ndb_dbug_lock.test
share/mysql/test/suite/ndb/t/ndb_dbug_tc_select.test
share/mysql/test/suite/ndb/t/ndb_dbug_tc_select_1.inc
share/mysql/test/suite/ndb/t/ndb_dbug_tc_select_2.inc
share/mysql/test/suite/ndb/t/ndb_dbug_tc_select_3.inc
share/mysql/test/suite/ndb/t/ndb_dd_alter.test
share/mysql/test/suite/ndb/t/ndb_dd_basic.test
share/mysql/test/suite/ndb/t/ndb_dd_bug12581213.cnf
share/mysql/test/suite/ndb/t/ndb_dd_bug12581213.test
share/mysql/test/suite/ndb/t/ndb_dd_ddl.test
share/mysql/test/suite/ndb/t/ndb_dd_disk2memory.test
share/mysql/test/suite/ndb/t/ndb_dd_dump.test
share/mysql/test/suite/ndb/t/ndb_dd_restore_compat.test
share/mysql/test/suite/ndb/t/ndb_dd_sql_features.test
share/mysql/test/suite/ndb/t/ndb_ddl_open_trans.test
share/mysql/test/suite/ndb/t/ndb_disconnect_ddl.test
share/mysql/test/suite/ndb/t/ndb_discover_db-master.opt
share/mysql/test/suite/ndb/t/ndb_discover_db.test
share/mysql/test/suite/ndb/t/ndb_dist_priv.test
share/mysql/test/suite/ndb/t/ndb_gis.test
share/mysql/test/suite/ndb/t/ndb_global_schema_lock.test
share/mysql/test/suite/ndb/t/ndb_global_schema_lock_error.test
share/mysql/test/suite/ndb/t/ndb_grant.later
share/mysql/test/suite/ndb/t/ndb_hidden_pk.test
share/mysql/test/suite/ndb/t/ndb_index.test
share/mysql/test/suite/ndb/t/ndb_index_ordered.test
share/mysql/test/suite/ndb/t/ndb_index_stat.test
share/mysql/test/suite/ndb/t/ndb_index_stat_enable.inc
share/mysql/test/suite/ndb/t/ndb_index_unique.test
share/mysql/test/suite/ndb/t/ndb_init_schema_locks_count.inc
share/mysql/test/suite/ndb/t/ndb_insert.test
share/mysql/test/suite/ndb/t/ndb_join_pushdown.test
share/mysql/test/suite/ndb/t/ndb_jtie.test
share/mysql/test/suite/ndb/t/ndb_limit.test
share/mysql/test/suite/ndb/t/ndb_load.test
share/mysql/test/suite/ndb/t/ndb_loaddatalocal.test
share/mysql/test/suite/ndb/t/ndb_lock.test
share/mysql/test/suite/ndb/t/ndb_lock_table.test
share/mysql/test/suite/ndb/t/ndb_mgm.inc
share/mysql/test/suite/ndb/t/ndb_mgm.test
share/mysql/test/suite/ndb/t/ndb_minmax.test
share/mysql/test/suite/ndb/t/ndb_multi.test
share/mysql/test/suite/ndb/t/ndb_multi_row.test
share/mysql/test/suite/ndb/t/ndb_native_default_support.test
share/mysql/test/suite/ndb/t/ndb_optimize_table.test
share/mysql/test/suite/ndb/t/ndb_optimized_node_selection.test
share/mysql/test/suite/ndb/t/ndb_partition_error.test
share/mysql/test/suite/ndb/t/ndb_partition_error2.test
share/mysql/test/suite/ndb/t/ndb_partition_hash.test
share/mysql/test/suite/ndb/t/ndb_partition_key.test
share/mysql/test/suite/ndb/t/ndb_partition_list.test
share/mysql/test/suite/ndb/t/ndb_partition_range.test
share/mysql/test/suite/ndb/t/ndb_read_multi_range.test
share/mysql/test/suite/ndb/t/ndb_reconnect.test
share/mysql/test/suite/ndb/t/ndb_rename.test
share/mysql/test/suite/ndb/t/ndb_replace.test
share/mysql/test/suite/ndb/t/ndb_restart_nostart.inc
share/mysql/test/suite/ndb/t/ndb_restart_start.inc
share/mysql/test/suite/ndb/t/ndb_restore_compat_compression-master.opt
share/mysql/test/suite/ndb/t/ndb_restore_compat_compression.test
share/mysql/test/suite/ndb/t/ndb_restore_compat_downward.test
share/mysql/test/suite/ndb/t/ndb_restore_compat_endianness.test
share/mysql/test/suite/ndb/t/ndb_restore_conv_lossy_charbinary.test
share/mysql/test/suite/ndb/t/ndb_restore_conv_lossy_integral.test
share/mysql/test/suite/ndb/t/ndb_restore_conv_padding.test
share/mysql/test/suite/ndb/t/ndb_restore_conv_promotion.test
Changes 5.6.26: * Security Fix: Due to the LogJam issue (https://weakdh.org/), OpenSSL has changed the Diffie-Hellman key length parameters for openssl-1.0.1n and up. * Replication: When using a multi-threaded slave, each worker thread has its own queue of transactions to process. In previous MySQL versions, STOP SLAVE waited for all workers to process their entire queue. This logic has been changed so that STOP SLAVE first finds the newest transaction that was committed by any worker thread. Then, it waits for all workers to complete transactions older than that. Newer transactions are not processed. The new logic allows STOP SLAVE to complete faster in case some worker queues contain multiple transactions. * Previously, the max_digest_length system variable controlled the maximum digest length for all server functions that computed statement digests. However, whereas the Performance Schema may need to maintain many digest values, other server functions such as MySQL Enterprise Firewall need only one digest per session. Increasing the max_digest_length value has little impact on total memory requirements for those functions, but can increase Performance Schema memory requirements significantly. To enable configuring digest length separately for the Performance Schema, its digest length is now controlled by the new performance_schema_max_digest_length system variable. * Previously, changes to the validate_password plugin dictionary file (named by the validate_password_dictionary_file system variable) while the server was running required a restart for the server to recognize the changes. Now validate_password_dictionary_file can be set at runtime and assigning a value causes the named file to be read without a restart. In addition, two new status variables are available. validate_password_dictionary_file_last_parsed indicates when the dictionary file was last read, and validate_password_dictionary_file_words_count indicates how many words it contains. * Bugs fixed
2015-07-30 16:39:18 +02:00
share/mysql/test/suite/ndb/t/ndb_restore_discover.test
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/ndb/t/ndb_restore_misc.test
share/mysql/test/suite/ndb/t/ndb_restore_print.test
share/mysql/test/suite/ndb/t/ndb_restore_schema_blobs.test
share/mysql/test/suite/ndb/t/ndb_restore_schema_partitions.test
share/mysql/test/suite/ndb/t/ndb_restore_schema_rewrites.test
share/mysql/test/suite/ndb/t/ndb_restore_schema_subsets.test
share/mysql/test/suite/ndb/t/ndb_restore_schema_tolerance.test
share/mysql/test/suite/ndb/t/ndb_restore_undolog.test
share/mysql/test/suite/ndb/t/ndb_row_count.test
share/mysql/test/suite/ndb/t/ndb_row_format.test
share/mysql/test/suite/ndb/t/ndb_schema_locks_count.inc
share/mysql/test/suite/ndb/t/ndb_select_count.test
share/mysql/test/suite/ndb/t/ndb_share.cnf
share/mysql/test/suite/ndb/t/ndb_share.test
share/mysql/test/suite/ndb/t/ndb_short_sigs.cnf
share/mysql/test/suite/ndb/t/ndb_short_sigs.test
share/mysql/test/suite/ndb/t/ndb_show_tables_result.inc
share/mysql/test/suite/ndb/t/ndb_single_user-master.opt
share/mysql/test/suite/ndb/t/ndb_single_user.test
share/mysql/test/suite/ndb/t/ndb_sp.test
share/mysql/test/suite/ndb/t/ndb_sql_allow_batching.test
share/mysql/test/suite/ndb/t/ndb_statistics.inc
share/mysql/test/suite/ndb/t/ndb_statistics0.test
share/mysql/test/suite/ndb/t/ndb_statistics1.test
share/mysql/test/suite/ndb/t/ndb_subquery.test
share/mysql/test/suite/ndb/t/ndb_temporary.test
share/mysql/test/suite/ndb/t/ndb_tmp_table_and_DDL.test
share/mysql/test/suite/ndb/t/ndb_transaction.test
share/mysql/test/suite/ndb/t/ndb_trigger.test
share/mysql/test/suite/ndb/t/ndb_truncate.test
share/mysql/test/suite/ndb/t/ndb_types.test
share/mysql/test/suite/ndb/t/ndb_update.test
share/mysql/test/suite/ndb/t/ndb_update_no_read.test
share/mysql/test/suite/ndb/t/ndb_view.test
share/mysql/test/suite/ndb/t/ndb_wait_nostart.inc
share/mysql/test/suite/ndb/t/ndb_wait_started.inc
share/mysql/test/suite/ndb/t/ndb_waiter.inc
share/mysql/test/suite/ndb/t/ndbapi.test
share/mysql/test/suite/ndb/t/ndbinfo.test
share/mysql/test/suite/ndb/t/ndbinfo_cache.test
share/mysql/test/suite/ndb/t/ndbinfo_create.inc
share/mysql/test/suite/ndb/t/ndbinfo_drop.inc
share/mysql/test/suite/ndb/t/ndbinfo_dump.test
share/mysql/test/suite/ndb/t/ps_7ndb.test
share/mysql/test/suite/ndb/t/show_attributes.inc
share/mysql/test/suite/ndb/t/show_primary_keys.inc
share/mysql/test/suite/ndb/t/show_varpart.inc
share/mysql/test/suite/ndb/t/strict_autoinc_5ndb.test
share/mysql/test/suite/ndb/t/test_mgmd.cnf
share/mysql/test/suite/ndb/t/test_mgmd.test
share/mysql/test/suite/ndb/t/test_ndbinfo.test
share/mysql/test/suite/ndb_big/bug37983.test
share/mysql/test/suite/ndb_big/end_timer.inc
share/mysql/test/suite/ndb_big/my.cnf
share/mysql/test/suite/ndb_big/run_query_with_retry.inc
share/mysql/test/suite/ndb_big/smoke.test
share/mysql/test/suite/ndb_big/start_timer.inc
share/mysql/test/suite/ndb_big/suite.inc
share/mysql/test/suite/ndb_binlog/my.cnf
share/mysql/test/suite/ndb_binlog/r/ndb_binlog_basic.result
share/mysql/test/suite/ndb_binlog/r/ndb_binlog_ddl_multi.result
share/mysql/test/suite/ndb_binlog/r/ndb_binlog_discover.result
share/mysql/test/suite/ndb_binlog/r/ndb_binlog_format.result
share/mysql/test/suite/ndb_binlog/r/ndb_binlog_ignore_db.result
share/mysql/test/suite/ndb_binlog/r/ndb_binlog_log_apply_status.result
share/mysql/test/suite/ndb_binlog/r/ndb_binlog_log_bin.result
share/mysql/test/suite/ndb_binlog/r/ndb_binlog_multi.result
share/mysql/test/suite/ndb_binlog/r/ndb_binlog_restore.result
share/mysql/test/suite/ndb_binlog/r/ndb_binlog_unique_epoch.result
share/mysql/test/suite/ndb_binlog/r/ndb_binlog_variants.result
share/mysql/test/suite/ndb_binlog/t/ndb_binlog_basic.test
share/mysql/test/suite/ndb_binlog/t/ndb_binlog_ddl_multi.test
share/mysql/test/suite/ndb_binlog/t/ndb_binlog_discover.test
share/mysql/test/suite/ndb_binlog/t/ndb_binlog_format.test
share/mysql/test/suite/ndb_binlog/t/ndb_binlog_get_binlog_stmts.inc
share/mysql/test/suite/ndb_binlog/t/ndb_binlog_get_binlog_stmts_basic.inc
share/mysql/test/suite/ndb_binlog/t/ndb_binlog_ignore_db-master.opt
share/mysql/test/suite/ndb_binlog/t/ndb_binlog_ignore_db.test
share/mysql/test/suite/ndb_binlog/t/ndb_binlog_log_apply_status.test
share/mysql/test/suite/ndb_binlog/t/ndb_binlog_log_bin.test
share/mysql/test/suite/ndb_binlog/t/ndb_binlog_multi.test
share/mysql/test/suite/ndb_binlog/t/ndb_binlog_restore.test
share/mysql/test/suite/ndb_binlog/t/ndb_binlog_unique_epoch.cnf
share/mysql/test/suite/ndb_binlog/t/ndb_binlog_unique_epoch.test
share/mysql/test/suite/ndb_binlog/t/ndb_binlog_variants.cnf
share/mysql/test/suite/ndb_binlog/t/ndb_binlog_variants.test
share/mysql/test/suite/ndb_rpl/my.cnf
share/mysql/test/suite/ndb_rpl/ndb_master-slave.inc
share/mysql/test/suite/ndb_rpl/ndb_master-slave_2ch.inc
share/mysql/test/suite/ndb_rpl/ndb_master-slave_2ch_end.inc
share/mysql/test/suite/ndb_rpl/r/ndb_rpl_2innodb.result
share/mysql/test/suite/ndb_rpl/r/ndb_rpl_2myisam.result
share/mysql/test/suite/ndb_rpl/r/ndb_rpl_2ndb.result
share/mysql/test/suite/ndb_rpl/r/ndb_rpl_2other.result
share/mysql/test/suite/ndb_rpl/r/ndb_rpl_add_column.result
share/mysql/test/suite/ndb_rpl/r/ndb_rpl_apply_status.result
share/mysql/test/suite/ndb_rpl/r/ndb_rpl_auto_inc.result
share/mysql/test/suite/ndb_rpl/r/ndb_rpl_bank.result
share/mysql/test/suite/ndb_rpl/r/ndb_rpl_basic.result
share/mysql/test/suite/ndb_rpl/r/ndb_rpl_binlog_format_errors.result
share/mysql/test/suite/ndb_rpl/r/ndb_rpl_bitfield.result
share/mysql/test/suite/ndb_rpl/r/ndb_rpl_blob.result
share/mysql/test/suite/ndb_rpl/r/ndb_rpl_break_3_chain.result
share/mysql/test/suite/ndb_rpl/r/ndb_rpl_bug22045.result
share/mysql/test/suite/ndb_rpl/r/ndb_rpl_check_for_mixed.result
share/mysql/test/suite/ndb_rpl/r/ndb_rpl_circular.result
share/mysql/test/suite/ndb_rpl/r/ndb_rpl_circular_2ch.result
share/mysql/test/suite/ndb_rpl/r/ndb_rpl_circular_2ch_rep_status.result
share/mysql/test/suite/ndb_rpl/r/ndb_rpl_circular_simplex.result
share/mysql/test/suite/ndb_rpl/r/ndb_rpl_conflict.result
share/mysql/test/suite/ndb_rpl/r/ndb_rpl_conflict_epoch.result
share/mysql/test/suite/ndb_rpl/r/ndb_rpl_conflict_max.result
share/mysql/test/suite/ndb_rpl/r/ndb_rpl_conflict_max_delete_win.result
share/mysql/test/suite/ndb_rpl/r/ndb_rpl_conflict_old.result
share/mysql/test/suite/ndb_rpl/r/ndb_rpl_ctype_ucs2_def.result
share/mysql/test/suite/ndb_rpl/r/ndb_rpl_dd_advance.result
share/mysql/test/suite/ndb_rpl/r/ndb_rpl_dd_basic.result
share/mysql/test/suite/ndb_rpl/r/ndb_rpl_dd_partitions.result
share/mysql/test/suite/ndb_rpl/r/ndb_rpl_do_db.result
share/mysql/test/suite/ndb_rpl/r/ndb_rpl_do_table.result
share/mysql/test/suite/ndb_rpl/r/ndb_rpl_empty_epoch.result
share/mysql/test/suite/ndb_rpl/r/ndb_rpl_gap_event.result
share/mysql/test/suite/ndb_rpl/r/ndb_rpl_idempotent.result
share/mysql/test/suite/ndb_rpl/r/ndb_rpl_ignore_db.result
share/mysql/test/suite/ndb_rpl/r/ndb_rpl_init_rep_status.result
share/mysql/test/suite/ndb_rpl/r/ndb_rpl_innodb2ndb.result
share/mysql/test/suite/ndb_rpl/r/ndb_rpl_innodb_trans.result
share/mysql/test/suite/ndb_rpl/r/ndb_rpl_load.result
share/mysql/test/suite/ndb_rpl/r/ndb_rpl_logging.result
share/mysql/test/suite/ndb_rpl/r/ndb_rpl_mix_eng_trans.result
share/mysql/test/suite/ndb_rpl/r/ndb_rpl_mix_innodb.result
share/mysql/test/suite/ndb_rpl/r/ndb_rpl_mixed_tables.result
share/mysql/test/suite/ndb_rpl/r/ndb_rpl_multi.result
share/mysql/test/suite/ndb_rpl/r/ndb_rpl_myisam2ndb.result
share/mysql/test/suite/ndb_rpl/r/ndb_rpl_ndbapi_multi.result
share/mysql/test/suite/ndb_rpl/r/ndb_rpl_rep_error.result
share/mysql/test/suite/ndb_rpl/r/ndb_rpl_rep_ignore.result
share/mysql/test/suite/ndb_rpl/r/ndb_rpl_skip_gap_event.result
share/mysql/test/suite/ndb_rpl/r/ndb_rpl_slave_lsu.result
share/mysql/test/suite/ndb_rpl/r/ndb_rpl_slave_lsu_anyval.result
share/mysql/test/suite/ndb_rpl/r/ndb_rpl_slave_restart.result
share/mysql/test/suite/ndb_rpl/r/ndb_rpl_stm_innodb.result
share/mysql/test/suite/ndb_rpl/r/ndb_rpl_sync.result
share/mysql/test/suite/ndb_rpl/r/ndb_rpl_ui.result
share/mysql/test/suite/ndb_rpl/r/ndb_rpl_ui2.result
share/mysql/test/suite/ndb_rpl/r/ndb_rpl_ui3.result
share/mysql/test/suite/ndb_rpl/r/rpl_truncate_7ndb.result
share/mysql/test/suite/ndb_rpl/r/rpl_truncate_7ndb_2.result
share/mysql/test/suite/ndb_rpl/t/disabled.def
share/mysql/test/suite/ndb_rpl/t/ndb_apply_status.frm
share/mysql/test/suite/ndb_rpl/t/ndb_conflict_info.inc
share/mysql/test/suite/ndb_rpl/t/ndb_conflict_info_init.inc
share/mysql/test/suite/ndb_rpl/t/ndb_rpl_2innodb-master.opt
share/mysql/test/suite/ndb_rpl/t/ndb_rpl_2innodb-slave.opt
share/mysql/test/suite/ndb_rpl/t/ndb_rpl_2innodb.test
share/mysql/test/suite/ndb_rpl/t/ndb_rpl_2multi_basic.inc
share/mysql/test/suite/ndb_rpl/t/ndb_rpl_2multi_eng.inc
share/mysql/test/suite/ndb_rpl/t/ndb_rpl_2myisam-master.opt
share/mysql/test/suite/ndb_rpl/t/ndb_rpl_2myisam-slave.opt
share/mysql/test/suite/ndb_rpl/t/ndb_rpl_2myisam.test
share/mysql/test/suite/ndb_rpl/t/ndb_rpl_2ndb-slave.opt
share/mysql/test/suite/ndb_rpl/t/ndb_rpl_2ndb.test
share/mysql/test/suite/ndb_rpl/t/ndb_rpl_2other-slave.opt
share/mysql/test/suite/ndb_rpl/t/ndb_rpl_2other.test
share/mysql/test/suite/ndb_rpl/t/ndb_rpl_add_column.test
share/mysql/test/suite/ndb_rpl/t/ndb_rpl_apply_status-master.opt
share/mysql/test/suite/ndb_rpl/t/ndb_rpl_apply_status.test
share/mysql/test/suite/ndb_rpl/t/ndb_rpl_auto_inc.test
share/mysql/test/suite/ndb_rpl/t/ndb_rpl_bank.test
share/mysql/test/suite/ndb_rpl/t/ndb_rpl_basic.test
share/mysql/test/suite/ndb_rpl/t/ndb_rpl_binlog_format_errors-master.opt
share/mysql/test/suite/ndb_rpl/t/ndb_rpl_binlog_format_errors-slave.opt
share/mysql/test/suite/ndb_rpl/t/ndb_rpl_binlog_format_errors.test
share/mysql/test/suite/ndb_rpl/t/ndb_rpl_bitfield.test
share/mysql/test/suite/ndb_rpl/t/ndb_rpl_blob.test
share/mysql/test/suite/ndb_rpl/t/ndb_rpl_break_3_chain.cnf
share/mysql/test/suite/ndb_rpl/t/ndb_rpl_break_3_chain.test
share/mysql/test/suite/ndb_rpl/t/ndb_rpl_bug22045.test
share/mysql/test/suite/ndb_rpl/t/ndb_rpl_check_for_mixed.test
share/mysql/test/suite/ndb_rpl/t/ndb_rpl_circular.test
share/mysql/test/suite/ndb_rpl/t/ndb_rpl_circular_2ch.cnf
share/mysql/test/suite/ndb_rpl/t/ndb_rpl_circular_2ch.test
share/mysql/test/suite/ndb_rpl/t/ndb_rpl_circular_2ch_rep_status.cnf
share/mysql/test/suite/ndb_rpl/t/ndb_rpl_circular_2ch_rep_status.test
share/mysql/test/suite/ndb_rpl/t/ndb_rpl_circular_simplex.test
share/mysql/test/suite/ndb_rpl/t/ndb_rpl_conflict.test
share/mysql/test/suite/ndb_rpl/t/ndb_rpl_conflict_1.inc
share/mysql/test/suite/ndb_rpl/t/ndb_rpl_conflict_epoch.cnf
share/mysql/test/suite/ndb_rpl/t/ndb_rpl_conflict_epoch.test
share/mysql/test/suite/ndb_rpl/t/ndb_rpl_conflict_epoch_1.inc
share/mysql/test/suite/ndb_rpl/t/ndb_rpl_conflict_max-master.opt
share/mysql/test/suite/ndb_rpl/t/ndb_rpl_conflict_max.test
share/mysql/test/suite/ndb_rpl/t/ndb_rpl_conflict_max_delete_win-master.opt
share/mysql/test/suite/ndb_rpl/t/ndb_rpl_conflict_max_delete_win.test
share/mysql/test/suite/ndb_rpl/t/ndb_rpl_conflict_old-master.opt
share/mysql/test/suite/ndb_rpl/t/ndb_rpl_conflict_old.test
share/mysql/test/suite/ndb_rpl/t/ndb_rpl_ctype_ucs2_def-master.opt
share/mysql/test/suite/ndb_rpl/t/ndb_rpl_ctype_ucs2_def.test
share/mysql/test/suite/ndb_rpl/t/ndb_rpl_dd_advance.test
share/mysql/test/suite/ndb_rpl/t/ndb_rpl_dd_basic.test
share/mysql/test/suite/ndb_rpl/t/ndb_rpl_dd_partitions-master.opt
share/mysql/test/suite/ndb_rpl/t/ndb_rpl_dd_partitions-slave.opt
share/mysql/test/suite/ndb_rpl/t/ndb_rpl_dd_partitions.test
share/mysql/test/suite/ndb_rpl/t/ndb_rpl_do_db-slave.opt
share/mysql/test/suite/ndb_rpl/t/ndb_rpl_do_db.test
share/mysql/test/suite/ndb_rpl/t/ndb_rpl_do_table-slave.opt
share/mysql/test/suite/ndb_rpl/t/ndb_rpl_do_table.test
share/mysql/test/suite/ndb_rpl/t/ndb_rpl_empty_epoch.test
share/mysql/test/suite/ndb_rpl/t/ndb_rpl_gap_event-master.opt
share/mysql/test/suite/ndb_rpl/t/ndb_rpl_gap_event.test
share/mysql/test/suite/ndb_rpl/t/ndb_rpl_get_binlog_events.inc
share/mysql/test/suite/ndb_rpl/t/ndb_rpl_idempotent.test
share/mysql/test/suite/ndb_rpl/t/ndb_rpl_ignore_db-master.opt
share/mysql/test/suite/ndb_rpl/t/ndb_rpl_ignore_db.test
share/mysql/test/suite/ndb_rpl/t/ndb_rpl_init_rep_status.test
share/mysql/test/suite/ndb_rpl/t/ndb_rpl_innodb2ndb-master.opt
share/mysql/test/suite/ndb_rpl/t/ndb_rpl_innodb2ndb-slave.opt
share/mysql/test/suite/ndb_rpl/t/ndb_rpl_innodb2ndb.test
share/mysql/test/suite/ndb_rpl/t/ndb_rpl_innodb_trans-slave.opt
share/mysql/test/suite/ndb_rpl/t/ndb_rpl_innodb_trans.test
share/mysql/test/suite/ndb_rpl/t/ndb_rpl_load.test
share/mysql/test/suite/ndb_rpl/t/ndb_rpl_logging.test
share/mysql/test/suite/ndb_rpl/t/ndb_rpl_mix_eng_trans-master.opt
share/mysql/test/suite/ndb_rpl/t/ndb_rpl_mix_eng_trans-slave.opt
share/mysql/test/suite/ndb_rpl/t/ndb_rpl_mix_eng_trans.test
share/mysql/test/suite/ndb_rpl/t/ndb_rpl_mix_innodb-master.opt
share/mysql/test/suite/ndb_rpl/t/ndb_rpl_mix_innodb.test
share/mysql/test/suite/ndb_rpl/t/ndb_rpl_mixed_tables-master.opt
share/mysql/test/suite/ndb_rpl/t/ndb_rpl_mixed_tables-slave.opt
share/mysql/test/suite/ndb_rpl/t/ndb_rpl_mixed_tables.test
share/mysql/test/suite/ndb_rpl/t/ndb_rpl_multi.test
share/mysql/test/suite/ndb_rpl/t/ndb_rpl_multi_binlog_update.cnf
share/mysql/test/suite/ndb_rpl/t/ndb_rpl_multi_binlog_update.inc
share/mysql/test/suite/ndb_rpl/t/ndb_rpl_multi_update2-slave.opt
share/mysql/test/suite/ndb_rpl/t/ndb_rpl_myisam2ndb-slave.opt
share/mysql/test/suite/ndb_rpl/t/ndb_rpl_myisam2ndb.test
share/mysql/test/suite/ndb_rpl/t/ndb_rpl_ndbapi_multi.test
share/mysql/test/suite/ndb_rpl/t/ndb_rpl_relayrotate-slave.opt
share/mysql/test/suite/ndb_rpl/t/ndb_rpl_rep_error.test
share/mysql/test/suite/ndb_rpl/t/ndb_rpl_rep_ignore-slave.opt
share/mysql/test/suite/ndb_rpl/t/ndb_rpl_rep_ignore.test
share/mysql/test/suite/ndb_rpl/t/ndb_rpl_skip_gap_event-slave.opt
share/mysql/test/suite/ndb_rpl/t/ndb_rpl_skip_gap_event.test
share/mysql/test/suite/ndb_rpl/t/ndb_rpl_slave_lsu.cnf
share/mysql/test/suite/ndb_rpl/t/ndb_rpl_slave_lsu.test
share/mysql/test/suite/ndb_rpl/t/ndb_rpl_slave_lsu_anyval.cnf
share/mysql/test/suite/ndb_rpl/t/ndb_rpl_slave_lsu_anyval.test
share/mysql/test/suite/ndb_rpl/t/ndb_rpl_slave_restart.test
share/mysql/test/suite/ndb_rpl/t/ndb_rpl_stm_innodb-master.opt
share/mysql/test/suite/ndb_rpl/t/ndb_rpl_stm_innodb.test
share/mysql/test/suite/ndb_rpl/t/ndb_rpl_sync.test
share/mysql/test/suite/ndb_rpl/t/ndb_rpl_ui.test
share/mysql/test/suite/ndb_rpl/t/ndb_rpl_ui2.test
share/mysql/test/suite/ndb_rpl/t/ndb_rpl_ui3.test
share/mysql/test/suite/ndb_rpl/t/ndb_rpl_xxx_innodb.inc
share/mysql/test/suite/ndb_rpl/t/rpl_truncate_7ndb.test
share/mysql/test/suite/ndb_rpl/t/rpl_truncate_7ndb_2.test
share/mysql/test/suite/ndb_rpl/t/select_ndb_apply_status.inc
share/mysql/test/suite/ndb_rpl/t/wait_schema_logging.inc
share/mysql/test/suite/ndb_team/my.cnf
share/mysql/test/suite/ndb_team/r/ndb_autodiscover.result
share/mysql/test/suite/ndb_team/r/ndb_autodiscover2.result
share/mysql/test/suite/ndb_team/r/ndb_autodiscover3.result
share/mysql/test/suite/ndb_team/r/ndb_backup_print.result
share/mysql/test/suite/ndb_team/r/ndb_dd_backuprestore.result
share/mysql/test/suite/ndb_team/r/ndb_restart.result
share/mysql/test/suite/ndb_team/t/disabled.def
share/mysql/test/suite/ndb_team/t/ndb_autodiscover.test
share/mysql/test/suite/ndb_team/t/ndb_autodiscover2-master.opt
share/mysql/test/suite/ndb_team/t/ndb_autodiscover2.test
share/mysql/test/suite/ndb_team/t/ndb_autodiscover3-master.opt
share/mysql/test/suite/ndb_team/t/ndb_autodiscover3.test
share/mysql/test/suite/ndb_team/t/ndb_backup_print.test
share/mysql/test/suite/ndb_team/t/ndb_dd_backuprestore.test
share/mysql/test/suite/ndb_team/t/ndb_restart.test
share/mysql/test/suite/opt_trace/include/bugs.inc
share/mysql/test/suite/opt_trace/include/filesort_pq.inc
share/mysql/test/suite/opt_trace/include/general.inc
share/mysql/test/suite/opt_trace/include/general2.inc
share/mysql/test/suite/opt_trace/include/range.inc
share/mysql/test/suite/opt_trace/include/security.inc
share/mysql/test/suite/opt_trace/include/subquery.inc
share/mysql/test/suite/opt_trace/r/bugs_no_prot_all.result
share/mysql/test/suite/opt_trace/r/bugs_no_prot_none.result
share/mysql/test/suite/opt_trace/r/bugs_ps_prot_all.result
share/mysql/test/suite/opt_trace/r/bugs_ps_prot_none.result
share/mysql/test/suite/opt_trace/r/charset.result
share/mysql/test/suite/opt_trace/r/debug.result
share/mysql/test/suite/opt_trace/r/eq_range_statistics.result
share/mysql/test/suite/opt_trace/r/filesort_pq.result
share/mysql/test/suite/opt_trace/r/general2_no_prot.result
share/mysql/test/suite/opt_trace/r/general2_ps_prot.result
share/mysql/test/suite/opt_trace/r/general_no_prot_all.result
share/mysql/test/suite/opt_trace/r/general_no_prot_none.result
share/mysql/test/suite/opt_trace/r/general_ps_prot_all.result
share/mysql/test/suite/opt_trace/r/general_ps_prot_none.result
share/mysql/test/suite/opt_trace/r/range_no_prot.result
share/mysql/test/suite/opt_trace/r/range_ps_prot.result
share/mysql/test/suite/opt_trace/r/security_no_prot.result
share/mysql/test/suite/opt_trace/r/security_ps_prot.result
share/mysql/test/suite/opt_trace/r/subquery_no_prot.result
share/mysql/test/suite/opt_trace/r/subquery_ps_prot.result
share/mysql/test/suite/opt_trace/r/temp_table.result
share/mysql/test/suite/opt_trace/t/bugs_no_prot_all.test
share/mysql/test/suite/opt_trace/t/bugs_no_prot_none.test
share/mysql/test/suite/opt_trace/t/bugs_ps_prot_all.test
share/mysql/test/suite/opt_trace/t/bugs_ps_prot_none.test
share/mysql/test/suite/opt_trace/t/charset.test
share/mysql/test/suite/opt_trace/t/debug.test
share/mysql/test/suite/opt_trace/t/eq_range_statistics.test
share/mysql/test/suite/opt_trace/t/filesort_pq.test
share/mysql/test/suite/opt_trace/t/general2_no_prot.test
share/mysql/test/suite/opt_trace/t/general2_ps_prot.test
share/mysql/test/suite/opt_trace/t/general_no_prot_all.test
share/mysql/test/suite/opt_trace/t/general_no_prot_none.test
share/mysql/test/suite/opt_trace/t/general_ps_prot_all.test
share/mysql/test/suite/opt_trace/t/general_ps_prot_none.test
share/mysql/test/suite/opt_trace/t/range_no_prot.test
share/mysql/test/suite/opt_trace/t/range_ps_prot.test
share/mysql/test/suite/opt_trace/t/security_no_prot.test
share/mysql/test/suite/opt_trace/t/security_ps_prot.test
share/mysql/test/suite/opt_trace/t/subquery_no_prot.test
share/mysql/test/suite/opt_trace/t/subquery_ps_prot.test
share/mysql/test/suite/opt_trace/t/temp_table.test
share/mysql/test/suite/opt_trace/validate_json.py
share/mysql/test/suite/parts/inc/methods1.inc
share/mysql/test/suite/parts/inc/part_blocked_sql_funcs_main.inc
share/mysql/test/suite/parts/inc/part_exch_drop_tabs.inc
share/mysql/test/suite/parts/inc/part_exch_qa.inc
share/mysql/test/suite/parts/inc/part_exch_qa_1.inc
share/mysql/test/suite/parts/inc/part_exch_qa_13.inc
share/mysql/test/suite/parts/inc/part_exch_qa_4.inc
share/mysql/test/suite/parts/inc/part_exch_qa_5.inc
share/mysql/test/suite/parts/inc/part_exch_qa_7.inc
share/mysql/test/suite/parts/inc/part_exch_qa_8.inc
share/mysql/test/suite/parts/inc/part_exch_tabs.inc
share/mysql/test/suite/parts/inc/part_supported_sql_funcs_delete.inc
share/mysql/test/suite/parts/inc/part_supported_sql_funcs_main.inc
share/mysql/test/suite/parts/inc/partition-dml-1-1-modes.inc
share/mysql/test/suite/parts/inc/partition-dml-1-1.inc
share/mysql/test/suite/parts/inc/partition-dml-1-10.inc
share/mysql/test/suite/parts/inc/partition-dml-1-11.inc
share/mysql/test/suite/parts/inc/partition-dml-1-2.inc
share/mysql/test/suite/parts/inc/partition-dml-1-3.inc
share/mysql/test/suite/parts/inc/partition-dml-1-4.inc
share/mysql/test/suite/parts/inc/partition-dml-1-5.inc
share/mysql/test/suite/parts/inc/partition-dml-1-6.inc
share/mysql/test/suite/parts/inc/partition-dml-1-7.inc
share/mysql/test/suite/parts/inc/partition-dml-1-8.inc
share/mysql/test/suite/parts/inc/partition-dml-1-9.inc
share/mysql/test/suite/parts/inc/partition-dml_cr_tab.inc
share/mysql/test/suite/parts/inc/partition-dml_ins_tab.inc
share/mysql/test/suite/parts/inc/partition.pre
share/mysql/test/suite/parts/inc/partition_10.inc
share/mysql/test/suite/parts/inc/partition_11.inc
share/mysql/test/suite/parts/inc/partition_12.inc
share/mysql/test/suite/parts/inc/partition_20.inc
share/mysql/test/suite/parts/inc/partition_alter1_1.inc
share/mysql/test/suite/parts/inc/partition_alter1_1_2.inc
share/mysql/test/suite/parts/inc/partition_alter1_2.inc
share/mysql/test/suite/parts/inc/partition_alter2_1.inc
share/mysql/test/suite/parts/inc/partition_alter2_2.inc
share/mysql/test/suite/parts/inc/partition_alter3.inc
share/mysql/test/suite/parts/inc/partition_alter4.inc
share/mysql/test/suite/parts/inc/partition_alter_1.inc
share/mysql/test/suite/parts/inc/partition_alter_11.inc
share/mysql/test/suite/parts/inc/partition_alter_13.inc
share/mysql/test/suite/parts/inc/partition_alter_41.inc
share/mysql/test/suite/parts/inc/partition_auto_increment.inc
share/mysql/test/suite/parts/inc/partition_basic.inc
share/mysql/test/suite/parts/inc/partition_basic_symlink.inc
share/mysql/test/suite/parts/inc/partition_bigint.inc
share/mysql/test/suite/parts/inc/partition_binary.inc
share/mysql/test/suite/parts/inc/partition_bit.inc
share/mysql/test/suite/parts/inc/partition_blob.inc
share/mysql/test/suite/parts/inc/partition_blocked_sql_funcs.inc
share/mysql/test/suite/parts/inc/partition_char.inc
share/mysql/test/suite/parts/inc/partition_check.inc
share/mysql/test/suite/parts/inc/partition_check_drop.inc
share/mysql/test/suite/parts/inc/partition_check_read.inc
share/mysql/test/suite/parts/inc/partition_check_read1.inc
share/mysql/test/suite/parts/inc/partition_check_read2.inc
share/mysql/test/suite/parts/inc/partition_cleanup.inc
share/mysql/test/suite/parts/inc/partition_crash.inc
share/mysql/test/suite/parts/inc/partition_crash_add.inc
share/mysql/test/suite/parts/inc/partition_crash_change.inc
share/mysql/test/suite/parts/inc/partition_crash_drop.inc
share/mysql/test/suite/parts/inc/partition_crash_exchange.inc
share/mysql/test/suite/parts/inc/partition_crash_t2.inc
share/mysql/test/suite/parts/inc/partition_date.inc
share/mysql/test/suite/parts/inc/partition_datetime.inc
share/mysql/test/suite/parts/inc/partition_decimal.inc
share/mysql/test/suite/parts/inc/partition_directory.inc
share/mysql/test/suite/parts/inc/partition_double.inc
share/mysql/test/suite/parts/inc/partition_engine.inc
share/mysql/test/suite/parts/inc/partition_enum.inc
share/mysql/test/suite/parts/inc/partition_exchange.inc
share/mysql/test/suite/parts/inc/partition_fail.inc
share/mysql/test/suite/parts/inc/partition_fail_add.inc
share/mysql/test/suite/parts/inc/partition_fail_change.inc
share/mysql/test/suite/parts/inc/partition_fail_drop.inc
share/mysql/test/suite/parts/inc/partition_fail_exchange.inc
share/mysql/test/suite/parts/inc/partition_fail_t2.inc
share/mysql/test/suite/parts/inc/partition_float.inc
share/mysql/test/suite/parts/inc/partition_int.inc
share/mysql/test/suite/parts/inc/partition_key_16col.inc
share/mysql/test/suite/parts/inc/partition_key_32col.inc
share/mysql/test/suite/parts/inc/partition_key_4col.inc
share/mysql/test/suite/parts/inc/partition_key_8col.inc
share/mysql/test/suite/parts/inc/partition_layout.inc
share/mysql/test/suite/parts/inc/partition_layout_check1.inc
share/mysql/test/suite/parts/inc/partition_layout_check2.inc
share/mysql/test/suite/parts/inc/partition_max_parts_hash.inc
share/mysql/test/suite/parts/inc/partition_max_parts_inv.inc
share/mysql/test/suite/parts/inc/partition_max_parts_key.inc
share/mysql/test/suite/parts/inc/partition_max_parts_list.inc
share/mysql/test/suite/parts/inc/partition_max_parts_range.inc
share/mysql/test/suite/parts/inc/partition_max_sub_parts_key_list.inc
share/mysql/test/suite/parts/inc/partition_max_sub_parts_key_range.inc
share/mysql/test/suite/parts/inc/partition_max_sub_parts_list.inc
share/mysql/test/suite/parts/inc/partition_max_sub_parts_range.inc
share/mysql/test/suite/parts/inc/partition_mediumint.inc
share/mysql/test/suite/parts/inc/partition_methods1.inc
share/mysql/test/suite/parts/inc/partition_methods2.inc
share/mysql/test/suite/parts/inc/partition_mgm.inc
share/mysql/test/suite/parts/inc/partition_mgm_crash.inc
share/mysql/test/suite/parts/inc/partition_set.inc
share/mysql/test/suite/parts/inc/partition_smallint.inc
share/mysql/test/suite/parts/inc/partition_supported_sql_funcs.inc
share/mysql/test/suite/parts/inc/partition_syntax.inc
share/mysql/test/suite/parts/inc/partition_syntax_1.inc
share/mysql/test/suite/parts/inc/partition_syntax_2.inc
share/mysql/test/suite/parts/inc/partition_text.inc
share/mysql/test/suite/parts/inc/partition_time.inc
share/mysql/test/suite/parts/inc/partition_timestamp.inc
share/mysql/test/suite/parts/inc/partition_tinyint.inc
share/mysql/test/suite/parts/inc/partition_trigg1.inc
share/mysql/test/suite/parts/inc/partition_trigg2.inc
share/mysql/test/suite/parts/inc/partition_trigg3.inc
share/mysql/test/suite/parts/inc/partition_value.inc
share/mysql/test/suite/parts/inc/partition_varbinary.inc
share/mysql/test/suite/parts/inc/partition_varchar.inc
share/mysql/test/suite/parts/inc/partition_year.inc
share/mysql/test/suite/parts/inc/rpl-partition-dml-1-1.inc
share/mysql/test/suite/parts/r/part_blocked_sql_func_innodb.result
share/mysql/test/suite/parts/r/part_blocked_sql_func_myisam.result
share/mysql/test/suite/parts/r/part_ctype_utf32.result
share/mysql/test/suite/parts/r/part_supported_sql_func_innodb.result
share/mysql/test/suite/parts/r/part_supported_sql_func_myisam.result
share/mysql/test/suite/parts/r/partition-dml-1-1-innodb-modes.result
share/mysql/test/suite/parts/r/partition-dml-1-1-innodb.result
share/mysql/test/suite/parts/r/partition-dml-1-1-myisam-modes.result
share/mysql/test/suite/parts/r/partition-dml-1-1-myisam.result
share/mysql/test/suite/parts/r/partition-dml-1-10-innodb.result
share/mysql/test/suite/parts/r/partition-dml-1-10-myisam.result
share/mysql/test/suite/parts/r/partition-dml-1-11-innodb.result
share/mysql/test/suite/parts/r/partition-dml-1-11-myisam.result
share/mysql/test/suite/parts/r/partition-dml-1-2-innodb.result
share/mysql/test/suite/parts/r/partition-dml-1-2-myisam.result
share/mysql/test/suite/parts/r/partition-dml-1-3-innodb.result
share/mysql/test/suite/parts/r/partition-dml-1-4-innodb.result
share/mysql/test/suite/parts/r/partition-dml-1-5-innodb.result
share/mysql/test/suite/parts/r/partition-dml-1-6-innodb.result
share/mysql/test/suite/parts/r/partition-dml-1-7-innodb.result
share/mysql/test/suite/parts/r/partition-dml-1-8-innodb.result
share/mysql/test/suite/parts/r/partition-dml-1-9-innodb.result
share/mysql/test/suite/parts/r/partition-dml-1-9-myisam.result
share/mysql/test/suite/parts/r/partition_alter1_1_2_innodb.result
share/mysql/test/suite/parts/r/partition_alter1_1_2_myisam.result
share/mysql/test/suite/parts/r/partition_alter1_1_innodb.result
share/mysql/test/suite/parts/r/partition_alter1_1_myisam.result
share/mysql/test/suite/parts/r/partition_alter1_2_innodb.result
share/mysql/test/suite/parts/r/partition_alter1_2_myisam.result
share/mysql/test/suite/parts/r/partition_alter2_1_1_innodb.result
share/mysql/test/suite/parts/r/partition_alter2_1_2_innodb.result
share/mysql/test/suite/parts/r/partition_alter2_1_myisam.result
share/mysql/test/suite/parts/r/partition_alter2_2_1_innodb.result
share/mysql/test/suite/parts/r/partition_alter2_2_2_innodb.result
share/mysql/test/suite/parts/r/partition_alter2_2_myisam.result
share/mysql/test/suite/parts/r/partition_alter3_innodb.result
share/mysql/test/suite/parts/r/partition_alter3_myisam.result
share/mysql/test/suite/parts/r/partition_alter4_innodb.result
share/mysql/test/suite/parts/r/partition_alter4_myisam.result
share/mysql/test/suite/parts/r/partition_auto_increment_archive.result
share/mysql/test/suite/parts/r/partition_auto_increment_blackhole.result
share/mysql/test/suite/parts/r/partition_auto_increment_innodb.result
share/mysql/test/suite/parts/r/partition_auto_increment_memory.result
share/mysql/test/suite/parts/r/partition_auto_increment_myisam.result
share/mysql/test/suite/parts/r/partition_basic_innodb.result
share/mysql/test/suite/parts/r/partition_basic_myisam.result
share/mysql/test/suite/parts/r/partition_basic_symlink_innodb.result
share/mysql/test/suite/parts/r/partition_basic_symlink_myisam.result
share/mysql/test/suite/parts/r/partition_bit_innodb.result
share/mysql/test/suite/parts/r/partition_bit_myisam.result
share/mysql/test/suite/parts/r/partition_char_innodb.result
share/mysql/test/suite/parts/r/partition_char_myisam.result
share/mysql/test/suite/parts/r/partition_datetime_innodb.result
share/mysql/test/suite/parts/r/partition_datetime_myisam.result
share/mysql/test/suite/parts/r/partition_debug.result
share/mysql/test/suite/parts/r/partition_debug_innodb.result
share/mysql/test/suite/parts/r/partition_debug_myisam.result
share/mysql/test/suite/parts/r/partition_debug_sync_innodb.result
share/mysql/test/suite/parts/r/partition_decimal_innodb.result
share/mysql/test/suite/parts/r/partition_decimal_myisam.result
share/mysql/test/suite/parts/r/partition_engine_innodb.result
share/mysql/test/suite/parts/r/partition_engine_myisam.result
share/mysql/test/suite/parts/r/partition_exch_innodb.result
share/mysql/test/suite/parts/r/partition_exch_myisam.result
share/mysql/test/suite/parts/r/partition_exch_myisam_innodb.result
share/mysql/test/suite/parts/r/partition_exch_qa.result
share/mysql/test/suite/parts/r/partition_exch_qa_10.result
share/mysql/test/suite/parts/r/partition_exch_qa_11.result
share/mysql/test/suite/parts/r/partition_exch_qa_12.result
share/mysql/test/suite/parts/r/partition_exch_qa_13.result
share/mysql/test/suite/parts/r/partition_exch_qa_14.result
share/mysql/test/suite/parts/r/partition_exch_qa_15.result
share/mysql/test/suite/parts/r/partition_exch_qa_1_innodb.result
share/mysql/test/suite/parts/r/partition_exch_qa_1_myisam.result
share/mysql/test/suite/parts/r/partition_exch_qa_2.result
share/mysql/test/suite/parts/r/partition_exch_qa_3.result
share/mysql/test/suite/parts/r/partition_exch_qa_4_innodb.result
share/mysql/test/suite/parts/r/partition_exch_qa_4_myisam.result
share/mysql/test/suite/parts/r/partition_exch_qa_5_innodb.result
share/mysql/test/suite/parts/r/partition_exch_qa_5_myisam.result
share/mysql/test/suite/parts/r/partition_exch_qa_6.result
share/mysql/test/suite/parts/r/partition_exch_qa_7_innodb.result
share/mysql/test/suite/parts/r/partition_exch_qa_7_myisam.result
share/mysql/test/suite/parts/r/partition_exch_qa_8_innodb.result
share/mysql/test/suite/parts/r/partition_exch_qa_8_myisam.result
share/mysql/test/suite/parts/r/partition_exchange_archive.result
share/mysql/test/suite/parts/r/partition_exchange_blackhole.result
share/mysql/test/suite/parts/r/partition_exchange_innodb.result
share/mysql/test/suite/parts/r/partition_exchange_memory.result
share/mysql/test/suite/parts/r/partition_exchange_myisam.result
share/mysql/test/suite/parts/r/partition_float_innodb.result
share/mysql/test/suite/parts/r/partition_float_myisam.result
share/mysql/test/suite/parts/r/partition_innodb_status_file.result
share/mysql/test/suite/parts/r/partition_int_innodb.result
share/mysql/test/suite/parts/r/partition_int_myisam.result
share/mysql/test/suite/parts/r/partition_max_parts_hash_innodb.result
share/mysql/test/suite/parts/r/partition_max_parts_hash_myisam.result
share/mysql/test/suite/parts/r/partition_max_parts_inv_innodb.result
share/mysql/test/suite/parts/r/partition_max_parts_inv_myisam.result
share/mysql/test/suite/parts/r/partition_max_parts_key_innodb.result
share/mysql/test/suite/parts/r/partition_max_parts_key_myisam.result
share/mysql/test/suite/parts/r/partition_max_parts_list_innodb.result
share/mysql/test/suite/parts/r/partition_max_parts_list_myisam.result
share/mysql/test/suite/parts/r/partition_max_parts_range_innodb.result
share/mysql/test/suite/parts/r/partition_max_parts_range_myisam.result
share/mysql/test/suite/parts/r/partition_max_sub_parts_key_list_innodb.result
share/mysql/test/suite/parts/r/partition_max_sub_parts_key_list_myisam.result
share/mysql/test/suite/parts/r/partition_max_sub_parts_key_range_innodb.result
share/mysql/test/suite/parts/r/partition_max_sub_parts_key_range_myisam.result
share/mysql/test/suite/parts/r/partition_max_sub_parts_list_innodb.result
share/mysql/test/suite/parts/r/partition_max_sub_parts_list_myisam.result
share/mysql/test/suite/parts/r/partition_max_sub_parts_range_innodb.result
share/mysql/test/suite/parts/r/partition_max_sub_parts_range_myisam.result
share/mysql/test/suite/parts/r/partition_mgm_lc0_archive.result
share/mysql/test/suite/parts/r/partition_mgm_lc0_innodb.result
share/mysql/test/suite/parts/r/partition_mgm_lc0_memory.result
share/mysql/test/suite/parts/r/partition_mgm_lc0_myisam.result
share/mysql/test/suite/parts/r/partition_mgm_lc1_archive.result
share/mysql/test/suite/parts/r/partition_mgm_lc1_innodb.result
share/mysql/test/suite/parts/r/partition_mgm_lc1_memory.result
share/mysql/test/suite/parts/r/partition_mgm_lc1_myisam.result
share/mysql/test/suite/parts/r/partition_mgm_lc2_archive.result
share/mysql/test/suite/parts/r/partition_mgm_lc2_innodb.result
share/mysql/test/suite/parts/r/partition_mgm_lc2_memory.result
share/mysql/test/suite/parts/r/partition_mgm_lc2_myisam.result
share/mysql/test/suite/parts/r/partition_recover_myisam.result
share/mysql/test/suite/parts/r/partition_reorganize_innodb.result
share/mysql/test/suite/parts/r/partition_reorganize_myisam.result
share/mysql/test/suite/parts/r/partition_repair_myisam.result
share/mysql/test/suite/parts/r/partition_special_innodb.result
share/mysql/test/suite/parts/r/partition_special_myisam.result
share/mysql/test/suite/parts/r/partition_syntax_innodb.result
share/mysql/test/suite/parts/r/partition_syntax_myisam.result
share/mysql/test/suite/parts/r/partition_t55.out
share/mysql/test/suite/parts/r/partition_value_innodb.result
share/mysql/test/suite/parts/r/partition_value_myisam.result
share/mysql/test/suite/parts/r/rpl-partition-dml-1-1-innodb.result
share/mysql/test/suite/parts/r/rpl-partition-dml-1-1-myisam.result
share/mysql/test/suite/parts/r/rpl_partition.result
share/mysql/test/suite/parts/t/disabled.def
share/mysql/test/suite/parts/t/part_blocked_sql_func_innodb.test
share/mysql/test/suite/parts/t/part_blocked_sql_func_myisam.test
share/mysql/test/suite/parts/t/part_ctype_utf32.test
share/mysql/test/suite/parts/t/part_supported_sql_func_innodb.test
share/mysql/test/suite/parts/t/part_supported_sql_func_myisam.test
share/mysql/test/suite/parts/t/partition-dml-1-1-innodb-modes.test
share/mysql/test/suite/parts/t/partition-dml-1-1-innodb.test
share/mysql/test/suite/parts/t/partition-dml-1-1-myisam-modes.test
share/mysql/test/suite/parts/t/partition-dml-1-1-myisam.test
share/mysql/test/suite/parts/t/partition-dml-1-10-innodb.test
share/mysql/test/suite/parts/t/partition-dml-1-10-myisam.test
share/mysql/test/suite/parts/t/partition-dml-1-11-innodb.test
share/mysql/test/suite/parts/t/partition-dml-1-11-myisam.test
share/mysql/test/suite/parts/t/partition-dml-1-2-innodb.test
share/mysql/test/suite/parts/t/partition-dml-1-2-myisam.test
share/mysql/test/suite/parts/t/partition-dml-1-3-innodb.test
share/mysql/test/suite/parts/t/partition-dml-1-4-innodb.test
share/mysql/test/suite/parts/t/partition-dml-1-5-innodb.test
share/mysql/test/suite/parts/t/partition-dml-1-6-innodb.test
share/mysql/test/suite/parts/t/partition-dml-1-7-innodb.test
share/mysql/test/suite/parts/t/partition-dml-1-8-innodb.test
share/mysql/test/suite/parts/t/partition-dml-1-9-innodb.test
share/mysql/test/suite/parts/t/partition-dml-1-9-myisam.test
share/mysql/test/suite/parts/t/partition_alter1_1_2_innodb.test
share/mysql/test/suite/parts/t/partition_alter1_1_2_myisam.test
share/mysql/test/suite/parts/t/partition_alter1_1_innodb.test
share/mysql/test/suite/parts/t/partition_alter1_1_myisam.test
share/mysql/test/suite/parts/t/partition_alter1_2_innodb.test
share/mysql/test/suite/parts/t/partition_alter1_2_myisam.test
share/mysql/test/suite/parts/t/partition_alter2_1_1_innodb.test
share/mysql/test/suite/parts/t/partition_alter2_1_2_innodb.test
share/mysql/test/suite/parts/t/partition_alter2_1_myisam.test
share/mysql/test/suite/parts/t/partition_alter2_2_1_innodb.test
share/mysql/test/suite/parts/t/partition_alter2_2_2_innodb.test
share/mysql/test/suite/parts/t/partition_alter2_2_myisam.test
share/mysql/test/suite/parts/t/partition_alter3_innodb.test
share/mysql/test/suite/parts/t/partition_alter3_myisam.test
share/mysql/test/suite/parts/t/partition_alter4_innodb.test
share/mysql/test/suite/parts/t/partition_alter4_myisam.test
share/mysql/test/suite/parts/t/partition_auto_increment_archive.test
share/mysql/test/suite/parts/t/partition_auto_increment_blackhole.test
share/mysql/test/suite/parts/t/partition_auto_increment_innodb.test
share/mysql/test/suite/parts/t/partition_auto_increment_memory.test
share/mysql/test/suite/parts/t/partition_auto_increment_myisam.test
share/mysql/test/suite/parts/t/partition_basic_innodb.test
share/mysql/test/suite/parts/t/partition_basic_myisam.test
share/mysql/test/suite/parts/t/partition_basic_symlink_innodb.test
share/mysql/test/suite/parts/t/partition_basic_symlink_myisam.test
share/mysql/test/suite/parts/t/partition_bit_innodb.test
share/mysql/test/suite/parts/t/partition_bit_myisam.test
share/mysql/test/suite/parts/t/partition_char_innodb.test
share/mysql/test/suite/parts/t/partition_char_myisam.test
share/mysql/test/suite/parts/t/partition_datetime_innodb.test
share/mysql/test/suite/parts/t/partition_datetime_myisam.test
share/mysql/test/suite/parts/t/partition_debug.test
share/mysql/test/suite/parts/t/partition_debug_innodb-master.opt
share/mysql/test/suite/parts/t/partition_debug_innodb.test
share/mysql/test/suite/parts/t/partition_debug_myisam.test
share/mysql/test/suite/parts/t/partition_debug_sync_innodb-master.opt
share/mysql/test/suite/parts/t/partition_debug_sync_innodb.test
share/mysql/test/suite/parts/t/partition_decimal_innodb.test
share/mysql/test/suite/parts/t/partition_decimal_myisam.test
share/mysql/test/suite/parts/t/partition_engine_innodb.test
share/mysql/test/suite/parts/t/partition_engine_myisam.test
share/mysql/test/suite/parts/t/partition_exch_innodb.test
share/mysql/test/suite/parts/t/partition_exch_myisam.test
share/mysql/test/suite/parts/t/partition_exch_myisam_innodb.test
share/mysql/test/suite/parts/t/partition_exch_qa.test
share/mysql/test/suite/parts/t/partition_exch_qa_10.test
share/mysql/test/suite/parts/t/partition_exch_qa_11.test
share/mysql/test/suite/parts/t/partition_exch_qa_12.test
share/mysql/test/suite/parts/t/partition_exch_qa_13.test
share/mysql/test/suite/parts/t/partition_exch_qa_14.test
share/mysql/test/suite/parts/t/partition_exch_qa_15.test
share/mysql/test/suite/parts/t/partition_exch_qa_1_innodb.test
share/mysql/test/suite/parts/t/partition_exch_qa_1_myisam.test
share/mysql/test/suite/parts/t/partition_exch_qa_2.test
share/mysql/test/suite/parts/t/partition_exch_qa_3.test
share/mysql/test/suite/parts/t/partition_exch_qa_4_innodb.test
share/mysql/test/suite/parts/t/partition_exch_qa_4_myisam.test
share/mysql/test/suite/parts/t/partition_exch_qa_5_innodb.test
share/mysql/test/suite/parts/t/partition_exch_qa_5_myisam.test
share/mysql/test/suite/parts/t/partition_exch_qa_6.test
share/mysql/test/suite/parts/t/partition_exch_qa_7_innodb.test
share/mysql/test/suite/parts/t/partition_exch_qa_7_myisam.test
share/mysql/test/suite/parts/t/partition_exch_qa_8_innodb.test
share/mysql/test/suite/parts/t/partition_exch_qa_8_myisam.test
share/mysql/test/suite/parts/t/partition_exchange_archive.test
share/mysql/test/suite/parts/t/partition_exchange_blackhole.test
share/mysql/test/suite/parts/t/partition_exchange_innodb.test
share/mysql/test/suite/parts/t/partition_exchange_memory.test
share/mysql/test/suite/parts/t/partition_exchange_myisam.test
share/mysql/test/suite/parts/t/partition_float_innodb.test
share/mysql/test/suite/parts/t/partition_float_myisam.test
share/mysql/test/suite/parts/t/partition_innodb_status_file-master.opt
share/mysql/test/suite/parts/t/partition_innodb_status_file.test
share/mysql/test/suite/parts/t/partition_int_innodb.test
share/mysql/test/suite/parts/t/partition_int_myisam.test
Changes 5.6.15: * Previously, MySQL Server distributions included the MySQL Reference Manual in Info format (the Docs/mysql.info file). Because the license for the manual restricts redistribution, its inclusion in Community packages caused problems for downstream redistributors, such as those who create Linux distributions. Community distributions of MySQL Server no longer include the mysql.info file, to make the repackaging and redistribution process easier (for example, the source tarball and its checksum can be used directly). This change applies to all source and binary Community packaging formats. Commercial (Enterprise) distributions are unchanged. * Incompatible Change: Several statement instruments in the setup_instruments table are used by the Performance Schema during the early stages of statement classification before the exact statement type is known. * The Performance Schema now instruments the read/write lock Delegate::lock * A new CMake option, WITH_ASAN, permits enabling address sanitization for compilers that support it. * The hash function used for metadata locking was modified to reduce overhead. * Bugs Fixed
2013-12-03 21:02:41 +01:00
share/mysql/test/suite/parts/t/partition_max_parts_hash_innodb-master.opt
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/parts/t/partition_max_parts_hash_innodb.test
Changes 5.6.15: * Previously, MySQL Server distributions included the MySQL Reference Manual in Info format (the Docs/mysql.info file). Because the license for the manual restricts redistribution, its inclusion in Community packages caused problems for downstream redistributors, such as those who create Linux distributions. Community distributions of MySQL Server no longer include the mysql.info file, to make the repackaging and redistribution process easier (for example, the source tarball and its checksum can be used directly). This change applies to all source and binary Community packaging formats. Commercial (Enterprise) distributions are unchanged. * Incompatible Change: Several statement instruments in the setup_instruments table are used by the Performance Schema during the early stages of statement classification before the exact statement type is known. * The Performance Schema now instruments the read/write lock Delegate::lock * A new CMake option, WITH_ASAN, permits enabling address sanitization for compilers that support it. * The hash function used for metadata locking was modified to reduce overhead. * Bugs Fixed
2013-12-03 21:02:41 +01:00
share/mysql/test/suite/parts/t/partition_max_parts_hash_myisam-master.opt
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/parts/t/partition_max_parts_hash_myisam.test
Changes 5.6.15: * Previously, MySQL Server distributions included the MySQL Reference Manual in Info format (the Docs/mysql.info file). Because the license for the manual restricts redistribution, its inclusion in Community packages caused problems for downstream redistributors, such as those who create Linux distributions. Community distributions of MySQL Server no longer include the mysql.info file, to make the repackaging and redistribution process easier (for example, the source tarball and its checksum can be used directly). This change applies to all source and binary Community packaging formats. Commercial (Enterprise) distributions are unchanged. * Incompatible Change: Several statement instruments in the setup_instruments table are used by the Performance Schema during the early stages of statement classification before the exact statement type is known. * The Performance Schema now instruments the read/write lock Delegate::lock * A new CMake option, WITH_ASAN, permits enabling address sanitization for compilers that support it. * The hash function used for metadata locking was modified to reduce overhead. * Bugs Fixed
2013-12-03 21:02:41 +01:00
share/mysql/test/suite/parts/t/partition_max_parts_inv_innodb-master.opt
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/parts/t/partition_max_parts_inv_innodb.test
Changes 5.6.15: * Previously, MySQL Server distributions included the MySQL Reference Manual in Info format (the Docs/mysql.info file). Because the license for the manual restricts redistribution, its inclusion in Community packages caused problems for downstream redistributors, such as those who create Linux distributions. Community distributions of MySQL Server no longer include the mysql.info file, to make the repackaging and redistribution process easier (for example, the source tarball and its checksum can be used directly). This change applies to all source and binary Community packaging formats. Commercial (Enterprise) distributions are unchanged. * Incompatible Change: Several statement instruments in the setup_instruments table are used by the Performance Schema during the early stages of statement classification before the exact statement type is known. * The Performance Schema now instruments the read/write lock Delegate::lock * A new CMake option, WITH_ASAN, permits enabling address sanitization for compilers that support it. * The hash function used for metadata locking was modified to reduce overhead. * Bugs Fixed
2013-12-03 21:02:41 +01:00
share/mysql/test/suite/parts/t/partition_max_parts_inv_myisam-master.opt
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/parts/t/partition_max_parts_inv_myisam.test
Changes 5.6.15: * Previously, MySQL Server distributions included the MySQL Reference Manual in Info format (the Docs/mysql.info file). Because the license for the manual restricts redistribution, its inclusion in Community packages caused problems for downstream redistributors, such as those who create Linux distributions. Community distributions of MySQL Server no longer include the mysql.info file, to make the repackaging and redistribution process easier (for example, the source tarball and its checksum can be used directly). This change applies to all source and binary Community packaging formats. Commercial (Enterprise) distributions are unchanged. * Incompatible Change: Several statement instruments in the setup_instruments table are used by the Performance Schema during the early stages of statement classification before the exact statement type is known. * The Performance Schema now instruments the read/write lock Delegate::lock * A new CMake option, WITH_ASAN, permits enabling address sanitization for compilers that support it. * The hash function used for metadata locking was modified to reduce overhead. * Bugs Fixed
2013-12-03 21:02:41 +01:00
share/mysql/test/suite/parts/t/partition_max_parts_key_innodb-master.opt
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/parts/t/partition_max_parts_key_innodb.test
Changes 5.6.15: * Previously, MySQL Server distributions included the MySQL Reference Manual in Info format (the Docs/mysql.info file). Because the license for the manual restricts redistribution, its inclusion in Community packages caused problems for downstream redistributors, such as those who create Linux distributions. Community distributions of MySQL Server no longer include the mysql.info file, to make the repackaging and redistribution process easier (for example, the source tarball and its checksum can be used directly). This change applies to all source and binary Community packaging formats. Commercial (Enterprise) distributions are unchanged. * Incompatible Change: Several statement instruments in the setup_instruments table are used by the Performance Schema during the early stages of statement classification before the exact statement type is known. * The Performance Schema now instruments the read/write lock Delegate::lock * A new CMake option, WITH_ASAN, permits enabling address sanitization for compilers that support it. * The hash function used for metadata locking was modified to reduce overhead. * Bugs Fixed
2013-12-03 21:02:41 +01:00
share/mysql/test/suite/parts/t/partition_max_parts_key_myisam-master.opt
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/parts/t/partition_max_parts_key_myisam.test
Changes 5.6.15: * Previously, MySQL Server distributions included the MySQL Reference Manual in Info format (the Docs/mysql.info file). Because the license for the manual restricts redistribution, its inclusion in Community packages caused problems for downstream redistributors, such as those who create Linux distributions. Community distributions of MySQL Server no longer include the mysql.info file, to make the repackaging and redistribution process easier (for example, the source tarball and its checksum can be used directly). This change applies to all source and binary Community packaging formats. Commercial (Enterprise) distributions are unchanged. * Incompatible Change: Several statement instruments in the setup_instruments table are used by the Performance Schema during the early stages of statement classification before the exact statement type is known. * The Performance Schema now instruments the read/write lock Delegate::lock * A new CMake option, WITH_ASAN, permits enabling address sanitization for compilers that support it. * The hash function used for metadata locking was modified to reduce overhead. * Bugs Fixed
2013-12-03 21:02:41 +01:00
share/mysql/test/suite/parts/t/partition_max_parts_list_innodb-master.opt
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/parts/t/partition_max_parts_list_innodb.test
Changes 5.6.15: * Previously, MySQL Server distributions included the MySQL Reference Manual in Info format (the Docs/mysql.info file). Because the license for the manual restricts redistribution, its inclusion in Community packages caused problems for downstream redistributors, such as those who create Linux distributions. Community distributions of MySQL Server no longer include the mysql.info file, to make the repackaging and redistribution process easier (for example, the source tarball and its checksum can be used directly). This change applies to all source and binary Community packaging formats. Commercial (Enterprise) distributions are unchanged. * Incompatible Change: Several statement instruments in the setup_instruments table are used by the Performance Schema during the early stages of statement classification before the exact statement type is known. * The Performance Schema now instruments the read/write lock Delegate::lock * A new CMake option, WITH_ASAN, permits enabling address sanitization for compilers that support it. * The hash function used for metadata locking was modified to reduce overhead. * Bugs Fixed
2013-12-03 21:02:41 +01:00
share/mysql/test/suite/parts/t/partition_max_parts_list_myisam-master.opt
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/parts/t/partition_max_parts_list_myisam.test
Changes 5.6.15: * Previously, MySQL Server distributions included the MySQL Reference Manual in Info format (the Docs/mysql.info file). Because the license for the manual restricts redistribution, its inclusion in Community packages caused problems for downstream redistributors, such as those who create Linux distributions. Community distributions of MySQL Server no longer include the mysql.info file, to make the repackaging and redistribution process easier (for example, the source tarball and its checksum can be used directly). This change applies to all source and binary Community packaging formats. Commercial (Enterprise) distributions are unchanged. * Incompatible Change: Several statement instruments in the setup_instruments table are used by the Performance Schema during the early stages of statement classification before the exact statement type is known. * The Performance Schema now instruments the read/write lock Delegate::lock * A new CMake option, WITH_ASAN, permits enabling address sanitization for compilers that support it. * The hash function used for metadata locking was modified to reduce overhead. * Bugs Fixed
2013-12-03 21:02:41 +01:00
share/mysql/test/suite/parts/t/partition_max_parts_range_innodb-master.opt
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/parts/t/partition_max_parts_range_innodb.test
Changes 5.6.15: * Previously, MySQL Server distributions included the MySQL Reference Manual in Info format (the Docs/mysql.info file). Because the license for the manual restricts redistribution, its inclusion in Community packages caused problems for downstream redistributors, such as those who create Linux distributions. Community distributions of MySQL Server no longer include the mysql.info file, to make the repackaging and redistribution process easier (for example, the source tarball and its checksum can be used directly). This change applies to all source and binary Community packaging formats. Commercial (Enterprise) distributions are unchanged. * Incompatible Change: Several statement instruments in the setup_instruments table are used by the Performance Schema during the early stages of statement classification before the exact statement type is known. * The Performance Schema now instruments the read/write lock Delegate::lock * A new CMake option, WITH_ASAN, permits enabling address sanitization for compilers that support it. * The hash function used for metadata locking was modified to reduce overhead. * Bugs Fixed
2013-12-03 21:02:41 +01:00
share/mysql/test/suite/parts/t/partition_max_parts_range_myisam-master.opt
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/parts/t/partition_max_parts_range_myisam.test
Changes 5.6.15: * Previously, MySQL Server distributions included the MySQL Reference Manual in Info format (the Docs/mysql.info file). Because the license for the manual restricts redistribution, its inclusion in Community packages caused problems for downstream redistributors, such as those who create Linux distributions. Community distributions of MySQL Server no longer include the mysql.info file, to make the repackaging and redistribution process easier (for example, the source tarball and its checksum can be used directly). This change applies to all source and binary Community packaging formats. Commercial (Enterprise) distributions are unchanged. * Incompatible Change: Several statement instruments in the setup_instruments table are used by the Performance Schema during the early stages of statement classification before the exact statement type is known. * The Performance Schema now instruments the read/write lock Delegate::lock * A new CMake option, WITH_ASAN, permits enabling address sanitization for compilers that support it. * The hash function used for metadata locking was modified to reduce overhead. * Bugs Fixed
2013-12-03 21:02:41 +01:00
share/mysql/test/suite/parts/t/partition_max_sub_parts_key_list_innodb-master.opt
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/parts/t/partition_max_sub_parts_key_list_innodb.test
Changes 5.6.15: * Previously, MySQL Server distributions included the MySQL Reference Manual in Info format (the Docs/mysql.info file). Because the license for the manual restricts redistribution, its inclusion in Community packages caused problems for downstream redistributors, such as those who create Linux distributions. Community distributions of MySQL Server no longer include the mysql.info file, to make the repackaging and redistribution process easier (for example, the source tarball and its checksum can be used directly). This change applies to all source and binary Community packaging formats. Commercial (Enterprise) distributions are unchanged. * Incompatible Change: Several statement instruments in the setup_instruments table are used by the Performance Schema during the early stages of statement classification before the exact statement type is known. * The Performance Schema now instruments the read/write lock Delegate::lock * A new CMake option, WITH_ASAN, permits enabling address sanitization for compilers that support it. * The hash function used for metadata locking was modified to reduce overhead. * Bugs Fixed
2013-12-03 21:02:41 +01:00
share/mysql/test/suite/parts/t/partition_max_sub_parts_key_list_myisam-master.opt
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/parts/t/partition_max_sub_parts_key_list_myisam.test
Changes 5.6.15: * Previously, MySQL Server distributions included the MySQL Reference Manual in Info format (the Docs/mysql.info file). Because the license for the manual restricts redistribution, its inclusion in Community packages caused problems for downstream redistributors, such as those who create Linux distributions. Community distributions of MySQL Server no longer include the mysql.info file, to make the repackaging and redistribution process easier (for example, the source tarball and its checksum can be used directly). This change applies to all source and binary Community packaging formats. Commercial (Enterprise) distributions are unchanged. * Incompatible Change: Several statement instruments in the setup_instruments table are used by the Performance Schema during the early stages of statement classification before the exact statement type is known. * The Performance Schema now instruments the read/write lock Delegate::lock * A new CMake option, WITH_ASAN, permits enabling address sanitization for compilers that support it. * The hash function used for metadata locking was modified to reduce overhead. * Bugs Fixed
2013-12-03 21:02:41 +01:00
share/mysql/test/suite/parts/t/partition_max_sub_parts_key_range_innodb-master.opt
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/parts/t/partition_max_sub_parts_key_range_innodb.test
Changes 5.6.15: * Previously, MySQL Server distributions included the MySQL Reference Manual in Info format (the Docs/mysql.info file). Because the license for the manual restricts redistribution, its inclusion in Community packages caused problems for downstream redistributors, such as those who create Linux distributions. Community distributions of MySQL Server no longer include the mysql.info file, to make the repackaging and redistribution process easier (for example, the source tarball and its checksum can be used directly). This change applies to all source and binary Community packaging formats. Commercial (Enterprise) distributions are unchanged. * Incompatible Change: Several statement instruments in the setup_instruments table are used by the Performance Schema during the early stages of statement classification before the exact statement type is known. * The Performance Schema now instruments the read/write lock Delegate::lock * A new CMake option, WITH_ASAN, permits enabling address sanitization for compilers that support it. * The hash function used for metadata locking was modified to reduce overhead. * Bugs Fixed
2013-12-03 21:02:41 +01:00
share/mysql/test/suite/parts/t/partition_max_sub_parts_key_range_myisam-master.opt
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/parts/t/partition_max_sub_parts_key_range_myisam.test
Changes 5.6.15: * Previously, MySQL Server distributions included the MySQL Reference Manual in Info format (the Docs/mysql.info file). Because the license for the manual restricts redistribution, its inclusion in Community packages caused problems for downstream redistributors, such as those who create Linux distributions. Community distributions of MySQL Server no longer include the mysql.info file, to make the repackaging and redistribution process easier (for example, the source tarball and its checksum can be used directly). This change applies to all source and binary Community packaging formats. Commercial (Enterprise) distributions are unchanged. * Incompatible Change: Several statement instruments in the setup_instruments table are used by the Performance Schema during the early stages of statement classification before the exact statement type is known. * The Performance Schema now instruments the read/write lock Delegate::lock * A new CMake option, WITH_ASAN, permits enabling address sanitization for compilers that support it. * The hash function used for metadata locking was modified to reduce overhead. * Bugs Fixed
2013-12-03 21:02:41 +01:00
share/mysql/test/suite/parts/t/partition_max_sub_parts_list_innodb-master.opt
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/parts/t/partition_max_sub_parts_list_innodb.test
Changes 5.6.15: * Previously, MySQL Server distributions included the MySQL Reference Manual in Info format (the Docs/mysql.info file). Because the license for the manual restricts redistribution, its inclusion in Community packages caused problems for downstream redistributors, such as those who create Linux distributions. Community distributions of MySQL Server no longer include the mysql.info file, to make the repackaging and redistribution process easier (for example, the source tarball and its checksum can be used directly). This change applies to all source and binary Community packaging formats. Commercial (Enterprise) distributions are unchanged. * Incompatible Change: Several statement instruments in the setup_instruments table are used by the Performance Schema during the early stages of statement classification before the exact statement type is known. * The Performance Schema now instruments the read/write lock Delegate::lock * A new CMake option, WITH_ASAN, permits enabling address sanitization for compilers that support it. * The hash function used for metadata locking was modified to reduce overhead. * Bugs Fixed
2013-12-03 21:02:41 +01:00
share/mysql/test/suite/parts/t/partition_max_sub_parts_list_myisam-master.opt
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/parts/t/partition_max_sub_parts_list_myisam.test
Changes 5.6.15: * Previously, MySQL Server distributions included the MySQL Reference Manual in Info format (the Docs/mysql.info file). Because the license for the manual restricts redistribution, its inclusion in Community packages caused problems for downstream redistributors, such as those who create Linux distributions. Community distributions of MySQL Server no longer include the mysql.info file, to make the repackaging and redistribution process easier (for example, the source tarball and its checksum can be used directly). This change applies to all source and binary Community packaging formats. Commercial (Enterprise) distributions are unchanged. * Incompatible Change: Several statement instruments in the setup_instruments table are used by the Performance Schema during the early stages of statement classification before the exact statement type is known. * The Performance Schema now instruments the read/write lock Delegate::lock * A new CMake option, WITH_ASAN, permits enabling address sanitization for compilers that support it. * The hash function used for metadata locking was modified to reduce overhead. * Bugs Fixed
2013-12-03 21:02:41 +01:00
share/mysql/test/suite/parts/t/partition_max_sub_parts_range_innodb-master.opt
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/parts/t/partition_max_sub_parts_range_innodb.test
Changes 5.6.15: * Previously, MySQL Server distributions included the MySQL Reference Manual in Info format (the Docs/mysql.info file). Because the license for the manual restricts redistribution, its inclusion in Community packages caused problems for downstream redistributors, such as those who create Linux distributions. Community distributions of MySQL Server no longer include the mysql.info file, to make the repackaging and redistribution process easier (for example, the source tarball and its checksum can be used directly). This change applies to all source and binary Community packaging formats. Commercial (Enterprise) distributions are unchanged. * Incompatible Change: Several statement instruments in the setup_instruments table are used by the Performance Schema during the early stages of statement classification before the exact statement type is known. * The Performance Schema now instruments the read/write lock Delegate::lock * A new CMake option, WITH_ASAN, permits enabling address sanitization for compilers that support it. * The hash function used for metadata locking was modified to reduce overhead. * Bugs Fixed
2013-12-03 21:02:41 +01:00
share/mysql/test/suite/parts/t/partition_max_sub_parts_range_myisam-master.opt
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/parts/t/partition_max_sub_parts_range_myisam.test
share/mysql/test/suite/parts/t/partition_mgm_lc0_archive.test
share/mysql/test/suite/parts/t/partition_mgm_lc0_innodb.test
share/mysql/test/suite/parts/t/partition_mgm_lc0_memory.test
share/mysql/test/suite/parts/t/partition_mgm_lc0_myisam.test
share/mysql/test/suite/parts/t/partition_mgm_lc1_archive-master.opt
share/mysql/test/suite/parts/t/partition_mgm_lc1_archive.test
share/mysql/test/suite/parts/t/partition_mgm_lc1_innodb-master.opt
share/mysql/test/suite/parts/t/partition_mgm_lc1_innodb.test
share/mysql/test/suite/parts/t/partition_mgm_lc1_memory-master.opt
share/mysql/test/suite/parts/t/partition_mgm_lc1_memory.test
share/mysql/test/suite/parts/t/partition_mgm_lc1_myisam-master.opt
share/mysql/test/suite/parts/t/partition_mgm_lc1_myisam.test
share/mysql/test/suite/parts/t/partition_mgm_lc2_archive-master.opt
share/mysql/test/suite/parts/t/partition_mgm_lc2_archive.test
share/mysql/test/suite/parts/t/partition_mgm_lc2_innodb-master.opt
share/mysql/test/suite/parts/t/partition_mgm_lc2_innodb.test
share/mysql/test/suite/parts/t/partition_mgm_lc2_memory-master.opt
share/mysql/test/suite/parts/t/partition_mgm_lc2_memory.test
share/mysql/test/suite/parts/t/partition_mgm_lc2_myisam-master.opt
share/mysql/test/suite/parts/t/partition_mgm_lc2_myisam.test
share/mysql/test/suite/parts/t/partition_recover_myisam-master.opt
share/mysql/test/suite/parts/t/partition_recover_myisam.test
share/mysql/test/suite/parts/t/partition_reorganize_innodb.test
share/mysql/test/suite/parts/t/partition_reorganize_myisam.test
share/mysql/test/suite/parts/t/partition_repair_myisam.test
share/mysql/test/suite/parts/t/partition_special_innodb-master.opt
share/mysql/test/suite/parts/t/partition_special_innodb.test
share/mysql/test/suite/parts/t/partition_special_myisam.test
share/mysql/test/suite/parts/t/partition_syntax_innodb.test
share/mysql/test/suite/parts/t/partition_syntax_myisam.test
share/mysql/test/suite/parts/t/partition_value_innodb.test
share/mysql/test/suite/parts/t/partition_value_myisam.test
share/mysql/test/suite/parts/t/rpl-partition-dml-1-1-innodb.test
share/mysql/test/suite/parts/t/rpl-partition-dml-1-1-myisam.test
share/mysql/test/suite/parts/t/rpl_partition.test
share/mysql/test/suite/perfschema/include/binlog_edge_common.inc
share/mysql/test/suite/perfschema/include/binlog_ok_common.inc
share/mysql/test/suite/perfschema/include/cleanup_helper.inc
share/mysql/test/suite/perfschema/include/connection_cleanup.inc
share/mysql/test/suite/perfschema/include/connection_load.inc
share/mysql/test/suite/perfschema/include/connection_setup.inc
share/mysql/test/suite/perfschema/include/digest_cleanup.inc
share/mysql/test/suite/perfschema/include/digest_execution.inc
share/mysql/test/suite/perfschema/include/digest_setup.inc
Changes 5.6.13: * Important Change; Replication: By default, when promoting integers from a smaller type on the master to a larger type on the slave (for example, from a SMALLINT column on the master to a BIGINT column on the slave), the promoted values are treated as though they are signed. Now in such cases it is possible to modify or override this behavior using one or both of ALL_SIGNED, ALL_UNSIGNED in the set of values specified for the slave_type_conversions server system variable. For more information, see Row-based replication: attribute promotion and demotion, as well as the description of the variable. * Previously, program options could be specified in full or as any unambiguous prefix. For example, the --compress option could be given to mysqldump as --compr, but not as --comp because the latter is ambiguous. Option prefixes now are deprecated. They can cause problems when new options are implemented for programs. A prefix that is currently unambiguous might become ambiguous in the future. If an unambiguous prefix is given, a warning now occurs to provide feedback. For example: Warning: Using unique option prefix compr instead of compress is deprecated and will be removed in a future release. Please use the full name instead. Option prefixes are no longer supported in MySQL 5.7; only full options are accepted. * The C API libmysqlclient shared-library .so files now have version 18.1.0 (up from version 18.0.0 used in MySQL 5.5). * In batch mode, mysql formatted result status messages such as “"Query OK, 1 row affected"” but did not print them. Now these messages are not formatted. * Bugs Fixed
2013-07-31 11:51:38 +02:00
share/mysql/test/suite/perfschema/include/disable_instruments.inc
share/mysql/test/suite/perfschema/include/enable_instruments.inc
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/perfschema/include/event_aggregate_cleanup.inc
share/mysql/test/suite/perfschema/include/event_aggregate_load.inc
share/mysql/test/suite/perfschema/include/event_aggregate_setup.inc
share/mysql/test/suite/perfschema/include/have_aligned_memory.inc
share/mysql/test/suite/perfschema/include/hostcache_dump.inc
share/mysql/test/suite/perfschema/include/hostcache_set_state.inc
share/mysql/test/suite/perfschema/include/privilege.inc
Changes 5.6.13: * Important Change; Replication: By default, when promoting integers from a smaller type on the master to a larger type on the slave (for example, from a SMALLINT column on the master to a BIGINT column on the slave), the promoted values are treated as though they are signed. Now in such cases it is possible to modify or override this behavior using one or both of ALL_SIGNED, ALL_UNSIGNED in the set of values specified for the slave_type_conversions server system variable. For more information, see Row-based replication: attribute promotion and demotion, as well as the description of the variable. * Previously, program options could be specified in full or as any unambiguous prefix. For example, the --compress option could be given to mysqldump as --compr, but not as --comp because the latter is ambiguous. Option prefixes now are deprecated. They can cause problems when new options are implemented for programs. A prefix that is currently unambiguous might become ambiguous in the future. If an unambiguous prefix is given, a warning now occurs to provide feedback. For example: Warning: Using unique option prefix compr instead of compress is deprecated and will be removed in a future release. Please use the full name instead. Option prefixes are no longer supported in MySQL 5.7; only full options are accepted. * The C API libmysqlclient shared-library .so files now have version 18.1.0 (up from version 18.0.0 used in MySQL 5.5). * In batch mode, mysql formatted result status messages such as “"Query OK, 1 row affected"” but did not print them. Now these messages are not formatted. * Bugs Fixed
2013-07-31 11:51:38 +02:00
share/mysql/test/suite/perfschema/include/rpl_statements_truncate.inc
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/perfschema/include/schema.inc
share/mysql/test/suite/perfschema/include/setup_helper.inc
share/mysql/test/suite/perfschema/include/sizing_auto.inc
share/mysql/test/suite/perfschema/include/socket_check1.inc
share/mysql/test/suite/perfschema/include/socket_event.inc
share/mysql/test/suite/perfschema/include/socket_event_dbg.inc
share/mysql/test/suite/perfschema/include/socket_ipv6.inc
share/mysql/test/suite/perfschema/include/socket_summary_check.inc
share/mysql/test/suite/perfschema/include/socket_summary_check_dbg.inc
share/mysql/test/suite/perfschema/include/stage_cleanup.inc
share/mysql/test/suite/perfschema/include/stage_setup.inc
share/mysql/test/suite/perfschema/include/start_server_common.inc
share/mysql/test/suite/perfschema/include/table_aggregate_cleanup.inc
share/mysql/test/suite/perfschema/include/table_aggregate_load.inc
share/mysql/test/suite/perfschema/include/table_aggregate_setup.inc
share/mysql/test/suite/perfschema/include/table_io_basic_dml.inc
share/mysql/test/suite/perfschema/include/table_io_cleanup_helper.inc
share/mysql/test/suite/perfschema/include/table_io_result_helper.inc
share/mysql/test/suite/perfschema/include/table_io_setup_helper.inc
share/mysql/test/suite/perfschema/include/upgrade_check.inc
share/mysql/test/suite/perfschema/include/wait_for_pfs_thread_count.inc
share/mysql/test/suite/perfschema/include/wait_till_sleep.inc
share/mysql/test/suite/perfschema/r/aggregate.result
share/mysql/test/suite/perfschema/r/all_tests.result
share/mysql/test/suite/perfschema/r/bad_option_1.result
share/mysql/test/suite/perfschema/r/bad_option_2.result
share/mysql/test/suite/perfschema/r/bad_option_3.result
share/mysql/test/suite/perfschema/r/bad_option_4.result
share/mysql/test/suite/perfschema/r/bad_option_5.result
share/mysql/test/suite/perfschema/r/binlog_edge_mix.result
share/mysql/test/suite/perfschema/r/binlog_edge_row.result
share/mysql/test/suite/perfschema/r/binlog_edge_stmt.result
share/mysql/test/suite/perfschema/r/binlog_ok_mix.result
share/mysql/test/suite/perfschema/r/binlog_ok_row.result
share/mysql/test/suite/perfschema/r/binlog_ok_stmt.result
share/mysql/test/suite/perfschema/r/checksum.result
share/mysql/test/suite/perfschema/r/cnf_option.result
share/mysql/test/suite/perfschema/r/column_privilege.result
share/mysql/test/suite/perfschema/r/connect_attrs.result
share/mysql/test/suite/perfschema/r/connection.result
share/mysql/test/suite/perfschema/r/connection_3a.result
share/mysql/test/suite/perfschema/r/connection_3a_3u.result
share/mysql/test/suite/perfschema/r/connection_3u.result
share/mysql/test/suite/perfschema/r/csv_table_io.result
share/mysql/test/suite/perfschema/r/ddl_accounts.result
share/mysql/test/suite/perfschema/r/ddl_cond_instances.result
share/mysql/test/suite/perfschema/r/ddl_esgs_by_account_by_event_name.result
share/mysql/test/suite/perfschema/r/ddl_esgs_by_host_by_event_name.result
share/mysql/test/suite/perfschema/r/ddl_esgs_by_thread_by_event_name.result
share/mysql/test/suite/perfschema/r/ddl_esgs_by_user_by_event_name.result
share/mysql/test/suite/perfschema/r/ddl_esgs_global_by_event_name.result
share/mysql/test/suite/perfschema/r/ddl_esms_by_account_by_event_name.result
share/mysql/test/suite/perfschema/r/ddl_esms_by_digest.result
share/mysql/test/suite/perfschema/r/ddl_esms_by_host_by_event_name.result
share/mysql/test/suite/perfschema/r/ddl_esms_by_thread_by_event_name.result
share/mysql/test/suite/perfschema/r/ddl_esms_by_user_by_event_name.result
share/mysql/test/suite/perfschema/r/ddl_esms_global_by_event_name.result
share/mysql/test/suite/perfschema/r/ddl_events_stages_current.result
share/mysql/test/suite/perfschema/r/ddl_events_stages_history.result
share/mysql/test/suite/perfschema/r/ddl_events_stages_history_long.result
share/mysql/test/suite/perfschema/r/ddl_events_statements_current.result
share/mysql/test/suite/perfschema/r/ddl_events_statements_history.result
share/mysql/test/suite/perfschema/r/ddl_events_statements_history_long.result
share/mysql/test/suite/perfschema/r/ddl_events_waits_current.result
share/mysql/test/suite/perfschema/r/ddl_events_waits_history.result
share/mysql/test/suite/perfschema/r/ddl_events_waits_history_long.result
share/mysql/test/suite/perfschema/r/ddl_ews_by_account_by_event_name.result
share/mysql/test/suite/perfschema/r/ddl_ews_by_host_by_event_name.result
share/mysql/test/suite/perfschema/r/ddl_ews_by_instance.result
share/mysql/test/suite/perfschema/r/ddl_ews_by_thread_by_event_name.result
share/mysql/test/suite/perfschema/r/ddl_ews_by_user_by_event_name.result
share/mysql/test/suite/perfschema/r/ddl_ews_global_by_event_name.result
share/mysql/test/suite/perfschema/r/ddl_file_instances.result
share/mysql/test/suite/perfschema/r/ddl_fs_by_event_name.result
share/mysql/test/suite/perfschema/r/ddl_fs_by_instance.result
share/mysql/test/suite/perfschema/r/ddl_host_cache.result
share/mysql/test/suite/perfschema/r/ddl_hosts.result
share/mysql/test/suite/perfschema/r/ddl_mutex_instances.result
share/mysql/test/suite/perfschema/r/ddl_os_global_by_type.result
share/mysql/test/suite/perfschema/r/ddl_performance_timers.result
share/mysql/test/suite/perfschema/r/ddl_rwlock_instances.result
share/mysql/test/suite/perfschema/r/ddl_session_account_connect_attrs.result
share/mysql/test/suite/perfschema/r/ddl_session_connect_attrs.result
share/mysql/test/suite/perfschema/r/ddl_setup_actors.result
share/mysql/test/suite/perfschema/r/ddl_setup_consumers.result
share/mysql/test/suite/perfschema/r/ddl_setup_instruments.result
share/mysql/test/suite/perfschema/r/ddl_setup_objects.result
share/mysql/test/suite/perfschema/r/ddl_setup_timers.result
share/mysql/test/suite/perfschema/r/ddl_socket_instances.result
share/mysql/test/suite/perfschema/r/ddl_socket_summary_by_event_name.result
share/mysql/test/suite/perfschema/r/ddl_socket_summary_by_instance.result
share/mysql/test/suite/perfschema/r/ddl_threads.result
share/mysql/test/suite/perfschema/r/ddl_tiws_by_index_usage.result
share/mysql/test/suite/perfschema/r/ddl_tiws_by_table.result
share/mysql/test/suite/perfschema/r/ddl_tlws_by_table.result
share/mysql/test/suite/perfschema/r/ddl_users.result
Changes 5.6.24: * CMake support was updated to handle CMake version 3.1. * The server now includes its version number when it writes the initial “starting” message to the error log, to make it easier to tell which server instance error log output applies to. This value is the same as that available from the version system variable. * ALTER TABLE did not take advantage of fast alterations that might otherwise apply to the operation to be performed, if the table contained temporal columns found to be in pre-5.6.4 format (TIME, DATETIME, and TIMESTAMP columns without support for fractional seconds precision). * Statement digesting as done previously by the Performance Schema is now done at the SQL level regardless of whether the Performance Schema is compiled in and is available to other aspects of server operation that could benefit from it. The default space available for digesting is 1024 bytes, but can be changed at server startup using the max_digest_length system variable. * Bug fixes.
2015-04-08 12:38:48 +02:00
share/mysql/test/suite/perfschema/r/digest_null_literal.result
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/perfschema/r/digest_table_full.result
share/mysql/test/suite/perfschema/r/dml_accounts.result
share/mysql/test/suite/perfschema/r/dml_cond_instances.result
share/mysql/test/suite/perfschema/r/dml_esgs_by_account_by_event_name.result
share/mysql/test/suite/perfschema/r/dml_esgs_by_host_by_event_name.result
share/mysql/test/suite/perfschema/r/dml_esgs_by_thread_by_event_name.result
share/mysql/test/suite/perfschema/r/dml_esgs_by_user_by_event_name.result
share/mysql/test/suite/perfschema/r/dml_esgs_global_by_event_name.result
share/mysql/test/suite/perfschema/r/dml_esms_by_account_by_event_name.result
share/mysql/test/suite/perfschema/r/dml_esms_by_digest.result
share/mysql/test/suite/perfschema/r/dml_esms_by_host_by_event_name.result
share/mysql/test/suite/perfschema/r/dml_esms_by_thread_by_event_name.result
share/mysql/test/suite/perfschema/r/dml_esms_by_user_by_event_name.result
share/mysql/test/suite/perfschema/r/dml_esms_global_by_event_name.result
share/mysql/test/suite/perfschema/r/dml_events_stages_current.result
share/mysql/test/suite/perfschema/r/dml_events_stages_history.result
share/mysql/test/suite/perfschema/r/dml_events_stages_history_long.result
share/mysql/test/suite/perfschema/r/dml_events_statements_current.result
share/mysql/test/suite/perfschema/r/dml_events_statements_history.result
share/mysql/test/suite/perfschema/r/dml_events_statements_history_long.result
share/mysql/test/suite/perfschema/r/dml_events_waits_current.result
share/mysql/test/suite/perfschema/r/dml_events_waits_history.result
share/mysql/test/suite/perfschema/r/dml_events_waits_history_long.result
share/mysql/test/suite/perfschema/r/dml_ews_by_account_by_event_name.result
share/mysql/test/suite/perfschema/r/dml_ews_by_host_by_event_name.result
share/mysql/test/suite/perfschema/r/dml_ews_by_instance.result
share/mysql/test/suite/perfschema/r/dml_ews_by_thread_by_event_name.result
share/mysql/test/suite/perfschema/r/dml_ews_by_user_by_event_name.result
share/mysql/test/suite/perfschema/r/dml_ews_global_by_event_name.result
share/mysql/test/suite/perfschema/r/dml_file_instances.result
share/mysql/test/suite/perfschema/r/dml_fs_by_event_name.result
share/mysql/test/suite/perfschema/r/dml_fs_by_instance.result
share/mysql/test/suite/perfschema/r/dml_handler.result
share/mysql/test/suite/perfschema/r/dml_host_cache.result
share/mysql/test/suite/perfschema/r/dml_hosts.result
share/mysql/test/suite/perfschema/r/dml_mutex_instances.result
share/mysql/test/suite/perfschema/r/dml_os_global_by_type.result
share/mysql/test/suite/perfschema/r/dml_performance_timers.result
share/mysql/test/suite/perfschema/r/dml_rwlock_instances.result
share/mysql/test/suite/perfschema/r/dml_session_account_connect_attrs.result
share/mysql/test/suite/perfschema/r/dml_session_connect_attrs.result
share/mysql/test/suite/perfschema/r/dml_setup_actors.result
share/mysql/test/suite/perfschema/r/dml_setup_consumers.result
share/mysql/test/suite/perfschema/r/dml_setup_instruments.result
share/mysql/test/suite/perfschema/r/dml_setup_objects.result
share/mysql/test/suite/perfschema/r/dml_setup_timers.result
share/mysql/test/suite/perfschema/r/dml_socket_instances.result
share/mysql/test/suite/perfschema/r/dml_socket_summary_by_event_name.result
share/mysql/test/suite/perfschema/r/dml_socket_summary_by_instance.result
share/mysql/test/suite/perfschema/r/dml_threads.result
share/mysql/test/suite/perfschema/r/dml_tiws_by_index_usage.result
share/mysql/test/suite/perfschema/r/dml_tiws_by_table.result
share/mysql/test/suite/perfschema/r/dml_tlws_by_table.result
share/mysql/test/suite/perfschema/r/dml_users.result
share/mysql/test/suite/perfschema/r/event_aggregate.result
share/mysql/test/suite/perfschema/r/event_aggregate_no_a.result
share/mysql/test/suite/perfschema/r/event_aggregate_no_a_no_h.result
share/mysql/test/suite/perfschema/r/event_aggregate_no_a_no_u.result
share/mysql/test/suite/perfschema/r/event_aggregate_no_a_no_u_no_h.result
share/mysql/test/suite/perfschema/r/event_aggregate_no_h.result
share/mysql/test/suite/perfschema/r/event_aggregate_no_u.result
share/mysql/test/suite/perfschema/r/event_aggregate_no_u_no_h.result
share/mysql/test/suite/perfschema/r/func_file_io.result
share/mysql/test/suite/perfschema/r/func_mutex.result
share/mysql/test/suite/perfschema/r/global_read_lock.result
share/mysql/test/suite/perfschema/r/hostcache_ipv4_addrinfo_again_allow.result
share/mysql/test/suite/perfschema/r/hostcache_ipv4_addrinfo_again_deny.result
share/mysql/test/suite/perfschema/r/hostcache_ipv4_addrinfo_bad_allow.result
share/mysql/test/suite/perfschema/r/hostcache_ipv4_addrinfo_bad_deny.result
share/mysql/test/suite/perfschema/r/hostcache_ipv4_addrinfo_good_allow.result
share/mysql/test/suite/perfschema/r/hostcache_ipv4_addrinfo_good_deny.result
share/mysql/test/suite/perfschema/r/hostcache_ipv4_addrinfo_noname_allow.result
share/mysql/test/suite/perfschema/r/hostcache_ipv4_addrinfo_noname_deny.result
share/mysql/test/suite/perfschema/r/hostcache_ipv4_auth_plugin.result
share/mysql/test/suite/perfschema/r/hostcache_ipv4_blocked.result
share/mysql/test/suite/perfschema/r/hostcache_ipv4_format.result
share/mysql/test/suite/perfschema/r/hostcache_ipv4_max_con.result
share/mysql/test/suite/perfschema/r/hostcache_ipv4_nameinfo_again_allow.result
share/mysql/test/suite/perfschema/r/hostcache_ipv4_nameinfo_again_deny.result
share/mysql/test/suite/perfschema/r/hostcache_ipv4_nameinfo_noname_allow.result
share/mysql/test/suite/perfschema/r/hostcache_ipv4_nameinfo_noname_deny.result
share/mysql/test/suite/perfschema/r/hostcache_ipv4_passwd.result
share/mysql/test/suite/perfschema/r/hostcache_ipv4_ssl.result
share/mysql/test/suite/perfschema/r/hostcache_ipv6_addrinfo_again_allow.result
share/mysql/test/suite/perfschema/r/hostcache_ipv6_addrinfo_again_deny.result
share/mysql/test/suite/perfschema/r/hostcache_ipv6_addrinfo_bad_allow.result
share/mysql/test/suite/perfschema/r/hostcache_ipv6_addrinfo_bad_deny.result
share/mysql/test/suite/perfschema/r/hostcache_ipv6_addrinfo_good_allow.result
share/mysql/test/suite/perfschema/r/hostcache_ipv6_addrinfo_good_deny.result
share/mysql/test/suite/perfschema/r/hostcache_ipv6_addrinfo_noname_allow.result
share/mysql/test/suite/perfschema/r/hostcache_ipv6_addrinfo_noname_deny.result
share/mysql/test/suite/perfschema/r/hostcache_ipv6_auth_plugin.result
share/mysql/test/suite/perfschema/r/hostcache_ipv6_blocked.result
share/mysql/test/suite/perfschema/r/hostcache_ipv6_max_con.result
share/mysql/test/suite/perfschema/r/hostcache_ipv6_nameinfo_again_allow.result
share/mysql/test/suite/perfschema/r/hostcache_ipv6_nameinfo_again_deny.result
share/mysql/test/suite/perfschema/r/hostcache_ipv6_nameinfo_noname_allow.result
share/mysql/test/suite/perfschema/r/hostcache_ipv6_nameinfo_noname_deny.result
share/mysql/test/suite/perfschema/r/hostcache_ipv6_passwd.result
share/mysql/test/suite/perfschema/r/hostcache_ipv6_ssl.result
share/mysql/test/suite/perfschema/r/hostcache_peer_addr.result
share/mysql/test/suite/perfschema/r/indexed_table_io.result
share/mysql/test/suite/perfschema/r/information_schema.result
share/mysql/test/suite/perfschema/r/innodb_table_io.result
share/mysql/test/suite/perfschema/r/memory_table_io.result
share/mysql/test/suite/perfschema/r/merge_table_io.result
share/mysql/test/suite/perfschema/r/misc.result
share/mysql/test/suite/perfschema/r/multi_table_io.result
share/mysql/test/suite/perfschema/r/myisam_file_io.result
share/mysql/test/suite/perfschema/r/myisam_table_io.result
share/mysql/test/suite/perfschema/r/nesting.result
share/mysql/test/suite/perfschema/r/no_threads.result
share/mysql/test/suite/perfschema/r/one_thread_per_con.result
share/mysql/test/suite/perfschema/r/ortho_iter.result
share/mysql/test/suite/perfschema/r/part_table_io.result
share/mysql/test/suite/perfschema/r/pfs_upgrade_event.result
share/mysql/test/suite/perfschema/r/pfs_upgrade_func.result
share/mysql/test/suite/perfschema/r/pfs_upgrade_proc.result
share/mysql/test/suite/perfschema/r/pfs_upgrade_table.result
share/mysql/test/suite/perfschema/r/pfs_upgrade_view.result
share/mysql/test/suite/perfschema/r/privilege.result
share/mysql/test/suite/perfschema/r/privilege_table_io.result
share/mysql/test/suite/perfschema/r/query_cache.result
share/mysql/test/suite/perfschema/r/read_only.result
share/mysql/test/suite/perfschema/r/relaylog.result
share/mysql/test/suite/perfschema/r/rollback_table_io.result
share/mysql/test/suite/perfschema/r/rpl_gtid_func.result
Changes 5.6.13: * Important Change; Replication: By default, when promoting integers from a smaller type on the master to a larger type on the slave (for example, from a SMALLINT column on the master to a BIGINT column on the slave), the promoted values are treated as though they are signed. Now in such cases it is possible to modify or override this behavior using one or both of ALL_SIGNED, ALL_UNSIGNED in the set of values specified for the slave_type_conversions server system variable. For more information, see Row-based replication: attribute promotion and demotion, as well as the description of the variable. * Previously, program options could be specified in full or as any unambiguous prefix. For example, the --compress option could be given to mysqldump as --compr, but not as --comp because the latter is ambiguous. Option prefixes now are deprecated. They can cause problems when new options are implemented for programs. A prefix that is currently unambiguous might become ambiguous in the future. If an unambiguous prefix is given, a warning now occurs to provide feedback. For example: Warning: Using unique option prefix compr instead of compress is deprecated and will be removed in a future release. Please use the full name instead. Option prefixes are no longer supported in MySQL 5.7; only full options are accepted. * The C API libmysqlclient shared-library .so files now have version 18.1.0 (up from version 18.0.0 used in MySQL 5.5). * In batch mode, mysql formatted result status messages such as “"Query OK, 1 row affected"” but did not print them. Now these messages are not formatted. * Bugs Fixed
2013-07-31 11:51:38 +02:00
share/mysql/test/suite/perfschema/r/rpl_statements.result
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/perfschema/r/schema.result
share/mysql/test/suite/perfschema/r/selects.result
share/mysql/test/suite/perfschema/r/server_init.result
share/mysql/test/suite/perfschema/r/setup_actors.result
share/mysql/test/suite/perfschema/r/setup_consumers_defaults.result
share/mysql/test/suite/perfschema/r/setup_instruments_defaults.result
share/mysql/test/suite/perfschema/r/setup_objects.result
share/mysql/test/suite/perfschema/r/short_option_1.result
share/mysql/test/suite/perfschema/r/short_option_2.result
share/mysql/test/suite/perfschema/r/sizing_default.result
share/mysql/test/suite/perfschema/r/sizing_growth.result
share/mysql/test/suite/perfschema/r/sizing_high.result
share/mysql/test/suite/perfschema/r/sizing_low.result
share/mysql/test/suite/perfschema/r/sizing_med.result
share/mysql/test/suite/perfschema/r/sizing_off.result
share/mysql/test/suite/perfschema/r/socket_connect.result
share/mysql/test/suite/perfschema/r/socket_instances_func.result
share/mysql/test/suite/perfschema/r/socket_instances_func_win.result
share/mysql/test/suite/perfschema/r/socket_summary_by_event_name_func.result
share/mysql/test/suite/perfschema/r/socket_summary_by_instance_func.result
share/mysql/test/suite/perfschema/r/socket_summary_by_instance_func_win.result
share/mysql/test/suite/perfschema/r/stage_mdl_function.result
share/mysql/test/suite/perfschema/r/stage_mdl_global.result
share/mysql/test/suite/perfschema/r/stage_mdl_procedure.result
share/mysql/test/suite/perfschema/r/stage_mdl_table.result
share/mysql/test/suite/perfschema/r/start_server_disable_idle.result
share/mysql/test/suite/perfschema/r/start_server_disable_stages.result
share/mysql/test/suite/perfschema/r/start_server_disable_statements.result
share/mysql/test/suite/perfschema/r/start_server_disable_waits.result
share/mysql/test/suite/perfschema/r/start_server_innodb.result
Changes 5.6.24: * CMake support was updated to handle CMake version 3.1. * The server now includes its version number when it writes the initial “starting” message to the error log, to make it easier to tell which server instance error log output applies to. This value is the same as that available from the version system variable. * ALTER TABLE did not take advantage of fast alterations that might otherwise apply to the operation to be performed, if the table contained temporal columns found to be in pre-5.6.4 format (TIME, DATETIME, and TIMESTAMP columns without support for fractional seconds precision). * Statement digesting as done previously by the Performance Schema is now done at the SQL level regardless of whether the Performance Schema is compiled in and is available to other aspects of server operation that could benefit from it. The default space available for digesting is 1024 bytes, but can be changed at server startup using the max_digest_length system variable. * Bug fixes.
2015-04-08 12:38:48 +02:00
share/mysql/test/suite/perfschema/r/start_server_low_digest.result
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/perfschema/r/start_server_no_account.result
share/mysql/test/suite/perfschema/r/start_server_no_cond_class.result
share/mysql/test/suite/perfschema/r/start_server_no_cond_inst.result
share/mysql/test/suite/perfschema/r/start_server_no_digests.result
share/mysql/test/suite/perfschema/r/start_server_no_file_class.result
share/mysql/test/suite/perfschema/r/start_server_no_file_inst.result
share/mysql/test/suite/perfschema/r/start_server_no_host.result
share/mysql/test/suite/perfschema/r/start_server_no_mutex_class.result
share/mysql/test/suite/perfschema/r/start_server_no_mutex_inst.result
share/mysql/test/suite/perfschema/r/start_server_no_rwlock_class.result
share/mysql/test/suite/perfschema/r/start_server_no_rwlock_inst.result
share/mysql/test/suite/perfschema/r/start_server_no_setup_actors.result
share/mysql/test/suite/perfschema/r/start_server_no_setup_objects.result
share/mysql/test/suite/perfschema/r/start_server_no_socket_class.result
share/mysql/test/suite/perfschema/r/start_server_no_socket_inst.result
share/mysql/test/suite/perfschema/r/start_server_no_stage_class.result
share/mysql/test/suite/perfschema/r/start_server_no_stages_history.result
share/mysql/test/suite/perfschema/r/start_server_no_stages_history_long.result
share/mysql/test/suite/perfschema/r/start_server_no_statement_class.result
share/mysql/test/suite/perfschema/r/start_server_no_statements_history.result
share/mysql/test/suite/perfschema/r/start_server_no_statements_history_long.result
share/mysql/test/suite/perfschema/r/start_server_no_table_hdl.result
share/mysql/test/suite/perfschema/r/start_server_no_table_inst.result
share/mysql/test/suite/perfschema/r/start_server_no_thread_class.result
share/mysql/test/suite/perfschema/r/start_server_no_thread_inst.result
share/mysql/test/suite/perfschema/r/start_server_no_user.result
share/mysql/test/suite/perfschema/r/start_server_no_waits_history.result
share/mysql/test/suite/perfschema/r/start_server_no_waits_history_long.result
share/mysql/test/suite/perfschema/r/start_server_nothing.result
share/mysql/test/suite/perfschema/r/start_server_off.result
share/mysql/test/suite/perfschema/r/start_server_on.result
share/mysql/test/suite/perfschema/r/statement_digest.result
share/mysql/test/suite/perfschema/r/statement_digest_charset.result
share/mysql/test/suite/perfschema/r/statement_digest_consumers.result
share/mysql/test/suite/perfschema/r/statement_digest_consumers2.result
share/mysql/test/suite/perfschema/r/statement_digest_long_query.result
share/mysql/test/suite/perfschema/r/table_aggregate_global_2u_2t.result
share/mysql/test/suite/perfschema/r/table_aggregate_global_2u_3t.result
share/mysql/test/suite/perfschema/r/table_aggregate_global_4u_2t.result
share/mysql/test/suite/perfschema/r/table_aggregate_global_4u_3t.result
share/mysql/test/suite/perfschema/r/table_aggregate_hist_2u_2t.result
share/mysql/test/suite/perfschema/r/table_aggregate_hist_2u_3t.result
share/mysql/test/suite/perfschema/r/table_aggregate_hist_4u_2t.result
share/mysql/test/suite/perfschema/r/table_aggregate_hist_4u_3t.result
share/mysql/test/suite/perfschema/r/table_aggregate_off.result
share/mysql/test/suite/perfschema/r/table_aggregate_thread_2u_2t.result
share/mysql/test/suite/perfschema/r/table_aggregate_thread_2u_3t.result
share/mysql/test/suite/perfschema/r/table_aggregate_thread_4u_2t.result
share/mysql/test/suite/perfschema/r/table_aggregate_thread_4u_3t.result
share/mysql/test/suite/perfschema/r/table_io_aggregate_global_2u_2t.result
share/mysql/test/suite/perfschema/r/table_io_aggregate_global_2u_3t.result
share/mysql/test/suite/perfschema/r/table_io_aggregate_global_4u_2t.result
share/mysql/test/suite/perfschema/r/table_io_aggregate_global_4u_3t.result
share/mysql/test/suite/perfschema/r/table_io_aggregate_hist_2u_2t.result
share/mysql/test/suite/perfschema/r/table_io_aggregate_hist_2u_3t.result
share/mysql/test/suite/perfschema/r/table_io_aggregate_hist_4u_2t.result
share/mysql/test/suite/perfschema/r/table_io_aggregate_hist_4u_3t.result
share/mysql/test/suite/perfschema/r/table_io_aggregate_thread_2u_2t.result
share/mysql/test/suite/perfschema/r/table_io_aggregate_thread_2u_3t.result
share/mysql/test/suite/perfschema/r/table_io_aggregate_thread_4u_2t.result
share/mysql/test/suite/perfschema/r/table_io_aggregate_thread_4u_3t.result
share/mysql/test/suite/perfschema/r/table_lock_aggregate_global_2u_2t.result
share/mysql/test/suite/perfschema/r/table_lock_aggregate_global_2u_3t.result
share/mysql/test/suite/perfschema/r/table_lock_aggregate_global_4u_2t.result
share/mysql/test/suite/perfschema/r/table_lock_aggregate_global_4u_3t.result
share/mysql/test/suite/perfschema/r/table_lock_aggregate_hist_2u_2t.result
share/mysql/test/suite/perfschema/r/table_lock_aggregate_hist_2u_3t.result
share/mysql/test/suite/perfschema/r/table_lock_aggregate_hist_4u_2t.result
share/mysql/test/suite/perfschema/r/table_lock_aggregate_hist_4u_3t.result
share/mysql/test/suite/perfschema/r/table_lock_aggregate_thread_2u_2t.result
share/mysql/test/suite/perfschema/r/table_lock_aggregate_thread_2u_3t.result
share/mysql/test/suite/perfschema/r/table_lock_aggregate_thread_4u_2t.result
share/mysql/test/suite/perfschema/r/table_lock_aggregate_thread_4u_3t.result
share/mysql/test/suite/perfschema/r/table_schema.result
share/mysql/test/suite/perfschema/r/tampered_perfschema_table1.result
share/mysql/test/suite/perfschema/r/temp_table_io.result
share/mysql/test/suite/perfschema/r/thread_cache.result
share/mysql/test/suite/perfschema/r/threads_innodb.result
share/mysql/test/suite/perfschema/r/threads_insert_delayed.result
share/mysql/test/suite/perfschema/r/threads_mysql.result
share/mysql/test/suite/perfschema/r/trigger_table_io.result
Changes 5.6.22: * Noisy compiler warnings on FreeBSD 10 were silenced. * CMake workarounds for older Mac OS X and XCode versions were removed. On Mac OS X, compilation always uses Clang, even for 32-bit builds. * Previously, the MYSQL_MAINTAINER_MODE CMake option was turned on by default for debug builds and off for release builds, and MYSQL_MAINTAINER_MODE caused -Werror to be enabled when building with GCC. This made it cumbersome to enable -Werror under certain conditions, such as when compiling with Clang. * Build support was modified to produce the same warnings for Clang as for gcc. * CMake configuration for the Clang compiler sets more appropriate flags for building on Linux. Specifically, -g -fno-omit-frame-pointer -fno-strict-aliasing is now added. * Bugs fixed.
2014-12-02 13:40:09 +01:00
share/mysql/test/suite/perfschema/r/unary_digest.result
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/perfschema/r/view_table_io.result
share/mysql/test/suite/perfschema/t/aggregate.test
share/mysql/test/suite/perfschema/t/all_tests.test
share/mysql/test/suite/perfschema/t/bad_option_1.test
share/mysql/test/suite/perfschema/t/bad_option_2.test
share/mysql/test/suite/perfschema/t/bad_option_3.test
share/mysql/test/suite/perfschema/t/bad_option_4.test
share/mysql/test/suite/perfschema/t/bad_option_5.test
share/mysql/test/suite/perfschema/t/binlog_edge_mix-master.opt
share/mysql/test/suite/perfschema/t/binlog_edge_mix.test
share/mysql/test/suite/perfschema/t/binlog_edge_row-master.opt
share/mysql/test/suite/perfschema/t/binlog_edge_row.test
share/mysql/test/suite/perfschema/t/binlog_edge_stmt-master.opt
share/mysql/test/suite/perfschema/t/binlog_edge_stmt.test
share/mysql/test/suite/perfschema/t/binlog_ok_mix-master.opt
share/mysql/test/suite/perfschema/t/binlog_ok_mix.test
share/mysql/test/suite/perfschema/t/binlog_ok_row-master.opt
share/mysql/test/suite/perfschema/t/binlog_ok_row.test
share/mysql/test/suite/perfschema/t/binlog_ok_stmt-master.opt
share/mysql/test/suite/perfschema/t/binlog_ok_stmt.test
share/mysql/test/suite/perfschema/t/checksum.test
share/mysql/test/suite/perfschema/t/cnf_option.cnf
share/mysql/test/suite/perfschema/t/cnf_option.test
share/mysql/test/suite/perfschema/t/column_privilege.test
share/mysql/test/suite/perfschema/t/connect_attrs.test
share/mysql/test/suite/perfschema/t/connection.test
share/mysql/test/suite/perfschema/t/connection_3a-master.opt
share/mysql/test/suite/perfschema/t/connection_3a.test
share/mysql/test/suite/perfschema/t/connection_3a_3u-master.opt
share/mysql/test/suite/perfschema/t/connection_3a_3u.test
share/mysql/test/suite/perfschema/t/connection_3u-master.opt
share/mysql/test/suite/perfschema/t/connection_3u.test
share/mysql/test/suite/perfschema/t/csv_table_io.test
share/mysql/test/suite/perfschema/t/ddl_accounts.test
share/mysql/test/suite/perfschema/t/ddl_cond_instances.test
share/mysql/test/suite/perfschema/t/ddl_esgs_by_account_by_event_name.test
share/mysql/test/suite/perfschema/t/ddl_esgs_by_host_by_event_name.test
share/mysql/test/suite/perfschema/t/ddl_esgs_by_thread_by_event_name.test
share/mysql/test/suite/perfschema/t/ddl_esgs_by_user_by_event_name.test
share/mysql/test/suite/perfschema/t/ddl_esgs_global_by_event_name.test
share/mysql/test/suite/perfschema/t/ddl_esms_by_account_by_event_name.test
share/mysql/test/suite/perfschema/t/ddl_esms_by_digest.test
share/mysql/test/suite/perfschema/t/ddl_esms_by_host_by_event_name.test
share/mysql/test/suite/perfschema/t/ddl_esms_by_thread_by_event_name.test
share/mysql/test/suite/perfschema/t/ddl_esms_by_user_by_event_name.test
share/mysql/test/suite/perfschema/t/ddl_esms_global_by_event_name.test
share/mysql/test/suite/perfschema/t/ddl_events_stages_current.test
share/mysql/test/suite/perfschema/t/ddl_events_stages_history.test
share/mysql/test/suite/perfschema/t/ddl_events_stages_history_long.test
share/mysql/test/suite/perfschema/t/ddl_events_statements_current.test
share/mysql/test/suite/perfschema/t/ddl_events_statements_history.test
share/mysql/test/suite/perfschema/t/ddl_events_statements_history_long.test
share/mysql/test/suite/perfschema/t/ddl_events_waits_current.test
share/mysql/test/suite/perfschema/t/ddl_events_waits_history.test
share/mysql/test/suite/perfschema/t/ddl_events_waits_history_long.test
share/mysql/test/suite/perfschema/t/ddl_ews_by_account_by_event_name.test
share/mysql/test/suite/perfschema/t/ddl_ews_by_host_by_event_name.test
share/mysql/test/suite/perfschema/t/ddl_ews_by_instance.test
share/mysql/test/suite/perfschema/t/ddl_ews_by_thread_by_event_name.test
share/mysql/test/suite/perfschema/t/ddl_ews_by_user_by_event_name.test
share/mysql/test/suite/perfschema/t/ddl_ews_global_by_event_name.test
share/mysql/test/suite/perfschema/t/ddl_file_instances.test
share/mysql/test/suite/perfschema/t/ddl_fs_by_event_name.test
share/mysql/test/suite/perfschema/t/ddl_fs_by_instance.test
share/mysql/test/suite/perfschema/t/ddl_host_cache.test
share/mysql/test/suite/perfschema/t/ddl_hosts.test
share/mysql/test/suite/perfschema/t/ddl_mutex_instances.test
share/mysql/test/suite/perfschema/t/ddl_os_global_by_type.test
share/mysql/test/suite/perfschema/t/ddl_performance_timers.test
share/mysql/test/suite/perfschema/t/ddl_rwlock_instances.test
share/mysql/test/suite/perfschema/t/ddl_session_account_connect_attrs.test
share/mysql/test/suite/perfschema/t/ddl_session_connect_attrs.test
share/mysql/test/suite/perfschema/t/ddl_setup_actors.test
share/mysql/test/suite/perfschema/t/ddl_setup_consumers.test
share/mysql/test/suite/perfschema/t/ddl_setup_instruments.test
share/mysql/test/suite/perfschema/t/ddl_setup_objects.test
share/mysql/test/suite/perfschema/t/ddl_setup_timers.test
share/mysql/test/suite/perfschema/t/ddl_socket_instances.test
share/mysql/test/suite/perfschema/t/ddl_socket_summary_by_event_name.test
share/mysql/test/suite/perfschema/t/ddl_socket_summary_by_instance.test
share/mysql/test/suite/perfschema/t/ddl_threads.test
share/mysql/test/suite/perfschema/t/ddl_tiws_by_index_usage.test
share/mysql/test/suite/perfschema/t/ddl_tiws_by_table.test
share/mysql/test/suite/perfschema/t/ddl_tlws_by_table.test
share/mysql/test/suite/perfschema/t/ddl_users.test
Changes 5.6.24: * CMake support was updated to handle CMake version 3.1. * The server now includes its version number when it writes the initial “starting” message to the error log, to make it easier to tell which server instance error log output applies to. This value is the same as that available from the version system variable. * ALTER TABLE did not take advantage of fast alterations that might otherwise apply to the operation to be performed, if the table contained temporal columns found to be in pre-5.6.4 format (TIME, DATETIME, and TIMESTAMP columns without support for fractional seconds precision). * Statement digesting as done previously by the Performance Schema is now done at the SQL level regardless of whether the Performance Schema is compiled in and is available to other aspects of server operation that could benefit from it. The default space available for digesting is 1024 bytes, but can be changed at server startup using the max_digest_length system variable. * Bug fixes.
2015-04-08 12:38:48 +02:00
share/mysql/test/suite/perfschema/t/digest_null_literal.test
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/perfschema/t/digest_table_full-master.opt
share/mysql/test/suite/perfschema/t/digest_table_full.test
share/mysql/test/suite/perfschema/t/disabled.def
share/mysql/test/suite/perfschema/t/dml_accounts.test
share/mysql/test/suite/perfschema/t/dml_cond_instances.test
share/mysql/test/suite/perfschema/t/dml_esgs_by_account_by_event_name.test
share/mysql/test/suite/perfschema/t/dml_esgs_by_host_by_event_name.test
share/mysql/test/suite/perfschema/t/dml_esgs_by_thread_by_event_name.test
share/mysql/test/suite/perfschema/t/dml_esgs_by_user_by_event_name.test
share/mysql/test/suite/perfschema/t/dml_esgs_global_by_event_name.test
share/mysql/test/suite/perfschema/t/dml_esms_by_account_by_event_name.test
share/mysql/test/suite/perfschema/t/dml_esms_by_digest.test
share/mysql/test/suite/perfschema/t/dml_esms_by_host_by_event_name.test
share/mysql/test/suite/perfschema/t/dml_esms_by_thread_by_event_name.test
share/mysql/test/suite/perfschema/t/dml_esms_by_user_by_event_name.test
share/mysql/test/suite/perfschema/t/dml_esms_global_by_event_name.test
share/mysql/test/suite/perfschema/t/dml_events_stages_current.test
share/mysql/test/suite/perfschema/t/dml_events_stages_history.test
share/mysql/test/suite/perfschema/t/dml_events_stages_history_long.test
share/mysql/test/suite/perfschema/t/dml_events_statements_current.test
share/mysql/test/suite/perfschema/t/dml_events_statements_history.test
share/mysql/test/suite/perfschema/t/dml_events_statements_history_long.test
share/mysql/test/suite/perfschema/t/dml_events_waits_current.test
share/mysql/test/suite/perfschema/t/dml_events_waits_history.test
share/mysql/test/suite/perfschema/t/dml_events_waits_history_long.test
share/mysql/test/suite/perfschema/t/dml_ews_by_account_by_event_name.test
share/mysql/test/suite/perfschema/t/dml_ews_by_host_by_event_name.test
share/mysql/test/suite/perfschema/t/dml_ews_by_instance.test
share/mysql/test/suite/perfschema/t/dml_ews_by_thread_by_event_name.test
share/mysql/test/suite/perfschema/t/dml_ews_by_user_by_event_name.test
share/mysql/test/suite/perfschema/t/dml_ews_global_by_event_name.test
share/mysql/test/suite/perfschema/t/dml_file_instances.test
share/mysql/test/suite/perfschema/t/dml_fs_by_event_name.test
share/mysql/test/suite/perfschema/t/dml_fs_by_instance.test
share/mysql/test/suite/perfschema/t/dml_handler.test
share/mysql/test/suite/perfschema/t/dml_host_cache.test
share/mysql/test/suite/perfschema/t/dml_hosts.test
share/mysql/test/suite/perfschema/t/dml_mutex_instances.test
share/mysql/test/suite/perfschema/t/dml_os_global_by_type.test
share/mysql/test/suite/perfschema/t/dml_performance_timers.test
share/mysql/test/suite/perfschema/t/dml_rwlock_instances.test
share/mysql/test/suite/perfschema/t/dml_session_account_connect_attrs.test
share/mysql/test/suite/perfschema/t/dml_session_connect_attrs.test
share/mysql/test/suite/perfschema/t/dml_setup_actors.test
share/mysql/test/suite/perfschema/t/dml_setup_consumers.test
share/mysql/test/suite/perfschema/t/dml_setup_instruments.test
share/mysql/test/suite/perfschema/t/dml_setup_objects.test
share/mysql/test/suite/perfschema/t/dml_setup_timers.test
share/mysql/test/suite/perfschema/t/dml_socket_instances.test
share/mysql/test/suite/perfschema/t/dml_socket_summary_by_event_name.test
share/mysql/test/suite/perfschema/t/dml_socket_summary_by_instance.test
share/mysql/test/suite/perfschema/t/dml_threads.test
share/mysql/test/suite/perfschema/t/dml_tiws_by_index_usage.test
share/mysql/test/suite/perfschema/t/dml_tiws_by_table.test
share/mysql/test/suite/perfschema/t/dml_tlws_by_table.test
share/mysql/test/suite/perfschema/t/dml_users.test
share/mysql/test/suite/perfschema/t/event_aggregate-master.opt
share/mysql/test/suite/perfschema/t/event_aggregate.test
share/mysql/test/suite/perfschema/t/event_aggregate_no_a-master.opt
share/mysql/test/suite/perfschema/t/event_aggregate_no_a.test
share/mysql/test/suite/perfschema/t/event_aggregate_no_a_no_h-master.opt
share/mysql/test/suite/perfschema/t/event_aggregate_no_a_no_h.test
share/mysql/test/suite/perfschema/t/event_aggregate_no_a_no_u-master.opt
share/mysql/test/suite/perfschema/t/event_aggregate_no_a_no_u.test
share/mysql/test/suite/perfschema/t/event_aggregate_no_a_no_u_no_h-master.opt
share/mysql/test/suite/perfschema/t/event_aggregate_no_a_no_u_no_h.test
share/mysql/test/suite/perfschema/t/event_aggregate_no_h-master.opt
share/mysql/test/suite/perfschema/t/event_aggregate_no_h.test
share/mysql/test/suite/perfschema/t/event_aggregate_no_u-master.opt
share/mysql/test/suite/perfschema/t/event_aggregate_no_u.test
share/mysql/test/suite/perfschema/t/event_aggregate_no_u_no_h-master.opt
share/mysql/test/suite/perfschema/t/event_aggregate_no_u_no_h.test
share/mysql/test/suite/perfschema/t/func_file_io.test
share/mysql/test/suite/perfschema/t/func_mutex.test
share/mysql/test/suite/perfschema/t/global_read_lock.test
share/mysql/test/suite/perfschema/t/hostcache_ipv4_addrinfo_again_allow.test
share/mysql/test/suite/perfschema/t/hostcache_ipv4_addrinfo_again_deny.test
share/mysql/test/suite/perfschema/t/hostcache_ipv4_addrinfo_bad_allow.test
share/mysql/test/suite/perfschema/t/hostcache_ipv4_addrinfo_bad_deny.test
share/mysql/test/suite/perfschema/t/hostcache_ipv4_addrinfo_good_allow.test
share/mysql/test/suite/perfschema/t/hostcache_ipv4_addrinfo_good_deny.test
share/mysql/test/suite/perfschema/t/hostcache_ipv4_addrinfo_noname_allow.test
share/mysql/test/suite/perfschema/t/hostcache_ipv4_addrinfo_noname_deny.test
share/mysql/test/suite/perfschema/t/hostcache_ipv4_auth_plugin-master.opt
share/mysql/test/suite/perfschema/t/hostcache_ipv4_auth_plugin.test
share/mysql/test/suite/perfschema/t/hostcache_ipv4_blocked.test
share/mysql/test/suite/perfschema/t/hostcache_ipv4_format.test
share/mysql/test/suite/perfschema/t/hostcache_ipv4_max_con.test
share/mysql/test/suite/perfschema/t/hostcache_ipv4_nameinfo_again_allow.test
share/mysql/test/suite/perfschema/t/hostcache_ipv4_nameinfo_again_deny.test
share/mysql/test/suite/perfschema/t/hostcache_ipv4_nameinfo_noname_allow.test
share/mysql/test/suite/perfschema/t/hostcache_ipv4_nameinfo_noname_deny.test
share/mysql/test/suite/perfschema/t/hostcache_ipv4_passwd.test
share/mysql/test/suite/perfschema/t/hostcache_ipv4_ssl.test
share/mysql/test/suite/perfschema/t/hostcache_ipv6_addrinfo_again_allow-master.opt
share/mysql/test/suite/perfschema/t/hostcache_ipv6_addrinfo_again_allow.test
share/mysql/test/suite/perfschema/t/hostcache_ipv6_addrinfo_again_deny-master.opt
share/mysql/test/suite/perfschema/t/hostcache_ipv6_addrinfo_again_deny.test
share/mysql/test/suite/perfschema/t/hostcache_ipv6_addrinfo_bad_allow-master.opt
share/mysql/test/suite/perfschema/t/hostcache_ipv6_addrinfo_bad_allow.test
share/mysql/test/suite/perfschema/t/hostcache_ipv6_addrinfo_bad_deny-master.opt
share/mysql/test/suite/perfschema/t/hostcache_ipv6_addrinfo_bad_deny.test
share/mysql/test/suite/perfschema/t/hostcache_ipv6_addrinfo_good_allow-master.opt
share/mysql/test/suite/perfschema/t/hostcache_ipv6_addrinfo_good_allow.test
share/mysql/test/suite/perfschema/t/hostcache_ipv6_addrinfo_good_deny-master.opt
share/mysql/test/suite/perfschema/t/hostcache_ipv6_addrinfo_good_deny.test
share/mysql/test/suite/perfschema/t/hostcache_ipv6_addrinfo_noname_allow-master.opt
share/mysql/test/suite/perfschema/t/hostcache_ipv6_addrinfo_noname_allow.test
share/mysql/test/suite/perfschema/t/hostcache_ipv6_addrinfo_noname_deny-master.opt
share/mysql/test/suite/perfschema/t/hostcache_ipv6_addrinfo_noname_deny.test
share/mysql/test/suite/perfschema/t/hostcache_ipv6_auth_plugin-master.opt
share/mysql/test/suite/perfschema/t/hostcache_ipv6_auth_plugin.test
share/mysql/test/suite/perfschema/t/hostcache_ipv6_blocked-master.opt
share/mysql/test/suite/perfschema/t/hostcache_ipv6_blocked.test
share/mysql/test/suite/perfschema/t/hostcache_ipv6_max_con-master.opt
share/mysql/test/suite/perfschema/t/hostcache_ipv6_max_con.test
share/mysql/test/suite/perfschema/t/hostcache_ipv6_nameinfo_again_allow-master.opt
share/mysql/test/suite/perfschema/t/hostcache_ipv6_nameinfo_again_allow.test
share/mysql/test/suite/perfschema/t/hostcache_ipv6_nameinfo_again_deny-master.opt
share/mysql/test/suite/perfschema/t/hostcache_ipv6_nameinfo_again_deny.test
share/mysql/test/suite/perfschema/t/hostcache_ipv6_nameinfo_noname_allow-master.opt
share/mysql/test/suite/perfschema/t/hostcache_ipv6_nameinfo_noname_allow.test
share/mysql/test/suite/perfschema/t/hostcache_ipv6_nameinfo_noname_deny-master.opt
share/mysql/test/suite/perfschema/t/hostcache_ipv6_nameinfo_noname_deny.test
share/mysql/test/suite/perfschema/t/hostcache_ipv6_passwd-master.opt
share/mysql/test/suite/perfschema/t/hostcache_ipv6_passwd.test
share/mysql/test/suite/perfschema/t/hostcache_ipv6_ssl-master.opt
share/mysql/test/suite/perfschema/t/hostcache_ipv6_ssl.test
share/mysql/test/suite/perfschema/t/hostcache_peer_addr.test
share/mysql/test/suite/perfschema/t/indexed_table_io.test
share/mysql/test/suite/perfschema/t/information_schema.test
share/mysql/test/suite/perfschema/t/innodb_table_io.test
share/mysql/test/suite/perfschema/t/memory_table_io.test
share/mysql/test/suite/perfschema/t/merge_table_io.test
share/mysql/test/suite/perfschema/t/misc.test
share/mysql/test/suite/perfschema/t/multi_table_io.test
share/mysql/test/suite/perfschema/t/myisam_file_io.opt
share/mysql/test/suite/perfschema/t/myisam_file_io.test
share/mysql/test/suite/perfschema/t/myisam_table_io.test
share/mysql/test/suite/perfschema/t/nesting.test
share/mysql/test/suite/perfschema/t/no_threads-master.opt
share/mysql/test/suite/perfschema/t/no_threads.test
share/mysql/test/suite/perfschema/t/one_thread_per_con-master.opt
share/mysql/test/suite/perfschema/t/one_thread_per_con.test
share/mysql/test/suite/perfschema/t/ortho_iter.test
share/mysql/test/suite/perfschema/t/part_table_io.test
share/mysql/test/suite/perfschema/t/pfs_upgrade_event.test
share/mysql/test/suite/perfschema/t/pfs_upgrade_func.test
share/mysql/test/suite/perfschema/t/pfs_upgrade_proc.test
share/mysql/test/suite/perfschema/t/pfs_upgrade_table.test
share/mysql/test/suite/perfschema/t/pfs_upgrade_view.test
share/mysql/test/suite/perfschema/t/pool_of_threads-master.opt
share/mysql/test/suite/perfschema/t/privilege.test
share/mysql/test/suite/perfschema/t/privilege_table_io.test
share/mysql/test/suite/perfschema/t/query_cache-master.opt
share/mysql/test/suite/perfschema/t/query_cache.test
share/mysql/test/suite/perfschema/t/read_only.test
share/mysql/test/suite/perfschema/t/relaylog-slave.opt
share/mysql/test/suite/perfschema/t/relaylog.test
share/mysql/test/suite/perfschema/t/rollback_table_io.test
share/mysql/test/suite/perfschema/t/rpl_gtid_func.test
Changes 5.6.13: * Important Change; Replication: By default, when promoting integers from a smaller type on the master to a larger type on the slave (for example, from a SMALLINT column on the master to a BIGINT column on the slave), the promoted values are treated as though they are signed. Now in such cases it is possible to modify or override this behavior using one or both of ALL_SIGNED, ALL_UNSIGNED in the set of values specified for the slave_type_conversions server system variable. For more information, see Row-based replication: attribute promotion and demotion, as well as the description of the variable. * Previously, program options could be specified in full or as any unambiguous prefix. For example, the --compress option could be given to mysqldump as --compr, but not as --comp because the latter is ambiguous. Option prefixes now are deprecated. They can cause problems when new options are implemented for programs. A prefix that is currently unambiguous might become ambiguous in the future. If an unambiguous prefix is given, a warning now occurs to provide feedback. For example: Warning: Using unique option prefix compr instead of compress is deprecated and will be removed in a future release. Please use the full name instead. Option prefixes are no longer supported in MySQL 5.7; only full options are accepted. * The C API libmysqlclient shared-library .so files now have version 18.1.0 (up from version 18.0.0 used in MySQL 5.5). * In batch mode, mysql formatted result status messages such as “"Query OK, 1 row affected"” but did not print them. Now these messages are not formatted. * Bugs Fixed
2013-07-31 11:51:38 +02:00
share/mysql/test/suite/perfschema/t/rpl_statements-master.opt
share/mysql/test/suite/perfschema/t/rpl_statements-slave.opt
share/mysql/test/suite/perfschema/t/rpl_statements.test
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/perfschema/t/schema.test
share/mysql/test/suite/perfschema/t/selects-master.opt
share/mysql/test/suite/perfschema/t/selects.test
share/mysql/test/suite/perfschema/t/server_init.test
share/mysql/test/suite/perfschema/t/setup_actors.test
share/mysql/test/suite/perfschema/t/setup_consumers_defaults-master.opt
share/mysql/test/suite/perfschema/t/setup_consumers_defaults.test
share/mysql/test/suite/perfschema/t/setup_instruments_defaults-master.opt
share/mysql/test/suite/perfschema/t/setup_instruments_defaults.test
share/mysql/test/suite/perfschema/t/setup_objects.test
share/mysql/test/suite/perfschema/t/short_option_1-master.opt
share/mysql/test/suite/perfschema/t/short_option_1.test
share/mysql/test/suite/perfschema/t/short_option_2-master.opt
share/mysql/test/suite/perfschema/t/short_option_2.test
share/mysql/test/suite/perfschema/t/sizing_default.cnf
share/mysql/test/suite/perfschema/t/sizing_default.test
share/mysql/test/suite/perfschema/t/sizing_growth-master.opt
share/mysql/test/suite/perfschema/t/sizing_growth.test
share/mysql/test/suite/perfschema/t/sizing_high.cnf
share/mysql/test/suite/perfschema/t/sizing_high.test
share/mysql/test/suite/perfschema/t/sizing_low.cnf
share/mysql/test/suite/perfschema/t/sizing_low.test
share/mysql/test/suite/perfschema/t/sizing_med.cnf
share/mysql/test/suite/perfschema/t/sizing_med.test
share/mysql/test/suite/perfschema/t/sizing_off.cnf
share/mysql/test/suite/perfschema/t/sizing_off.test
share/mysql/test/suite/perfschema/t/socket_connect.test
share/mysql/test/suite/perfschema/t/socket_instances_func-master.opt
share/mysql/test/suite/perfschema/t/socket_instances_func.test
share/mysql/test/suite/perfschema/t/socket_instances_func_win-master.opt
share/mysql/test/suite/perfschema/t/socket_instances_func_win.test
share/mysql/test/suite/perfschema/t/socket_summary_by_event_name_func.test
share/mysql/test/suite/perfschema/t/socket_summary_by_instance_func.test
share/mysql/test/suite/perfschema/t/socket_summary_by_instance_func_win.test
share/mysql/test/suite/perfschema/t/stage_mdl_function.test
share/mysql/test/suite/perfschema/t/stage_mdl_global-master.opt
share/mysql/test/suite/perfschema/t/stage_mdl_global.test
share/mysql/test/suite/perfschema/t/stage_mdl_procedure.test
share/mysql/test/suite/perfschema/t/stage_mdl_table.test
share/mysql/test/suite/perfschema/t/start_server_disable_idle-master.opt
share/mysql/test/suite/perfschema/t/start_server_disable_idle.test
share/mysql/test/suite/perfschema/t/start_server_disable_stages-master.opt
share/mysql/test/suite/perfschema/t/start_server_disable_stages.test
share/mysql/test/suite/perfschema/t/start_server_disable_statements-master.opt
share/mysql/test/suite/perfschema/t/start_server_disable_statements.test
share/mysql/test/suite/perfschema/t/start_server_disable_waits-master.opt
share/mysql/test/suite/perfschema/t/start_server_disable_waits.test
share/mysql/test/suite/perfschema/t/start_server_innodb-master.opt
share/mysql/test/suite/perfschema/t/start_server_innodb.test
Changes 5.6.24: * CMake support was updated to handle CMake version 3.1. * The server now includes its version number when it writes the initial “starting” message to the error log, to make it easier to tell which server instance error log output applies to. This value is the same as that available from the version system variable. * ALTER TABLE did not take advantage of fast alterations that might otherwise apply to the operation to be performed, if the table contained temporal columns found to be in pre-5.6.4 format (TIME, DATETIME, and TIMESTAMP columns without support for fractional seconds precision). * Statement digesting as done previously by the Performance Schema is now done at the SQL level regardless of whether the Performance Schema is compiled in and is available to other aspects of server operation that could benefit from it. The default space available for digesting is 1024 bytes, but can be changed at server startup using the max_digest_length system variable. * Bug fixes.
2015-04-08 12:38:48 +02:00
share/mysql/test/suite/perfschema/t/start_server_low_digest-master.opt
share/mysql/test/suite/perfschema/t/start_server_low_digest.test
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/perfschema/t/start_server_no_account-master.opt
share/mysql/test/suite/perfschema/t/start_server_no_account.test
share/mysql/test/suite/perfschema/t/start_server_no_cond_class-master.opt
share/mysql/test/suite/perfschema/t/start_server_no_cond_class.test
share/mysql/test/suite/perfschema/t/start_server_no_cond_inst-master.opt
share/mysql/test/suite/perfschema/t/start_server_no_cond_inst.test
share/mysql/test/suite/perfschema/t/start_server_no_digests-master.opt
share/mysql/test/suite/perfschema/t/start_server_no_digests.test
share/mysql/test/suite/perfschema/t/start_server_no_file_class-master.opt
share/mysql/test/suite/perfschema/t/start_server_no_file_class.test
share/mysql/test/suite/perfschema/t/start_server_no_file_inst-master.opt
share/mysql/test/suite/perfschema/t/start_server_no_file_inst.test
share/mysql/test/suite/perfschema/t/start_server_no_host-master.opt
share/mysql/test/suite/perfschema/t/start_server_no_host.test
share/mysql/test/suite/perfschema/t/start_server_no_mutex_class-master.opt
share/mysql/test/suite/perfschema/t/start_server_no_mutex_class.test
share/mysql/test/suite/perfschema/t/start_server_no_mutex_inst-master.opt
share/mysql/test/suite/perfschema/t/start_server_no_mutex_inst.test
share/mysql/test/suite/perfschema/t/start_server_no_rwlock_class-master.opt
share/mysql/test/suite/perfschema/t/start_server_no_rwlock_class.test
share/mysql/test/suite/perfschema/t/start_server_no_rwlock_inst-master.opt
share/mysql/test/suite/perfschema/t/start_server_no_rwlock_inst.test
share/mysql/test/suite/perfschema/t/start_server_no_setup_actors-master.opt
share/mysql/test/suite/perfschema/t/start_server_no_setup_actors.test
share/mysql/test/suite/perfschema/t/start_server_no_setup_objects-master.opt
share/mysql/test/suite/perfschema/t/start_server_no_setup_objects.test
share/mysql/test/suite/perfschema/t/start_server_no_socket_class-master.opt
share/mysql/test/suite/perfschema/t/start_server_no_socket_class.test
share/mysql/test/suite/perfschema/t/start_server_no_socket_inst-master.opt
share/mysql/test/suite/perfschema/t/start_server_no_socket_inst.test
share/mysql/test/suite/perfschema/t/start_server_no_stage_class-master.opt
share/mysql/test/suite/perfschema/t/start_server_no_stage_class.test
share/mysql/test/suite/perfschema/t/start_server_no_stages_history-master.opt
share/mysql/test/suite/perfschema/t/start_server_no_stages_history.test
share/mysql/test/suite/perfschema/t/start_server_no_stages_history_long-master.opt
share/mysql/test/suite/perfschema/t/start_server_no_stages_history_long.test
share/mysql/test/suite/perfschema/t/start_server_no_statement_class-master.opt
share/mysql/test/suite/perfschema/t/start_server_no_statement_class.test
share/mysql/test/suite/perfschema/t/start_server_no_statements_history-master.opt
share/mysql/test/suite/perfschema/t/start_server_no_statements_history.test
share/mysql/test/suite/perfschema/t/start_server_no_statements_history_long-master.opt
share/mysql/test/suite/perfschema/t/start_server_no_statements_history_long.test
share/mysql/test/suite/perfschema/t/start_server_no_table_hdl-master.opt
share/mysql/test/suite/perfschema/t/start_server_no_table_hdl.test
share/mysql/test/suite/perfschema/t/start_server_no_table_inst-master.opt
share/mysql/test/suite/perfschema/t/start_server_no_table_inst.test
share/mysql/test/suite/perfschema/t/start_server_no_thread_class-master.opt
share/mysql/test/suite/perfschema/t/start_server_no_thread_class.test
share/mysql/test/suite/perfschema/t/start_server_no_thread_inst-master.opt
share/mysql/test/suite/perfschema/t/start_server_no_thread_inst.test
share/mysql/test/suite/perfschema/t/start_server_no_user-master.opt
share/mysql/test/suite/perfschema/t/start_server_no_user.test
share/mysql/test/suite/perfschema/t/start_server_no_waits_history-master.opt
share/mysql/test/suite/perfschema/t/start_server_no_waits_history.test
share/mysql/test/suite/perfschema/t/start_server_no_waits_history_long-master.opt
share/mysql/test/suite/perfschema/t/start_server_no_waits_history_long.test
share/mysql/test/suite/perfschema/t/start_server_nothing-master.opt
share/mysql/test/suite/perfschema/t/start_server_nothing.test
share/mysql/test/suite/perfschema/t/start_server_off-master.opt
share/mysql/test/suite/perfschema/t/start_server_off.test
share/mysql/test/suite/perfschema/t/start_server_on-master.opt
share/mysql/test/suite/perfschema/t/start_server_on.test
share/mysql/test/suite/perfschema/t/statement_digest.test
share/mysql/test/suite/perfschema/t/statement_digest_charset.test
share/mysql/test/suite/perfschema/t/statement_digest_consumers-master.opt
share/mysql/test/suite/perfschema/t/statement_digest_consumers.test
share/mysql/test/suite/perfschema/t/statement_digest_consumers2-master.opt
share/mysql/test/suite/perfschema/t/statement_digest_consumers2.test
share/mysql/test/suite/perfschema/t/statement_digest_long_query-master.opt
share/mysql/test/suite/perfschema/t/statement_digest_long_query.test
share/mysql/test/suite/perfschema/t/table_aggregate_global_2u_2t.test
share/mysql/test/suite/perfschema/t/table_aggregate_global_2u_3t.test
share/mysql/test/suite/perfschema/t/table_aggregate_global_4u_2t.test
share/mysql/test/suite/perfschema/t/table_aggregate_global_4u_3t.test
share/mysql/test/suite/perfschema/t/table_aggregate_hist_2u_2t.test
share/mysql/test/suite/perfschema/t/table_aggregate_hist_2u_3t.test
share/mysql/test/suite/perfschema/t/table_aggregate_hist_4u_2t.test
share/mysql/test/suite/perfschema/t/table_aggregate_hist_4u_3t.test
share/mysql/test/suite/perfschema/t/table_aggregate_off.test
share/mysql/test/suite/perfschema/t/table_aggregate_thread_2u_2t.test
share/mysql/test/suite/perfschema/t/table_aggregate_thread_2u_3t.test
share/mysql/test/suite/perfschema/t/table_aggregate_thread_4u_2t.test
share/mysql/test/suite/perfschema/t/table_aggregate_thread_4u_3t.test
share/mysql/test/suite/perfschema/t/table_io_aggregate_global_2u_2t.test
share/mysql/test/suite/perfschema/t/table_io_aggregate_global_2u_3t.test
share/mysql/test/suite/perfschema/t/table_io_aggregate_global_4u_2t.test
share/mysql/test/suite/perfschema/t/table_io_aggregate_global_4u_3t.test
share/mysql/test/suite/perfschema/t/table_io_aggregate_hist_2u_2t.test
share/mysql/test/suite/perfschema/t/table_io_aggregate_hist_2u_3t.test
share/mysql/test/suite/perfschema/t/table_io_aggregate_hist_4u_2t.test
share/mysql/test/suite/perfschema/t/table_io_aggregate_hist_4u_3t.test
share/mysql/test/suite/perfschema/t/table_io_aggregate_thread_2u_2t.test
share/mysql/test/suite/perfschema/t/table_io_aggregate_thread_2u_3t.test
share/mysql/test/suite/perfschema/t/table_io_aggregate_thread_4u_2t.test
share/mysql/test/suite/perfschema/t/table_io_aggregate_thread_4u_3t.test
share/mysql/test/suite/perfschema/t/table_lock_aggregate_global_2u_2t.test
share/mysql/test/suite/perfschema/t/table_lock_aggregate_global_2u_3t.test
share/mysql/test/suite/perfschema/t/table_lock_aggregate_global_4u_2t.test
share/mysql/test/suite/perfschema/t/table_lock_aggregate_global_4u_3t.test
share/mysql/test/suite/perfschema/t/table_lock_aggregate_hist_2u_2t.test
share/mysql/test/suite/perfschema/t/table_lock_aggregate_hist_2u_3t.test
share/mysql/test/suite/perfschema/t/table_lock_aggregate_hist_4u_2t.test
share/mysql/test/suite/perfschema/t/table_lock_aggregate_hist_4u_3t.test
share/mysql/test/suite/perfschema/t/table_lock_aggregate_thread_2u_2t.test
share/mysql/test/suite/perfschema/t/table_lock_aggregate_thread_2u_3t.test
share/mysql/test/suite/perfschema/t/table_lock_aggregate_thread_4u_2t.test
share/mysql/test/suite/perfschema/t/table_lock_aggregate_thread_4u_3t.test
share/mysql/test/suite/perfschema/t/table_schema.test
share/mysql/test/suite/perfschema/t/tampered_perfschema_table1-master.opt
share/mysql/test/suite/perfschema/t/tampered_perfschema_table1.test
share/mysql/test/suite/perfschema/t/temp_table_io.test
share/mysql/test/suite/perfschema/t/thread_cache-master.opt
share/mysql/test/suite/perfschema/t/thread_cache.test
share/mysql/test/suite/perfschema/t/threads_innodb.test
share/mysql/test/suite/perfschema/t/threads_insert_delayed.test
share/mysql/test/suite/perfschema/t/threads_mysql-master.opt
share/mysql/test/suite/perfschema/t/threads_mysql.test
share/mysql/test/suite/perfschema/t/trigger_table_io.test
Changes 5.6.22: * Noisy compiler warnings on FreeBSD 10 were silenced. * CMake workarounds for older Mac OS X and XCode versions were removed. On Mac OS X, compilation always uses Clang, even for 32-bit builds. * Previously, the MYSQL_MAINTAINER_MODE CMake option was turned on by default for debug builds and off for release builds, and MYSQL_MAINTAINER_MODE caused -Werror to be enabled when building with GCC. This made it cumbersome to enable -Werror under certain conditions, such as when compiling with Clang. * Build support was modified to produce the same warnings for Clang as for gcc. * CMake configuration for the Clang compiler sets more appropriate flags for building on Linux. Specifically, -g -fno-omit-frame-pointer -fno-strict-aliasing is now added. * Bugs fixed.
2014-12-02 13:40:09 +01:00
share/mysql/test/suite/perfschema/t/unary_digest.test
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/perfschema/t/view_table_io.test
share/mysql/test/suite/perfschema_stress/README
share/mysql/test/suite/perfschema_stress/include/settings.inc
share/mysql/test/suite/perfschema_stress/r/modify.result
share/mysql/test/suite/perfschema_stress/r/read.result
share/mysql/test/suite/perfschema_stress/r/work.result
share/mysql/test/suite/perfschema_stress/stress_init.txt
share/mysql/test/suite/perfschema_stress/stress_tests.txt
share/mysql/test/suite/perfschema_stress/t/modify.test
share/mysql/test/suite/perfschema_stress/t/read.test
share/mysql/test/suite/perfschema_stress/t/setup.test
share/mysql/test/suite/perfschema_stress/t/work.test
share/mysql/test/suite/rpl/README
share/mysql/test/suite/rpl/combinations
share/mysql/test/suite/rpl/extension/README
share/mysql/test/suite/rpl/extension/README.bhs
share/mysql/test/suite/rpl/extension/README.checksum
share/mysql/test/suite/rpl/extension/bhs.pl
share/mysql/test/suite/rpl/extension/bhs/default.rules
share/mysql/test/suite/rpl/extension/bhs/disabled.def
share/mysql/test/suite/rpl/extension/bhs/master-slave-bhs.inc
share/mysql/test/suite/rpl/extension/bhs/master-slave.inc
share/mysql/test/suite/rpl/extension/bhs/my.cnf
share/mysql/test/suite/rpl/extension/bhs/rpl_1slave_base.cnf
share/mysql/test/suite/rpl/extension/bhs/update_test_cases
share/mysql/test/suite/rpl/extension/checksum.pl
share/mysql/test/suite/rpl/include/rpl_mixed_check_db.inc
share/mysql/test/suite/rpl/include/rpl_mixed_check_event.inc
share/mysql/test/suite/rpl/include/rpl_mixed_check_select.inc
share/mysql/test/suite/rpl/include/rpl_mixed_check_table.inc
share/mysql/test/suite/rpl/include/rpl_mixed_check_user.inc
share/mysql/test/suite/rpl/include/rpl_mixed_check_view.inc
share/mysql/test/suite/rpl/include/rpl_mixed_clear_tables.inc
share/mysql/test/suite/rpl/include/rpl_mixed_ddl.inc
share/mysql/test/suite/rpl/include/rpl_mixed_dml.inc
share/mysql/test/suite/rpl/include/rpl_mixed_show_binlog_format.inc
share/mysql/test/suite/rpl/include/rpl_partition.inc
share/mysql/test/suite/rpl/my.cnf
share/mysql/test/suite/rpl/r/rpl000001.a.result
share/mysql/test/suite/rpl/r/rpl000001.b.result
share/mysql/test/suite/rpl/r/rpl_000010.result
share/mysql/test/suite/rpl/r/rpl_000011.result
share/mysql/test/suite/rpl/r/rpl_000013.result
share/mysql/test/suite/rpl/r/rpl_000017.result
Changes 5.6.20: Security Fix: The linked OpenSSL library for the MySQL 5.6 Commercial Server has been updated from version 1.0.1g to version 1.0.1h. Versions of OpenSSL prior to and including 1.0.1g are reported to be vulnerable to CVE-2014-0224. This change does not affect the Oracle-produced MySQL Community build of MySQL Server 5.6, which uses the yaSSL library instead. DTrace Support MySQL now includes DTrace support on Oracle Linux 6 or higher with UEK kernel. If DTrace is present, server builds will detect it with no special CMake options required. For information about using DTrace on MySQL, see Tracing mysqld Using DTrace. InnoDB Notes Important Change: Redo log writes for large, externally stored BLOB fields could overwrite the most recent checkpoint. The 5.6.20 patch limits the size of redo log BLOB writes to 10% of the redo log file size. The 5.7.5 patch addresses the bug without imposing a limitation. For MySQL 5.5, the bug remains a known limitation. As a result of the redo log BLOB write limit introduced for MySQL 5.6, innodb_log_file_size should be set to a value greater than 10 times the largest BLOB data size found in the rows of your tables plus the length of other variable length fields (VARCHAR, VARBINARY, and TEXT type fields). Failing to do so could result in “Row size too large” errors. No action is required if your innodb_log_file_size setting is already sufficiently large or your tables contain no BLOB data. Functionality Added or Changed Replication: The new system variable binlog_impossible_mode controls what happens if the server cannot write to the binary log, for example, due to a file error. For backward compatibility, the default for binlog_impossible_mode is IGNORE_ERROR, meaning the server logs the error, halts logging, and continues updates to the database. Setting this variable to ABORT_SERVER makes the server halt logging and shut down if it cannot write to the binary log. CMake support was updated to handle CMake version 3. New Debian7, Ubuntu12.04, and Ubuntu14.04 distribution support that was introduced with 5.6.17 now comes with the platform-specific packaging source placed under the packaging directory, in the deb-precise, deb-wheezy, and deb-trusty directories. Support for LinuxThreads has been removed from the source code. LinuxThreads was superseded by NPTL in Linux 2.6. By default, mysql_install_db creates a my.cnf file in the installation base directory using a template. This may be undesireable for some deployments. To enable this behavior to be suppressed, mysql_install_db now supports a --keep-my-cnf option to preserve any existing my.cnf file and not create a new my.cnf file. The mysqlhotcopy utility is now deprecated and will be removed in a future version of MySQL. Among the reasons for this: It works only for the MyISAM and ARCHIVE storage engines; it works on Unix but not Windows. Alternatives include mysqldump and MySQL Enterprise Backup. The timed_mutexes system variable has no effect and is deprecated. Bugs Fixed
2014-08-10 17:11:57 +02:00
share/mysql/test/suite/rpl/r/rpl_4threads_deadlock.result
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/rpl/r/rpl_DML_error.result
share/mysql/test/suite/rpl/r/rpl_EE_err.result
share/mysql/test/suite/rpl/r/rpl_LD_INFILE.result
share/mysql/test/suite/rpl/r/rpl_alter.result
share/mysql/test/suite/rpl/r/rpl_alter_db.result
share/mysql/test/suite/rpl/r/rpl_alter_repository.result
Changes 5.6.24: * CMake support was updated to handle CMake version 3.1. * The server now includes its version number when it writes the initial “starting” message to the error log, to make it easier to tell which server instance error log output applies to. This value is the same as that available from the version system variable. * ALTER TABLE did not take advantage of fast alterations that might otherwise apply to the operation to be performed, if the table contained temporal columns found to be in pre-5.6.4 format (TIME, DATETIME, and TIMESTAMP columns without support for fractional seconds precision). * Statement digesting as done previously by the Performance Schema is now done at the SQL level regardless of whether the Performance Schema is compiled in and is available to other aspects of server operation that could benefit from it. The default space available for digesting is 1024 bytes, but can be changed at server startup using the max_digest_length system variable. * Bug fixes.
2015-04-08 12:38:48 +02:00
share/mysql/test/suite/rpl/r/rpl_apply_binlog_with_anonymous_gtid.result
share/mysql/test/suite/rpl/r/rpl_apply_binlog_with_anonymous_gtid_when_gtid_mode_on.result
share/mysql/test/suite/rpl/r/rpl_apply_binlog_with_gtid_when_gtid_mode_off.result
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/rpl/r/rpl_auto_increment.result
share/mysql/test/suite/rpl/r/rpl_auto_increment_11932.result
share/mysql/test/suite/rpl/r/rpl_auto_increment_bug33029.result
share/mysql/test/suite/rpl/r/rpl_auto_increment_bug45679.result
share/mysql/test/suite/rpl/r/rpl_auto_increment_update_failure.result
Changes 5.6.29: * InnoDB: A new InnoDB configuration option, innodb_tmpdir, allows you to configure a separate temporary file directory for online ALTER TABLE operations. This option was introduced to help avoid tmpdir overflows that could occur as a result of large temporary files created during online ALTER TABLE operations. innodb_tmpdir is a SESSION variable and can be configured dynamically using a SET statement. * yaSSL was upgraded to version 2.3.9. This upgrade corrects an issue in which yaSSL handled only cases of zero or one leading zeros for the key agreement instead of potentially any number, which in rare cases could cause connections to fail when using DHE cipher suites. * The Valgrind function signature in mysql-test/valgrind.supp was upgraded for Valgrind 3.11. * Bugs Fixed
2016-02-28 09:58:03 +01:00
share/mysql/test/suite/rpl/r/rpl_autogen_query_multi_byte_char.result
Changes 5.6.24: * CMake support was updated to handle CMake version 3.1. * The server now includes its version number when it writes the initial “starting” message to the error log, to make it easier to tell which server instance error log output applies to. This value is the same as that available from the version system variable. * ALTER TABLE did not take advantage of fast alterations that might otherwise apply to the operation to be performed, if the table contained temporal columns found to be in pre-5.6.4 format (TIME, DATETIME, and TIMESTAMP columns without support for fractional seconds precision). * Statement digesting as done previously by the Performance Schema is now done at the SQL level regardless of whether the Performance Schema is compiled in and is available to other aspects of server operation that could benefit from it. The default space available for digesting is 1024 bytes, but can be changed at server startup using the max_digest_length system variable. * Bug fixes.
2015-04-08 12:38:48 +02:00
share/mysql/test/suite/rpl/r/rpl_avoid_temporal_upgrade.result
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/rpl/r/rpl_begin_commit_rollback.result
share/mysql/test/suite/rpl/r/rpl_binlog_corruption.result
share/mysql/test/suite/rpl/r/rpl_binlog_errors.result
share/mysql/test/suite/rpl/r/rpl_binlog_gcommit_options.result
share/mysql/test/suite/rpl/r/rpl_binlog_grant.result
share/mysql/test/suite/rpl/r/rpl_binlog_index.result
share/mysql/test/suite/rpl/r/rpl_bit.result
share/mysql/test/suite/rpl/r/rpl_bit_npk.result
share/mysql/test/suite/rpl/r/rpl_blackhole.result
share/mysql/test/suite/rpl/r/rpl_bug26395.result
share/mysql/test/suite/rpl/r/rpl_bug31076.result
share/mysql/test/suite/rpl/r/rpl_bug33931.result
share/mysql/test/suite/rpl/r/rpl_bug37426.result
share/mysql/test/suite/rpl/r/rpl_bug38694.result
share/mysql/test/suite/rpl/r/rpl_bug41902.result
share/mysql/test/suite/rpl/r/rpl_change_master.result
share/mysql/test/suite/rpl/r/rpl_change_master_crash_safe.result
share/mysql/test/suite/rpl/r/rpl_change_master_dbug.result
share/mysql/test/suite/rpl/r/rpl_charset.result
share/mysql/test/suite/rpl/r/rpl_charset_sjis.result
share/mysql/test/suite/rpl/r/rpl_check_gtid.result
share/mysql/test/suite/rpl/r/rpl_checksum.result
share/mysql/test/suite/rpl/r/rpl_checksum_cache.result
share/mysql/test/suite/rpl/r/rpl_checksum_undef.result
share/mysql/test/suite/rpl/r/rpl_circular_for_4_hosts.result
share/mysql/test/suite/rpl/r/rpl_colSize.result
share/mysql/test/suite/rpl/r/rpl_commit_after_flush.result
share/mysql/test/suite/rpl/r/rpl_concurrency_error.result
share/mysql/test/suite/rpl/r/rpl_conditional_comments.result
share/mysql/test/suite/rpl/r/rpl_connection.result
share/mysql/test/suite/rpl/r/rpl_corruption.result
share/mysql/test/suite/rpl/r/rpl_crash_safe_master.result
Changes 5.6.27: * InnoDB: The new innodb_numa_interleave read-only configuration option allows you to enable the NUMA interleave memory policy for allocation of the InnoDB buffer pool. When innodb_numa_interleave is enabled, the NUMA memory policy is set to MPOL_INTERLEAVE for the mysqld process. After the InnoDB buffer pool is allocated, the NUMA memory policy is set back to MPOL_DEFAULT. This option is only available on NUMA-enabled systems. * yaSSL was upgraded to version 2.3.8. * RPM .spec files were updated so that MySQL Server builds from source RPM packages will include the proper files to take advantage of operating system NUMA capabilities. This introduces a runtime dependency on libnuma.so.1. RPM and yum detect this and refuse to install if that library is not installed. * InnoDB: Reloading a table that was evicted while empty caused an AUTO_INCREMENT value to be reset. * InnoDB: Memory allocation sanity checks were added to the memcached code. * InnoDB: A memcached flush_all command raised an assertion. A function that starts a transaction was called from within assertion code. * InnoDB: A data corruption occurred on ARM64. GCC builtins did not issue the correct fences when setting or unsetting the lock word. * InnoDB: Server shutdown was delayed waiting for the purge thread to exit. To avoid this problem, the number of calls to trx_purge() was reduced, and the trx_purge() batch size was reduced to 20. * InnoDB: In READ COMMITTED mode, a REPLACE operation on a unique secondary index resulted in a constraint violation. * InnoDB: The IBUF_BITMAP_FREE bit indicated that there was more free space in the leaf page than was actually available. * InnoDB: Setting lower_case_table_names=0 on a case-insensitive file system could result in a hang condition when running an INSERT INTO ... SELECT ... FROM tbl_name operation with the wrong tbl_name letter case. An error message is now printed and the server exits when attempting to start the server with --lower_case_table_names=0 on a case-insensitive file system. * InnoDB: The server failed to start with an innodb_force_recovery setting greater than 3. InnoDB was set to read-only mode before redo logs were applied. * InnoDB: The trx_sys_read_pertable_file_format_id() function reported the wrong file format. * Partitioning: CREATE TABLE statements that used an invalid function in a subpartitioning expression did not always fail gracefully as expected. * Partitioning: Error handling for failed partitioning-related ALTER TABLE operations against non-partitioned tables was not performed correctly * Partitioning: ALTER TABLE when executed from a stored procedure did not always work correctly with tables partitioned by RANGE. * Replication: Repeatedly checking for ERR_LOCK_WAIT_TIMEOUT (as done, for example by repeatedly executing SHOW SLAVE STATUS) during a prolonged write lock on a table led to an assert. * Replication: If statement based logging was in use, when updating multiple tables in a single statement, a single transaction could be logged as two different transactions. This was due to the binary logging process not properly identifying statements which were operating over transactional tables. The fix ensures that they are correctly identified, even if such statements do not change the contents of the tables.
2015-10-03 14:46:13 +02:00
share/mysql/test/suite/rpl/r/rpl_crc_check.result
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/rpl/r/rpl_create_database.result
Changes 5.6.19: Functionality Added or Changed The obsolete and unmaintained charset2html utility has been removed from MySQL distributions. The mysqlbug, mysql_waitpid, and mysql_zap utilities have been deprecated and will be removed in MySQL 5.7. Bugs Fixed InnoDB: After upgrading from 5.6.10 to MySQL versions up to and including MySQL 5.6.18, InnoDB would attempt to rename obsolete full-text search auxiliary tables on server startup, resulting in an assertion failure. InnoDB: For each insert, memset would be called three times to allocate memory for system fields. To reduce CPU usage, the three memset calls are now combined into a single call. InnoDB: Enabling the InnoDB Table Monitor would result in a ib_table->stat_initialized assertion failure. InnoDB: Setting innodb_max_dirty_pages_pct=0 would leave 1% of dirty pages unflushed. Buffer pool flushing is initiated when the percentage of dirty pages is greater innodb_max_dirty_pages_pct. The internal variables that store the innodb_max_dirty_pages_pct value and the percentage of dirty pages (buf_get_modified_ratio_pct and srv_max_buf_pool_modified_pct) were defined as unsigned integer data types, which meant that a innodb_max_dirty_pages_pct value of 0 required a dirty pages percentage of 1 or greater to initiate buffer pool flushing. To address this problem, the buf_get_modified_ratio_pct and srv_max_buf_pool_modified_pct internal variables are redefined as double data types, which changes the range value for innodb_max_dirty_pages_pct and innodb_max_dirty_pages_pct_lwm from 0 .. 99 to 0 .. 99.99. Additionally, buffer pool flushing is now initiated when the percentage of dirty pages is “greater than or equal to” innodb_max_dirty_pages_pct. Replication: Log rotation events could cause group_relay_log_pos to be moved forward incorrectly within a group. This meant that, when the transaction was retried, or if the SQL thread was stopped in the middle of a transaction following one or more log rotations (such that the transaction or group spanned multiple relay log files), part or all of the group was silently skipped. This issue has been addressed by correcting a problem in the logic used to avoid touching the coordinates of the SQL thread when updating the log position as part of a relay log rotation whereby it was possible to update the SQL thread's coordinates when not using a multi-threaded slave, even in the middle of a group. Replication: When running the server with --gtid-mode=ON, STOP SLAVE followed by START SLAVE resulted in a mismatch between the information provided by INFORMATION_SCHEMA.INNODB_TEMP_TABLE_INFO and the Slave_open_temp_tables status variable: the INNODB_TEMP_TABLE_INFO table showed that no temporary tables existed, but Slave_open_temp_tables had a nonzero value. Replication: In certain cases, the server mishandled triggers and stored procedures that tried to modify other tables when called by CREATE TABLE ... SELECT. This is now handled correctly as an error. Replication: When used on a table employing a transactional storage engine, a failed TRUNCATE TABLE was still written to the binary log and thus replayed on the slave. This could lead to inconsistency when the master retained data that was removed on the slave. Now in such cases TRUNCATE TABLE is logged only when it executes successfully. Replication: The server did not always handle the auto.cnf file correctly in cases where this file's permissions were incorrect. Replication: When the binary log was rotated due to receipt of a SIGHUP signal, the new binary log did not contain the Previous_gtid_event required for subsequent processing of that binary log's GTID events. Now when SIGHUP is received, steps are taken to insure that the server writes the necessary Previous_gtid_event to the new log before writing any GTID events to the new log.
2014-06-02 09:30:38 +02:00
share/mysql/test/suite/rpl/r/rpl_create_drop_temp_table.result
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/rpl/r/rpl_create_if_not_exists.result
share/mysql/test/suite/rpl/r/rpl_create_tmp_table_if_not_exists.result
share/mysql/test/suite/rpl/r/rpl_critical_errors.result
share/mysql/test/suite/rpl/r/rpl_critical_errors.result.txt
share/mysql/test/suite/rpl/r/rpl_cross_version.result
share/mysql/test/suite/rpl/r/rpl_current_user.result
share/mysql/test/suite/rpl/r/rpl_ddl.result
share/mysql/test/suite/rpl/r/rpl_deadlock_innodb.result
share/mysql/test/suite/rpl/r/rpl_delayed_slave.result
share/mysql/test/suite/rpl/r/rpl_delete_no_where.result
share/mysql/test/suite/rpl/r/rpl_do_db_filter.result
share/mysql/test/suite/rpl/r/rpl_do_grant.result
share/mysql/test/suite/rpl/r/rpl_do_table_filter_insensitive.result
share/mysql/test/suite/rpl/r/rpl_do_table_filter_sensitive.result
share/mysql/test/suite/rpl/r/rpl_drop.result
share/mysql/test/suite/rpl/r/rpl_drop_db.result
Changes 5.6.23: * The linked OpenSSL library for the MySQL Commercial Server has been updated from version 1.0.1j to version 1.0.1k. * Support for the SSL 2.0 and SSL 3.0 protocols has been disabled because they provide weak encryption. * yaSSL was upgraded to version 2.3.7. * The valid date range of the SSL certificates in mysql-test/std_data has been extended to the year 2029. * Bugs Fixed
2015-02-07 20:23:40 +01:00
share/mysql/test/suite/rpl/r/rpl_drop_db_fail.result
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/rpl/r/rpl_drop_temp.result
Changes 5.6.21: The --skip-innodb option is now deprecated and its use results in a warning. It will be removed in a future MySQL release. This also applies to its synonyms (--innodb=OFF, --disable-innodb, and so forth). MySQL Enterprise Edition now includes a set of encryption functions based on the OpenSSL library that expose OpenSSL capabilities at the SQL level. Replication: The new variable simplified_binlog_gtid_recovery can be used to change the way binary log files are searched for previous GTIDs during recovery, speeding up the process when a large number of binary log files exist. Internally, spatial data types such as Geometry are represented as BLOB values, so when invoked with the --hex-blob option, mysqldump now displays spatial values in hex. Bugs Fixed...
2014-10-01 10:34:23 +02:00
share/mysql/test/suite/rpl/r/rpl_drop_temp_gtid.result
Changes 5.6.29: * InnoDB: A new InnoDB configuration option, innodb_tmpdir, allows you to configure a separate temporary file directory for online ALTER TABLE operations. This option was introduced to help avoid tmpdir overflows that could occur as a result of large temporary files created during online ALTER TABLE operations. innodb_tmpdir is a SESSION variable and can be configured dynamically using a SET statement. * yaSSL was upgraded to version 2.3.9. This upgrade corrects an issue in which yaSSL handled only cases of zero or one leading zeros for the key agreement instead of potentially any number, which in rare cases could cause connections to fail when using DHE cipher suites. * The Valgrind function signature in mysql-test/valgrind.supp was upgraded for Valgrind 3.11. * Bugs Fixed
2016-02-28 09:58:03 +01:00
share/mysql/test/suite/rpl/r/rpl_drop_temp_tbl_with_rewrite_db.result
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/rpl/r/rpl_drop_view.result
share/mysql/test/suite/rpl/r/rpl_dual_pos_advance.result
Changes 5.6.27: * InnoDB: The new innodb_numa_interleave read-only configuration option allows you to enable the NUMA interleave memory policy for allocation of the InnoDB buffer pool. When innodb_numa_interleave is enabled, the NUMA memory policy is set to MPOL_INTERLEAVE for the mysqld process. After the InnoDB buffer pool is allocated, the NUMA memory policy is set back to MPOL_DEFAULT. This option is only available on NUMA-enabled systems. * yaSSL was upgraded to version 2.3.8. * RPM .spec files were updated so that MySQL Server builds from source RPM packages will include the proper files to take advantage of operating system NUMA capabilities. This introduces a runtime dependency on libnuma.so.1. RPM and yum detect this and refuse to install if that library is not installed. * InnoDB: Reloading a table that was evicted while empty caused an AUTO_INCREMENT value to be reset. * InnoDB: Memory allocation sanity checks were added to the memcached code. * InnoDB: A memcached flush_all command raised an assertion. A function that starts a transaction was called from within assertion code. * InnoDB: A data corruption occurred on ARM64. GCC builtins did not issue the correct fences when setting or unsetting the lock word. * InnoDB: Server shutdown was delayed waiting for the purge thread to exit. To avoid this problem, the number of calls to trx_purge() was reduced, and the trx_purge() batch size was reduced to 20. * InnoDB: In READ COMMITTED mode, a REPLACE operation on a unique secondary index resulted in a constraint violation. * InnoDB: The IBUF_BITMAP_FREE bit indicated that there was more free space in the leaf page than was actually available. * InnoDB: Setting lower_case_table_names=0 on a case-insensitive file system could result in a hang condition when running an INSERT INTO ... SELECT ... FROM tbl_name operation with the wrong tbl_name letter case. An error message is now printed and the server exits when attempting to start the server with --lower_case_table_names=0 on a case-insensitive file system. * InnoDB: The server failed to start with an innodb_force_recovery setting greater than 3. InnoDB was set to read-only mode before redo logs were applied. * InnoDB: The trx_sys_read_pertable_file_format_id() function reported the wrong file format. * Partitioning: CREATE TABLE statements that used an invalid function in a subpartitioning expression did not always fail gracefully as expected. * Partitioning: Error handling for failed partitioning-related ALTER TABLE operations against non-partitioned tables was not performed correctly * Partitioning: ALTER TABLE when executed from a stored procedure did not always work correctly with tables partitioned by RANGE. * Replication: Repeatedly checking for ERR_LOCK_WAIT_TIMEOUT (as done, for example by repeatedly executing SHOW SLAVE STATUS) during a prolonged write lock on a table led to an assert. * Replication: If statement based logging was in use, when updating multiple tables in a single statement, a single transaction could be logged as two different transactions. This was due to the binary logging process not properly identifying statements which were operating over transactional tables. The fix ensures that they are correctly identified, even if such statements do not change the contents of the tables.
2015-10-03 14:46:13 +02:00
share/mysql/test/suite/rpl/r/rpl_dump_thread_kill.result
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/rpl/r/rpl_empty_master_host.result
Changes 5.6.27: * InnoDB: The new innodb_numa_interleave read-only configuration option allows you to enable the NUMA interleave memory policy for allocation of the InnoDB buffer pool. When innodb_numa_interleave is enabled, the NUMA memory policy is set to MPOL_INTERLEAVE for the mysqld process. After the InnoDB buffer pool is allocated, the NUMA memory policy is set back to MPOL_DEFAULT. This option is only available on NUMA-enabled systems. * yaSSL was upgraded to version 2.3.8. * RPM .spec files were updated so that MySQL Server builds from source RPM packages will include the proper files to take advantage of operating system NUMA capabilities. This introduces a runtime dependency on libnuma.so.1. RPM and yum detect this and refuse to install if that library is not installed. * InnoDB: Reloading a table that was evicted while empty caused an AUTO_INCREMENT value to be reset. * InnoDB: Memory allocation sanity checks were added to the memcached code. * InnoDB: A memcached flush_all command raised an assertion. A function that starts a transaction was called from within assertion code. * InnoDB: A data corruption occurred on ARM64. GCC builtins did not issue the correct fences when setting or unsetting the lock word. * InnoDB: Server shutdown was delayed waiting for the purge thread to exit. To avoid this problem, the number of calls to trx_purge() was reduced, and the trx_purge() batch size was reduced to 20. * InnoDB: In READ COMMITTED mode, a REPLACE operation on a unique secondary index resulted in a constraint violation. * InnoDB: The IBUF_BITMAP_FREE bit indicated that there was more free space in the leaf page than was actually available. * InnoDB: Setting lower_case_table_names=0 on a case-insensitive file system could result in a hang condition when running an INSERT INTO ... SELECT ... FROM tbl_name operation with the wrong tbl_name letter case. An error message is now printed and the server exits when attempting to start the server with --lower_case_table_names=0 on a case-insensitive file system. * InnoDB: The server failed to start with an innodb_force_recovery setting greater than 3. InnoDB was set to read-only mode before redo logs were applied. * InnoDB: The trx_sys_read_pertable_file_format_id() function reported the wrong file format. * Partitioning: CREATE TABLE statements that used an invalid function in a subpartitioning expression did not always fail gracefully as expected. * Partitioning: Error handling for failed partitioning-related ALTER TABLE operations against non-partitioned tables was not performed correctly * Partitioning: ALTER TABLE when executed from a stored procedure did not always work correctly with tables partitioned by RANGE. * Replication: Repeatedly checking for ERR_LOCK_WAIT_TIMEOUT (as done, for example by repeatedly executing SHOW SLAVE STATUS) during a prolonged write lock on a table led to an assert. * Replication: If statement based logging was in use, when updating multiple tables in a single statement, a single transaction could be logged as two different transactions. This was due to the binary logging process not properly identifying statements which were operating over transactional tables. The fix ensures that they are correctly identified, even if such statements do not change the contents of the tables.
2015-10-03 14:46:13 +02:00
share/mysql/test/suite/rpl/r/rpl_empty_multi_update.result
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/rpl/r/rpl_err_ignoredtable.result
share/mysql/test/suite/rpl/r/rpl_events.result
share/mysql/test/suite/rpl/r/rpl_extra_col_master_innodb.result
share/mysql/test/suite/rpl/r/rpl_extra_col_master_myisam.result
share/mysql/test/suite/rpl/r/rpl_extra_col_slave_innodb.result
share/mysql/test/suite/rpl/r/rpl_extra_col_slave_myisam.result
share/mysql/test/suite/rpl/r/rpl_extra_row_data.result
share/mysql/test/suite/rpl/r/rpl_failed_optimize.result
share/mysql/test/suite/rpl/r/rpl_filter_database.result
share/mysql/test/suite/rpl/r/rpl_filter_tables_not_exist.result
Changes 5.6.17: Functionality Added or Changed Incompatible Change: The AES_ENCRYPT() and AES_DECRYPT() functions now permit control of the block encryption mode and take an optional initialization vector argument: The new block_encryption_mode system variable controls the mode for block-based encryption algorithms. Its default value is aes-128-ecb, which signifies encryption using a key length of 128 bits and ECB mode. An optional init_vector argument provides an initialization vector for encryption modes that require it: AES_ENCRYPT(str,key_str[,init_vector]) AES_DECRYPT(crypt_str,key_str[,init_vector]) A random string of bytes to use for the initialization vector can be produced by calling the new RANDOM_BYTES() function. For more information, see Encryption and Compression Functions. These changes make statements that use AES_ENCRYPT() or AES_DECRYPT() unsafe for statement-based replication and they cannot be stored in the query cache. Queries that use RANDOM_BYTES() are unsafe for statement-based replication and cannot be stored in the query cache. Incompatible Change: The ERROR_FOR_DIVISION_BY_ZERO, NO_ZERO_DATE, and NO_ZERO_IN_DATE SQL modes now are deprecated and setting the sql_mode value to include any of them generates a warning. In MySQL 5.7, these modes do nothing. Instead, their effects are included in the effects of strict SQL mode (STRICT_ALL_TABLES or STRICT_TRANS_TABLES). The motivation for the change in MySQL 5.7 is to reduce the number of SQL modes with an effect dependent on strict mode and make them part of strict mode itself. To make advance preparation for an upgrade to MySQL 5.7, see SQL Mode Changes in MySQL 5.7. That discussion provides guidelines to assess whether your applications will be affected by the SQL mode changes in MySQL 5.7. InnoDB: MySQL now supports rebuilding regular and partitioned InnoDB tables using online DDL (ALGORITHM=INPLACE) for the following operations: OPTIMIZE TABLE ALTER TABLE ... FORCE ALTER TABLE ... ENGINE=INNODB (when run on an InnoDB table) Online DDL support reduces table rebuild time and permits concurrent DML, which helps reduce user application downtime. For additional information, see Overview of Online DDL. On Solaris, mysql_config --libs now includes -R/path/to/library so that libraries can be found at runtime. mysql_install_db provides a more informative diagnostic message when required Perl modules are missing. The IGNORE clause for ALTER TABLE is now deprecated and will be removed in a future version of MySQL. ALTER IGNORE TABLE causes problems for replication, prevents online ALTER TABLE for unique index creation, and causes problems with foreign keys (rows removed in the parent table). Bugs Fixed
2014-03-31 12:32:13 +02:00
share/mysql/test/suite/rpl/r/rpl_filter_warnings.result
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/rpl/r/rpl_flush_logs.result
share/mysql/test/suite/rpl/r/rpl_flushlog_loop.result
share/mysql/test/suite/rpl/r/rpl_foreign_key_innodb.result
share/mysql/test/suite/rpl/r/rpl_free_items.result
share/mysql/test/suite/rpl/r/rpl_function_defaults.result
Changes 5.6.27: * InnoDB: The new innodb_numa_interleave read-only configuration option allows you to enable the NUMA interleave memory policy for allocation of the InnoDB buffer pool. When innodb_numa_interleave is enabled, the NUMA memory policy is set to MPOL_INTERLEAVE for the mysqld process. After the InnoDB buffer pool is allocated, the NUMA memory policy is set back to MPOL_DEFAULT. This option is only available on NUMA-enabled systems. * yaSSL was upgraded to version 2.3.8. * RPM .spec files were updated so that MySQL Server builds from source RPM packages will include the proper files to take advantage of operating system NUMA capabilities. This introduces a runtime dependency on libnuma.so.1. RPM and yum detect this and refuse to install if that library is not installed. * InnoDB: Reloading a table that was evicted while empty caused an AUTO_INCREMENT value to be reset. * InnoDB: Memory allocation sanity checks were added to the memcached code. * InnoDB: A memcached flush_all command raised an assertion. A function that starts a transaction was called from within assertion code. * InnoDB: A data corruption occurred on ARM64. GCC builtins did not issue the correct fences when setting or unsetting the lock word. * InnoDB: Server shutdown was delayed waiting for the purge thread to exit. To avoid this problem, the number of calls to trx_purge() was reduced, and the trx_purge() batch size was reduced to 20. * InnoDB: In READ COMMITTED mode, a REPLACE operation on a unique secondary index resulted in a constraint violation. * InnoDB: The IBUF_BITMAP_FREE bit indicated that there was more free space in the leaf page than was actually available. * InnoDB: Setting lower_case_table_names=0 on a case-insensitive file system could result in a hang condition when running an INSERT INTO ... SELECT ... FROM tbl_name operation with the wrong tbl_name letter case. An error message is now printed and the server exits when attempting to start the server with --lower_case_table_names=0 on a case-insensitive file system. * InnoDB: The server failed to start with an innodb_force_recovery setting greater than 3. InnoDB was set to read-only mode before redo logs were applied. * InnoDB: The trx_sys_read_pertable_file_format_id() function reported the wrong file format. * Partitioning: CREATE TABLE statements that used an invalid function in a subpartitioning expression did not always fail gracefully as expected. * Partitioning: Error handling for failed partitioning-related ALTER TABLE operations against non-partitioned tables was not performed correctly * Partitioning: ALTER TABLE when executed from a stored procedure did not always work correctly with tables partitioned by RANGE. * Replication: Repeatedly checking for ERR_LOCK_WAIT_TIMEOUT (as done, for example by repeatedly executing SHOW SLAVE STATUS) during a prolonged write lock on a table led to an assert. * Replication: If statement based logging was in use, when updating multiple tables in a single statement, a single transaction could be logged as two different transactions. This was due to the binary logging process not properly identifying statements which were operating over transactional tables. The fix ensures that they are correctly identified, even if such statements do not change the contents of the tables.
2015-10-03 14:46:13 +02:00
share/mysql/test/suite/rpl/r/rpl_gap_in_retrieved_gtid_set.result
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/rpl/r/rpl_general_log.result
share/mysql/test/suite/rpl/r/rpl_geometry.result
share/mysql/test/suite/rpl/r/rpl_get_lock.result
share/mysql/test/suite/rpl/r/rpl_get_master_version_and_clock.result
share/mysql/test/suite/rpl/r/rpl_grant.result
share/mysql/test/suite/rpl/r/rpl_grant_plugin.result
Changes 5.6.12: * mysql_upgrade now verifies that the server version matches the version against which it was compiled, and exits if there is a mismatch. In addiion, a --version-check option permits specifying whether to enable version checking (the default), or disable checking if given as --skip-version-checking. * Bugs Fixed
2013-06-04 20:17:25 +02:00
share/mysql/test/suite/rpl/r/rpl_group_commit_deadlock.result
Changes 5.6.22: * Noisy compiler warnings on FreeBSD 10 were silenced. * CMake workarounds for older Mac OS X and XCode versions were removed. On Mac OS X, compilation always uses Clang, even for 32-bit builds. * Previously, the MYSQL_MAINTAINER_MODE CMake option was turned on by default for debug builds and off for release builds, and MYSQL_MAINTAINER_MODE caused -Werror to be enabled when building with GCC. This made it cumbersome to enable -Werror under certain conditions, such as when compiling with Clang. * Build support was modified to produce the same warnings for Clang as for gcc. * CMake configuration for the Clang compiler sets more appropriate flags for building on Linux. Specifically, -g -fno-omit-frame-pointer -fno-strict-aliasing is now added. * Bugs fixed.
2014-12-02 13:40:09 +01:00
share/mysql/test/suite/rpl/r/rpl_gtid_binary_log_as_relay_log.result
Changes 5.6.17: Functionality Added or Changed Incompatible Change: The AES_ENCRYPT() and AES_DECRYPT() functions now permit control of the block encryption mode and take an optional initialization vector argument: The new block_encryption_mode system variable controls the mode for block-based encryption algorithms. Its default value is aes-128-ecb, which signifies encryption using a key length of 128 bits and ECB mode. An optional init_vector argument provides an initialization vector for encryption modes that require it: AES_ENCRYPT(str,key_str[,init_vector]) AES_DECRYPT(crypt_str,key_str[,init_vector]) A random string of bytes to use for the initialization vector can be produced by calling the new RANDOM_BYTES() function. For more information, see Encryption and Compression Functions. These changes make statements that use AES_ENCRYPT() or AES_DECRYPT() unsafe for statement-based replication and they cannot be stored in the query cache. Queries that use RANDOM_BYTES() are unsafe for statement-based replication and cannot be stored in the query cache. Incompatible Change: The ERROR_FOR_DIVISION_BY_ZERO, NO_ZERO_DATE, and NO_ZERO_IN_DATE SQL modes now are deprecated and setting the sql_mode value to include any of them generates a warning. In MySQL 5.7, these modes do nothing. Instead, their effects are included in the effects of strict SQL mode (STRICT_ALL_TABLES or STRICT_TRANS_TABLES). The motivation for the change in MySQL 5.7 is to reduce the number of SQL modes with an effect dependent on strict mode and make them part of strict mode itself. To make advance preparation for an upgrade to MySQL 5.7, see SQL Mode Changes in MySQL 5.7. That discussion provides guidelines to assess whether your applications will be affected by the SQL mode changes in MySQL 5.7. InnoDB: MySQL now supports rebuilding regular and partitioned InnoDB tables using online DDL (ALGORITHM=INPLACE) for the following operations: OPTIMIZE TABLE ALTER TABLE ... FORCE ALTER TABLE ... ENGINE=INNODB (when run on an InnoDB table) Online DDL support reduces table rebuild time and permits concurrent DML, which helps reduce user application downtime. For additional information, see Overview of Online DDL. On Solaris, mysql_config --libs now includes -R/path/to/library so that libraries can be found at runtime. mysql_install_db provides a more informative diagnostic message when required Perl modules are missing. The IGNORE clause for ALTER TABLE is now deprecated and will be removed in a future version of MySQL. ALTER IGNORE TABLE causes problems for replication, prevents online ALTER TABLE for unique index creation, and causes problems with foreign keys (rows removed in the parent table). Bugs Fixed
2014-03-31 12:32:13 +02:00
share/mysql/test/suite/rpl/r/rpl_gtid_binlog_errors.result
share/mysql/test/suite/rpl/r/rpl_gtid_do_table_filter_insensitive.result
share/mysql/test/suite/rpl/r/rpl_gtid_do_table_filter_sensitive.result
Changes 5.6.20: Security Fix: The linked OpenSSL library for the MySQL 5.6 Commercial Server has been updated from version 1.0.1g to version 1.0.1h. Versions of OpenSSL prior to and including 1.0.1g are reported to be vulnerable to CVE-2014-0224. This change does not affect the Oracle-produced MySQL Community build of MySQL Server 5.6, which uses the yaSSL library instead. DTrace Support MySQL now includes DTrace support on Oracle Linux 6 or higher with UEK kernel. If DTrace is present, server builds will detect it with no special CMake options required. For information about using DTrace on MySQL, see Tracing mysqld Using DTrace. InnoDB Notes Important Change: Redo log writes for large, externally stored BLOB fields could overwrite the most recent checkpoint. The 5.6.20 patch limits the size of redo log BLOB writes to 10% of the redo log file size. The 5.7.5 patch addresses the bug without imposing a limitation. For MySQL 5.5, the bug remains a known limitation. As a result of the redo log BLOB write limit introduced for MySQL 5.6, innodb_log_file_size should be set to a value greater than 10 times the largest BLOB data size found in the rows of your tables plus the length of other variable length fields (VARCHAR, VARBINARY, and TEXT type fields). Failing to do so could result in “Row size too large” errors. No action is required if your innodb_log_file_size setting is already sufficiently large or your tables contain no BLOB data. Functionality Added or Changed Replication: The new system variable binlog_impossible_mode controls what happens if the server cannot write to the binary log, for example, due to a file error. For backward compatibility, the default for binlog_impossible_mode is IGNORE_ERROR, meaning the server logs the error, halts logging, and continues updates to the database. Setting this variable to ABORT_SERVER makes the server halt logging and shut down if it cannot write to the binary log. CMake support was updated to handle CMake version 3. New Debian7, Ubuntu12.04, and Ubuntu14.04 distribution support that was introduced with 5.6.17 now comes with the platform-specific packaging source placed under the packaging directory, in the deb-precise, deb-wheezy, and deb-trusty directories. Support for LinuxThreads has been removed from the source code. LinuxThreads was superseded by NPTL in Linux 2.6. By default, mysql_install_db creates a my.cnf file in the installation base directory using a template. This may be undesireable for some deployments. To enable this behavior to be suppressed, mysql_install_db now supports a --keep-my-cnf option to preserve any existing my.cnf file and not create a new my.cnf file. The mysqlhotcopy utility is now deprecated and will be removed in a future version of MySQL. Among the reasons for this: It works only for the MyISAM and ARCHIVE storage engines; it works on Unix but not Windows. Alternatives include mysqldump and MySQL Enterprise Backup. The timed_mutexes system variable has no effect and is deprecated. Bugs Fixed
2014-08-10 17:11:57 +02:00
share/mysql/test/suite/rpl/r/rpl_gtid_drop_table.result
Changes 5.6.19: Functionality Added or Changed The obsolete and unmaintained charset2html utility has been removed from MySQL distributions. The mysqlbug, mysql_waitpid, and mysql_zap utilities have been deprecated and will be removed in MySQL 5.7. Bugs Fixed InnoDB: After upgrading from 5.6.10 to MySQL versions up to and including MySQL 5.6.18, InnoDB would attempt to rename obsolete full-text search auxiliary tables on server startup, resulting in an assertion failure. InnoDB: For each insert, memset would be called three times to allocate memory for system fields. To reduce CPU usage, the three memset calls are now combined into a single call. InnoDB: Enabling the InnoDB Table Monitor would result in a ib_table->stat_initialized assertion failure. InnoDB: Setting innodb_max_dirty_pages_pct=0 would leave 1% of dirty pages unflushed. Buffer pool flushing is initiated when the percentage of dirty pages is greater innodb_max_dirty_pages_pct. The internal variables that store the innodb_max_dirty_pages_pct value and the percentage of dirty pages (buf_get_modified_ratio_pct and srv_max_buf_pool_modified_pct) were defined as unsigned integer data types, which meant that a innodb_max_dirty_pages_pct value of 0 required a dirty pages percentage of 1 or greater to initiate buffer pool flushing. To address this problem, the buf_get_modified_ratio_pct and srv_max_buf_pool_modified_pct internal variables are redefined as double data types, which changes the range value for innodb_max_dirty_pages_pct and innodb_max_dirty_pages_pct_lwm from 0 .. 99 to 0 .. 99.99. Additionally, buffer pool flushing is now initiated when the percentage of dirty pages is “greater than or equal to” innodb_max_dirty_pages_pct. Replication: Log rotation events could cause group_relay_log_pos to be moved forward incorrectly within a group. This meant that, when the transaction was retried, or if the SQL thread was stopped in the middle of a transaction following one or more log rotations (such that the transaction or group spanned multiple relay log files), part or all of the group was silently skipped. This issue has been addressed by correcting a problem in the logic used to avoid touching the coordinates of the SQL thread when updating the log position as part of a relay log rotation whereby it was possible to update the SQL thread's coordinates when not using a multi-threaded slave, even in the middle of a group. Replication: When running the server with --gtid-mode=ON, STOP SLAVE followed by START SLAVE resulted in a mismatch between the information provided by INFORMATION_SCHEMA.INNODB_TEMP_TABLE_INFO and the Slave_open_temp_tables status variable: the INNODB_TEMP_TABLE_INFO table showed that no temporary tables existed, but Slave_open_temp_tables had a nonzero value. Replication: In certain cases, the server mishandled triggers and stored procedures that tried to modify other tables when called by CREATE TABLE ... SELECT. This is now handled correctly as an error. Replication: When used on a table employing a transactional storage engine, a failed TRUNCATE TABLE was still written to the binary log and thus replayed on the slave. This could lead to inconsistency when the master retained data that was removed on the slave. Now in such cases TRUNCATE TABLE is logged only when it executes successfully. Replication: The server did not always handle the auto.cnf file correctly in cases where this file's permissions were incorrect. Replication: When the binary log was rotated due to receipt of a SIGHUP signal, the new binary log did not contain the Previous_gtid_event required for subsequent processing of that binary log's GTID events. Now when SIGHUP is received, steps are taken to insure that the server writes the necessary Previous_gtid_event to the new log before writing any GTID events to the new log.
2014-06-02 09:30:38 +02:00
share/mysql/test/suite/rpl/r/rpl_gtid_empty_transaction.result
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/rpl/r/rpl_gtid_execution.result
share/mysql/test/suite/rpl/r/rpl_gtid_failover.result
Changes 5.6.17: Functionality Added or Changed Incompatible Change: The AES_ENCRYPT() and AES_DECRYPT() functions now permit control of the block encryption mode and take an optional initialization vector argument: The new block_encryption_mode system variable controls the mode for block-based encryption algorithms. Its default value is aes-128-ecb, which signifies encryption using a key length of 128 bits and ECB mode. An optional init_vector argument provides an initialization vector for encryption modes that require it: AES_ENCRYPT(str,key_str[,init_vector]) AES_DECRYPT(crypt_str,key_str[,init_vector]) A random string of bytes to use for the initialization vector can be produced by calling the new RANDOM_BYTES() function. For more information, see Encryption and Compression Functions. These changes make statements that use AES_ENCRYPT() or AES_DECRYPT() unsafe for statement-based replication and they cannot be stored in the query cache. Queries that use RANDOM_BYTES() are unsafe for statement-based replication and cannot be stored in the query cache. Incompatible Change: The ERROR_FOR_DIVISION_BY_ZERO, NO_ZERO_DATE, and NO_ZERO_IN_DATE SQL modes now are deprecated and setting the sql_mode value to include any of them generates a warning. In MySQL 5.7, these modes do nothing. Instead, their effects are included in the effects of strict SQL mode (STRICT_ALL_TABLES or STRICT_TRANS_TABLES). The motivation for the change in MySQL 5.7 is to reduce the number of SQL modes with an effect dependent on strict mode and make them part of strict mode itself. To make advance preparation for an upgrade to MySQL 5.7, see SQL Mode Changes in MySQL 5.7. That discussion provides guidelines to assess whether your applications will be affected by the SQL mode changes in MySQL 5.7. InnoDB: MySQL now supports rebuilding regular and partitioned InnoDB tables using online DDL (ALGORITHM=INPLACE) for the following operations: OPTIMIZE TABLE ALTER TABLE ... FORCE ALTER TABLE ... ENGINE=INNODB (when run on an InnoDB table) Online DDL support reduces table rebuild time and permits concurrent DML, which helps reduce user application downtime. For additional information, see Overview of Online DDL. On Solaris, mysql_config --libs now includes -R/path/to/library so that libraries can be found at runtime. mysql_install_db provides a more informative diagnostic message when required Perl modules are missing. The IGNORE clause for ALTER TABLE is now deprecated and will be removed in a future version of MySQL. ALTER IGNORE TABLE causes problems for replication, prevents online ALTER TABLE for unique index creation, and causes problems with foreign keys (rows removed in the parent table). Bugs Fixed
2014-03-31 12:32:13 +02:00
share/mysql/test/suite/rpl/r/rpl_gtid_heartbeat_2slave.result
share/mysql/test/suite/rpl/r/rpl_gtid_ignore_table_filter_insensitive.result
share/mysql/test/suite/rpl/r/rpl_gtid_ignore_table_filter_sensitive.result
share/mysql/test/suite/rpl/r/rpl_gtid_loaddata_s.result
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/rpl/r/rpl_gtid_mode.result
Changes 5.6.25: Functionality Added or Changed * MySQL Enterprise Firewall operates on parser states and does not work well together with the query cache, which circumvents the parser. MySQL Enterprise Firewall now checks whether the query cache is enabled. If so, it displays a message that the query cache must be disabled and does not load. * my_print_defaults now masks passwords. To display passwords in cleartext, use the new --show option. * MySQL distributions now include an innodb_stress suite of test cases. Thanks to Mark Callaghan for the contribution. Bugs Fixed * InnoDB; Partitioning: The CREATE_TIME column of the INFORMATION_SCHEMA.TABLES table now shows the correct table creation time for partitioned InnoDB tables. The CREATE_TIME column of the INFORMATION_SCHEMA.PARTITIONS table now shows the correct partition creation time for a partition of partitioned InnoDB tables. The UPDATE_TIME column of the INFORMATION_SCHEMA.TABLES table now shows when a partitioned InnoDB table was last updated by an INSERT, DELETE, or UPDATE. The UPDATE_TIME column of the INFORMATION_SCHEMA.PARTITIONS table now shows when a partition of a partitioned InnoDB table was last updated. * InnoDB: An assertion was raised on shutdown due to XA PREPARE transactions holding explicit locks. * InnoDB: The strict_* forms of innodb_checksum_algorithm settings (strict_none, strict_innodb, and strict_crc32) caused the server to halt when a non-matching checksum was encountered, even though the non-matching checksum was valid. For example, with innodb_checksum_algorithm=strict_crc32, encountering a valid innodb checksum caused the server to halt. Instead of halting the server, a message is now printed to the error log and the page is accepted as valid if it matches an innodb, crc32 or none checksum. * InnoDB: The memcached set command permitted a negative expire time value. Expire time is stored internally as an unsigned integer. A negative value would be converted to a large number and accepted. The maximum expire time value is now restricted to INT_MAX32 to prevent negative expire time values. * InnoDB: Removal of a foreign key object from the data dictionary cache during error handling caused the server to exit. * InnoDB: SHOW ENGINE INNODB STATUS output showed negative reservation and signal count values due to a counter overflow error. * InnoDB: Failure to check the status of a cursor transaction read-only option before reusing the cursor transaction for a write operation resulted in a server exit during a memcached workload. * InnoDB: MDL locks taken by memcached clients caused a MySQL Enterprise Backup FLUSH TABLES WITH READ LOCK operation to hang. * InnoDB: Estimates that were too low for the size of merge chunks in the result sorting algorithm caused a server exit. * InnoDB: For full-text searches, the optimizer could choose an index that does not produce correct relevancy rankings. * Partitioning: When creating a partitioned table, partition-level DATA DIRECTORY or INDEX DIRECTORY option values that contained an excessive number of characters were handled incorrectly. * Partitioning: Executing an ALTER TABLE on a partitioned table on which a write lock was in effect could cause subsequent SQL statements on this table to fail. * Replication: When binary logging was enabled, using stored functions and triggers resulting in a long running procedure that inserted many records caused the memory use to increase rapidly. This was due to memory being allocated per variable. The fix ensures that in such a situation, memory is allocated once and the same memory is reused. * Replication: If an error was encountered while adding a GTID to the received GTID set, the log lock was not being correctly released. This could cause a deadlock. more...
2015-06-01 10:15:05 +02:00
share/mysql/test/suite/rpl/r/rpl_gtid_mode_off_new_master.result
share/mysql/test/suite/rpl/r/rpl_gtid_mode_on_new_master.result
Changes 5.6.26: * Security Fix: Due to the LogJam issue (https://weakdh.org/), OpenSSL has changed the Diffie-Hellman key length parameters for openssl-1.0.1n and up. * Replication: When using a multi-threaded slave, each worker thread has its own queue of transactions to process. In previous MySQL versions, STOP SLAVE waited for all workers to process their entire queue. This logic has been changed so that STOP SLAVE first finds the newest transaction that was committed by any worker thread. Then, it waits for all workers to complete transactions older than that. Newer transactions are not processed. The new logic allows STOP SLAVE to complete faster in case some worker queues contain multiple transactions. * Previously, the max_digest_length system variable controlled the maximum digest length for all server functions that computed statement digests. However, whereas the Performance Schema may need to maintain many digest values, other server functions such as MySQL Enterprise Firewall need only one digest per session. Increasing the max_digest_length value has little impact on total memory requirements for those functions, but can increase Performance Schema memory requirements significantly. To enable configuring digest length separately for the Performance Schema, its digest length is now controlled by the new performance_schema_max_digest_length system variable. * Previously, changes to the validate_password plugin dictionary file (named by the validate_password_dictionary_file system variable) while the server was running required a restart for the server to recognize the changes. Now validate_password_dictionary_file can be set at runtime and assigning a value causes the named file to be read without a restart. In addition, two new status variables are available. validate_password_dictionary_file_last_parsed indicates when the dictionary file was last read, and validate_password_dictionary_file_words_count indicates how many words it contains. * Bugs fixed
2015-07-30 16:39:18 +02:00
share/mysql/test/suite/rpl/r/rpl_gtid_mts_relay_log_recovery_auto_pos_on_off.result
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/rpl/r/rpl_gtid_parallel.result
share/mysql/test/suite/rpl/r/rpl_gtid_purged_fail_to_connect.result
share/mysql/test/suite/rpl/r/rpl_gtid_purged_maintained.result
Changes 5.6.25: Functionality Added or Changed * MySQL Enterprise Firewall operates on parser states and does not work well together with the query cache, which circumvents the parser. MySQL Enterprise Firewall now checks whether the query cache is enabled. If so, it displays a message that the query cache must be disabled and does not load. * my_print_defaults now masks passwords. To display passwords in cleartext, use the new --show option. * MySQL distributions now include an innodb_stress suite of test cases. Thanks to Mark Callaghan for the contribution. Bugs Fixed * InnoDB; Partitioning: The CREATE_TIME column of the INFORMATION_SCHEMA.TABLES table now shows the correct table creation time for partitioned InnoDB tables. The CREATE_TIME column of the INFORMATION_SCHEMA.PARTITIONS table now shows the correct partition creation time for a partition of partitioned InnoDB tables. The UPDATE_TIME column of the INFORMATION_SCHEMA.TABLES table now shows when a partitioned InnoDB table was last updated by an INSERT, DELETE, or UPDATE. The UPDATE_TIME column of the INFORMATION_SCHEMA.PARTITIONS table now shows when a partition of a partitioned InnoDB table was last updated. * InnoDB: An assertion was raised on shutdown due to XA PREPARE transactions holding explicit locks. * InnoDB: The strict_* forms of innodb_checksum_algorithm settings (strict_none, strict_innodb, and strict_crc32) caused the server to halt when a non-matching checksum was encountered, even though the non-matching checksum was valid. For example, with innodb_checksum_algorithm=strict_crc32, encountering a valid innodb checksum caused the server to halt. Instead of halting the server, a message is now printed to the error log and the page is accepted as valid if it matches an innodb, crc32 or none checksum. * InnoDB: The memcached set command permitted a negative expire time value. Expire time is stored internally as an unsigned integer. A negative value would be converted to a large number and accepted. The maximum expire time value is now restricted to INT_MAX32 to prevent negative expire time values. * InnoDB: Removal of a foreign key object from the data dictionary cache during error handling caused the server to exit. * InnoDB: SHOW ENGINE INNODB STATUS output showed negative reservation and signal count values due to a counter overflow error. * InnoDB: Failure to check the status of a cursor transaction read-only option before reusing the cursor transaction for a write operation resulted in a server exit during a memcached workload. * InnoDB: MDL locks taken by memcached clients caused a MySQL Enterprise Backup FLUSH TABLES WITH READ LOCK operation to hang. * InnoDB: Estimates that were too low for the size of merge chunks in the result sorting algorithm caused a server exit. * InnoDB: For full-text searches, the optimizer could choose an index that does not produce correct relevancy rankings. * Partitioning: When creating a partitioned table, partition-level DATA DIRECTORY or INDEX DIRECTORY option values that contained an excessive number of characters were handled incorrectly. * Partitioning: Executing an ALTER TABLE on a partitioned table on which a write lock was in effect could cause subsequent SQL statements on this table to fail. * Replication: When binary logging was enabled, using stored functions and triggers resulting in a long running procedure that inserted many records caused the memory use to increase rapidly. This was due to memory being allocated per variable. The fix ensures that in such a situation, memory is allocated once and the same memory is reused. * Replication: If an error was encountered while adding a GTID to the received GTID set, the log lock was not being correctly released. This could cause a deadlock. more...
2015-06-01 10:15:05 +02:00
share/mysql/test/suite/rpl/r/rpl_gtid_replay_relaylog.result
Changes 5.6.17: Functionality Added or Changed Incompatible Change: The AES_ENCRYPT() and AES_DECRYPT() functions now permit control of the block encryption mode and take an optional initialization vector argument: The new block_encryption_mode system variable controls the mode for block-based encryption algorithms. Its default value is aes-128-ecb, which signifies encryption using a key length of 128 bits and ECB mode. An optional init_vector argument provides an initialization vector for encryption modes that require it: AES_ENCRYPT(str,key_str[,init_vector]) AES_DECRYPT(crypt_str,key_str[,init_vector]) A random string of bytes to use for the initialization vector can be produced by calling the new RANDOM_BYTES() function. For more information, see Encryption and Compression Functions. These changes make statements that use AES_ENCRYPT() or AES_DECRYPT() unsafe for statement-based replication and they cannot be stored in the query cache. Queries that use RANDOM_BYTES() are unsafe for statement-based replication and cannot be stored in the query cache. Incompatible Change: The ERROR_FOR_DIVISION_BY_ZERO, NO_ZERO_DATE, and NO_ZERO_IN_DATE SQL modes now are deprecated and setting the sql_mode value to include any of them generates a warning. In MySQL 5.7, these modes do nothing. Instead, their effects are included in the effects of strict SQL mode (STRICT_ALL_TABLES or STRICT_TRANS_TABLES). The motivation for the change in MySQL 5.7 is to reduce the number of SQL modes with an effect dependent on strict mode and make them part of strict mode itself. To make advance preparation for an upgrade to MySQL 5.7, see SQL Mode Changes in MySQL 5.7. That discussion provides guidelines to assess whether your applications will be affected by the SQL mode changes in MySQL 5.7. InnoDB: MySQL now supports rebuilding regular and partitioned InnoDB tables using online DDL (ALGORITHM=INPLACE) for the following operations: OPTIMIZE TABLE ALTER TABLE ... FORCE ALTER TABLE ... ENGINE=INNODB (when run on an InnoDB table) Online DDL support reduces table rebuild time and permits concurrent DML, which helps reduce user application downtime. For additional information, see Overview of Online DDL. On Solaris, mysql_config --libs now includes -R/path/to/library so that libraries can be found at runtime. mysql_install_db provides a more informative diagnostic message when required Perl modules are missing. The IGNORE clause for ALTER TABLE is now deprecated and will be removed in a future version of MySQL. ALTER IGNORE TABLE causes problems for replication, prevents online ALTER TABLE for unique index creation, and causes problems with foreign keys (rows removed in the parent table). Bugs Fixed
2014-03-31 12:32:13 +02:00
share/mysql/test/suite/rpl/r/rpl_gtid_row_event_max_size.result
share/mysql/test/suite/rpl/r/rpl_gtid_row_show_relaylog_events.result
Changes 5.6.19: Functionality Added or Changed The obsolete and unmaintained charset2html utility has been removed from MySQL distributions. The mysqlbug, mysql_waitpid, and mysql_zap utilities have been deprecated and will be removed in MySQL 5.7. Bugs Fixed InnoDB: After upgrading from 5.6.10 to MySQL versions up to and including MySQL 5.6.18, InnoDB would attempt to rename obsolete full-text search auxiliary tables on server startup, resulting in an assertion failure. InnoDB: For each insert, memset would be called three times to allocate memory for system fields. To reduce CPU usage, the three memset calls are now combined into a single call. InnoDB: Enabling the InnoDB Table Monitor would result in a ib_table->stat_initialized assertion failure. InnoDB: Setting innodb_max_dirty_pages_pct=0 would leave 1% of dirty pages unflushed. Buffer pool flushing is initiated when the percentage of dirty pages is greater innodb_max_dirty_pages_pct. The internal variables that store the innodb_max_dirty_pages_pct value and the percentage of dirty pages (buf_get_modified_ratio_pct and srv_max_buf_pool_modified_pct) were defined as unsigned integer data types, which meant that a innodb_max_dirty_pages_pct value of 0 required a dirty pages percentage of 1 or greater to initiate buffer pool flushing. To address this problem, the buf_get_modified_ratio_pct and srv_max_buf_pool_modified_pct internal variables are redefined as double data types, which changes the range value for innodb_max_dirty_pages_pct and innodb_max_dirty_pages_pct_lwm from 0 .. 99 to 0 .. 99.99. Additionally, buffer pool flushing is now initiated when the percentage of dirty pages is “greater than or equal to” innodb_max_dirty_pages_pct. Replication: Log rotation events could cause group_relay_log_pos to be moved forward incorrectly within a group. This meant that, when the transaction was retried, or if the SQL thread was stopped in the middle of a transaction following one or more log rotations (such that the transaction or group spanned multiple relay log files), part or all of the group was silently skipped. This issue has been addressed by correcting a problem in the logic used to avoid touching the coordinates of the SQL thread when updating the log position as part of a relay log rotation whereby it was possible to update the SQL thread's coordinates when not using a multi-threaded slave, even in the middle of a group. Replication: When running the server with --gtid-mode=ON, STOP SLAVE followed by START SLAVE resulted in a mismatch between the information provided by INFORMATION_SCHEMA.INNODB_TEMP_TABLE_INFO and the Slave_open_temp_tables status variable: the INNODB_TEMP_TABLE_INFO table showed that no temporary tables existed, but Slave_open_temp_tables had a nonzero value. Replication: In certain cases, the server mishandled triggers and stored procedures that tried to modify other tables when called by CREATE TABLE ... SELECT. This is now handled correctly as an error. Replication: When used on a table employing a transactional storage engine, a failed TRUNCATE TABLE was still written to the binary log and thus replayed on the slave. This could lead to inconsistency when the master retained data that was removed on the slave. Now in such cases TRUNCATE TABLE is logged only when it executes successfully. Replication: The server did not always handle the auto.cnf file correctly in cases where this file's permissions were incorrect. Replication: When the binary log was rotated due to receipt of a SIGHUP signal, the new binary log did not contain the Previous_gtid_event required for subsequent processing of that binary log's GTID events. Now when SIGHUP is received, steps are taken to insure that the server writes the necessary Previous_gtid_event to the new log before writing any GTID events to the new log.
2014-06-02 09:30:38 +02:00
share/mysql/test/suite/rpl/r/rpl_gtid_server_sighup.result
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/rpl/r/rpl_gtid_sql_until_before_after.result
Changes 5.6.17: Functionality Added or Changed Incompatible Change: The AES_ENCRYPT() and AES_DECRYPT() functions now permit control of the block encryption mode and take an optional initialization vector argument: The new block_encryption_mode system variable controls the mode for block-based encryption algorithms. Its default value is aes-128-ecb, which signifies encryption using a key length of 128 bits and ECB mode. An optional init_vector argument provides an initialization vector for encryption modes that require it: AES_ENCRYPT(str,key_str[,init_vector]) AES_DECRYPT(crypt_str,key_str[,init_vector]) A random string of bytes to use for the initialization vector can be produced by calling the new RANDOM_BYTES() function. For more information, see Encryption and Compression Functions. These changes make statements that use AES_ENCRYPT() or AES_DECRYPT() unsafe for statement-based replication and they cannot be stored in the query cache. Queries that use RANDOM_BYTES() are unsafe for statement-based replication and cannot be stored in the query cache. Incompatible Change: The ERROR_FOR_DIVISION_BY_ZERO, NO_ZERO_DATE, and NO_ZERO_IN_DATE SQL modes now are deprecated and setting the sql_mode value to include any of them generates a warning. In MySQL 5.7, these modes do nothing. Instead, their effects are included in the effects of strict SQL mode (STRICT_ALL_TABLES or STRICT_TRANS_TABLES). The motivation for the change in MySQL 5.7 is to reduce the number of SQL modes with an effect dependent on strict mode and make them part of strict mode itself. To make advance preparation for an upgrade to MySQL 5.7, see SQL Mode Changes in MySQL 5.7. That discussion provides guidelines to assess whether your applications will be affected by the SQL mode changes in MySQL 5.7. InnoDB: MySQL now supports rebuilding regular and partitioned InnoDB tables using online DDL (ALGORITHM=INPLACE) for the following operations: OPTIMIZE TABLE ALTER TABLE ... FORCE ALTER TABLE ... ENGINE=INNODB (when run on an InnoDB table) Online DDL support reduces table rebuild time and permits concurrent DML, which helps reduce user application downtime. For additional information, see Overview of Online DDL. On Solaris, mysql_config --libs now includes -R/path/to/library so that libraries can be found at runtime. mysql_install_db provides a more informative diagnostic message when required Perl modules are missing. The IGNORE clause for ALTER TABLE is now deprecated and will be removed in a future version of MySQL. ALTER IGNORE TABLE causes problems for replication, prevents online ALTER TABLE for unique index creation, and causes problems with foreign keys (rows removed in the parent table). Bugs Fixed
2014-03-31 12:32:13 +02:00
share/mysql/test/suite/rpl/r/rpl_gtid_stm_insert_delayed.result
share/mysql/test/suite/rpl/r/rpl_gtid_stm_mix_show_relaylog_events.result
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/rpl/r/rpl_gtid_stress_failover.result
Changes 5.6.29: * InnoDB: A new InnoDB configuration option, innodb_tmpdir, allows you to configure a separate temporary file directory for online ALTER TABLE operations. This option was introduced to help avoid tmpdir overflows that could occur as a result of large temporary files created during online ALTER TABLE operations. innodb_tmpdir is a SESSION variable and can be configured dynamically using a SET statement. * yaSSL was upgraded to version 2.3.9. This upgrade corrects an issue in which yaSSL handled only cases of zero or one leading zeros for the key agreement instead of potentially any number, which in rare cases could cause connections to fail when using DHE cipher suites. * The Valgrind function signature in mysql-test/valgrind.supp was upgraded for Valgrind 3.11. * Bugs Fixed
2016-02-28 09:58:03 +01:00
share/mysql/test/suite/rpl/r/rpl_gtid_temp_table.result
Changes 5.6.27: * InnoDB: The new innodb_numa_interleave read-only configuration option allows you to enable the NUMA interleave memory policy for allocation of the InnoDB buffer pool. When innodb_numa_interleave is enabled, the NUMA memory policy is set to MPOL_INTERLEAVE for the mysqld process. After the InnoDB buffer pool is allocated, the NUMA memory policy is set back to MPOL_DEFAULT. This option is only available on NUMA-enabled systems. * yaSSL was upgraded to version 2.3.8. * RPM .spec files were updated so that MySQL Server builds from source RPM packages will include the proper files to take advantage of operating system NUMA capabilities. This introduces a runtime dependency on libnuma.so.1. RPM and yum detect this and refuse to install if that library is not installed. * InnoDB: Reloading a table that was evicted while empty caused an AUTO_INCREMENT value to be reset. * InnoDB: Memory allocation sanity checks were added to the memcached code. * InnoDB: A memcached flush_all command raised an assertion. A function that starts a transaction was called from within assertion code. * InnoDB: A data corruption occurred on ARM64. GCC builtins did not issue the correct fences when setting or unsetting the lock word. * InnoDB: Server shutdown was delayed waiting for the purge thread to exit. To avoid this problem, the number of calls to trx_purge() was reduced, and the trx_purge() batch size was reduced to 20. * InnoDB: In READ COMMITTED mode, a REPLACE operation on a unique secondary index resulted in a constraint violation. * InnoDB: The IBUF_BITMAP_FREE bit indicated that there was more free space in the leaf page than was actually available. * InnoDB: Setting lower_case_table_names=0 on a case-insensitive file system could result in a hang condition when running an INSERT INTO ... SELECT ... FROM tbl_name operation with the wrong tbl_name letter case. An error message is now printed and the server exits when attempting to start the server with --lower_case_table_names=0 on a case-insensitive file system. * InnoDB: The server failed to start with an innodb_force_recovery setting greater than 3. InnoDB was set to read-only mode before redo logs were applied. * InnoDB: The trx_sys_read_pertable_file_format_id() function reported the wrong file format. * Partitioning: CREATE TABLE statements that used an invalid function in a subpartitioning expression did not always fail gracefully as expected. * Partitioning: Error handling for failed partitioning-related ALTER TABLE operations against non-partitioned tables was not performed correctly * Partitioning: ALTER TABLE when executed from a stored procedure did not always work correctly with tables partitioned by RANGE. * Replication: Repeatedly checking for ERR_LOCK_WAIT_TIMEOUT (as done, for example by repeatedly executing SHOW SLAVE STATUS) during a prolonged write lock on a table led to an assert. * Replication: If statement based logging was in use, when updating multiple tables in a single statement, a single transaction could be logged as two different transactions. This was due to the binary logging process not properly identifying statements which were operating over transactional tables. The fix ensures that they are correctly identified, even if such statements do not change the contents of the tables.
2015-10-03 14:46:13 +02:00
share/mysql/test/suite/rpl/r/rpl_gtid_transaction_split_across_relay_logs.result
Changes 5.6.22: * Noisy compiler warnings on FreeBSD 10 were silenced. * CMake workarounds for older Mac OS X and XCode versions were removed. On Mac OS X, compilation always uses Clang, even for 32-bit builds. * Previously, the MYSQL_MAINTAINER_MODE CMake option was turned on by default for debug builds and off for release builds, and MYSQL_MAINTAINER_MODE caused -Werror to be enabled when building with GCC. This made it cumbersome to enable -Werror under certain conditions, such as when compiling with Clang. * Build support was modified to produce the same warnings for Clang as for gcc. * CMake configuration for the Clang compiler sets more appropriate flags for building on Linux. Specifically, -g -fno-omit-frame-pointer -fno-strict-aliasing is now added. * Bugs fixed.
2014-12-02 13:40:09 +01:00
share/mysql/test/suite/rpl/r/rpl_gtid_validate_slave_gtids.result
Changes 5.6.21: The --skip-innodb option is now deprecated and its use results in a warning. It will be removed in a future MySQL release. This also applies to its synonyms (--innodb=OFF, --disable-innodb, and so forth). MySQL Enterprise Edition now includes a set of encryption functions based on the OpenSSL library that expose OpenSSL capabilities at the SQL level. Replication: The new variable simplified_binlog_gtid_recovery can be used to change the way binary log files are searched for previous GTIDs during recovery, speeding up the process when a large number of binary log files exist. Internally, spatial data types such as Geometry are represented as BLOB values, so when invoked with the --hex-blob option, mysqldump now displays spatial values in hex. Bugs Fixed...
2014-10-01 10:34:23 +02:00
share/mysql/test/suite/rpl/r/rpl_gtids_restart_slave_io_lost_trx.result
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/rpl/r/rpl_heartbeat.result
share/mysql/test/suite/rpl/r/rpl_heartbeat_2slaves.result
share/mysql/test/suite/rpl/r/rpl_heartbeat_basic.result
share/mysql/test/suite/rpl/r/rpl_heartbeat_ssl.result
share/mysql/test/suite/rpl/r/rpl_idempotency.result
share/mysql/test/suite/rpl/r/rpl_ignore_db_filter.result
share/mysql/test/suite/rpl/r/rpl_ignore_grant.result
share/mysql/test/suite/rpl/r/rpl_ignore_revoke.result
share/mysql/test/suite/rpl/r/rpl_ignore_table.result
share/mysql/test/suite/rpl/r/rpl_ignore_table_filter_insensitive.result
share/mysql/test/suite/rpl/r/rpl_ignore_table_filter_sensitive.result
share/mysql/test/suite/rpl/r/rpl_ignore_table_update.result
share/mysql/test/suite/rpl/r/rpl_incident.result
share/mysql/test/suite/rpl/r/rpl_init_slave.result
share/mysql/test/suite/rpl/r/rpl_init_slave_errors.result
share/mysql/test/suite/rpl/r/rpl_innodb_bug28430.result
share/mysql/test/suite/rpl/r/rpl_innodb_bug30888.result
share/mysql/test/suite/rpl/r/rpl_innodb_mixed_ddl.result
share/mysql/test/suite/rpl/r/rpl_innodb_mixed_dml.result
share/mysql/test/suite/rpl/r/rpl_insert.result
share/mysql/test/suite/rpl/r/rpl_insert_id.result
share/mysql/test/suite/rpl/r/rpl_insert_id_pk.result
share/mysql/test/suite/rpl/r/rpl_insert_ignore.result
Changes 5.6.20: Security Fix: The linked OpenSSL library for the MySQL 5.6 Commercial Server has been updated from version 1.0.1g to version 1.0.1h. Versions of OpenSSL prior to and including 1.0.1g are reported to be vulnerable to CVE-2014-0224. This change does not affect the Oracle-produced MySQL Community build of MySQL Server 5.6, which uses the yaSSL library instead. DTrace Support MySQL now includes DTrace support on Oracle Linux 6 or higher with UEK kernel. If DTrace is present, server builds will detect it with no special CMake options required. For information about using DTrace on MySQL, see Tracing mysqld Using DTrace. InnoDB Notes Important Change: Redo log writes for large, externally stored BLOB fields could overwrite the most recent checkpoint. The 5.6.20 patch limits the size of redo log BLOB writes to 10% of the redo log file size. The 5.7.5 patch addresses the bug without imposing a limitation. For MySQL 5.5, the bug remains a known limitation. As a result of the redo log BLOB write limit introduced for MySQL 5.6, innodb_log_file_size should be set to a value greater than 10 times the largest BLOB data size found in the rows of your tables plus the length of other variable length fields (VARCHAR, VARBINARY, and TEXT type fields). Failing to do so could result in “Row size too large” errors. No action is required if your innodb_log_file_size setting is already sufficiently large or your tables contain no BLOB data. Functionality Added or Changed Replication: The new system variable binlog_impossible_mode controls what happens if the server cannot write to the binary log, for example, due to a file error. For backward compatibility, the default for binlog_impossible_mode is IGNORE_ERROR, meaning the server logs the error, halts logging, and continues updates to the database. Setting this variable to ABORT_SERVER makes the server halt logging and shut down if it cannot write to the binary log. CMake support was updated to handle CMake version 3. New Debian7, Ubuntu12.04, and Ubuntu14.04 distribution support that was introduced with 5.6.17 now comes with the platform-specific packaging source placed under the packaging directory, in the deb-precise, deb-wheezy, and deb-trusty directories. Support for LinuxThreads has been removed from the source code. LinuxThreads was superseded by NPTL in Linux 2.6. By default, mysql_install_db creates a my.cnf file in the installation base directory using a template. This may be undesireable for some deployments. To enable this behavior to be suppressed, mysql_install_db now supports a --keep-my-cnf option to preserve any existing my.cnf file and not create a new my.cnf file. The mysqlhotcopy utility is now deprecated and will be removed in a future version of MySQL. Among the reasons for this: It works only for the MyISAM and ARCHIVE storage engines; it works on Unix but not Windows. Alternatives include mysqldump and MySQL Enterprise Backup. The timed_mutexes system variable has no effect and is deprecated. Bugs Fixed
2014-08-10 17:11:57 +02:00
share/mysql/test/suite/rpl/r/rpl_insert_on_update.result
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/rpl/r/rpl_invoked_features.result
share/mysql/test/suite/rpl/r/rpl_ip_mix.result
share/mysql/test/suite/rpl/r/rpl_ip_mix2.result
share/mysql/test/suite/rpl/r/rpl_ipv4_as_ipv6.result
share/mysql/test/suite/rpl/r/rpl_ipv6.result
Changes 5.6.19: Functionality Added or Changed The obsolete and unmaintained charset2html utility has been removed from MySQL distributions. The mysqlbug, mysql_waitpid, and mysql_zap utilities have been deprecated and will be removed in MySQL 5.7. Bugs Fixed InnoDB: After upgrading from 5.6.10 to MySQL versions up to and including MySQL 5.6.18, InnoDB would attempt to rename obsolete full-text search auxiliary tables on server startup, resulting in an assertion failure. InnoDB: For each insert, memset would be called three times to allocate memory for system fields. To reduce CPU usage, the three memset calls are now combined into a single call. InnoDB: Enabling the InnoDB Table Monitor would result in a ib_table->stat_initialized assertion failure. InnoDB: Setting innodb_max_dirty_pages_pct=0 would leave 1% of dirty pages unflushed. Buffer pool flushing is initiated when the percentage of dirty pages is greater innodb_max_dirty_pages_pct. The internal variables that store the innodb_max_dirty_pages_pct value and the percentage of dirty pages (buf_get_modified_ratio_pct and srv_max_buf_pool_modified_pct) were defined as unsigned integer data types, which meant that a innodb_max_dirty_pages_pct value of 0 required a dirty pages percentage of 1 or greater to initiate buffer pool flushing. To address this problem, the buf_get_modified_ratio_pct and srv_max_buf_pool_modified_pct internal variables are redefined as double data types, which changes the range value for innodb_max_dirty_pages_pct and innodb_max_dirty_pages_pct_lwm from 0 .. 99 to 0 .. 99.99. Additionally, buffer pool flushing is now initiated when the percentage of dirty pages is “greater than or equal to” innodb_max_dirty_pages_pct. Replication: Log rotation events could cause group_relay_log_pos to be moved forward incorrectly within a group. This meant that, when the transaction was retried, or if the SQL thread was stopped in the middle of a transaction following one or more log rotations (such that the transaction or group spanned multiple relay log files), part or all of the group was silently skipped. This issue has been addressed by correcting a problem in the logic used to avoid touching the coordinates of the SQL thread when updating the log position as part of a relay log rotation whereby it was possible to update the SQL thread's coordinates when not using a multi-threaded slave, even in the middle of a group. Replication: When running the server with --gtid-mode=ON, STOP SLAVE followed by START SLAVE resulted in a mismatch between the information provided by INFORMATION_SCHEMA.INNODB_TEMP_TABLE_INFO and the Slave_open_temp_tables status variable: the INNODB_TEMP_TABLE_INFO table showed that no temporary tables existed, but Slave_open_temp_tables had a nonzero value. Replication: In certain cases, the server mishandled triggers and stored procedures that tried to modify other tables when called by CREATE TABLE ... SELECT. This is now handled correctly as an error. Replication: When used on a table employing a transactional storage engine, a failed TRUNCATE TABLE was still written to the binary log and thus replayed on the slave. This could lead to inconsistency when the master retained data that was removed on the slave. Now in such cases TRUNCATE TABLE is logged only when it executes successfully. Replication: The server did not always handle the auto.cnf file correctly in cases where this file's permissions were incorrect. Replication: When the binary log was rotated due to receipt of a SIGHUP signal, the new binary log did not contain the Previous_gtid_event required for subsequent processing of that binary log's GTID events. Now when SIGHUP is received, steps are taken to insure that the server writes the necessary Previous_gtid_event to the new log before writing any GTID events to the new log.
2014-06-02 09:30:38 +02:00
share/mysql/test/suite/rpl/r/rpl_kill_query.result
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/rpl/r/rpl_killed_ddl.result
share/mysql/test/suite/rpl/r/rpl_known_bugs_detection.result
share/mysql/test/suite/rpl/r/rpl_lcase_tblnames_rewrite_db.result
share/mysql/test/suite/rpl/r/rpl_loaddata.result
share/mysql/test/suite/rpl/r/rpl_loaddata_charset.result
share/mysql/test/suite/rpl/r/rpl_loaddata_fatal.result
share/mysql/test/suite/rpl/r/rpl_loaddata_m.result
share/mysql/test/suite/rpl/r/rpl_loaddata_map.result
share/mysql/test/suite/rpl/r/rpl_loaddata_s.result
share/mysql/test/suite/rpl/r/rpl_loaddata_simple.result
share/mysql/test/suite/rpl/r/rpl_loaddata_symlink.result
share/mysql/test/suite/rpl/r/rpl_loaddatalocal.result
share/mysql/test/suite/rpl/r/rpl_loadfile.result
share/mysql/test/suite/rpl/r/rpl_locale.result
share/mysql/test/suite/rpl/r/rpl_log_pos.result
Changes 5.6.15: * Previously, MySQL Server distributions included the MySQL Reference Manual in Info format (the Docs/mysql.info file). Because the license for the manual restricts redistribution, its inclusion in Community packages caused problems for downstream redistributors, such as those who create Linux distributions. Community distributions of MySQL Server no longer include the mysql.info file, to make the repackaging and redistribution process easier (for example, the source tarball and its checksum can be used directly). This change applies to all source and binary Community packaging formats. Commercial (Enterprise) distributions are unchanged. * Incompatible Change: Several statement instruments in the setup_instruments table are used by the Performance Schema during the early stages of statement classification before the exact statement type is known. * The Performance Schema now instruments the read/write lock Delegate::lock * A new CMake option, WITH_ASAN, permits enabling address sanitization for compilers that support it. * The hash function used for metadata locking was modified to reduce overhead. * Bugs Fixed
2013-12-03 21:02:41 +01:00
share/mysql/test/suite/rpl/r/rpl_lost_events_on_rotate.result
Changes 5.6.24: * CMake support was updated to handle CMake version 3.1. * The server now includes its version number when it writes the initial “starting” message to the error log, to make it easier to tell which server instance error log output applies to. This value is the same as that available from the version system variable. * ALTER TABLE did not take advantage of fast alterations that might otherwise apply to the operation to be performed, if the table contained temporal columns found to be in pre-5.6.4 format (TIME, DATETIME, and TIMESTAMP columns without support for fractional seconds precision). * Statement digesting as done previously by the Performance Schema is now done at the SQL level regardless of whether the Performance Schema is compiled in and is available to other aspects of server operation that could benefit from it. The default space available for digesting is 1024 bytes, but can be changed at server startup using the max_digest_length system variable. * Bug fixes.
2015-04-08 12:38:48 +02:00
share/mysql/test/suite/rpl/r/rpl_low_slave_net_time_out.result
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/rpl/r/rpl_manual_change_index_file.result
share/mysql/test/suite/rpl/r/rpl_many_optimize.result
share/mysql/test/suite/rpl/r/rpl_master_connection.result
share/mysql/test/suite/rpl/r/rpl_master_pos_wait.result
share/mysql/test/suite/rpl/r/rpl_migration_crash_safe.result
share/mysql/test/suite/rpl/r/rpl_misc_functions.result
share/mysql/test/suite/rpl/r/rpl_mix_found_rows.result
share/mysql/test/suite/rpl/r/rpl_mix_insert_delayed.result
Changes 5.6.29: * InnoDB: A new InnoDB configuration option, innodb_tmpdir, allows you to configure a separate temporary file directory for online ALTER TABLE operations. This option was introduced to help avoid tmpdir overflows that could occur as a result of large temporary files created during online ALTER TABLE operations. innodb_tmpdir is a SESSION variable and can be configured dynamically using a SET statement. * yaSSL was upgraded to version 2.3.9. This upgrade corrects an issue in which yaSSL handled only cases of zero or one leading zeros for the key agreement instead of potentially any number, which in rare cases could cause connections to fail when using DHE cipher suites. * The Valgrind function signature in mysql-test/valgrind.supp was upgraded for Valgrind 3.11. * Bugs Fixed
2016-02-28 09:58:03 +01:00
share/mysql/test/suite/rpl/r/rpl_mix_missing_data_on_slave.result
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/rpl/r/rpl_mixed_binlog_max_cache_size.result
share/mysql/test/suite/rpl/r/rpl_mixed_bit_pk.result
share/mysql/test/suite/rpl/r/rpl_mixed_ddl_dml.result
share/mysql/test/suite/rpl/r/rpl_mixed_drop_create_temp_table.result
share/mysql/test/suite/rpl/r/rpl_mixed_implicit_commit_binlog.result
share/mysql/test/suite/rpl/r/rpl_mixed_mixing_engines.result
share/mysql/test/suite/rpl/r/rpl_mixed_row_innodb.result
share/mysql/test/suite/rpl/r/rpl_mts_debug.result
Changes 5.6.22: * Noisy compiler warnings on FreeBSD 10 were silenced. * CMake workarounds for older Mac OS X and XCode versions were removed. On Mac OS X, compilation always uses Clang, even for 32-bit builds. * Previously, the MYSQL_MAINTAINER_MODE CMake option was turned on by default for debug builds and off for release builds, and MYSQL_MAINTAINER_MODE caused -Werror to be enabled when building with GCC. This made it cumbersome to enable -Werror under certain conditions, such as when compiling with Clang. * Build support was modified to produce the same warnings for Clang as for gcc. * CMake configuration for the Clang compiler sets more appropriate flags for building on Linux. Specifically, -g -fno-omit-frame-pointer -fno-strict-aliasing is now added. * Bugs fixed.
2014-12-02 13:40:09 +01:00
share/mysql/test/suite/rpl/r/rpl_mts_execute_partial_trx_with_auto_pos_off.result
share/mysql/test/suite/rpl/r/rpl_mts_execute_partial_trx_with_auto_pos_on.result
Changes 5.6.21: The --skip-innodb option is now deprecated and its use results in a warning. It will be removed in a future MySQL release. This also applies to its synonyms (--innodb=OFF, --disable-innodb, and so forth). MySQL Enterprise Edition now includes a set of encryption functions based on the OpenSSL library that expose OpenSSL capabilities at the SQL level. Replication: The new variable simplified_binlog_gtid_recovery can be used to change the way binary log files are searched for previous GTIDs during recovery, speeding up the process when a large number of binary log files exist. Internally, spatial data types such as Geometry are represented as BLOB values, so when invoked with the --hex-blob option, mysqldump now displays spatial values in hex. Bugs Fixed...
2014-10-01 10:34:23 +02:00
share/mysql/test/suite/rpl/r/rpl_mts_gtids_restart_slave_io_lost_trx.result
Changes 5.6.22: * Noisy compiler warnings on FreeBSD 10 were silenced. * CMake workarounds for older Mac OS X and XCode versions were removed. On Mac OS X, compilation always uses Clang, even for 32-bit builds. * Previously, the MYSQL_MAINTAINER_MODE CMake option was turned on by default for debug builds and off for release builds, and MYSQL_MAINTAINER_MODE caused -Werror to be enabled when building with GCC. This made it cumbersome to enable -Werror under certain conditions, such as when compiling with Clang. * Build support was modified to produce the same warnings for Clang as for gcc. * CMake configuration for the Clang compiler sets more appropriate flags for building on Linux. Specifically, -g -fno-omit-frame-pointer -fno-strict-aliasing is now added. * Bugs fixed.
2014-12-02 13:40:09 +01:00
share/mysql/test/suite/rpl/r/rpl_mts_slave_hang_with_partial_trx.result
Changes 5.6.26: * Security Fix: Due to the LogJam issue (https://weakdh.org/), OpenSSL has changed the Diffie-Hellman key length parameters for openssl-1.0.1n and up. * Replication: When using a multi-threaded slave, each worker thread has its own queue of transactions to process. In previous MySQL versions, STOP SLAVE waited for all workers to process their entire queue. This logic has been changed so that STOP SLAVE first finds the newest transaction that was committed by any worker thread. Then, it waits for all workers to complete transactions older than that. Newer transactions are not processed. The new logic allows STOP SLAVE to complete faster in case some worker queues contain multiple transactions. * Previously, the max_digest_length system variable controlled the maximum digest length for all server functions that computed statement digests. However, whereas the Performance Schema may need to maintain many digest values, other server functions such as MySQL Enterprise Firewall need only one digest per session. Increasing the max_digest_length value has little impact on total memory requirements for those functions, but can increase Performance Schema memory requirements significantly. To enable configuring digest length separately for the Performance Schema, its digest length is now controlled by the new performance_schema_max_digest_length system variable. * Previously, changes to the validate_password plugin dictionary file (named by the validate_password_dictionary_file system variable) while the server was running required a restart for the server to recognize the changes. Now validate_password_dictionary_file can be set at runtime and assigning a value causes the named file to be read without a restart. In addition, two new status variables are available. validate_password_dictionary_file_last_parsed indicates when the dictionary file was last read, and validate_password_dictionary_file_words_count indicates how many words it contains. * Bugs fixed
2015-07-30 16:39:18 +02:00
share/mysql/test/suite/rpl/r/rpl_mts_stop_slave.result
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/rpl/r/rpl_multi_delete.result
share/mysql/test/suite/rpl/r/rpl_multi_delete2.result
share/mysql/test/suite/rpl/r/rpl_multi_engine.result
share/mysql/test/suite/rpl/r/rpl_multi_update.result
share/mysql/test/suite/rpl/r/rpl_multi_update2.result
share/mysql/test/suite/rpl/r/rpl_multi_update3.result
share/mysql/test/suite/rpl/r/rpl_multi_update4.result
share/mysql/test/suite/rpl/r/rpl_mysql_upgrade.result
share/mysql/test/suite/rpl/r/rpl_mysqlbinlog_gtid_on.result
share/mysql/test/suite/rpl/r/rpl_name_const.result
share/mysql/test/suite/rpl/r/rpl_non_direct_mixed_mixing_engines.result
share/mysql/test/suite/rpl/r/rpl_non_direct_row_mixing_engines.result
share/mysql/test/suite/rpl/r/rpl_non_direct_stm_mixing_engines.result
share/mysql/test/suite/rpl/r/rpl_nondeterministic_functions.result
share/mysql/test/suite/rpl/r/rpl_not_null_innodb.result
share/mysql/test/suite/rpl/r/rpl_not_null_myisam.result
share/mysql/test/suite/rpl/r/rpl_optimize.result
share/mysql/test/suite/rpl/r/rpl_packet.result
share/mysql/test/suite/rpl/r/rpl_parallel.result
share/mysql/test/suite/rpl/r/rpl_parallel_change_master.result
share/mysql/test/suite/rpl/r/rpl_parallel_conf_limits.result
share/mysql/test/suite/rpl/r/rpl_parallel_conflicts.result
share/mysql/test/suite/rpl/r/rpl_parallel_ddl.result
share/mysql/test/suite/rpl/r/rpl_parallel_fallback.result
share/mysql/test/suite/rpl/r/rpl_parallel_innodb.result
share/mysql/test/suite/rpl/r/rpl_parallel_load_data.result
share/mysql/test/suite/rpl/r/rpl_parallel_multi_db.result
share/mysql/test/suite/rpl/r/rpl_parallel_seconds_behind_master.result
share/mysql/test/suite/rpl/r/rpl_parallel_show_binlog_events_purge_logs.result
share/mysql/test/suite/rpl/r/rpl_parallel_start_stop.result
share/mysql/test/suite/rpl/r/rpl_parallel_switch_sequential.result
share/mysql/test/suite/rpl/r/rpl_parallel_temp_query.result
Changes 5.6.20: Security Fix: The linked OpenSSL library for the MySQL 5.6 Commercial Server has been updated from version 1.0.1g to version 1.0.1h. Versions of OpenSSL prior to and including 1.0.1g are reported to be vulnerable to CVE-2014-0224. This change does not affect the Oracle-produced MySQL Community build of MySQL Server 5.6, which uses the yaSSL library instead. DTrace Support MySQL now includes DTrace support on Oracle Linux 6 or higher with UEK kernel. If DTrace is present, server builds will detect it with no special CMake options required. For information about using DTrace on MySQL, see Tracing mysqld Using DTrace. InnoDB Notes Important Change: Redo log writes for large, externally stored BLOB fields could overwrite the most recent checkpoint. The 5.6.20 patch limits the size of redo log BLOB writes to 10% of the redo log file size. The 5.7.5 patch addresses the bug without imposing a limitation. For MySQL 5.5, the bug remains a known limitation. As a result of the redo log BLOB write limit introduced for MySQL 5.6, innodb_log_file_size should be set to a value greater than 10 times the largest BLOB data size found in the rows of your tables plus the length of other variable length fields (VARCHAR, VARBINARY, and TEXT type fields). Failing to do so could result in “Row size too large” errors. No action is required if your innodb_log_file_size setting is already sufficiently large or your tables contain no BLOB data. Functionality Added or Changed Replication: The new system variable binlog_impossible_mode controls what happens if the server cannot write to the binary log, for example, due to a file error. For backward compatibility, the default for binlog_impossible_mode is IGNORE_ERROR, meaning the server logs the error, halts logging, and continues updates to the database. Setting this variable to ABORT_SERVER makes the server halt logging and shut down if it cannot write to the binary log. CMake support was updated to handle CMake version 3. New Debian7, Ubuntu12.04, and Ubuntu14.04 distribution support that was introduced with 5.6.17 now comes with the platform-specific packaging source placed under the packaging directory, in the deb-precise, deb-wheezy, and deb-trusty directories. Support for LinuxThreads has been removed from the source code. LinuxThreads was superseded by NPTL in Linux 2.6. By default, mysql_install_db creates a my.cnf file in the installation base directory using a template. This may be undesireable for some deployments. To enable this behavior to be suppressed, mysql_install_db now supports a --keep-my-cnf option to preserve any existing my.cnf file and not create a new my.cnf file. The mysqlhotcopy utility is now deprecated and will be removed in a future version of MySQL. Among the reasons for this: It works only for the MyISAM and ARCHIVE storage engines; it works on Unix but not Windows. Alternatives include mysqldump and MySQL Enterprise Backup. The timed_mutexes system variable has no effect and is deprecated. Bugs Fixed
2014-08-10 17:11:57 +02:00
share/mysql/test/suite/rpl/r/rpl_parallel_worker_error.result
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/rpl/r/rpl_partition_archive.result
share/mysql/test/suite/rpl/r/rpl_partition_innodb.result
share/mysql/test/suite/rpl/r/rpl_partition_memory.result
share/mysql/test/suite/rpl/r/rpl_partition_myisam.result
share/mysql/test/suite/rpl/r/rpl_plugin_load.result
share/mysql/test/suite/rpl/r/rpl_ps.result
share/mysql/test/suite/rpl/r/rpl_rbr_to_sbr.result
share/mysql/test/suite/rpl/r/rpl_read_old_relay_log_info.result
share/mysql/test/suite/rpl/r/rpl_read_only.result
Changes 5.6.22: * Noisy compiler warnings on FreeBSD 10 were silenced. * CMake workarounds for older Mac OS X and XCode versions were removed. On Mac OS X, compilation always uses Clang, even for 32-bit builds. * Previously, the MYSQL_MAINTAINER_MODE CMake option was turned on by default for debug builds and off for release builds, and MYSQL_MAINTAINER_MODE caused -Werror to be enabled when building with GCC. This made it cumbersome to enable -Werror under certain conditions, such as when compiling with Clang. * Build support was modified to produce the same warnings for Clang as for gcc. * CMake configuration for the Clang compiler sets more appropriate flags for building on Linux. Specifically, -g -fno-omit-frame-pointer -fno-strict-aliasing is now added. * Bugs fixed.
2014-12-02 13:40:09 +01:00
share/mysql/test/suite/rpl/r/rpl_recovery_empty_sqlthd_pos.result
share/mysql/test/suite/rpl/r/rpl_recovery_replicate_same_server_id.result
Changes 5.6.27: * InnoDB: The new innodb_numa_interleave read-only configuration option allows you to enable the NUMA interleave memory policy for allocation of the InnoDB buffer pool. When innodb_numa_interleave is enabled, the NUMA memory policy is set to MPOL_INTERLEAVE for the mysqld process. After the InnoDB buffer pool is allocated, the NUMA memory policy is set back to MPOL_DEFAULT. This option is only available on NUMA-enabled systems. * yaSSL was upgraded to version 2.3.8. * RPM .spec files were updated so that MySQL Server builds from source RPM packages will include the proper files to take advantage of operating system NUMA capabilities. This introduces a runtime dependency on libnuma.so.1. RPM and yum detect this and refuse to install if that library is not installed. * InnoDB: Reloading a table that was evicted while empty caused an AUTO_INCREMENT value to be reset. * InnoDB: Memory allocation sanity checks were added to the memcached code. * InnoDB: A memcached flush_all command raised an assertion. A function that starts a transaction was called from within assertion code. * InnoDB: A data corruption occurred on ARM64. GCC builtins did not issue the correct fences when setting or unsetting the lock word. * InnoDB: Server shutdown was delayed waiting for the purge thread to exit. To avoid this problem, the number of calls to trx_purge() was reduced, and the trx_purge() batch size was reduced to 20. * InnoDB: In READ COMMITTED mode, a REPLACE operation on a unique secondary index resulted in a constraint violation. * InnoDB: The IBUF_BITMAP_FREE bit indicated that there was more free space in the leaf page than was actually available. * InnoDB: Setting lower_case_table_names=0 on a case-insensitive file system could result in a hang condition when running an INSERT INTO ... SELECT ... FROM tbl_name operation with the wrong tbl_name letter case. An error message is now printed and the server exits when attempting to start the server with --lower_case_table_names=0 on a case-insensitive file system. * InnoDB: The server failed to start with an innodb_force_recovery setting greater than 3. InnoDB was set to read-only mode before redo logs were applied. * InnoDB: The trx_sys_read_pertable_file_format_id() function reported the wrong file format. * Partitioning: CREATE TABLE statements that used an invalid function in a subpartitioning expression did not always fail gracefully as expected. * Partitioning: Error handling for failed partitioning-related ALTER TABLE operations against non-partitioned tables was not performed correctly * Partitioning: ALTER TABLE when executed from a stored procedure did not always work correctly with tables partitioned by RANGE. * Replication: Repeatedly checking for ERR_LOCK_WAIT_TIMEOUT (as done, for example by repeatedly executing SHOW SLAVE STATUS) during a prolonged write lock on a table led to an assert. * Replication: If statement based logging was in use, when updating multiple tables in a single statement, a single transaction could be logged as two different transactions. This was due to the binary logging process not properly identifying statements which were operating over transactional tables. The fix ensures that they are correctly identified, even if such statements do not change the contents of the tables.
2015-10-03 14:46:13 +02:00
share/mysql/test/suite/rpl/r/rpl_relay_log_recovery_positions.result
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/rpl/r/rpl_relay_space_innodb.result
share/mysql/test/suite/rpl/r/rpl_relay_space_myisam.result
share/mysql/test/suite/rpl/r/rpl_relayrotate.result
share/mysql/test/suite/rpl/r/rpl_relayspace.result
share/mysql/test/suite/rpl/r/rpl_replicate_do.result
Changes 5.6.17: Functionality Added or Changed Incompatible Change: The AES_ENCRYPT() and AES_DECRYPT() functions now permit control of the block encryption mode and take an optional initialization vector argument: The new block_encryption_mode system variable controls the mode for block-based encryption algorithms. Its default value is aes-128-ecb, which signifies encryption using a key length of 128 bits and ECB mode. An optional init_vector argument provides an initialization vector for encryption modes that require it: AES_ENCRYPT(str,key_str[,init_vector]) AES_DECRYPT(crypt_str,key_str[,init_vector]) A random string of bytes to use for the initialization vector can be produced by calling the new RANDOM_BYTES() function. For more information, see Encryption and Compression Functions. These changes make statements that use AES_ENCRYPT() or AES_DECRYPT() unsafe for statement-based replication and they cannot be stored in the query cache. Queries that use RANDOM_BYTES() are unsafe for statement-based replication and cannot be stored in the query cache. Incompatible Change: The ERROR_FOR_DIVISION_BY_ZERO, NO_ZERO_DATE, and NO_ZERO_IN_DATE SQL modes now are deprecated and setting the sql_mode value to include any of them generates a warning. In MySQL 5.7, these modes do nothing. Instead, their effects are included in the effects of strict SQL mode (STRICT_ALL_TABLES or STRICT_TRANS_TABLES). The motivation for the change in MySQL 5.7 is to reduce the number of SQL modes with an effect dependent on strict mode and make them part of strict mode itself. To make advance preparation for an upgrade to MySQL 5.7, see SQL Mode Changes in MySQL 5.7. That discussion provides guidelines to assess whether your applications will be affected by the SQL mode changes in MySQL 5.7. InnoDB: MySQL now supports rebuilding regular and partitioned InnoDB tables using online DDL (ALGORITHM=INPLACE) for the following operations: OPTIMIZE TABLE ALTER TABLE ... FORCE ALTER TABLE ... ENGINE=INNODB (when run on an InnoDB table) Online DDL support reduces table rebuild time and permits concurrent DML, which helps reduce user application downtime. For additional information, see Overview of Online DDL. On Solaris, mysql_config --libs now includes -R/path/to/library so that libraries can be found at runtime. mysql_install_db provides a more informative diagnostic message when required Perl modules are missing. The IGNORE clause for ALTER TABLE is now deprecated and will be removed in a future version of MySQL. ALTER IGNORE TABLE causes problems for replication, prevents online ALTER TABLE for unique index creation, and causes problems with foreign keys (rows removed in the parent table). Bugs Fixed
2014-03-31 12:32:13 +02:00
share/mysql/test/suite/rpl/r/rpl_replicate_event_after_sync_stage.result
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/rpl/r/rpl_replicate_ignore_db.result
share/mysql/test/suite/rpl/r/rpl_replicate_rewrite_db.result
share/mysql/test/suite/rpl/r/rpl_report.result
share/mysql/test/suite/rpl/r/rpl_report_port.result
share/mysql/test/suite/rpl/r/rpl_rewrite_db_filter.result
share/mysql/test/suite/rpl/r/rpl_rewrt_db.result
Changes 5.6.21: The --skip-innodb option is now deprecated and its use results in a warning. It will be removed in a future MySQL release. This also applies to its synonyms (--innodb=OFF, --disable-innodb, and so forth). MySQL Enterprise Edition now includes a set of encryption functions based on the OpenSSL library that expose OpenSSL capabilities at the SQL level. Replication: The new variable simplified_binlog_gtid_recovery can be used to change the way binary log files are searched for previous GTIDs during recovery, speeding up the process when a large number of binary log files exist. Internally, spatial data types such as Geometry are represented as BLOB values, so when invoked with the --hex-blob option, mysqldump now displays spatial values in hex. Bugs Fixed...
2014-10-01 10:34:23 +02:00
share/mysql/test/suite/rpl/r/rpl_rotate_gtid.result
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/rpl/r/rpl_rotate_logs.result
share/mysql/test/suite/rpl/r/rpl_rotate_purge_deadlock.result
Changes 5.6.19: Functionality Added or Changed The obsolete and unmaintained charset2html utility has been removed from MySQL distributions. The mysqlbug, mysql_waitpid, and mysql_zap utilities have been deprecated and will be removed in MySQL 5.7. Bugs Fixed InnoDB: After upgrading from 5.6.10 to MySQL versions up to and including MySQL 5.6.18, InnoDB would attempt to rename obsolete full-text search auxiliary tables on server startup, resulting in an assertion failure. InnoDB: For each insert, memset would be called three times to allocate memory for system fields. To reduce CPU usage, the three memset calls are now combined into a single call. InnoDB: Enabling the InnoDB Table Monitor would result in a ib_table->stat_initialized assertion failure. InnoDB: Setting innodb_max_dirty_pages_pct=0 would leave 1% of dirty pages unflushed. Buffer pool flushing is initiated when the percentage of dirty pages is greater innodb_max_dirty_pages_pct. The internal variables that store the innodb_max_dirty_pages_pct value and the percentage of dirty pages (buf_get_modified_ratio_pct and srv_max_buf_pool_modified_pct) were defined as unsigned integer data types, which meant that a innodb_max_dirty_pages_pct value of 0 required a dirty pages percentage of 1 or greater to initiate buffer pool flushing. To address this problem, the buf_get_modified_ratio_pct and srv_max_buf_pool_modified_pct internal variables are redefined as double data types, which changes the range value for innodb_max_dirty_pages_pct and innodb_max_dirty_pages_pct_lwm from 0 .. 99 to 0 .. 99.99. Additionally, buffer pool flushing is now initiated when the percentage of dirty pages is “greater than or equal to” innodb_max_dirty_pages_pct. Replication: Log rotation events could cause group_relay_log_pos to be moved forward incorrectly within a group. This meant that, when the transaction was retried, or if the SQL thread was stopped in the middle of a transaction following one or more log rotations (such that the transaction or group spanned multiple relay log files), part or all of the group was silently skipped. This issue has been addressed by correcting a problem in the logic used to avoid touching the coordinates of the SQL thread when updating the log position as part of a relay log rotation whereby it was possible to update the SQL thread's coordinates when not using a multi-threaded slave, even in the middle of a group. Replication: When running the server with --gtid-mode=ON, STOP SLAVE followed by START SLAVE resulted in a mismatch between the information provided by INFORMATION_SCHEMA.INNODB_TEMP_TABLE_INFO and the Slave_open_temp_tables status variable: the INNODB_TEMP_TABLE_INFO table showed that no temporary tables existed, but Slave_open_temp_tables had a nonzero value. Replication: In certain cases, the server mishandled triggers and stored procedures that tried to modify other tables when called by CREATE TABLE ... SELECT. This is now handled correctly as an error. Replication: When used on a table employing a transactional storage engine, a failed TRUNCATE TABLE was still written to the binary log and thus replayed on the slave. This could lead to inconsistency when the master retained data that was removed on the slave. Now in such cases TRUNCATE TABLE is logged only when it executes successfully. Replication: The server did not always handle the auto.cnf file correctly in cases where this file's permissions were incorrect. Replication: When the binary log was rotated due to receipt of a SIGHUP signal, the new binary log did not contain the Previous_gtid_event required for subsequent processing of that binary log's GTID events. Now when SIGHUP is received, steps are taken to insure that the server writes the necessary Previous_gtid_event to the new log before writing any GTID events to the new log.
2014-06-02 09:30:38 +02:00
share/mysql/test/suite/rpl/r/rpl_rotate_row_trans.result
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/rpl/r/rpl_row_001.result
share/mysql/test/suite/rpl/r/rpl_row_4_bytes.result
share/mysql/test/suite/rpl/r/rpl_row_NOW.result
share/mysql/test/suite/rpl/r/rpl_row_USER.result
share/mysql/test/suite/rpl/r/rpl_row_UUID.result
share/mysql/test/suite/rpl/r/rpl_row_basic_11bugs.result
share/mysql/test/suite/rpl/r/rpl_row_basic_2myisam.result
share/mysql/test/suite/rpl/r/rpl_row_basic_3innodb.result
share/mysql/test/suite/rpl/r/rpl_row_basic_8partition.result
share/mysql/test/suite/rpl/r/rpl_row_basic_allow_batching.result
share/mysql/test/suite/rpl/r/rpl_row_binlog_max_cache_size.result
share/mysql/test/suite/rpl/r/rpl_row_blob_innodb.result
share/mysql/test/suite/rpl/r/rpl_row_blob_myisam.result
share/mysql/test/suite/rpl/r/rpl_row_colSize.result
share/mysql/test/suite/rpl/r/rpl_row_conflicts.result
Changes 5.6.19: Functionality Added or Changed The obsolete and unmaintained charset2html utility has been removed from MySQL distributions. The mysqlbug, mysql_waitpid, and mysql_zap utilities have been deprecated and will be removed in MySQL 5.7. Bugs Fixed InnoDB: After upgrading from 5.6.10 to MySQL versions up to and including MySQL 5.6.18, InnoDB would attempt to rename obsolete full-text search auxiliary tables on server startup, resulting in an assertion failure. InnoDB: For each insert, memset would be called three times to allocate memory for system fields. To reduce CPU usage, the three memset calls are now combined into a single call. InnoDB: Enabling the InnoDB Table Monitor would result in a ib_table->stat_initialized assertion failure. InnoDB: Setting innodb_max_dirty_pages_pct=0 would leave 1% of dirty pages unflushed. Buffer pool flushing is initiated when the percentage of dirty pages is greater innodb_max_dirty_pages_pct. The internal variables that store the innodb_max_dirty_pages_pct value and the percentage of dirty pages (buf_get_modified_ratio_pct and srv_max_buf_pool_modified_pct) were defined as unsigned integer data types, which meant that a innodb_max_dirty_pages_pct value of 0 required a dirty pages percentage of 1 or greater to initiate buffer pool flushing. To address this problem, the buf_get_modified_ratio_pct and srv_max_buf_pool_modified_pct internal variables are redefined as double data types, which changes the range value for innodb_max_dirty_pages_pct and innodb_max_dirty_pages_pct_lwm from 0 .. 99 to 0 .. 99.99. Additionally, buffer pool flushing is now initiated when the percentage of dirty pages is “greater than or equal to” innodb_max_dirty_pages_pct. Replication: Log rotation events could cause group_relay_log_pos to be moved forward incorrectly within a group. This meant that, when the transaction was retried, or if the SQL thread was stopped in the middle of a transaction following one or more log rotations (such that the transaction or group spanned multiple relay log files), part or all of the group was silently skipped. This issue has been addressed by correcting a problem in the logic used to avoid touching the coordinates of the SQL thread when updating the log position as part of a relay log rotation whereby it was possible to update the SQL thread's coordinates when not using a multi-threaded slave, even in the middle of a group. Replication: When running the server with --gtid-mode=ON, STOP SLAVE followed by START SLAVE resulted in a mismatch between the information provided by INFORMATION_SCHEMA.INNODB_TEMP_TABLE_INFO and the Slave_open_temp_tables status variable: the INNODB_TEMP_TABLE_INFO table showed that no temporary tables existed, but Slave_open_temp_tables had a nonzero value. Replication: In certain cases, the server mishandled triggers and stored procedures that tried to modify other tables when called by CREATE TABLE ... SELECT. This is now handled correctly as an error. Replication: When used on a table employing a transactional storage engine, a failed TRUNCATE TABLE was still written to the binary log and thus replayed on the slave. This could lead to inconsistency when the master retained data that was removed on the slave. Now in such cases TRUNCATE TABLE is logged only when it executes successfully. Replication: The server did not always handle the auto.cnf file correctly in cases where this file's permissions were incorrect. Replication: When the binary log was rotated due to receipt of a SIGHUP signal, the new binary log did not contain the Previous_gtid_event required for subsequent processing of that binary log's GTID events. Now when SIGHUP is received, steps are taken to insure that the server writes the necessary Previous_gtid_event to the new log before writing any GTID events to the new log.
2014-06-02 09:30:38 +02:00
share/mysql/test/suite/rpl/r/rpl_row_corrupt.result
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/rpl/r/rpl_row_corruption.result
share/mysql/test/suite/rpl/r/rpl_row_crash_safe.result
Changes 5.6.19: Functionality Added or Changed The obsolete and unmaintained charset2html utility has been removed from MySQL distributions. The mysqlbug, mysql_waitpid, and mysql_zap utilities have been deprecated and will be removed in MySQL 5.7. Bugs Fixed InnoDB: After upgrading from 5.6.10 to MySQL versions up to and including MySQL 5.6.18, InnoDB would attempt to rename obsolete full-text search auxiliary tables on server startup, resulting in an assertion failure. InnoDB: For each insert, memset would be called three times to allocate memory for system fields. To reduce CPU usage, the three memset calls are now combined into a single call. InnoDB: Enabling the InnoDB Table Monitor would result in a ib_table->stat_initialized assertion failure. InnoDB: Setting innodb_max_dirty_pages_pct=0 would leave 1% of dirty pages unflushed. Buffer pool flushing is initiated when the percentage of dirty pages is greater innodb_max_dirty_pages_pct. The internal variables that store the innodb_max_dirty_pages_pct value and the percentage of dirty pages (buf_get_modified_ratio_pct and srv_max_buf_pool_modified_pct) were defined as unsigned integer data types, which meant that a innodb_max_dirty_pages_pct value of 0 required a dirty pages percentage of 1 or greater to initiate buffer pool flushing. To address this problem, the buf_get_modified_ratio_pct and srv_max_buf_pool_modified_pct internal variables are redefined as double data types, which changes the range value for innodb_max_dirty_pages_pct and innodb_max_dirty_pages_pct_lwm from 0 .. 99 to 0 .. 99.99. Additionally, buffer pool flushing is now initiated when the percentage of dirty pages is “greater than or equal to” innodb_max_dirty_pages_pct. Replication: Log rotation events could cause group_relay_log_pos to be moved forward incorrectly within a group. This meant that, when the transaction was retried, or if the SQL thread was stopped in the middle of a transaction following one or more log rotations (such that the transaction or group spanned multiple relay log files), part or all of the group was silently skipped. This issue has been addressed by correcting a problem in the logic used to avoid touching the coordinates of the SQL thread when updating the log position as part of a relay log rotation whereby it was possible to update the SQL thread's coordinates when not using a multi-threaded slave, even in the middle of a group. Replication: When running the server with --gtid-mode=ON, STOP SLAVE followed by START SLAVE resulted in a mismatch between the information provided by INFORMATION_SCHEMA.INNODB_TEMP_TABLE_INFO and the Slave_open_temp_tables status variable: the INNODB_TEMP_TABLE_INFO table showed that no temporary tables existed, but Slave_open_temp_tables had a nonzero value. Replication: In certain cases, the server mishandled triggers and stored procedures that tried to modify other tables when called by CREATE TABLE ... SELECT. This is now handled correctly as an error. Replication: When used on a table employing a transactional storage engine, a failed TRUNCATE TABLE was still written to the binary log and thus replayed on the slave. This could lead to inconsistency when the master retained data that was removed on the slave. Now in such cases TRUNCATE TABLE is logged only when it executes successfully. Replication: The server did not always handle the auto.cnf file correctly in cases where this file's permissions were incorrect. Replication: When the binary log was rotated due to receipt of a SIGHUP signal, the new binary log did not contain the Previous_gtid_event required for subsequent processing of that binary log's GTID events. Now when SIGHUP is received, steps are taken to insure that the server writes the necessary Previous_gtid_event to the new log before writing any GTID events to the new log.
2014-06-02 09:30:38 +02:00
share/mysql/test/suite/rpl/r/rpl_row_create_select.result
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/rpl/r/rpl_row_create_table.result
share/mysql/test/suite/rpl/r/rpl_row_delayed_ins.result
share/mysql/test/suite/rpl/r/rpl_row_drop.result
share/mysql/test/suite/rpl/r/rpl_row_drop_create_temp_table.result
share/mysql/test/suite/rpl/r/rpl_row_err_ignoredtable.result
share/mysql/test/suite/rpl/r/rpl_row_event_max_size.result
share/mysql/test/suite/rpl/r/rpl_row_find_row.result
share/mysql/test/suite/rpl/r/rpl_row_flsh_tbls.result
share/mysql/test/suite/rpl/r/rpl_row_func001.result
share/mysql/test/suite/rpl/r/rpl_row_func002.result
share/mysql/test/suite/rpl/r/rpl_row_func003.result
share/mysql/test/suite/rpl/r/rpl_row_hash_scan.result
share/mysql/test/suite/rpl/r/rpl_row_hash_scan_sanity.result
share/mysql/test/suite/rpl/r/rpl_row_idempotency.result
share/mysql/test/suite/rpl/r/rpl_row_ignorable_event.result
share/mysql/test/suite/rpl/r/rpl_row_img_blobs.result
share/mysql/test/suite/rpl/r/rpl_row_img_eng_full.result
share/mysql/test/suite/rpl/r/rpl_row_img_eng_min.result
share/mysql/test/suite/rpl/r/rpl_row_img_eng_noblob.result
share/mysql/test/suite/rpl/r/rpl_row_img_idx_full.result
share/mysql/test/suite/rpl/r/rpl_row_img_idx_min.result
share/mysql/test/suite/rpl/r/rpl_row_img_idx_noblob.result
share/mysql/test/suite/rpl/r/rpl_row_img_misc.result
share/mysql/test/suite/rpl/r/rpl_row_img_sanity.result
share/mysql/test/suite/rpl/r/rpl_row_implicit_commit_binlog.result
share/mysql/test/suite/rpl/r/rpl_row_inexist_tbl.result
share/mysql/test/suite/rpl/r/rpl_row_insert_delayed.result
share/mysql/test/suite/rpl/r/rpl_row_lcase_tblnames.result
share/mysql/test/suite/rpl/r/rpl_row_loaddata_concurrent.result
share/mysql/test/suite/rpl/r/rpl_row_loaddata_m.result
share/mysql/test/suite/rpl/r/rpl_row_log.result
share/mysql/test/suite/rpl/r/rpl_row_log_innodb.result
share/mysql/test/suite/rpl/r/rpl_row_max_relay_size.result
share/mysql/test/suite/rpl/r/rpl_row_merge_engine.result
share/mysql/test/suite/rpl/r/rpl_row_mixing_engines.result
share/mysql/test/suite/rpl/r/rpl_row_mts_crash_safe.result
share/mysql/test/suite/rpl/r/rpl_row_mts_rec_crash_safe.result
share/mysql/test/suite/rpl/r/rpl_row_mts_show_relaylog_events.result
share/mysql/test/suite/rpl/r/rpl_row_multi_query.result
share/mysql/test/suite/rpl/r/rpl_row_mysqlbinlog.result
share/mysql/test/suite/rpl/r/rpl_row_rec_comp_innodb.result
share/mysql/test/suite/rpl/r/rpl_row_rec_comp_myisam.result
share/mysql/test/suite/rpl/r/rpl_row_record_find_myisam.result
share/mysql/test/suite/rpl/r/rpl_row_reset_slave.result
Changes 5.6.27: * InnoDB: The new innodb_numa_interleave read-only configuration option allows you to enable the NUMA interleave memory policy for allocation of the InnoDB buffer pool. When innodb_numa_interleave is enabled, the NUMA memory policy is set to MPOL_INTERLEAVE for the mysqld process. After the InnoDB buffer pool is allocated, the NUMA memory policy is set back to MPOL_DEFAULT. This option is only available on NUMA-enabled systems. * yaSSL was upgraded to version 2.3.8. * RPM .spec files were updated so that MySQL Server builds from source RPM packages will include the proper files to take advantage of operating system NUMA capabilities. This introduces a runtime dependency on libnuma.so.1. RPM and yum detect this and refuse to install if that library is not installed. * InnoDB: Reloading a table that was evicted while empty caused an AUTO_INCREMENT value to be reset. * InnoDB: Memory allocation sanity checks were added to the memcached code. * InnoDB: A memcached flush_all command raised an assertion. A function that starts a transaction was called from within assertion code. * InnoDB: A data corruption occurred on ARM64. GCC builtins did not issue the correct fences when setting or unsetting the lock word. * InnoDB: Server shutdown was delayed waiting for the purge thread to exit. To avoid this problem, the number of calls to trx_purge() was reduced, and the trx_purge() batch size was reduced to 20. * InnoDB: In READ COMMITTED mode, a REPLACE operation on a unique secondary index resulted in a constraint violation. * InnoDB: The IBUF_BITMAP_FREE bit indicated that there was more free space in the leaf page than was actually available. * InnoDB: Setting lower_case_table_names=0 on a case-insensitive file system could result in a hang condition when running an INSERT INTO ... SELECT ... FROM tbl_name operation with the wrong tbl_name letter case. An error message is now printed and the server exits when attempting to start the server with --lower_case_table_names=0 on a case-insensitive file system. * InnoDB: The server failed to start with an innodb_force_recovery setting greater than 3. InnoDB was set to read-only mode before redo logs were applied. * InnoDB: The trx_sys_read_pertable_file_format_id() function reported the wrong file format. * Partitioning: CREATE TABLE statements that used an invalid function in a subpartitioning expression did not always fail gracefully as expected. * Partitioning: Error handling for failed partitioning-related ALTER TABLE operations against non-partitioned tables was not performed correctly * Partitioning: ALTER TABLE when executed from a stored procedure did not always work correctly with tables partitioned by RANGE. * Replication: Repeatedly checking for ERR_LOCK_WAIT_TIMEOUT (as done, for example by repeatedly executing SHOW SLAVE STATUS) during a prolonged write lock on a table led to an assert. * Replication: If statement based logging was in use, when updating multiple tables in a single statement, a single transaction could be logged as two different transactions. This was due to the binary logging process not properly identifying statements which were operating over transactional tables. The fix ensures that they are correctly identified, even if such statements do not change the contents of the tables.
2015-10-03 14:46:13 +02:00
share/mysql/test/suite/rpl/r/rpl_row_rollback_to_savepoint.result
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/rpl/r/rpl_row_show_relaylog_events.result
share/mysql/test/suite/rpl/r/rpl_row_sp001.result
share/mysql/test/suite/rpl/r/rpl_row_sp002_innodb.result
share/mysql/test/suite/rpl/r/rpl_row_sp003.result
share/mysql/test/suite/rpl/r/rpl_row_sp005.result
share/mysql/test/suite/rpl/r/rpl_row_sp006_InnoDB.result
share/mysql/test/suite/rpl/r/rpl_row_sp007_innodb.result
share/mysql/test/suite/rpl/r/rpl_row_sp008.result
share/mysql/test/suite/rpl/r/rpl_row_sp009.result
share/mysql/test/suite/rpl/r/rpl_row_sp010.result
share/mysql/test/suite/rpl/r/rpl_row_sp011.result
share/mysql/test/suite/rpl/r/rpl_row_sp012.result
share/mysql/test/suite/rpl/r/rpl_row_tabledefs_2myisam.result
share/mysql/test/suite/rpl/r/rpl_row_tabledefs_3innodb.result
share/mysql/test/suite/rpl/r/rpl_row_tbl_metadata.result
share/mysql/test/suite/rpl/r/rpl_row_trig001.result
share/mysql/test/suite/rpl/r/rpl_row_trig002.result
share/mysql/test/suite/rpl/r/rpl_row_trig003.result
share/mysql/test/suite/rpl/r/rpl_row_trig004.result
share/mysql/test/suite/rpl/r/rpl_row_trunc_temp.result
share/mysql/test/suite/rpl/r/rpl_row_unsafe_funcs.result
share/mysql/test/suite/rpl/r/rpl_row_until.result
share/mysql/test/suite/rpl/r/rpl_row_utf16.result
share/mysql/test/suite/rpl/r/rpl_row_utf32.result
share/mysql/test/suite/rpl/r/rpl_row_view01.result
share/mysql/test/suite/rpl/r/rpl_row_wide_table.result
share/mysql/test/suite/rpl/r/rpl_savepoint.result
Changes 5.6.23: * The linked OpenSSL library for the MySQL Commercial Server has been updated from version 1.0.1j to version 1.0.1k. * Support for the SSL 2.0 and SSL 3.0 protocols has been disabled because they provide weak encryption. * yaSSL was upgraded to version 2.3.7. * The valid date range of the SSL certificates in mysql-test/std_data has been extended to the year 2029. * Bugs Fixed
2015-02-07 20:23:40 +01:00
share/mysql/test/suite/rpl/r/rpl_sbm_previous_gtid_event.result
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/rpl/r/rpl_seconds_behind_master.result
share/mysql/test/suite/rpl/r/rpl_semi_sync.result
Changes 5.6.12: * mysql_upgrade now verifies that the server version matches the version against which it was compiled, and exits if there is a mismatch. In addiion, a --version-check option permits specifying whether to enable version checking (the default), or disable checking if given as --skip-version-checking. * Bugs Fixed
2013-06-04 20:17:25 +02:00
share/mysql/test/suite/rpl/r/rpl_semi_sync_deadlock.result
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/rpl/r/rpl_semi_sync_event.result
Changes 5.6.21: The --skip-innodb option is now deprecated and its use results in a warning. It will be removed in a future MySQL release. This also applies to its synonyms (--innodb=OFF, --disable-innodb, and so forth). MySQL Enterprise Edition now includes a set of encryption functions based on the OpenSSL library that expose OpenSSL capabilities at the SQL level. Replication: The new variable simplified_binlog_gtid_recovery can be used to change the way binary log files are searched for previous GTIDs during recovery, speeding up the process when a large number of binary log files exist. Internally, spatial data types such as Geometry are represented as BLOB values, so when invoked with the --hex-blob option, mysqldump now displays spatial values in hex. Bugs Fixed...
2014-10-01 10:34:23 +02:00
share/mysql/test/suite/rpl/r/rpl_semi_sync_future_logpos.result
Changes 5.6.12: * mysql_upgrade now verifies that the server version matches the version against which it was compiled, and exits if there is a mismatch. In addiion, a --version-check option permits specifying whether to enable version checking (the default), or disable checking if given as --skip-version-checking. * Bugs Fixed
2013-06-04 20:17:25 +02:00
share/mysql/test/suite/rpl/r/rpl_semi_sync_group_commit_deadlock.result
share/mysql/test/suite/rpl/r/rpl_semi_sync_non_group_commit_deadlock.result
Changes 5.6.21: The --skip-innodb option is now deprecated and its use results in a warning. It will be removed in a future MySQL release. This also applies to its synonyms (--innodb=OFF, --disable-innodb, and so forth). MySQL Enterprise Edition now includes a set of encryption functions based on the OpenSSL library that expose OpenSSL capabilities at the SQL level. Replication: The new variable simplified_binlog_gtid_recovery can be used to change the way binary log files are searched for previous GTIDs during recovery, speeding up the process when a large number of binary log files exist. Internally, spatial data types such as Geometry are represented as BLOB values, so when invoked with the --hex-blob option, mysqldump now displays spatial values in hex. Bugs Fixed...
2014-10-01 10:34:23 +02:00
share/mysql/test/suite/rpl/r/rpl_semi_sync_shutdown_hang.result
Changes 5.6.20: Security Fix: The linked OpenSSL library for the MySQL 5.6 Commercial Server has been updated from version 1.0.1g to version 1.0.1h. Versions of OpenSSL prior to and including 1.0.1g are reported to be vulnerable to CVE-2014-0224. This change does not affect the Oracle-produced MySQL Community build of MySQL Server 5.6, which uses the yaSSL library instead. DTrace Support MySQL now includes DTrace support on Oracle Linux 6 or higher with UEK kernel. If DTrace is present, server builds will detect it with no special CMake options required. For information about using DTrace on MySQL, see Tracing mysqld Using DTrace. InnoDB Notes Important Change: Redo log writes for large, externally stored BLOB fields could overwrite the most recent checkpoint. The 5.6.20 patch limits the size of redo log BLOB writes to 10% of the redo log file size. The 5.7.5 patch addresses the bug without imposing a limitation. For MySQL 5.5, the bug remains a known limitation. As a result of the redo log BLOB write limit introduced for MySQL 5.6, innodb_log_file_size should be set to a value greater than 10 times the largest BLOB data size found in the rows of your tables plus the length of other variable length fields (VARCHAR, VARBINARY, and TEXT type fields). Failing to do so could result in “Row size too large” errors. No action is required if your innodb_log_file_size setting is already sufficiently large or your tables contain no BLOB data. Functionality Added or Changed Replication: The new system variable binlog_impossible_mode controls what happens if the server cannot write to the binary log, for example, due to a file error. For backward compatibility, the default for binlog_impossible_mode is IGNORE_ERROR, meaning the server logs the error, halts logging, and continues updates to the database. Setting this variable to ABORT_SERVER makes the server halt logging and shut down if it cannot write to the binary log. CMake support was updated to handle CMake version 3. New Debian7, Ubuntu12.04, and Ubuntu14.04 distribution support that was introduced with 5.6.17 now comes with the platform-specific packaging source placed under the packaging directory, in the deb-precise, deb-wheezy, and deb-trusty directories. Support for LinuxThreads has been removed from the source code. LinuxThreads was superseded by NPTL in Linux 2.6. By default, mysql_install_db creates a my.cnf file in the installation base directory using a template. This may be undesireable for some deployments. To enable this behavior to be suppressed, mysql_install_db now supports a --keep-my-cnf option to preserve any existing my.cnf file and not create a new my.cnf file. The mysqlhotcopy utility is now deprecated and will be removed in a future version of MySQL. Among the reasons for this: It works only for the MyISAM and ARCHIVE storage engines; it works on Unix but not Windows. Alternatives include mysqldump and MySQL Enterprise Backup. The timed_mutexes system variable has no effect and is deprecated. Bugs Fixed
2014-08-10 17:11:57 +02:00
share/mysql/test/suite/rpl/r/rpl_semi_sync_uninstall_plugin.result
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/rpl/r/rpl_sequential.result
share/mysql/test/suite/rpl/r/rpl_server_id1.result
share/mysql/test/suite/rpl/r/rpl_server_id2.result
share/mysql/test/suite/rpl/r/rpl_server_id_ignore.result
share/mysql/test/suite/rpl/r/rpl_server_uuid.result
share/mysql/test/suite/rpl/r/rpl_session_var.result
share/mysql/test/suite/rpl/r/rpl_set_charset.result
share/mysql/test/suite/rpl/r/rpl_set_null_innodb.result
share/mysql/test/suite/rpl/r/rpl_set_null_myisam.result
share/mysql/test/suite/rpl/r/rpl_show_errors.result
share/mysql/test/suite/rpl/r/rpl_show_master_info_file.result
share/mysql/test/suite/rpl/r/rpl_show_slave_hosts.result
share/mysql/test/suite/rpl/r/rpl_show_slave_running.result
Changes 5.6.23: * The linked OpenSSL library for the MySQL Commercial Server has been updated from version 1.0.1j to version 1.0.1k. * Support for the SSL 2.0 and SSL 3.0 protocols has been disabled because they provide weak encryption. * yaSSL was upgraded to version 2.3.7. * The valid date range of the SSL certificates in mysql-test/std_data has been extended to the year 2029. * Bugs Fixed
2015-02-07 20:23:40 +01:00
share/mysql/test/suite/rpl/r/rpl_show_slave_status_deadlock.result
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/rpl/r/rpl_skip_ddl_errors_cli.result
share/mysql/test/suite/rpl/r/rpl_skip_error.result
share/mysql/test/suite/rpl/r/rpl_skip_incident.result
Changes 5.6.17: Functionality Added or Changed Incompatible Change: The AES_ENCRYPT() and AES_DECRYPT() functions now permit control of the block encryption mode and take an optional initialization vector argument: The new block_encryption_mode system variable controls the mode for block-based encryption algorithms. Its default value is aes-128-ecb, which signifies encryption using a key length of 128 bits and ECB mode. An optional init_vector argument provides an initialization vector for encryption modes that require it: AES_ENCRYPT(str,key_str[,init_vector]) AES_DECRYPT(crypt_str,key_str[,init_vector]) A random string of bytes to use for the initialization vector can be produced by calling the new RANDOM_BYTES() function. For more information, see Encryption and Compression Functions. These changes make statements that use AES_ENCRYPT() or AES_DECRYPT() unsafe for statement-based replication and they cannot be stored in the query cache. Queries that use RANDOM_BYTES() are unsafe for statement-based replication and cannot be stored in the query cache. Incompatible Change: The ERROR_FOR_DIVISION_BY_ZERO, NO_ZERO_DATE, and NO_ZERO_IN_DATE SQL modes now are deprecated and setting the sql_mode value to include any of them generates a warning. In MySQL 5.7, these modes do nothing. Instead, their effects are included in the effects of strict SQL mode (STRICT_ALL_TABLES or STRICT_TRANS_TABLES). The motivation for the change in MySQL 5.7 is to reduce the number of SQL modes with an effect dependent on strict mode and make them part of strict mode itself. To make advance preparation for an upgrade to MySQL 5.7, see SQL Mode Changes in MySQL 5.7. That discussion provides guidelines to assess whether your applications will be affected by the SQL mode changes in MySQL 5.7. InnoDB: MySQL now supports rebuilding regular and partitioned InnoDB tables using online DDL (ALGORITHM=INPLACE) for the following operations: OPTIMIZE TABLE ALTER TABLE ... FORCE ALTER TABLE ... ENGINE=INNODB (when run on an InnoDB table) Online DDL support reduces table rebuild time and permits concurrent DML, which helps reduce user application downtime. For additional information, see Overview of Online DDL. On Solaris, mysql_config --libs now includes -R/path/to/library so that libraries can be found at runtime. mysql_install_db provides a more informative diagnostic message when required Perl modules are missing. The IGNORE clause for ALTER TABLE is now deprecated and will be removed in a future version of MySQL. ALTER IGNORE TABLE causes problems for replication, prevents online ALTER TABLE for unique index creation, and causes problems with foreign keys (rows removed in the parent table). Bugs Fixed
2014-03-31 12:32:13 +02:00
share/mysql/test/suite/rpl/r/rpl_skip_slave_err_warnings.result
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/rpl/r/rpl_slave_grp_exec.result
share/mysql/test/suite/rpl/r/rpl_slave_load_in.result
share/mysql/test/suite/rpl/r/rpl_slave_load_remove_tmpfile.result
share/mysql/test/suite/rpl/r/rpl_slave_load_tmpdir_not_exist.result
share/mysql/test/suite/rpl/r/rpl_slave_skip.result
share/mysql/test/suite/rpl/r/rpl_slave_start.result
share/mysql/test/suite/rpl/r/rpl_slave_status.result
share/mysql/test/suite/rpl/r/rpl_slow_query_log.result
share/mysql/test/suite/rpl/r/rpl_sp.result
share/mysql/test/suite/rpl/r/rpl_sp004.result
share/mysql/test/suite/rpl/r/rpl_sp_effects.result
Changes 5.6.24: * CMake support was updated to handle CMake version 3.1. * The server now includes its version number when it writes the initial “starting” message to the error log, to make it easier to tell which server instance error log output applies to. This value is the same as that available from the version system variable. * ALTER TABLE did not take advantage of fast alterations that might otherwise apply to the operation to be performed, if the table contained temporal columns found to be in pre-5.6.4 format (TIME, DATETIME, and TIMESTAMP columns without support for fractional seconds precision). * Statement digesting as done previously by the Performance Schema is now done at the SQL level regardless of whether the Performance Schema is compiled in and is available to other aspects of server operation that could benefit from it. The default space available for digesting is 1024 bytes, but can be changed at server startup using the max_digest_length system variable. * Bug fixes.
2015-04-08 12:38:48 +02:00
share/mysql/test/suite/rpl/r/rpl_sp_privileges.result
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/rpl/r/rpl_spec_variables.result
Changes 5.6.24: * CMake support was updated to handle CMake version 3.1. * The server now includes its version number when it writes the initial “starting” message to the error log, to make it easier to tell which server instance error log output applies to. This value is the same as that available from the version system variable. * ALTER TABLE did not take advantage of fast alterations that might otherwise apply to the operation to be performed, if the table contained temporal columns found to be in pre-5.6.4 format (TIME, DATETIME, and TIMESTAMP columns without support for fractional seconds precision). * Statement digesting as done previously by the Performance Schema is now done at the SQL level regardless of whether the Performance Schema is compiled in and is available to other aspects of server operation that could benefit from it. The default space available for digesting is 1024 bytes, but can be changed at server startup using the max_digest_length system variable. * Bug fixes.
2015-04-08 12:38:48 +02:00
share/mysql/test/suite/rpl/r/rpl_special_charset.result
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/rpl/r/rpl_sporadic_master.result
Changes 5.6.21: The --skip-innodb option is now deprecated and its use results in a warning. It will be removed in a future MySQL release. This also applies to its synonyms (--innodb=OFF, --disable-innodb, and so forth). MySQL Enterprise Edition now includes a set of encryption functions based on the OpenSSL library that expose OpenSSL capabilities at the SQL level. Replication: The new variable simplified_binlog_gtid_recovery can be used to change the way binary log files are searched for previous GTIDs during recovery, speeding up the process when a large number of binary log files exist. Internally, spatial data types such as Geometry are represented as BLOB values, so when invoked with the --hex-blob option, mysqldump now displays spatial values in hex. Bugs Fixed...
2014-10-01 10:34:23 +02:00
share/mysql/test/suite/rpl/r/rpl_sql_thread_killed_waiting_commit_lock.result
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/rpl/r/rpl_ssl.result
share/mysql/test/suite/rpl/r/rpl_ssl1.result
share/mysql/test/suite/rpl/r/rpl_stm_000001.result
share/mysql/test/suite/rpl/r/rpl_stm_EE_err2.result
share/mysql/test/suite/rpl/r/rpl_stm_auto_increment_bug33029.result
share/mysql/test/suite/rpl/r/rpl_stm_binlog_max_cache_size.result
share/mysql/test/suite/rpl/r/rpl_stm_conflicts.result
share/mysql/test/suite/rpl/r/rpl_stm_drop_create_temp_table.result
share/mysql/test/suite/rpl/r/rpl_stm_flsh_tbls.result
share/mysql/test/suite/rpl/r/rpl_stm_found_rows.result
Changes 5.6.27: * InnoDB: The new innodb_numa_interleave read-only configuration option allows you to enable the NUMA interleave memory policy for allocation of the InnoDB buffer pool. When innodb_numa_interleave is enabled, the NUMA memory policy is set to MPOL_INTERLEAVE for the mysqld process. After the InnoDB buffer pool is allocated, the NUMA memory policy is set back to MPOL_DEFAULT. This option is only available on NUMA-enabled systems. * yaSSL was upgraded to version 2.3.8. * RPM .spec files were updated so that MySQL Server builds from source RPM packages will include the proper files to take advantage of operating system NUMA capabilities. This introduces a runtime dependency on libnuma.so.1. RPM and yum detect this and refuse to install if that library is not installed. * InnoDB: Reloading a table that was evicted while empty caused an AUTO_INCREMENT value to be reset. * InnoDB: Memory allocation sanity checks were added to the memcached code. * InnoDB: A memcached flush_all command raised an assertion. A function that starts a transaction was called from within assertion code. * InnoDB: A data corruption occurred on ARM64. GCC builtins did not issue the correct fences when setting or unsetting the lock word. * InnoDB: Server shutdown was delayed waiting for the purge thread to exit. To avoid this problem, the number of calls to trx_purge() was reduced, and the trx_purge() batch size was reduced to 20. * InnoDB: In READ COMMITTED mode, a REPLACE operation on a unique secondary index resulted in a constraint violation. * InnoDB: The IBUF_BITMAP_FREE bit indicated that there was more free space in the leaf page than was actually available. * InnoDB: Setting lower_case_table_names=0 on a case-insensitive file system could result in a hang condition when running an INSERT INTO ... SELECT ... FROM tbl_name operation with the wrong tbl_name letter case. An error message is now printed and the server exits when attempting to start the server with --lower_case_table_names=0 on a case-insensitive file system. * InnoDB: The server failed to start with an innodb_force_recovery setting greater than 3. InnoDB was set to read-only mode before redo logs were applied. * InnoDB: The trx_sys_read_pertable_file_format_id() function reported the wrong file format. * Partitioning: CREATE TABLE statements that used an invalid function in a subpartitioning expression did not always fail gracefully as expected. * Partitioning: Error handling for failed partitioning-related ALTER TABLE operations against non-partitioned tables was not performed correctly * Partitioning: ALTER TABLE when executed from a stored procedure did not always work correctly with tables partitioned by RANGE. * Replication: Repeatedly checking for ERR_LOCK_WAIT_TIMEOUT (as done, for example by repeatedly executing SHOW SLAVE STATUS) during a prolonged write lock on a table led to an assert. * Replication: If statement based logging was in use, when updating multiple tables in a single statement, a single transaction could be logged as two different transactions. This was due to the binary logging process not properly identifying statements which were operating over transactional tables. The fix ensures that they are correctly identified, even if such statements do not change the contents of the tables.
2015-10-03 14:46:13 +02:00
share/mysql/test/suite/rpl/r/rpl_stm_ignore.result
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/rpl/r/rpl_stm_implicit_commit_binlog.result
share/mysql/test/suite/rpl/r/rpl_stm_innodb.result
share/mysql/test/suite/rpl/r/rpl_stm_insert_delayed.result
share/mysql/test/suite/rpl/r/rpl_stm_lcase_tblnames.result
share/mysql/test/suite/rpl/r/rpl_stm_loaddata_concurrent.result
share/mysql/test/suite/rpl/r/rpl_stm_loadfile.result
share/mysql/test/suite/rpl/r/rpl_stm_log.result
share/mysql/test/suite/rpl/r/rpl_stm_max_relay_size.result
share/mysql/test/suite/rpl/r/rpl_stm_mix_mts_show_relaylog_events.result
Changes 5.6.27: * InnoDB: The new innodb_numa_interleave read-only configuration option allows you to enable the NUMA interleave memory policy for allocation of the InnoDB buffer pool. When innodb_numa_interleave is enabled, the NUMA memory policy is set to MPOL_INTERLEAVE for the mysqld process. After the InnoDB buffer pool is allocated, the NUMA memory policy is set back to MPOL_DEFAULT. This option is only available on NUMA-enabled systems. * yaSSL was upgraded to version 2.3.8. * RPM .spec files were updated so that MySQL Server builds from source RPM packages will include the proper files to take advantage of operating system NUMA capabilities. This introduces a runtime dependency on libnuma.so.1. RPM and yum detect this and refuse to install if that library is not installed. * InnoDB: Reloading a table that was evicted while empty caused an AUTO_INCREMENT value to be reset. * InnoDB: Memory allocation sanity checks were added to the memcached code. * InnoDB: A memcached flush_all command raised an assertion. A function that starts a transaction was called from within assertion code. * InnoDB: A data corruption occurred on ARM64. GCC builtins did not issue the correct fences when setting or unsetting the lock word. * InnoDB: Server shutdown was delayed waiting for the purge thread to exit. To avoid this problem, the number of calls to trx_purge() was reduced, and the trx_purge() batch size was reduced to 20. * InnoDB: In READ COMMITTED mode, a REPLACE operation on a unique secondary index resulted in a constraint violation. * InnoDB: The IBUF_BITMAP_FREE bit indicated that there was more free space in the leaf page than was actually available. * InnoDB: Setting lower_case_table_names=0 on a case-insensitive file system could result in a hang condition when running an INSERT INTO ... SELECT ... FROM tbl_name operation with the wrong tbl_name letter case. An error message is now printed and the server exits when attempting to start the server with --lower_case_table_names=0 on a case-insensitive file system. * InnoDB: The server failed to start with an innodb_force_recovery setting greater than 3. InnoDB was set to read-only mode before redo logs were applied. * InnoDB: The trx_sys_read_pertable_file_format_id() function reported the wrong file format. * Partitioning: CREATE TABLE statements that used an invalid function in a subpartitioning expression did not always fail gracefully as expected. * Partitioning: Error handling for failed partitioning-related ALTER TABLE operations against non-partitioned tables was not performed correctly * Partitioning: ALTER TABLE when executed from a stored procedure did not always work correctly with tables partitioned by RANGE. * Replication: Repeatedly checking for ERR_LOCK_WAIT_TIMEOUT (as done, for example by repeatedly executing SHOW SLAVE STATUS) during a prolonged write lock on a table led to an assert. * Replication: If statement based logging was in use, when updating multiple tables in a single statement, a single transaction could be logged as two different transactions. This was due to the binary logging process not properly identifying statements which were operating over transactional tables. The fix ensures that they are correctly identified, even if such statements do not change the contents of the tables.
2015-10-03 14:46:13 +02:00
share/mysql/test/suite/rpl/r/rpl_stm_mix_rollback_to_savepoint.result
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/rpl/r/rpl_stm_mix_show_relaylog_events.result
share/mysql/test/suite/rpl/r/rpl_stm_mixed_crash_safe.result
Changes 5.6.11: 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. 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. mysql_config_editor now supports --port and --socket options for specifying TCP/IP port number and Unix socket file name. 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. The only supported value for the innodb_mirrored_log_groups system variable is 1, so this variable is now deprecated. Setting it to 1 at startup results in a warning. Setting it to a value other than 1 at startup results in an error and the server exits. This variable will be removed in a future release.
2013-04-20 10:06:01 +02:00
share/mysql/test/suite/rpl/r/rpl_stm_mixed_mts_crash_safe.result
share/mysql/test/suite/rpl/r/rpl_stm_mixed_mts_rec_crash_safe.result
share/mysql/test/suite/rpl/r/rpl_stm_mixed_mts_rec_crash_safe_checksum.result
share/mysql/test/suite/rpl/r/rpl_stm_mixed_mts_rec_crash_safe_small.result
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/rpl/r/rpl_stm_mixing_engines.result
share/mysql/test/suite/rpl/r/rpl_stm_multi_query.result
share/mysql/test/suite/rpl/r/rpl_stm_no_op.result
share/mysql/test/suite/rpl/r/rpl_stm_relay_ign_space.result
share/mysql/test/suite/rpl/r/rpl_stm_reset_slave.result
share/mysql/test/suite/rpl/r/rpl_stm_sql_mode.result
share/mysql/test/suite/rpl/r/rpl_stm_start_stop_slave.result
share/mysql/test/suite/rpl/r/rpl_stm_stop_middle_group.result
share/mysql/test/suite/rpl/r/rpl_stm_until.result
Changes 5.6.21: The --skip-innodb option is now deprecated and its use results in a warning. It will be removed in a future MySQL release. This also applies to its synonyms (--innodb=OFF, --disable-innodb, and so forth). MySQL Enterprise Edition now includes a set of encryption functions based on the OpenSSL library that expose OpenSSL capabilities at the SQL level. Replication: The new variable simplified_binlog_gtid_recovery can be used to change the way binary log files are searched for previous GTIDs during recovery, speeding up the process when a large number of binary log files exist. Internally, spatial data types such as Geometry are represented as BLOB values, so when invoked with the --hex-blob option, mysqldump now displays spatial values in hex. Bugs Fixed...
2014-10-01 10:34:23 +02:00
share/mysql/test/suite/rpl/r/rpl_stm_until_pos_middle_gtid.result
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/rpl/r/rpl_stm_user_variables.result
share/mysql/test/suite/rpl/r/rpl_stop_slave.result
share/mysql/test/suite/rpl/r/rpl_switch_stm_row_mixed.result
share/mysql/test/suite/rpl/r/rpl_sync.result
share/mysql/test/suite/rpl/r/rpl_temp_table.result
share/mysql/test/suite/rpl/r/rpl_temp_table_mix_row.result
share/mysql/test/suite/rpl/r/rpl_temporal_fractional.result
share/mysql/test/suite/rpl/r/rpl_temporary.result
Changes 5.6.27: * InnoDB: The new innodb_numa_interleave read-only configuration option allows you to enable the NUMA interleave memory policy for allocation of the InnoDB buffer pool. When innodb_numa_interleave is enabled, the NUMA memory policy is set to MPOL_INTERLEAVE for the mysqld process. After the InnoDB buffer pool is allocated, the NUMA memory policy is set back to MPOL_DEFAULT. This option is only available on NUMA-enabled systems. * yaSSL was upgraded to version 2.3.8. * RPM .spec files were updated so that MySQL Server builds from source RPM packages will include the proper files to take advantage of operating system NUMA capabilities. This introduces a runtime dependency on libnuma.so.1. RPM and yum detect this and refuse to install if that library is not installed. * InnoDB: Reloading a table that was evicted while empty caused an AUTO_INCREMENT value to be reset. * InnoDB: Memory allocation sanity checks were added to the memcached code. * InnoDB: A memcached flush_all command raised an assertion. A function that starts a transaction was called from within assertion code. * InnoDB: A data corruption occurred on ARM64. GCC builtins did not issue the correct fences when setting or unsetting the lock word. * InnoDB: Server shutdown was delayed waiting for the purge thread to exit. To avoid this problem, the number of calls to trx_purge() was reduced, and the trx_purge() batch size was reduced to 20. * InnoDB: In READ COMMITTED mode, a REPLACE operation on a unique secondary index resulted in a constraint violation. * InnoDB: The IBUF_BITMAP_FREE bit indicated that there was more free space in the leaf page than was actually available. * InnoDB: Setting lower_case_table_names=0 on a case-insensitive file system could result in a hang condition when running an INSERT INTO ... SELECT ... FROM tbl_name operation with the wrong tbl_name letter case. An error message is now printed and the server exits when attempting to start the server with --lower_case_table_names=0 on a case-insensitive file system. * InnoDB: The server failed to start with an innodb_force_recovery setting greater than 3. InnoDB was set to read-only mode before redo logs were applied. * InnoDB: The trx_sys_read_pertable_file_format_id() function reported the wrong file format. * Partitioning: CREATE TABLE statements that used an invalid function in a subpartitioning expression did not always fail gracefully as expected. * Partitioning: Error handling for failed partitioning-related ALTER TABLE operations against non-partitioned tables was not performed correctly * Partitioning: ALTER TABLE when executed from a stored procedure did not always work correctly with tables partitioned by RANGE. * Replication: Repeatedly checking for ERR_LOCK_WAIT_TIMEOUT (as done, for example by repeatedly executing SHOW SLAVE STATUS) during a prolonged write lock on a table led to an assert. * Replication: If statement based logging was in use, when updating multiple tables in a single statement, a single transaction could be logged as two different transactions. This was due to the binary logging process not properly identifying statements which were operating over transactional tables. The fix ensures that they are correctly identified, even if such statements do not change the contents of the tables.
2015-10-03 14:46:13 +02:00
share/mysql/test/suite/rpl/r/rpl_temporary_error_table_repository.result
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/rpl/r/rpl_temporary_errors.result
share/mysql/test/suite/rpl/r/rpl_test_framework.result
Changes 5.6.20: Security Fix: The linked OpenSSL library for the MySQL 5.6 Commercial Server has been updated from version 1.0.1g to version 1.0.1h. Versions of OpenSSL prior to and including 1.0.1g are reported to be vulnerable to CVE-2014-0224. This change does not affect the Oracle-produced MySQL Community build of MySQL Server 5.6, which uses the yaSSL library instead. DTrace Support MySQL now includes DTrace support on Oracle Linux 6 or higher with UEK kernel. If DTrace is present, server builds will detect it with no special CMake options required. For information about using DTrace on MySQL, see Tracing mysqld Using DTrace. InnoDB Notes Important Change: Redo log writes for large, externally stored BLOB fields could overwrite the most recent checkpoint. The 5.6.20 patch limits the size of redo log BLOB writes to 10% of the redo log file size. The 5.7.5 patch addresses the bug without imposing a limitation. For MySQL 5.5, the bug remains a known limitation. As a result of the redo log BLOB write limit introduced for MySQL 5.6, innodb_log_file_size should be set to a value greater than 10 times the largest BLOB data size found in the rows of your tables plus the length of other variable length fields (VARCHAR, VARBINARY, and TEXT type fields). Failing to do so could result in “Row size too large” errors. No action is required if your innodb_log_file_size setting is already sufficiently large or your tables contain no BLOB data. Functionality Added or Changed Replication: The new system variable binlog_impossible_mode controls what happens if the server cannot write to the binary log, for example, due to a file error. For backward compatibility, the default for binlog_impossible_mode is IGNORE_ERROR, meaning the server logs the error, halts logging, and continues updates to the database. Setting this variable to ABORT_SERVER makes the server halt logging and shut down if it cannot write to the binary log. CMake support was updated to handle CMake version 3. New Debian7, Ubuntu12.04, and Ubuntu14.04 distribution support that was introduced with 5.6.17 now comes with the platform-specific packaging source placed under the packaging directory, in the deb-precise, deb-wheezy, and deb-trusty directories. Support for LinuxThreads has been removed from the source code. LinuxThreads was superseded by NPTL in Linux 2.6. By default, mysql_install_db creates a my.cnf file in the installation base directory using a template. This may be undesireable for some deployments. To enable this behavior to be suppressed, mysql_install_db now supports a --keep-my-cnf option to preserve any existing my.cnf file and not create a new my.cnf file. The mysqlhotcopy utility is now deprecated and will be removed in a future version of MySQL. Among the reasons for this: It works only for the MyISAM and ARCHIVE storage engines; it works on Unix but not Windows. Alternatives include mysqldump and MySQL Enterprise Backup. The timed_mutexes system variable has no effect and is deprecated. Bugs Fixed
2014-08-10 17:11:57 +02:00
share/mysql/test/suite/rpl/r/rpl_timestamp_upgrage_55.result
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/rpl/r/rpl_timezone.result
share/mysql/test/suite/rpl/r/rpl_tmp_table_and_DDL.result
share/mysql/test/suite/rpl/r/rpl_trigger.result
share/mysql/test/suite/rpl/r/rpl_trunc_temp.result
share/mysql/test/suite/rpl/r/rpl_truncate_2myisam.result
share/mysql/test/suite/rpl/r/rpl_truncate_3innodb.result
share/mysql/test/suite/rpl/r/rpl_typeconv.result
share/mysql/test/suite/rpl/r/rpl_typeconv_innodb.result
share/mysql/test/suite/rpl/r/rpl_udf.result
Changes 5.6.23: * The linked OpenSSL library for the MySQL Commercial Server has been updated from version 1.0.1j to version 1.0.1k. * Support for the SSL 2.0 and SSL 3.0 protocols has been disabled because they provide weak encryption. * yaSSL was upgraded to version 2.3.7. * The valid date range of the SSL certificates in mysql-test/std_data has been extended to the year 2029. * Bugs Fixed
2015-02-07 20:23:40 +01:00
share/mysql/test/suite/rpl/r/rpl_unknown_ignorable_event.result
Changes 5.6.29: * InnoDB: A new InnoDB configuration option, innodb_tmpdir, allows you to configure a separate temporary file directory for online ALTER TABLE operations. This option was introduced to help avoid tmpdir overflows that could occur as a result of large temporary files created during online ALTER TABLE operations. innodb_tmpdir is a SESSION variable and can be configured dynamically using a SET statement. * yaSSL was upgraded to version 2.3.9. This upgrade corrects an issue in which yaSSL handled only cases of zero or one leading zeros for the key agreement instead of potentially any number, which in rare cases could cause connections to fail when using DHE cipher suites. * The Valgrind function signature in mysql-test/valgrind.supp was upgraded for Valgrind 3.11. * Bugs Fixed
2016-02-28 09:58:03 +01:00
share/mysql/test/suite/rpl/r/rpl_unsafe_statements.result
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/rpl/r/rpl_user.result
share/mysql/test/suite/rpl/r/rpl_user_variables.result
share/mysql/test/suite/rpl/r/rpl_variables.result
share/mysql/test/suite/rpl/r/rpl_variables_stm.result
share/mysql/test/suite/rpl/r/rpl_view.result
share/mysql/test/suite/rpl/r/rpl_view_multi.result
share/mysql/test/suite/rpl/rpl_1slave_base.cnf
share/mysql/test/suite/rpl/t/disabled.def
share/mysql/test/suite/rpl/t/rpl_000010-slave.opt
share/mysql/test/suite/rpl/t/rpl_000010.test
share/mysql/test/suite/rpl/t/rpl_000011.test
share/mysql/test/suite/rpl/t/rpl_000013.test
share/mysql/test/suite/rpl/t/rpl_000017.test
Changes 5.6.20: Security Fix: The linked OpenSSL library for the MySQL 5.6 Commercial Server has been updated from version 1.0.1g to version 1.0.1h. Versions of OpenSSL prior to and including 1.0.1g are reported to be vulnerable to CVE-2014-0224. This change does not affect the Oracle-produced MySQL Community build of MySQL Server 5.6, which uses the yaSSL library instead. DTrace Support MySQL now includes DTrace support on Oracle Linux 6 or higher with UEK kernel. If DTrace is present, server builds will detect it with no special CMake options required. For information about using DTrace on MySQL, see Tracing mysqld Using DTrace. InnoDB Notes Important Change: Redo log writes for large, externally stored BLOB fields could overwrite the most recent checkpoint. The 5.6.20 patch limits the size of redo log BLOB writes to 10% of the redo log file size. The 5.7.5 patch addresses the bug without imposing a limitation. For MySQL 5.5, the bug remains a known limitation. As a result of the redo log BLOB write limit introduced for MySQL 5.6, innodb_log_file_size should be set to a value greater than 10 times the largest BLOB data size found in the rows of your tables plus the length of other variable length fields (VARCHAR, VARBINARY, and TEXT type fields). Failing to do so could result in “Row size too large” errors. No action is required if your innodb_log_file_size setting is already sufficiently large or your tables contain no BLOB data. Functionality Added or Changed Replication: The new system variable binlog_impossible_mode controls what happens if the server cannot write to the binary log, for example, due to a file error. For backward compatibility, the default for binlog_impossible_mode is IGNORE_ERROR, meaning the server logs the error, halts logging, and continues updates to the database. Setting this variable to ABORT_SERVER makes the server halt logging and shut down if it cannot write to the binary log. CMake support was updated to handle CMake version 3. New Debian7, Ubuntu12.04, and Ubuntu14.04 distribution support that was introduced with 5.6.17 now comes with the platform-specific packaging source placed under the packaging directory, in the deb-precise, deb-wheezy, and deb-trusty directories. Support for LinuxThreads has been removed from the source code. LinuxThreads was superseded by NPTL in Linux 2.6. By default, mysql_install_db creates a my.cnf file in the installation base directory using a template. This may be undesireable for some deployments. To enable this behavior to be suppressed, mysql_install_db now supports a --keep-my-cnf option to preserve any existing my.cnf file and not create a new my.cnf file. The mysqlhotcopy utility is now deprecated and will be removed in a future version of MySQL. Among the reasons for this: It works only for the MyISAM and ARCHIVE storage engines; it works on Unix but not Windows. Alternatives include mysqldump and MySQL Enterprise Backup. The timed_mutexes system variable has no effect and is deprecated. Bugs Fixed
2014-08-10 17:11:57 +02:00
share/mysql/test/suite/rpl/t/rpl_4threads_deadlock.test
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/rpl/t/rpl_DML_error.test
share/mysql/test/suite/rpl/t/rpl_EE_err.test
share/mysql/test/suite/rpl/t/rpl_LD_INFILE.test
share/mysql/test/suite/rpl/t/rpl_alter.test
share/mysql/test/suite/rpl/t/rpl_alter_db.test
share/mysql/test/suite/rpl/t/rpl_alter_repository.test
Changes 5.6.24: * CMake support was updated to handle CMake version 3.1. * The server now includes its version number when it writes the initial “starting” message to the error log, to make it easier to tell which server instance error log output applies to. This value is the same as that available from the version system variable. * ALTER TABLE did not take advantage of fast alterations that might otherwise apply to the operation to be performed, if the table contained temporal columns found to be in pre-5.6.4 format (TIME, DATETIME, and TIMESTAMP columns without support for fractional seconds precision). * Statement digesting as done previously by the Performance Schema is now done at the SQL level regardless of whether the Performance Schema is compiled in and is available to other aspects of server operation that could benefit from it. The default space available for digesting is 1024 bytes, but can be changed at server startup using the max_digest_length system variable. * Bug fixes.
2015-04-08 12:38:48 +02:00
share/mysql/test/suite/rpl/t/rpl_apply_binlog_with_anonymous_gtid.test
share/mysql/test/suite/rpl/t/rpl_apply_binlog_with_anonymous_gtid_when_gtid_mode_on.test
share/mysql/test/suite/rpl/t/rpl_apply_binlog_with_gtid_when_gtid_mode_off.test
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/rpl/t/rpl_auto_increment-master.opt
share/mysql/test/suite/rpl/t/rpl_auto_increment.test
share/mysql/test/suite/rpl/t/rpl_auto_increment_11932.test
share/mysql/test/suite/rpl/t/rpl_auto_increment_bug33029.test
share/mysql/test/suite/rpl/t/rpl_auto_increment_bug45679.test
share/mysql/test/suite/rpl/t/rpl_auto_increment_update_failure.test
Changes 5.6.29: * InnoDB: A new InnoDB configuration option, innodb_tmpdir, allows you to configure a separate temporary file directory for online ALTER TABLE operations. This option was introduced to help avoid tmpdir overflows that could occur as a result of large temporary files created during online ALTER TABLE operations. innodb_tmpdir is a SESSION variable and can be configured dynamically using a SET statement. * yaSSL was upgraded to version 2.3.9. This upgrade corrects an issue in which yaSSL handled only cases of zero or one leading zeros for the key agreement instead of potentially any number, which in rare cases could cause connections to fail when using DHE cipher suites. * The Valgrind function signature in mysql-test/valgrind.supp was upgraded for Valgrind 3.11. * Bugs Fixed
2016-02-28 09:58:03 +01:00
share/mysql/test/suite/rpl/t/rpl_autogen_query_multi_byte_char.test
Changes 5.6.24: * CMake support was updated to handle CMake version 3.1. * The server now includes its version number when it writes the initial “starting” message to the error log, to make it easier to tell which server instance error log output applies to. This value is the same as that available from the version system variable. * ALTER TABLE did not take advantage of fast alterations that might otherwise apply to the operation to be performed, if the table contained temporal columns found to be in pre-5.6.4 format (TIME, DATETIME, and TIMESTAMP columns without support for fractional seconds precision). * Statement digesting as done previously by the Performance Schema is now done at the SQL level regardless of whether the Performance Schema is compiled in and is available to other aspects of server operation that could benefit from it. The default space available for digesting is 1024 bytes, but can be changed at server startup using the max_digest_length system variable. * Bug fixes.
2015-04-08 12:38:48 +02:00
share/mysql/test/suite/rpl/t/rpl_avoid_temporal_upgrade.test
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/rpl/t/rpl_begin_commit_rollback-master.opt
share/mysql/test/suite/rpl/t/rpl_begin_commit_rollback-slave.opt
share/mysql/test/suite/rpl/t/rpl_begin_commit_rollback.test
share/mysql/test/suite/rpl/t/rpl_binlog_corruption.test
share/mysql/test/suite/rpl/t/rpl_binlog_errors-master.opt
share/mysql/test/suite/rpl/t/rpl_binlog_errors.test
share/mysql/test/suite/rpl/t/rpl_binlog_gcommit_options-master.opt
share/mysql/test/suite/rpl/t/rpl_binlog_gcommit_options.test
share/mysql/test/suite/rpl/t/rpl_binlog_grant.test
share/mysql/test/suite/rpl/t/rpl_binlog_index.test
share/mysql/test/suite/rpl/t/rpl_bit.test
share/mysql/test/suite/rpl/t/rpl_bit_npk.test
share/mysql/test/suite/rpl/t/rpl_blackhole.test
share/mysql/test/suite/rpl/t/rpl_bug26395.test
share/mysql/test/suite/rpl/t/rpl_bug31076.test
share/mysql/test/suite/rpl/t/rpl_bug33931-master.opt
share/mysql/test/suite/rpl/t/rpl_bug33931.test
share/mysql/test/suite/rpl/t/rpl_bug37426.test
share/mysql/test/suite/rpl/t/rpl_bug38694-slave.opt
share/mysql/test/suite/rpl/t/rpl_bug38694.test
share/mysql/test/suite/rpl/t/rpl_bug41902-slave.opt
share/mysql/test/suite/rpl/t/rpl_bug41902.test
share/mysql/test/suite/rpl/t/rpl_change_master.test
share/mysql/test/suite/rpl/t/rpl_change_master_crash_safe-slave.opt
share/mysql/test/suite/rpl/t/rpl_change_master_crash_safe.test
share/mysql/test/suite/rpl/t/rpl_change_master_dbug.test
share/mysql/test/suite/rpl/t/rpl_charset.test
share/mysql/test/suite/rpl/t/rpl_charset_sjis.test
share/mysql/test/suite/rpl/t/rpl_check_gtid.test
share/mysql/test/suite/rpl/t/rpl_checksum-master.opt
share/mysql/test/suite/rpl/t/rpl_checksum.test
share/mysql/test/suite/rpl/t/rpl_checksum_cache.test
share/mysql/test/suite/rpl/t/rpl_checksum_undef.test
share/mysql/test/suite/rpl/t/rpl_circular_for_4_hosts-master.opt
share/mysql/test/suite/rpl/t/rpl_circular_for_4_hosts.cnf
share/mysql/test/suite/rpl/t/rpl_circular_for_4_hosts.test
share/mysql/test/suite/rpl/t/rpl_colSize.test
share/mysql/test/suite/rpl/t/rpl_commit_after_flush.test
share/mysql/test/suite/rpl/t/rpl_concurrency_error-master.opt
share/mysql/test/suite/rpl/t/rpl_concurrency_error.test
share/mysql/test/suite/rpl/t/rpl_conditional_comments.test
share/mysql/test/suite/rpl/t/rpl_connection.test
share/mysql/test/suite/rpl/t/rpl_corruption-master.opt
share/mysql/test/suite/rpl/t/rpl_corruption-slave.opt
share/mysql/test/suite/rpl/t/rpl_corruption.test
share/mysql/test/suite/rpl/t/rpl_crash_safe_master.test
Changes 5.6.27: * InnoDB: The new innodb_numa_interleave read-only configuration option allows you to enable the NUMA interleave memory policy for allocation of the InnoDB buffer pool. When innodb_numa_interleave is enabled, the NUMA memory policy is set to MPOL_INTERLEAVE for the mysqld process. After the InnoDB buffer pool is allocated, the NUMA memory policy is set back to MPOL_DEFAULT. This option is only available on NUMA-enabled systems. * yaSSL was upgraded to version 2.3.8. * RPM .spec files were updated so that MySQL Server builds from source RPM packages will include the proper files to take advantage of operating system NUMA capabilities. This introduces a runtime dependency on libnuma.so.1. RPM and yum detect this and refuse to install if that library is not installed. * InnoDB: Reloading a table that was evicted while empty caused an AUTO_INCREMENT value to be reset. * InnoDB: Memory allocation sanity checks were added to the memcached code. * InnoDB: A memcached flush_all command raised an assertion. A function that starts a transaction was called from within assertion code. * InnoDB: A data corruption occurred on ARM64. GCC builtins did not issue the correct fences when setting or unsetting the lock word. * InnoDB: Server shutdown was delayed waiting for the purge thread to exit. To avoid this problem, the number of calls to trx_purge() was reduced, and the trx_purge() batch size was reduced to 20. * InnoDB: In READ COMMITTED mode, a REPLACE operation on a unique secondary index resulted in a constraint violation. * InnoDB: The IBUF_BITMAP_FREE bit indicated that there was more free space in the leaf page than was actually available. * InnoDB: Setting lower_case_table_names=0 on a case-insensitive file system could result in a hang condition when running an INSERT INTO ... SELECT ... FROM tbl_name operation with the wrong tbl_name letter case. An error message is now printed and the server exits when attempting to start the server with --lower_case_table_names=0 on a case-insensitive file system. * InnoDB: The server failed to start with an innodb_force_recovery setting greater than 3. InnoDB was set to read-only mode before redo logs were applied. * InnoDB: The trx_sys_read_pertable_file_format_id() function reported the wrong file format. * Partitioning: CREATE TABLE statements that used an invalid function in a subpartitioning expression did not always fail gracefully as expected. * Partitioning: Error handling for failed partitioning-related ALTER TABLE operations against non-partitioned tables was not performed correctly * Partitioning: ALTER TABLE when executed from a stored procedure did not always work correctly with tables partitioned by RANGE. * Replication: Repeatedly checking for ERR_LOCK_WAIT_TIMEOUT (as done, for example by repeatedly executing SHOW SLAVE STATUS) during a prolonged write lock on a table led to an assert. * Replication: If statement based logging was in use, when updating multiple tables in a single statement, a single transaction could be logged as two different transactions. This was due to the binary logging process not properly identifying statements which were operating over transactional tables. The fix ensures that they are correctly identified, even if such statements do not change the contents of the tables.
2015-10-03 14:46:13 +02:00
share/mysql/test/suite/rpl/t/rpl_crc_check-master.opt
share/mysql/test/suite/rpl/t/rpl_crc_check.test
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/rpl/t/rpl_create_database-master.opt
share/mysql/test/suite/rpl/t/rpl_create_database-slave.opt
share/mysql/test/suite/rpl/t/rpl_create_database.test
Changes 5.6.19: Functionality Added or Changed The obsolete and unmaintained charset2html utility has been removed from MySQL distributions. The mysqlbug, mysql_waitpid, and mysql_zap utilities have been deprecated and will be removed in MySQL 5.7. Bugs Fixed InnoDB: After upgrading from 5.6.10 to MySQL versions up to and including MySQL 5.6.18, InnoDB would attempt to rename obsolete full-text search auxiliary tables on server startup, resulting in an assertion failure. InnoDB: For each insert, memset would be called three times to allocate memory for system fields. To reduce CPU usage, the three memset calls are now combined into a single call. InnoDB: Enabling the InnoDB Table Monitor would result in a ib_table->stat_initialized assertion failure. InnoDB: Setting innodb_max_dirty_pages_pct=0 would leave 1% of dirty pages unflushed. Buffer pool flushing is initiated when the percentage of dirty pages is greater innodb_max_dirty_pages_pct. The internal variables that store the innodb_max_dirty_pages_pct value and the percentage of dirty pages (buf_get_modified_ratio_pct and srv_max_buf_pool_modified_pct) were defined as unsigned integer data types, which meant that a innodb_max_dirty_pages_pct value of 0 required a dirty pages percentage of 1 or greater to initiate buffer pool flushing. To address this problem, the buf_get_modified_ratio_pct and srv_max_buf_pool_modified_pct internal variables are redefined as double data types, which changes the range value for innodb_max_dirty_pages_pct and innodb_max_dirty_pages_pct_lwm from 0 .. 99 to 0 .. 99.99. Additionally, buffer pool flushing is now initiated when the percentage of dirty pages is “greater than or equal to” innodb_max_dirty_pages_pct. Replication: Log rotation events could cause group_relay_log_pos to be moved forward incorrectly within a group. This meant that, when the transaction was retried, or if the SQL thread was stopped in the middle of a transaction following one or more log rotations (such that the transaction or group spanned multiple relay log files), part or all of the group was silently skipped. This issue has been addressed by correcting a problem in the logic used to avoid touching the coordinates of the SQL thread when updating the log position as part of a relay log rotation whereby it was possible to update the SQL thread's coordinates when not using a multi-threaded slave, even in the middle of a group. Replication: When running the server with --gtid-mode=ON, STOP SLAVE followed by START SLAVE resulted in a mismatch between the information provided by INFORMATION_SCHEMA.INNODB_TEMP_TABLE_INFO and the Slave_open_temp_tables status variable: the INNODB_TEMP_TABLE_INFO table showed that no temporary tables existed, but Slave_open_temp_tables had a nonzero value. Replication: In certain cases, the server mishandled triggers and stored procedures that tried to modify other tables when called by CREATE TABLE ... SELECT. This is now handled correctly as an error. Replication: When used on a table employing a transactional storage engine, a failed TRUNCATE TABLE was still written to the binary log and thus replayed on the slave. This could lead to inconsistency when the master retained data that was removed on the slave. Now in such cases TRUNCATE TABLE is logged only when it executes successfully. Replication: The server did not always handle the auto.cnf file correctly in cases where this file's permissions were incorrect. Replication: When the binary log was rotated due to receipt of a SIGHUP signal, the new binary log did not contain the Previous_gtid_event required for subsequent processing of that binary log's GTID events. Now when SIGHUP is received, steps are taken to insure that the server writes the necessary Previous_gtid_event to the new log before writing any GTID events to the new log.
2014-06-02 09:30:38 +02:00
share/mysql/test/suite/rpl/t/rpl_create_drop_temp_table.test
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/rpl/t/rpl_create_if_not_exists.test
share/mysql/test/suite/rpl/t/rpl_create_tmp_table_if_not_exists.test
share/mysql/test/suite/rpl/t/rpl_critical_errors.test
share/mysql/test/suite/rpl/t/rpl_cross_version-master.opt
share/mysql/test/suite/rpl/t/rpl_cross_version.test
share/mysql/test/suite/rpl/t/rpl_current_user-master.opt
share/mysql/test/suite/rpl/t/rpl_current_user.cnf
share/mysql/test/suite/rpl/t/rpl_current_user.test
share/mysql/test/suite/rpl/t/rpl_ddl.test
share/mysql/test/suite/rpl/t/rpl_deadlock_innodb-slave.opt
share/mysql/test/suite/rpl/t/rpl_deadlock_innodb.test
share/mysql/test/suite/rpl/t/rpl_delayed_slave.test
share/mysql/test/suite/rpl/t/rpl_delete_no_where.test
share/mysql/test/suite/rpl/t/rpl_do_db_filter-slave.opt
share/mysql/test/suite/rpl/t/rpl_do_db_filter.test
share/mysql/test/suite/rpl/t/rpl_do_grant.test
share/mysql/test/suite/rpl/t/rpl_do_table_filter_insensitive-master.opt
share/mysql/test/suite/rpl/t/rpl_do_table_filter_insensitive-slave.opt
share/mysql/test/suite/rpl/t/rpl_do_table_filter_insensitive.test
share/mysql/test/suite/rpl/t/rpl_do_table_filter_sensitive-slave.opt
share/mysql/test/suite/rpl/t/rpl_do_table_filter_sensitive.test
share/mysql/test/suite/rpl/t/rpl_drop.test
share/mysql/test/suite/rpl/t/rpl_drop_db.test
Changes 5.6.23: * The linked OpenSSL library for the MySQL Commercial Server has been updated from version 1.0.1j to version 1.0.1k. * Support for the SSL 2.0 and SSL 3.0 protocols has been disabled because they provide weak encryption. * yaSSL was upgraded to version 2.3.7. * The valid date range of the SSL certificates in mysql-test/std_data has been extended to the year 2029. * Bugs Fixed
2015-02-07 20:23:40 +01:00
share/mysql/test/suite/rpl/t/rpl_drop_db_fail.test
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/rpl/t/rpl_drop_temp-slave.opt
share/mysql/test/suite/rpl/t/rpl_drop_temp.test
Changes 5.6.21: The --skip-innodb option is now deprecated and its use results in a warning. It will be removed in a future MySQL release. This also applies to its synonyms (--innodb=OFF, --disable-innodb, and so forth). MySQL Enterprise Edition now includes a set of encryption functions based on the OpenSSL library that expose OpenSSL capabilities at the SQL level. Replication: The new variable simplified_binlog_gtid_recovery can be used to change the way binary log files are searched for previous GTIDs during recovery, speeding up the process when a large number of binary log files exist. Internally, spatial data types such as Geometry are represented as BLOB values, so when invoked with the --hex-blob option, mysqldump now displays spatial values in hex. Bugs Fixed...
2014-10-01 10:34:23 +02:00
share/mysql/test/suite/rpl/t/rpl_drop_temp_gtid.test
Changes 5.6.29: * InnoDB: A new InnoDB configuration option, innodb_tmpdir, allows you to configure a separate temporary file directory for online ALTER TABLE operations. This option was introduced to help avoid tmpdir overflows that could occur as a result of large temporary files created during online ALTER TABLE operations. innodb_tmpdir is a SESSION variable and can be configured dynamically using a SET statement. * yaSSL was upgraded to version 2.3.9. This upgrade corrects an issue in which yaSSL handled only cases of zero or one leading zeros for the key agreement instead of potentially any number, which in rare cases could cause connections to fail when using DHE cipher suites. * The Valgrind function signature in mysql-test/valgrind.supp was upgraded for Valgrind 3.11. * Bugs Fixed
2016-02-28 09:58:03 +01:00
share/mysql/test/suite/rpl/t/rpl_drop_temp_tbl_with_rewrite_db-slave.opt
share/mysql/test/suite/rpl/t/rpl_drop_temp_tbl_with_rewrite_db.test
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/rpl/t/rpl_drop_view.test
share/mysql/test/suite/rpl/t/rpl_dual_pos_advance-master.opt
share/mysql/test/suite/rpl/t/rpl_dual_pos_advance.test
Changes 5.6.27: * InnoDB: The new innodb_numa_interleave read-only configuration option allows you to enable the NUMA interleave memory policy for allocation of the InnoDB buffer pool. When innodb_numa_interleave is enabled, the NUMA memory policy is set to MPOL_INTERLEAVE for the mysqld process. After the InnoDB buffer pool is allocated, the NUMA memory policy is set back to MPOL_DEFAULT. This option is only available on NUMA-enabled systems. * yaSSL was upgraded to version 2.3.8. * RPM .spec files were updated so that MySQL Server builds from source RPM packages will include the proper files to take advantage of operating system NUMA capabilities. This introduces a runtime dependency on libnuma.so.1. RPM and yum detect this and refuse to install if that library is not installed. * InnoDB: Reloading a table that was evicted while empty caused an AUTO_INCREMENT value to be reset. * InnoDB: Memory allocation sanity checks were added to the memcached code. * InnoDB: A memcached flush_all command raised an assertion. A function that starts a transaction was called from within assertion code. * InnoDB: A data corruption occurred on ARM64. GCC builtins did not issue the correct fences when setting or unsetting the lock word. * InnoDB: Server shutdown was delayed waiting for the purge thread to exit. To avoid this problem, the number of calls to trx_purge() was reduced, and the trx_purge() batch size was reduced to 20. * InnoDB: In READ COMMITTED mode, a REPLACE operation on a unique secondary index resulted in a constraint violation. * InnoDB: The IBUF_BITMAP_FREE bit indicated that there was more free space in the leaf page than was actually available. * InnoDB: Setting lower_case_table_names=0 on a case-insensitive file system could result in a hang condition when running an INSERT INTO ... SELECT ... FROM tbl_name operation with the wrong tbl_name letter case. An error message is now printed and the server exits when attempting to start the server with --lower_case_table_names=0 on a case-insensitive file system. * InnoDB: The server failed to start with an innodb_force_recovery setting greater than 3. InnoDB was set to read-only mode before redo logs were applied. * InnoDB: The trx_sys_read_pertable_file_format_id() function reported the wrong file format. * Partitioning: CREATE TABLE statements that used an invalid function in a subpartitioning expression did not always fail gracefully as expected. * Partitioning: Error handling for failed partitioning-related ALTER TABLE operations against non-partitioned tables was not performed correctly * Partitioning: ALTER TABLE when executed from a stored procedure did not always work correctly with tables partitioned by RANGE. * Replication: Repeatedly checking for ERR_LOCK_WAIT_TIMEOUT (as done, for example by repeatedly executing SHOW SLAVE STATUS) during a prolonged write lock on a table led to an assert. * Replication: If statement based logging was in use, when updating multiple tables in a single statement, a single transaction could be logged as two different transactions. This was due to the binary logging process not properly identifying statements which were operating over transactional tables. The fix ensures that they are correctly identified, even if such statements do not change the contents of the tables.
2015-10-03 14:46:13 +02:00
share/mysql/test/suite/rpl/t/rpl_dump_thread_kill.test
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/rpl/t/rpl_empty_master_host.test
Changes 5.6.27: * InnoDB: The new innodb_numa_interleave read-only configuration option allows you to enable the NUMA interleave memory policy for allocation of the InnoDB buffer pool. When innodb_numa_interleave is enabled, the NUMA memory policy is set to MPOL_INTERLEAVE for the mysqld process. After the InnoDB buffer pool is allocated, the NUMA memory policy is set back to MPOL_DEFAULT. This option is only available on NUMA-enabled systems. * yaSSL was upgraded to version 2.3.8. * RPM .spec files were updated so that MySQL Server builds from source RPM packages will include the proper files to take advantage of operating system NUMA capabilities. This introduces a runtime dependency on libnuma.so.1. RPM and yum detect this and refuse to install if that library is not installed. * InnoDB: Reloading a table that was evicted while empty caused an AUTO_INCREMENT value to be reset. * InnoDB: Memory allocation sanity checks were added to the memcached code. * InnoDB: A memcached flush_all command raised an assertion. A function that starts a transaction was called from within assertion code. * InnoDB: A data corruption occurred on ARM64. GCC builtins did not issue the correct fences when setting or unsetting the lock word. * InnoDB: Server shutdown was delayed waiting for the purge thread to exit. To avoid this problem, the number of calls to trx_purge() was reduced, and the trx_purge() batch size was reduced to 20. * InnoDB: In READ COMMITTED mode, a REPLACE operation on a unique secondary index resulted in a constraint violation. * InnoDB: The IBUF_BITMAP_FREE bit indicated that there was more free space in the leaf page than was actually available. * InnoDB: Setting lower_case_table_names=0 on a case-insensitive file system could result in a hang condition when running an INSERT INTO ... SELECT ... FROM tbl_name operation with the wrong tbl_name letter case. An error message is now printed and the server exits when attempting to start the server with --lower_case_table_names=0 on a case-insensitive file system. * InnoDB: The server failed to start with an innodb_force_recovery setting greater than 3. InnoDB was set to read-only mode before redo logs were applied. * InnoDB: The trx_sys_read_pertable_file_format_id() function reported the wrong file format. * Partitioning: CREATE TABLE statements that used an invalid function in a subpartitioning expression did not always fail gracefully as expected. * Partitioning: Error handling for failed partitioning-related ALTER TABLE operations against non-partitioned tables was not performed correctly * Partitioning: ALTER TABLE when executed from a stored procedure did not always work correctly with tables partitioned by RANGE. * Replication: Repeatedly checking for ERR_LOCK_WAIT_TIMEOUT (as done, for example by repeatedly executing SHOW SLAVE STATUS) during a prolonged write lock on a table led to an assert. * Replication: If statement based logging was in use, when updating multiple tables in a single statement, a single transaction could be logged as two different transactions. This was due to the binary logging process not properly identifying statements which were operating over transactional tables. The fix ensures that they are correctly identified, even if such statements do not change the contents of the tables.
2015-10-03 14:46:13 +02:00
share/mysql/test/suite/rpl/t/rpl_empty_multi_update.test
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/rpl/t/rpl_err_ignoredtable-slave.opt
share/mysql/test/suite/rpl/t/rpl_err_ignoredtable.test
share/mysql/test/suite/rpl/t/rpl_events.test
share/mysql/test/suite/rpl/t/rpl_extra_col_master_innodb.test
share/mysql/test/suite/rpl/t/rpl_extra_col_master_myisam.test
share/mysql/test/suite/rpl/t/rpl_extra_col_slave_innodb.test
share/mysql/test/suite/rpl/t/rpl_extra_col_slave_myisam.test
share/mysql/test/suite/rpl/t/rpl_extra_row_data-master.opt
share/mysql/test/suite/rpl/t/rpl_extra_row_data-slave.opt
share/mysql/test/suite/rpl/t/rpl_extra_row_data.test
share/mysql/test/suite/rpl/t/rpl_failed_optimize.test
share/mysql/test/suite/rpl/t/rpl_filter_database-slave.opt
share/mysql/test/suite/rpl/t/rpl_filter_database.test
share/mysql/test/suite/rpl/t/rpl_filter_tables_not_exist-slave.opt
share/mysql/test/suite/rpl/t/rpl_filter_tables_not_exist.test
Changes 5.6.17: Functionality Added or Changed Incompatible Change: The AES_ENCRYPT() and AES_DECRYPT() functions now permit control of the block encryption mode and take an optional initialization vector argument: The new block_encryption_mode system variable controls the mode for block-based encryption algorithms. Its default value is aes-128-ecb, which signifies encryption using a key length of 128 bits and ECB mode. An optional init_vector argument provides an initialization vector for encryption modes that require it: AES_ENCRYPT(str,key_str[,init_vector]) AES_DECRYPT(crypt_str,key_str[,init_vector]) A random string of bytes to use for the initialization vector can be produced by calling the new RANDOM_BYTES() function. For more information, see Encryption and Compression Functions. These changes make statements that use AES_ENCRYPT() or AES_DECRYPT() unsafe for statement-based replication and they cannot be stored in the query cache. Queries that use RANDOM_BYTES() are unsafe for statement-based replication and cannot be stored in the query cache. Incompatible Change: The ERROR_FOR_DIVISION_BY_ZERO, NO_ZERO_DATE, and NO_ZERO_IN_DATE SQL modes now are deprecated and setting the sql_mode value to include any of them generates a warning. In MySQL 5.7, these modes do nothing. Instead, their effects are included in the effects of strict SQL mode (STRICT_ALL_TABLES or STRICT_TRANS_TABLES). The motivation for the change in MySQL 5.7 is to reduce the number of SQL modes with an effect dependent on strict mode and make them part of strict mode itself. To make advance preparation for an upgrade to MySQL 5.7, see SQL Mode Changes in MySQL 5.7. That discussion provides guidelines to assess whether your applications will be affected by the SQL mode changes in MySQL 5.7. InnoDB: MySQL now supports rebuilding regular and partitioned InnoDB tables using online DDL (ALGORITHM=INPLACE) for the following operations: OPTIMIZE TABLE ALTER TABLE ... FORCE ALTER TABLE ... ENGINE=INNODB (when run on an InnoDB table) Online DDL support reduces table rebuild time and permits concurrent DML, which helps reduce user application downtime. For additional information, see Overview of Online DDL. On Solaris, mysql_config --libs now includes -R/path/to/library so that libraries can be found at runtime. mysql_install_db provides a more informative diagnostic message when required Perl modules are missing. The IGNORE clause for ALTER TABLE is now deprecated and will be removed in a future version of MySQL. ALTER IGNORE TABLE causes problems for replication, prevents online ALTER TABLE for unique index creation, and causes problems with foreign keys (rows removed in the parent table). Bugs Fixed
2014-03-31 12:32:13 +02:00
share/mysql/test/suite/rpl/t/rpl_filter_warnings-slave.opt
share/mysql/test/suite/rpl/t/rpl_filter_warnings.test
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/rpl/t/rpl_flush_logs-master.opt
share/mysql/test/suite/rpl/t/rpl_flush_logs.test
share/mysql/test/suite/rpl/t/rpl_flushlog_loop-master.opt
share/mysql/test/suite/rpl/t/rpl_flushlog_loop-slave.opt
share/mysql/test/suite/rpl/t/rpl_flushlog_loop.test
share/mysql/test/suite/rpl/t/rpl_foreign_key_innodb.test
share/mysql/test/suite/rpl/t/rpl_free_items-slave.opt
share/mysql/test/suite/rpl/t/rpl_free_items.test
share/mysql/test/suite/rpl/t/rpl_function_defaults.test
Changes 5.6.27: * InnoDB: The new innodb_numa_interleave read-only configuration option allows you to enable the NUMA interleave memory policy for allocation of the InnoDB buffer pool. When innodb_numa_interleave is enabled, the NUMA memory policy is set to MPOL_INTERLEAVE for the mysqld process. After the InnoDB buffer pool is allocated, the NUMA memory policy is set back to MPOL_DEFAULT. This option is only available on NUMA-enabled systems. * yaSSL was upgraded to version 2.3.8. * RPM .spec files were updated so that MySQL Server builds from source RPM packages will include the proper files to take advantage of operating system NUMA capabilities. This introduces a runtime dependency on libnuma.so.1. RPM and yum detect this and refuse to install if that library is not installed. * InnoDB: Reloading a table that was evicted while empty caused an AUTO_INCREMENT value to be reset. * InnoDB: Memory allocation sanity checks were added to the memcached code. * InnoDB: A memcached flush_all command raised an assertion. A function that starts a transaction was called from within assertion code. * InnoDB: A data corruption occurred on ARM64. GCC builtins did not issue the correct fences when setting or unsetting the lock word. * InnoDB: Server shutdown was delayed waiting for the purge thread to exit. To avoid this problem, the number of calls to trx_purge() was reduced, and the trx_purge() batch size was reduced to 20. * InnoDB: In READ COMMITTED mode, a REPLACE operation on a unique secondary index resulted in a constraint violation. * InnoDB: The IBUF_BITMAP_FREE bit indicated that there was more free space in the leaf page than was actually available. * InnoDB: Setting lower_case_table_names=0 on a case-insensitive file system could result in a hang condition when running an INSERT INTO ... SELECT ... FROM tbl_name operation with the wrong tbl_name letter case. An error message is now printed and the server exits when attempting to start the server with --lower_case_table_names=0 on a case-insensitive file system. * InnoDB: The server failed to start with an innodb_force_recovery setting greater than 3. InnoDB was set to read-only mode before redo logs were applied. * InnoDB: The trx_sys_read_pertable_file_format_id() function reported the wrong file format. * Partitioning: CREATE TABLE statements that used an invalid function in a subpartitioning expression did not always fail gracefully as expected. * Partitioning: Error handling for failed partitioning-related ALTER TABLE operations against non-partitioned tables was not performed correctly * Partitioning: ALTER TABLE when executed from a stored procedure did not always work correctly with tables partitioned by RANGE. * Replication: Repeatedly checking for ERR_LOCK_WAIT_TIMEOUT (as done, for example by repeatedly executing SHOW SLAVE STATUS) during a prolonged write lock on a table led to an assert. * Replication: If statement based logging was in use, when updating multiple tables in a single statement, a single transaction could be logged as two different transactions. This was due to the binary logging process not properly identifying statements which were operating over transactional tables. The fix ensures that they are correctly identified, even if such statements do not change the contents of the tables.
2015-10-03 14:46:13 +02:00
share/mysql/test/suite/rpl/t/rpl_gap_in_retrieved_gtid_set.test
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/rpl/t/rpl_general_log.test
share/mysql/test/suite/rpl/t/rpl_geometry.test
share/mysql/test/suite/rpl/t/rpl_get_lock.test
share/mysql/test/suite/rpl/t/rpl_get_master_version_and_clock-slave.opt
share/mysql/test/suite/rpl/t/rpl_get_master_version_and_clock.test
share/mysql/test/suite/rpl/t/rpl_grant.test
share/mysql/test/suite/rpl/t/rpl_grant_plugin-master.opt
share/mysql/test/suite/rpl/t/rpl_grant_plugin-slave.opt
share/mysql/test/suite/rpl/t/rpl_grant_plugin.test
Changes 5.6.12: * mysql_upgrade now verifies that the server version matches the version against which it was compiled, and exits if there is a mismatch. In addiion, a --version-check option permits specifying whether to enable version checking (the default), or disable checking if given as --skip-version-checking. * Bugs Fixed
2013-06-04 20:17:25 +02:00
share/mysql/test/suite/rpl/t/rpl_group_commit_deadlock.test
Changes 5.6.22: * Noisy compiler warnings on FreeBSD 10 were silenced. * CMake workarounds for older Mac OS X and XCode versions were removed. On Mac OS X, compilation always uses Clang, even for 32-bit builds. * Previously, the MYSQL_MAINTAINER_MODE CMake option was turned on by default for debug builds and off for release builds, and MYSQL_MAINTAINER_MODE caused -Werror to be enabled when building with GCC. This made it cumbersome to enable -Werror under certain conditions, such as when compiling with Clang. * Build support was modified to produce the same warnings for Clang as for gcc. * CMake configuration for the Clang compiler sets more appropriate flags for building on Linux. Specifically, -g -fno-omit-frame-pointer -fno-strict-aliasing is now added. * Bugs fixed.
2014-12-02 13:40:09 +01:00
share/mysql/test/suite/rpl/t/rpl_gtid_binary_log_as_relay_log.test
Changes 5.6.17: Functionality Added or Changed Incompatible Change: The AES_ENCRYPT() and AES_DECRYPT() functions now permit control of the block encryption mode and take an optional initialization vector argument: The new block_encryption_mode system variable controls the mode for block-based encryption algorithms. Its default value is aes-128-ecb, which signifies encryption using a key length of 128 bits and ECB mode. An optional init_vector argument provides an initialization vector for encryption modes that require it: AES_ENCRYPT(str,key_str[,init_vector]) AES_DECRYPT(crypt_str,key_str[,init_vector]) A random string of bytes to use for the initialization vector can be produced by calling the new RANDOM_BYTES() function. For more information, see Encryption and Compression Functions. These changes make statements that use AES_ENCRYPT() or AES_DECRYPT() unsafe for statement-based replication and they cannot be stored in the query cache. Queries that use RANDOM_BYTES() are unsafe for statement-based replication and cannot be stored in the query cache. Incompatible Change: The ERROR_FOR_DIVISION_BY_ZERO, NO_ZERO_DATE, and NO_ZERO_IN_DATE SQL modes now are deprecated and setting the sql_mode value to include any of them generates a warning. In MySQL 5.7, these modes do nothing. Instead, their effects are included in the effects of strict SQL mode (STRICT_ALL_TABLES or STRICT_TRANS_TABLES). The motivation for the change in MySQL 5.7 is to reduce the number of SQL modes with an effect dependent on strict mode and make them part of strict mode itself. To make advance preparation for an upgrade to MySQL 5.7, see SQL Mode Changes in MySQL 5.7. That discussion provides guidelines to assess whether your applications will be affected by the SQL mode changes in MySQL 5.7. InnoDB: MySQL now supports rebuilding regular and partitioned InnoDB tables using online DDL (ALGORITHM=INPLACE) for the following operations: OPTIMIZE TABLE ALTER TABLE ... FORCE ALTER TABLE ... ENGINE=INNODB (when run on an InnoDB table) Online DDL support reduces table rebuild time and permits concurrent DML, which helps reduce user application downtime. For additional information, see Overview of Online DDL. On Solaris, mysql_config --libs now includes -R/path/to/library so that libraries can be found at runtime. mysql_install_db provides a more informative diagnostic message when required Perl modules are missing. The IGNORE clause for ALTER TABLE is now deprecated and will be removed in a future version of MySQL. ALTER IGNORE TABLE causes problems for replication, prevents online ALTER TABLE for unique index creation, and causes problems with foreign keys (rows removed in the parent table). Bugs Fixed
2014-03-31 12:32:13 +02:00
share/mysql/test/suite/rpl/t/rpl_gtid_binlog_errors-master.opt
share/mysql/test/suite/rpl/t/rpl_gtid_binlog_errors.test
share/mysql/test/suite/rpl/t/rpl_gtid_do_table_filter_insensitive-master.opt
share/mysql/test/suite/rpl/t/rpl_gtid_do_table_filter_insensitive-slave.opt
share/mysql/test/suite/rpl/t/rpl_gtid_do_table_filter_insensitive.test
share/mysql/test/suite/rpl/t/rpl_gtid_do_table_filter_sensitive-slave.opt
share/mysql/test/suite/rpl/t/rpl_gtid_do_table_filter_sensitive.test
Changes 5.6.20: Security Fix: The linked OpenSSL library for the MySQL 5.6 Commercial Server has been updated from version 1.0.1g to version 1.0.1h. Versions of OpenSSL prior to and including 1.0.1g are reported to be vulnerable to CVE-2014-0224. This change does not affect the Oracle-produced MySQL Community build of MySQL Server 5.6, which uses the yaSSL library instead. DTrace Support MySQL now includes DTrace support on Oracle Linux 6 or higher with UEK kernel. If DTrace is present, server builds will detect it with no special CMake options required. For information about using DTrace on MySQL, see Tracing mysqld Using DTrace. InnoDB Notes Important Change: Redo log writes for large, externally stored BLOB fields could overwrite the most recent checkpoint. The 5.6.20 patch limits the size of redo log BLOB writes to 10% of the redo log file size. The 5.7.5 patch addresses the bug without imposing a limitation. For MySQL 5.5, the bug remains a known limitation. As a result of the redo log BLOB write limit introduced for MySQL 5.6, innodb_log_file_size should be set to a value greater than 10 times the largest BLOB data size found in the rows of your tables plus the length of other variable length fields (VARCHAR, VARBINARY, and TEXT type fields). Failing to do so could result in “Row size too large” errors. No action is required if your innodb_log_file_size setting is already sufficiently large or your tables contain no BLOB data. Functionality Added or Changed Replication: The new system variable binlog_impossible_mode controls what happens if the server cannot write to the binary log, for example, due to a file error. For backward compatibility, the default for binlog_impossible_mode is IGNORE_ERROR, meaning the server logs the error, halts logging, and continues updates to the database. Setting this variable to ABORT_SERVER makes the server halt logging and shut down if it cannot write to the binary log. CMake support was updated to handle CMake version 3. New Debian7, Ubuntu12.04, and Ubuntu14.04 distribution support that was introduced with 5.6.17 now comes with the platform-specific packaging source placed under the packaging directory, in the deb-precise, deb-wheezy, and deb-trusty directories. Support for LinuxThreads has been removed from the source code. LinuxThreads was superseded by NPTL in Linux 2.6. By default, mysql_install_db creates a my.cnf file in the installation base directory using a template. This may be undesireable for some deployments. To enable this behavior to be suppressed, mysql_install_db now supports a --keep-my-cnf option to preserve any existing my.cnf file and not create a new my.cnf file. The mysqlhotcopy utility is now deprecated and will be removed in a future version of MySQL. Among the reasons for this: It works only for the MyISAM and ARCHIVE storage engines; it works on Unix but not Windows. Alternatives include mysqldump and MySQL Enterprise Backup. The timed_mutexes system variable has no effect and is deprecated. Bugs Fixed
2014-08-10 17:11:57 +02:00
share/mysql/test/suite/rpl/t/rpl_gtid_drop_table.cnf
share/mysql/test/suite/rpl/t/rpl_gtid_drop_table.test
Changes 5.6.19: Functionality Added or Changed The obsolete and unmaintained charset2html utility has been removed from MySQL distributions. The mysqlbug, mysql_waitpid, and mysql_zap utilities have been deprecated and will be removed in MySQL 5.7. Bugs Fixed InnoDB: After upgrading from 5.6.10 to MySQL versions up to and including MySQL 5.6.18, InnoDB would attempt to rename obsolete full-text search auxiliary tables on server startup, resulting in an assertion failure. InnoDB: For each insert, memset would be called three times to allocate memory for system fields. To reduce CPU usage, the three memset calls are now combined into a single call. InnoDB: Enabling the InnoDB Table Monitor would result in a ib_table->stat_initialized assertion failure. InnoDB: Setting innodb_max_dirty_pages_pct=0 would leave 1% of dirty pages unflushed. Buffer pool flushing is initiated when the percentage of dirty pages is greater innodb_max_dirty_pages_pct. The internal variables that store the innodb_max_dirty_pages_pct value and the percentage of dirty pages (buf_get_modified_ratio_pct and srv_max_buf_pool_modified_pct) were defined as unsigned integer data types, which meant that a innodb_max_dirty_pages_pct value of 0 required a dirty pages percentage of 1 or greater to initiate buffer pool flushing. To address this problem, the buf_get_modified_ratio_pct and srv_max_buf_pool_modified_pct internal variables are redefined as double data types, which changes the range value for innodb_max_dirty_pages_pct and innodb_max_dirty_pages_pct_lwm from 0 .. 99 to 0 .. 99.99. Additionally, buffer pool flushing is now initiated when the percentage of dirty pages is “greater than or equal to” innodb_max_dirty_pages_pct. Replication: Log rotation events could cause group_relay_log_pos to be moved forward incorrectly within a group. This meant that, when the transaction was retried, or if the SQL thread was stopped in the middle of a transaction following one or more log rotations (such that the transaction or group spanned multiple relay log files), part or all of the group was silently skipped. This issue has been addressed by correcting a problem in the logic used to avoid touching the coordinates of the SQL thread when updating the log position as part of a relay log rotation whereby it was possible to update the SQL thread's coordinates when not using a multi-threaded slave, even in the middle of a group. Replication: When running the server with --gtid-mode=ON, STOP SLAVE followed by START SLAVE resulted in a mismatch between the information provided by INFORMATION_SCHEMA.INNODB_TEMP_TABLE_INFO and the Slave_open_temp_tables status variable: the INNODB_TEMP_TABLE_INFO table showed that no temporary tables existed, but Slave_open_temp_tables had a nonzero value. Replication: In certain cases, the server mishandled triggers and stored procedures that tried to modify other tables when called by CREATE TABLE ... SELECT. This is now handled correctly as an error. Replication: When used on a table employing a transactional storage engine, a failed TRUNCATE TABLE was still written to the binary log and thus replayed on the slave. This could lead to inconsistency when the master retained data that was removed on the slave. Now in such cases TRUNCATE TABLE is logged only when it executes successfully. Replication: The server did not always handle the auto.cnf file correctly in cases where this file's permissions were incorrect. Replication: When the binary log was rotated due to receipt of a SIGHUP signal, the new binary log did not contain the Previous_gtid_event required for subsequent processing of that binary log's GTID events. Now when SIGHUP is received, steps are taken to insure that the server writes the necessary Previous_gtid_event to the new log before writing any GTID events to the new log.
2014-06-02 09:30:38 +02:00
share/mysql/test/suite/rpl/t/rpl_gtid_empty_transaction.cnf
share/mysql/test/suite/rpl/t/rpl_gtid_empty_transaction.test
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/rpl/t/rpl_gtid_execution-master.opt
share/mysql/test/suite/rpl/t/rpl_gtid_execution-slave.opt
share/mysql/test/suite/rpl/t/rpl_gtid_execution.test
share/mysql/test/suite/rpl/t/rpl_gtid_failover.cnf
share/mysql/test/suite/rpl/t/rpl_gtid_failover.test
Changes 5.6.17: Functionality Added or Changed Incompatible Change: The AES_ENCRYPT() and AES_DECRYPT() functions now permit control of the block encryption mode and take an optional initialization vector argument: The new block_encryption_mode system variable controls the mode for block-based encryption algorithms. Its default value is aes-128-ecb, which signifies encryption using a key length of 128 bits and ECB mode. An optional init_vector argument provides an initialization vector for encryption modes that require it: AES_ENCRYPT(str,key_str[,init_vector]) AES_DECRYPT(crypt_str,key_str[,init_vector]) A random string of bytes to use for the initialization vector can be produced by calling the new RANDOM_BYTES() function. For more information, see Encryption and Compression Functions. These changes make statements that use AES_ENCRYPT() or AES_DECRYPT() unsafe for statement-based replication and they cannot be stored in the query cache. Queries that use RANDOM_BYTES() are unsafe for statement-based replication and cannot be stored in the query cache. Incompatible Change: The ERROR_FOR_DIVISION_BY_ZERO, NO_ZERO_DATE, and NO_ZERO_IN_DATE SQL modes now are deprecated and setting the sql_mode value to include any of them generates a warning. In MySQL 5.7, these modes do nothing. Instead, their effects are included in the effects of strict SQL mode (STRICT_ALL_TABLES or STRICT_TRANS_TABLES). The motivation for the change in MySQL 5.7 is to reduce the number of SQL modes with an effect dependent on strict mode and make them part of strict mode itself. To make advance preparation for an upgrade to MySQL 5.7, see SQL Mode Changes in MySQL 5.7. That discussion provides guidelines to assess whether your applications will be affected by the SQL mode changes in MySQL 5.7. InnoDB: MySQL now supports rebuilding regular and partitioned InnoDB tables using online DDL (ALGORITHM=INPLACE) for the following operations: OPTIMIZE TABLE ALTER TABLE ... FORCE ALTER TABLE ... ENGINE=INNODB (when run on an InnoDB table) Online DDL support reduces table rebuild time and permits concurrent DML, which helps reduce user application downtime. For additional information, see Overview of Online DDL. On Solaris, mysql_config --libs now includes -R/path/to/library so that libraries can be found at runtime. mysql_install_db provides a more informative diagnostic message when required Perl modules are missing. The IGNORE clause for ALTER TABLE is now deprecated and will be removed in a future version of MySQL. ALTER IGNORE TABLE causes problems for replication, prevents online ALTER TABLE for unique index creation, and causes problems with foreign keys (rows removed in the parent table). Bugs Fixed
2014-03-31 12:32:13 +02:00
share/mysql/test/suite/rpl/t/rpl_gtid_heartbeat_2slave.cnf
share/mysql/test/suite/rpl/t/rpl_gtid_heartbeat_2slave.test
share/mysql/test/suite/rpl/t/rpl_gtid_ignore_table_filter_insensitive-master.opt
share/mysql/test/suite/rpl/t/rpl_gtid_ignore_table_filter_insensitive-slave.opt
share/mysql/test/suite/rpl/t/rpl_gtid_ignore_table_filter_insensitive.test
share/mysql/test/suite/rpl/t/rpl_gtid_ignore_table_filter_sensitive-slave.opt
share/mysql/test/suite/rpl/t/rpl_gtid_ignore_table_filter_sensitive.test
share/mysql/test/suite/rpl/t/rpl_gtid_loaddata_s-slave.opt
share/mysql/test/suite/rpl/t/rpl_gtid_loaddata_s.test
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/rpl/t/rpl_gtid_mode.test
Changes 5.6.25: Functionality Added or Changed * MySQL Enterprise Firewall operates on parser states and does not work well together with the query cache, which circumvents the parser. MySQL Enterprise Firewall now checks whether the query cache is enabled. If so, it displays a message that the query cache must be disabled and does not load. * my_print_defaults now masks passwords. To display passwords in cleartext, use the new --show option. * MySQL distributions now include an innodb_stress suite of test cases. Thanks to Mark Callaghan for the contribution. Bugs Fixed * InnoDB; Partitioning: The CREATE_TIME column of the INFORMATION_SCHEMA.TABLES table now shows the correct table creation time for partitioned InnoDB tables. The CREATE_TIME column of the INFORMATION_SCHEMA.PARTITIONS table now shows the correct partition creation time for a partition of partitioned InnoDB tables. The UPDATE_TIME column of the INFORMATION_SCHEMA.TABLES table now shows when a partitioned InnoDB table was last updated by an INSERT, DELETE, or UPDATE. The UPDATE_TIME column of the INFORMATION_SCHEMA.PARTITIONS table now shows when a partition of a partitioned InnoDB table was last updated. * InnoDB: An assertion was raised on shutdown due to XA PREPARE transactions holding explicit locks. * InnoDB: The strict_* forms of innodb_checksum_algorithm settings (strict_none, strict_innodb, and strict_crc32) caused the server to halt when a non-matching checksum was encountered, even though the non-matching checksum was valid. For example, with innodb_checksum_algorithm=strict_crc32, encountering a valid innodb checksum caused the server to halt. Instead of halting the server, a message is now printed to the error log and the page is accepted as valid if it matches an innodb, crc32 or none checksum. * InnoDB: The memcached set command permitted a negative expire time value. Expire time is stored internally as an unsigned integer. A negative value would be converted to a large number and accepted. The maximum expire time value is now restricted to INT_MAX32 to prevent negative expire time values. * InnoDB: Removal of a foreign key object from the data dictionary cache during error handling caused the server to exit. * InnoDB: SHOW ENGINE INNODB STATUS output showed negative reservation and signal count values due to a counter overflow error. * InnoDB: Failure to check the status of a cursor transaction read-only option before reusing the cursor transaction for a write operation resulted in a server exit during a memcached workload. * InnoDB: MDL locks taken by memcached clients caused a MySQL Enterprise Backup FLUSH TABLES WITH READ LOCK operation to hang. * InnoDB: Estimates that were too low for the size of merge chunks in the result sorting algorithm caused a server exit. * InnoDB: For full-text searches, the optimizer could choose an index that does not produce correct relevancy rankings. * Partitioning: When creating a partitioned table, partition-level DATA DIRECTORY or INDEX DIRECTORY option values that contained an excessive number of characters were handled incorrectly. * Partitioning: Executing an ALTER TABLE on a partitioned table on which a write lock was in effect could cause subsequent SQL statements on this table to fail. * Replication: When binary logging was enabled, using stored functions and triggers resulting in a long running procedure that inserted many records caused the memory use to increase rapidly. This was due to memory being allocated per variable. The fix ensures that in such a situation, memory is allocated once and the same memory is reused. * Replication: If an error was encountered while adding a GTID to the received GTID set, the log lock was not being correctly released. This could cause a deadlock. more...
2015-06-01 10:15:05 +02:00
share/mysql/test/suite/rpl/t/rpl_gtid_mode_off_new_master.test
share/mysql/test/suite/rpl/t/rpl_gtid_mode_on_new_master.test
Changes 5.6.26: * Security Fix: Due to the LogJam issue (https://weakdh.org/), OpenSSL has changed the Diffie-Hellman key length parameters for openssl-1.0.1n and up. * Replication: When using a multi-threaded slave, each worker thread has its own queue of transactions to process. In previous MySQL versions, STOP SLAVE waited for all workers to process their entire queue. This logic has been changed so that STOP SLAVE first finds the newest transaction that was committed by any worker thread. Then, it waits for all workers to complete transactions older than that. Newer transactions are not processed. The new logic allows STOP SLAVE to complete faster in case some worker queues contain multiple transactions. * Previously, the max_digest_length system variable controlled the maximum digest length for all server functions that computed statement digests. However, whereas the Performance Schema may need to maintain many digest values, other server functions such as MySQL Enterprise Firewall need only one digest per session. Increasing the max_digest_length value has little impact on total memory requirements for those functions, but can increase Performance Schema memory requirements significantly. To enable configuring digest length separately for the Performance Schema, its digest length is now controlled by the new performance_schema_max_digest_length system variable. * Previously, changes to the validate_password plugin dictionary file (named by the validate_password_dictionary_file system variable) while the server was running required a restart for the server to recognize the changes. Now validate_password_dictionary_file can be set at runtime and assigning a value causes the named file to be read without a restart. In addition, two new status variables are available. validate_password_dictionary_file_last_parsed indicates when the dictionary file was last read, and validate_password_dictionary_file_words_count indicates how many words it contains. * Bugs fixed
2015-07-30 16:39:18 +02:00
share/mysql/test/suite/rpl/t/rpl_gtid_mts_relay_log_recovery_auto_pos_on_off-master.opt
share/mysql/test/suite/rpl/t/rpl_gtid_mts_relay_log_recovery_auto_pos_on_off-slave.opt
share/mysql/test/suite/rpl/t/rpl_gtid_mts_relay_log_recovery_auto_pos_on_off.test
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/rpl/t/rpl_gtid_parallel.test
share/mysql/test/suite/rpl/t/rpl_gtid_purged_fail_to_connect-master.opt
share/mysql/test/suite/rpl/t/rpl_gtid_purged_fail_to_connect-slave.opt
share/mysql/test/suite/rpl/t/rpl_gtid_purged_fail_to_connect.test
share/mysql/test/suite/rpl/t/rpl_gtid_purged_maintained.test
Changes 5.6.25: Functionality Added or Changed * MySQL Enterprise Firewall operates on parser states and does not work well together with the query cache, which circumvents the parser. MySQL Enterprise Firewall now checks whether the query cache is enabled. If so, it displays a message that the query cache must be disabled and does not load. * my_print_defaults now masks passwords. To display passwords in cleartext, use the new --show option. * MySQL distributions now include an innodb_stress suite of test cases. Thanks to Mark Callaghan for the contribution. Bugs Fixed * InnoDB; Partitioning: The CREATE_TIME column of the INFORMATION_SCHEMA.TABLES table now shows the correct table creation time for partitioned InnoDB tables. The CREATE_TIME column of the INFORMATION_SCHEMA.PARTITIONS table now shows the correct partition creation time for a partition of partitioned InnoDB tables. The UPDATE_TIME column of the INFORMATION_SCHEMA.TABLES table now shows when a partitioned InnoDB table was last updated by an INSERT, DELETE, or UPDATE. The UPDATE_TIME column of the INFORMATION_SCHEMA.PARTITIONS table now shows when a partition of a partitioned InnoDB table was last updated. * InnoDB: An assertion was raised on shutdown due to XA PREPARE transactions holding explicit locks. * InnoDB: The strict_* forms of innodb_checksum_algorithm settings (strict_none, strict_innodb, and strict_crc32) caused the server to halt when a non-matching checksum was encountered, even though the non-matching checksum was valid. For example, with innodb_checksum_algorithm=strict_crc32, encountering a valid innodb checksum caused the server to halt. Instead of halting the server, a message is now printed to the error log and the page is accepted as valid if it matches an innodb, crc32 or none checksum. * InnoDB: The memcached set command permitted a negative expire time value. Expire time is stored internally as an unsigned integer. A negative value would be converted to a large number and accepted. The maximum expire time value is now restricted to INT_MAX32 to prevent negative expire time values. * InnoDB: Removal of a foreign key object from the data dictionary cache during error handling caused the server to exit. * InnoDB: SHOW ENGINE INNODB STATUS output showed negative reservation and signal count values due to a counter overflow error. * InnoDB: Failure to check the status of a cursor transaction read-only option before reusing the cursor transaction for a write operation resulted in a server exit during a memcached workload. * InnoDB: MDL locks taken by memcached clients caused a MySQL Enterprise Backup FLUSH TABLES WITH READ LOCK operation to hang. * InnoDB: Estimates that were too low for the size of merge chunks in the result sorting algorithm caused a server exit. * InnoDB: For full-text searches, the optimizer could choose an index that does not produce correct relevancy rankings. * Partitioning: When creating a partitioned table, partition-level DATA DIRECTORY or INDEX DIRECTORY option values that contained an excessive number of characters were handled incorrectly. * Partitioning: Executing an ALTER TABLE on a partitioned table on which a write lock was in effect could cause subsequent SQL statements on this table to fail. * Replication: When binary logging was enabled, using stored functions and triggers resulting in a long running procedure that inserted many records caused the memory use to increase rapidly. This was due to memory being allocated per variable. The fix ensures that in such a situation, memory is allocated once and the same memory is reused. * Replication: If an error was encountered while adding a GTID to the received GTID set, the log lock was not being correctly released. This could cause a deadlock. more...
2015-06-01 10:15:05 +02:00
share/mysql/test/suite/rpl/t/rpl_gtid_replay_relaylog.test
Changes 5.6.17: Functionality Added or Changed Incompatible Change: The AES_ENCRYPT() and AES_DECRYPT() functions now permit control of the block encryption mode and take an optional initialization vector argument: The new block_encryption_mode system variable controls the mode for block-based encryption algorithms. Its default value is aes-128-ecb, which signifies encryption using a key length of 128 bits and ECB mode. An optional init_vector argument provides an initialization vector for encryption modes that require it: AES_ENCRYPT(str,key_str[,init_vector]) AES_DECRYPT(crypt_str,key_str[,init_vector]) A random string of bytes to use for the initialization vector can be produced by calling the new RANDOM_BYTES() function. For more information, see Encryption and Compression Functions. These changes make statements that use AES_ENCRYPT() or AES_DECRYPT() unsafe for statement-based replication and they cannot be stored in the query cache. Queries that use RANDOM_BYTES() are unsafe for statement-based replication and cannot be stored in the query cache. Incompatible Change: The ERROR_FOR_DIVISION_BY_ZERO, NO_ZERO_DATE, and NO_ZERO_IN_DATE SQL modes now are deprecated and setting the sql_mode value to include any of them generates a warning. In MySQL 5.7, these modes do nothing. Instead, their effects are included in the effects of strict SQL mode (STRICT_ALL_TABLES or STRICT_TRANS_TABLES). The motivation for the change in MySQL 5.7 is to reduce the number of SQL modes with an effect dependent on strict mode and make them part of strict mode itself. To make advance preparation for an upgrade to MySQL 5.7, see SQL Mode Changes in MySQL 5.7. That discussion provides guidelines to assess whether your applications will be affected by the SQL mode changes in MySQL 5.7. InnoDB: MySQL now supports rebuilding regular and partitioned InnoDB tables using online DDL (ALGORITHM=INPLACE) for the following operations: OPTIMIZE TABLE ALTER TABLE ... FORCE ALTER TABLE ... ENGINE=INNODB (when run on an InnoDB table) Online DDL support reduces table rebuild time and permits concurrent DML, which helps reduce user application downtime. For additional information, see Overview of Online DDL. On Solaris, mysql_config --libs now includes -R/path/to/library so that libraries can be found at runtime. mysql_install_db provides a more informative diagnostic message when required Perl modules are missing. The IGNORE clause for ALTER TABLE is now deprecated and will be removed in a future version of MySQL. ALTER IGNORE TABLE causes problems for replication, prevents online ALTER TABLE for unique index creation, and causes problems with foreign keys (rows removed in the parent table). Bugs Fixed
2014-03-31 12:32:13 +02:00
share/mysql/test/suite/rpl/t/rpl_gtid_row_event_max_size-master.opt
share/mysql/test/suite/rpl/t/rpl_gtid_row_event_max_size-slave.opt
share/mysql/test/suite/rpl/t/rpl_gtid_row_event_max_size.test
share/mysql/test/suite/rpl/t/rpl_gtid_row_show_relaylog_events.test
Changes 5.6.19: Functionality Added or Changed The obsolete and unmaintained charset2html utility has been removed from MySQL distributions. The mysqlbug, mysql_waitpid, and mysql_zap utilities have been deprecated and will be removed in MySQL 5.7. Bugs Fixed InnoDB: After upgrading from 5.6.10 to MySQL versions up to and including MySQL 5.6.18, InnoDB would attempt to rename obsolete full-text search auxiliary tables on server startup, resulting in an assertion failure. InnoDB: For each insert, memset would be called three times to allocate memory for system fields. To reduce CPU usage, the three memset calls are now combined into a single call. InnoDB: Enabling the InnoDB Table Monitor would result in a ib_table->stat_initialized assertion failure. InnoDB: Setting innodb_max_dirty_pages_pct=0 would leave 1% of dirty pages unflushed. Buffer pool flushing is initiated when the percentage of dirty pages is greater innodb_max_dirty_pages_pct. The internal variables that store the innodb_max_dirty_pages_pct value and the percentage of dirty pages (buf_get_modified_ratio_pct and srv_max_buf_pool_modified_pct) were defined as unsigned integer data types, which meant that a innodb_max_dirty_pages_pct value of 0 required a dirty pages percentage of 1 or greater to initiate buffer pool flushing. To address this problem, the buf_get_modified_ratio_pct and srv_max_buf_pool_modified_pct internal variables are redefined as double data types, which changes the range value for innodb_max_dirty_pages_pct and innodb_max_dirty_pages_pct_lwm from 0 .. 99 to 0 .. 99.99. Additionally, buffer pool flushing is now initiated when the percentage of dirty pages is “greater than or equal to” innodb_max_dirty_pages_pct. Replication: Log rotation events could cause group_relay_log_pos to be moved forward incorrectly within a group. This meant that, when the transaction was retried, or if the SQL thread was stopped in the middle of a transaction following one or more log rotations (such that the transaction or group spanned multiple relay log files), part or all of the group was silently skipped. This issue has been addressed by correcting a problem in the logic used to avoid touching the coordinates of the SQL thread when updating the log position as part of a relay log rotation whereby it was possible to update the SQL thread's coordinates when not using a multi-threaded slave, even in the middle of a group. Replication: When running the server with --gtid-mode=ON, STOP SLAVE followed by START SLAVE resulted in a mismatch between the information provided by INFORMATION_SCHEMA.INNODB_TEMP_TABLE_INFO and the Slave_open_temp_tables status variable: the INNODB_TEMP_TABLE_INFO table showed that no temporary tables existed, but Slave_open_temp_tables had a nonzero value. Replication: In certain cases, the server mishandled triggers and stored procedures that tried to modify other tables when called by CREATE TABLE ... SELECT. This is now handled correctly as an error. Replication: When used on a table employing a transactional storage engine, a failed TRUNCATE TABLE was still written to the binary log and thus replayed on the slave. This could lead to inconsistency when the master retained data that was removed on the slave. Now in such cases TRUNCATE TABLE is logged only when it executes successfully. Replication: The server did not always handle the auto.cnf file correctly in cases where this file's permissions were incorrect. Replication: When the binary log was rotated due to receipt of a SIGHUP signal, the new binary log did not contain the Previous_gtid_event required for subsequent processing of that binary log's GTID events. Now when SIGHUP is received, steps are taken to insure that the server writes the necessary Previous_gtid_event to the new log before writing any GTID events to the new log.
2014-06-02 09:30:38 +02:00
share/mysql/test/suite/rpl/t/rpl_gtid_server_sighup.test
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/rpl/t/rpl_gtid_sql_until_before_after.test
Changes 5.6.17: Functionality Added or Changed Incompatible Change: The AES_ENCRYPT() and AES_DECRYPT() functions now permit control of the block encryption mode and take an optional initialization vector argument: The new block_encryption_mode system variable controls the mode for block-based encryption algorithms. Its default value is aes-128-ecb, which signifies encryption using a key length of 128 bits and ECB mode. An optional init_vector argument provides an initialization vector for encryption modes that require it: AES_ENCRYPT(str,key_str[,init_vector]) AES_DECRYPT(crypt_str,key_str[,init_vector]) A random string of bytes to use for the initialization vector can be produced by calling the new RANDOM_BYTES() function. For more information, see Encryption and Compression Functions. These changes make statements that use AES_ENCRYPT() or AES_DECRYPT() unsafe for statement-based replication and they cannot be stored in the query cache. Queries that use RANDOM_BYTES() are unsafe for statement-based replication and cannot be stored in the query cache. Incompatible Change: The ERROR_FOR_DIVISION_BY_ZERO, NO_ZERO_DATE, and NO_ZERO_IN_DATE SQL modes now are deprecated and setting the sql_mode value to include any of them generates a warning. In MySQL 5.7, these modes do nothing. Instead, their effects are included in the effects of strict SQL mode (STRICT_ALL_TABLES or STRICT_TRANS_TABLES). The motivation for the change in MySQL 5.7 is to reduce the number of SQL modes with an effect dependent on strict mode and make them part of strict mode itself. To make advance preparation for an upgrade to MySQL 5.7, see SQL Mode Changes in MySQL 5.7. That discussion provides guidelines to assess whether your applications will be affected by the SQL mode changes in MySQL 5.7. InnoDB: MySQL now supports rebuilding regular and partitioned InnoDB tables using online DDL (ALGORITHM=INPLACE) for the following operations: OPTIMIZE TABLE ALTER TABLE ... FORCE ALTER TABLE ... ENGINE=INNODB (when run on an InnoDB table) Online DDL support reduces table rebuild time and permits concurrent DML, which helps reduce user application downtime. For additional information, see Overview of Online DDL. On Solaris, mysql_config --libs now includes -R/path/to/library so that libraries can be found at runtime. mysql_install_db provides a more informative diagnostic message when required Perl modules are missing. The IGNORE clause for ALTER TABLE is now deprecated and will be removed in a future version of MySQL. ALTER IGNORE TABLE causes problems for replication, prevents online ALTER TABLE for unique index creation, and causes problems with foreign keys (rows removed in the parent table). Bugs Fixed
2014-03-31 12:32:13 +02:00
share/mysql/test/suite/rpl/t/rpl_gtid_stm_insert_delayed.test
share/mysql/test/suite/rpl/t/rpl_gtid_stm_mix_show_relaylog_events.test
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/rpl/t/rpl_gtid_stress_failover.cnf
share/mysql/test/suite/rpl/t/rpl_gtid_stress_failover.test
Changes 5.6.29: * InnoDB: A new InnoDB configuration option, innodb_tmpdir, allows you to configure a separate temporary file directory for online ALTER TABLE operations. This option was introduced to help avoid tmpdir overflows that could occur as a result of large temporary files created during online ALTER TABLE operations. innodb_tmpdir is a SESSION variable and can be configured dynamically using a SET statement. * yaSSL was upgraded to version 2.3.9. This upgrade corrects an issue in which yaSSL handled only cases of zero or one leading zeros for the key agreement instead of potentially any number, which in rare cases could cause connections to fail when using DHE cipher suites. * The Valgrind function signature in mysql-test/valgrind.supp was upgraded for Valgrind 3.11. * Bugs Fixed
2016-02-28 09:58:03 +01:00
share/mysql/test/suite/rpl/t/rpl_gtid_temp_table.test
Changes 5.6.27: * InnoDB: The new innodb_numa_interleave read-only configuration option allows you to enable the NUMA interleave memory policy for allocation of the InnoDB buffer pool. When innodb_numa_interleave is enabled, the NUMA memory policy is set to MPOL_INTERLEAVE for the mysqld process. After the InnoDB buffer pool is allocated, the NUMA memory policy is set back to MPOL_DEFAULT. This option is only available on NUMA-enabled systems. * yaSSL was upgraded to version 2.3.8. * RPM .spec files were updated so that MySQL Server builds from source RPM packages will include the proper files to take advantage of operating system NUMA capabilities. This introduces a runtime dependency on libnuma.so.1. RPM and yum detect this and refuse to install if that library is not installed. * InnoDB: Reloading a table that was evicted while empty caused an AUTO_INCREMENT value to be reset. * InnoDB: Memory allocation sanity checks were added to the memcached code. * InnoDB: A memcached flush_all command raised an assertion. A function that starts a transaction was called from within assertion code. * InnoDB: A data corruption occurred on ARM64. GCC builtins did not issue the correct fences when setting or unsetting the lock word. * InnoDB: Server shutdown was delayed waiting for the purge thread to exit. To avoid this problem, the number of calls to trx_purge() was reduced, and the trx_purge() batch size was reduced to 20. * InnoDB: In READ COMMITTED mode, a REPLACE operation on a unique secondary index resulted in a constraint violation. * InnoDB: The IBUF_BITMAP_FREE bit indicated that there was more free space in the leaf page than was actually available. * InnoDB: Setting lower_case_table_names=0 on a case-insensitive file system could result in a hang condition when running an INSERT INTO ... SELECT ... FROM tbl_name operation with the wrong tbl_name letter case. An error message is now printed and the server exits when attempting to start the server with --lower_case_table_names=0 on a case-insensitive file system. * InnoDB: The server failed to start with an innodb_force_recovery setting greater than 3. InnoDB was set to read-only mode before redo logs were applied. * InnoDB: The trx_sys_read_pertable_file_format_id() function reported the wrong file format. * Partitioning: CREATE TABLE statements that used an invalid function in a subpartitioning expression did not always fail gracefully as expected. * Partitioning: Error handling for failed partitioning-related ALTER TABLE operations against non-partitioned tables was not performed correctly * Partitioning: ALTER TABLE when executed from a stored procedure did not always work correctly with tables partitioned by RANGE. * Replication: Repeatedly checking for ERR_LOCK_WAIT_TIMEOUT (as done, for example by repeatedly executing SHOW SLAVE STATUS) during a prolonged write lock on a table led to an assert. * Replication: If statement based logging was in use, when updating multiple tables in a single statement, a single transaction could be logged as two different transactions. This was due to the binary logging process not properly identifying statements which were operating over transactional tables. The fix ensures that they are correctly identified, even if such statements do not change the contents of the tables.
2015-10-03 14:46:13 +02:00
share/mysql/test/suite/rpl/t/rpl_gtid_transaction_split_across_relay_logs.cnf
share/mysql/test/suite/rpl/t/rpl_gtid_transaction_split_across_relay_logs.test
Changes 5.6.22: * Noisy compiler warnings on FreeBSD 10 were silenced. * CMake workarounds for older Mac OS X and XCode versions were removed. On Mac OS X, compilation always uses Clang, even for 32-bit builds. * Previously, the MYSQL_MAINTAINER_MODE CMake option was turned on by default for debug builds and off for release builds, and MYSQL_MAINTAINER_MODE caused -Werror to be enabled when building with GCC. This made it cumbersome to enable -Werror under certain conditions, such as when compiling with Clang. * Build support was modified to produce the same warnings for Clang as for gcc. * CMake configuration for the Clang compiler sets more appropriate flags for building on Linux. Specifically, -g -fno-omit-frame-pointer -fno-strict-aliasing is now added. * Bugs fixed.
2014-12-02 13:40:09 +01:00
share/mysql/test/suite/rpl/t/rpl_gtid_validate_slave_gtids.test
Changes 5.6.21: The --skip-innodb option is now deprecated and its use results in a warning. It will be removed in a future MySQL release. This also applies to its synonyms (--innodb=OFF, --disable-innodb, and so forth). MySQL Enterprise Edition now includes a set of encryption functions based on the OpenSSL library that expose OpenSSL capabilities at the SQL level. Replication: The new variable simplified_binlog_gtid_recovery can be used to change the way binary log files are searched for previous GTIDs during recovery, speeding up the process when a large number of binary log files exist. Internally, spatial data types such as Geometry are represented as BLOB values, so when invoked with the --hex-blob option, mysqldump now displays spatial values in hex. Bugs Fixed...
2014-10-01 10:34:23 +02:00
share/mysql/test/suite/rpl/t/rpl_gtids_restart_slave_io_lost_trx.test
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/rpl/t/rpl_heartbeat-master.opt
share/mysql/test/suite/rpl/t/rpl_heartbeat.test
share/mysql/test/suite/rpl/t/rpl_heartbeat_2slaves.cnf
share/mysql/test/suite/rpl/t/rpl_heartbeat_2slaves.test
share/mysql/test/suite/rpl/t/rpl_heartbeat_basic.cnf
share/mysql/test/suite/rpl/t/rpl_heartbeat_basic.test
share/mysql/test/suite/rpl/t/rpl_heartbeat_ssl.test
share/mysql/test/suite/rpl/t/rpl_idempotency.test
share/mysql/test/suite/rpl/t/rpl_ignore_db_filter-master.opt
share/mysql/test/suite/rpl/t/rpl_ignore_db_filter-slave.opt
share/mysql/test/suite/rpl/t/rpl_ignore_db_filter.test
share/mysql/test/suite/rpl/t/rpl_ignore_grant-slave.opt
share/mysql/test/suite/rpl/t/rpl_ignore_grant.test
share/mysql/test/suite/rpl/t/rpl_ignore_revoke-slave.opt
share/mysql/test/suite/rpl/t/rpl_ignore_revoke.test
share/mysql/test/suite/rpl/t/rpl_ignore_table-slave.opt
share/mysql/test/suite/rpl/t/rpl_ignore_table.test
share/mysql/test/suite/rpl/t/rpl_ignore_table_filter_insensitive-master.opt
share/mysql/test/suite/rpl/t/rpl_ignore_table_filter_insensitive-slave.opt
share/mysql/test/suite/rpl/t/rpl_ignore_table_filter_insensitive.test
share/mysql/test/suite/rpl/t/rpl_ignore_table_filter_sensitive-slave.opt
share/mysql/test/suite/rpl/t/rpl_ignore_table_filter_sensitive.test
share/mysql/test/suite/rpl/t/rpl_ignore_table_update-slave.opt
share/mysql/test/suite/rpl/t/rpl_ignore_table_update.test
share/mysql/test/suite/rpl/t/rpl_incident-master.opt
share/mysql/test/suite/rpl/t/rpl_incident.test
share/mysql/test/suite/rpl/t/rpl_init_slave-slave.opt
share/mysql/test/suite/rpl/t/rpl_init_slave.test
share/mysql/test/suite/rpl/t/rpl_init_slave_errors.test
share/mysql/test/suite/rpl/t/rpl_innodb-master.opt
share/mysql/test/suite/rpl/t/rpl_innodb_bug28430-master.opt
share/mysql/test/suite/rpl/t/rpl_innodb_bug28430-slave.opt
share/mysql/test/suite/rpl/t/rpl_innodb_bug28430.test
share/mysql/test/suite/rpl/t/rpl_innodb_bug30888.test
share/mysql/test/suite/rpl/t/rpl_innodb_mixed_ddl.test
share/mysql/test/suite/rpl/t/rpl_innodb_mixed_dml.test
share/mysql/test/suite/rpl/t/rpl_insert.test
share/mysql/test/suite/rpl/t/rpl_insert_id-master.opt
share/mysql/test/suite/rpl/t/rpl_insert_id-slave.opt
share/mysql/test/suite/rpl/t/rpl_insert_id.test
share/mysql/test/suite/rpl/t/rpl_insert_id_pk.test
share/mysql/test/suite/rpl/t/rpl_insert_ignore.test
Changes 5.6.20: Security Fix: The linked OpenSSL library for the MySQL 5.6 Commercial Server has been updated from version 1.0.1g to version 1.0.1h. Versions of OpenSSL prior to and including 1.0.1g are reported to be vulnerable to CVE-2014-0224. This change does not affect the Oracle-produced MySQL Community build of MySQL Server 5.6, which uses the yaSSL library instead. DTrace Support MySQL now includes DTrace support on Oracle Linux 6 or higher with UEK kernel. If DTrace is present, server builds will detect it with no special CMake options required. For information about using DTrace on MySQL, see Tracing mysqld Using DTrace. InnoDB Notes Important Change: Redo log writes for large, externally stored BLOB fields could overwrite the most recent checkpoint. The 5.6.20 patch limits the size of redo log BLOB writes to 10% of the redo log file size. The 5.7.5 patch addresses the bug without imposing a limitation. For MySQL 5.5, the bug remains a known limitation. As a result of the redo log BLOB write limit introduced for MySQL 5.6, innodb_log_file_size should be set to a value greater than 10 times the largest BLOB data size found in the rows of your tables plus the length of other variable length fields (VARCHAR, VARBINARY, and TEXT type fields). Failing to do so could result in “Row size too large” errors. No action is required if your innodb_log_file_size setting is already sufficiently large or your tables contain no BLOB data. Functionality Added or Changed Replication: The new system variable binlog_impossible_mode controls what happens if the server cannot write to the binary log, for example, due to a file error. For backward compatibility, the default for binlog_impossible_mode is IGNORE_ERROR, meaning the server logs the error, halts logging, and continues updates to the database. Setting this variable to ABORT_SERVER makes the server halt logging and shut down if it cannot write to the binary log. CMake support was updated to handle CMake version 3. New Debian7, Ubuntu12.04, and Ubuntu14.04 distribution support that was introduced with 5.6.17 now comes with the platform-specific packaging source placed under the packaging directory, in the deb-precise, deb-wheezy, and deb-trusty directories. Support for LinuxThreads has been removed from the source code. LinuxThreads was superseded by NPTL in Linux 2.6. By default, mysql_install_db creates a my.cnf file in the installation base directory using a template. This may be undesireable for some deployments. To enable this behavior to be suppressed, mysql_install_db now supports a --keep-my-cnf option to preserve any existing my.cnf file and not create a new my.cnf file. The mysqlhotcopy utility is now deprecated and will be removed in a future version of MySQL. Among the reasons for this: It works only for the MyISAM and ARCHIVE storage engines; it works on Unix but not Windows. Alternatives include mysqldump and MySQL Enterprise Backup. The timed_mutexes system variable has no effect and is deprecated. Bugs Fixed
2014-08-10 17:11:57 +02:00
share/mysql/test/suite/rpl/t/rpl_insert_on_update.test
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/rpl/t/rpl_invoked_features-master.opt
share/mysql/test/suite/rpl/t/rpl_invoked_features.test
share/mysql/test/suite/rpl/t/rpl_ip_mix-master.opt
share/mysql/test/suite/rpl/t/rpl_ip_mix.cnf
share/mysql/test/suite/rpl/t/rpl_ip_mix.test
share/mysql/test/suite/rpl/t/rpl_ip_mix2-master.opt
share/mysql/test/suite/rpl/t/rpl_ip_mix2.cnf
share/mysql/test/suite/rpl/t/rpl_ip_mix2.test
share/mysql/test/suite/rpl/t/rpl_ipv4_as_ipv6.cnf
share/mysql/test/suite/rpl/t/rpl_ipv4_as_ipv6.test
share/mysql/test/suite/rpl/t/rpl_ipv6.cnf
share/mysql/test/suite/rpl/t/rpl_ipv6.test
Changes 5.6.19: Functionality Added or Changed The obsolete and unmaintained charset2html utility has been removed from MySQL distributions. The mysqlbug, mysql_waitpid, and mysql_zap utilities have been deprecated and will be removed in MySQL 5.7. Bugs Fixed InnoDB: After upgrading from 5.6.10 to MySQL versions up to and including MySQL 5.6.18, InnoDB would attempt to rename obsolete full-text search auxiliary tables on server startup, resulting in an assertion failure. InnoDB: For each insert, memset would be called three times to allocate memory for system fields. To reduce CPU usage, the three memset calls are now combined into a single call. InnoDB: Enabling the InnoDB Table Monitor would result in a ib_table->stat_initialized assertion failure. InnoDB: Setting innodb_max_dirty_pages_pct=0 would leave 1% of dirty pages unflushed. Buffer pool flushing is initiated when the percentage of dirty pages is greater innodb_max_dirty_pages_pct. The internal variables that store the innodb_max_dirty_pages_pct value and the percentage of dirty pages (buf_get_modified_ratio_pct and srv_max_buf_pool_modified_pct) were defined as unsigned integer data types, which meant that a innodb_max_dirty_pages_pct value of 0 required a dirty pages percentage of 1 or greater to initiate buffer pool flushing. To address this problem, the buf_get_modified_ratio_pct and srv_max_buf_pool_modified_pct internal variables are redefined as double data types, which changes the range value for innodb_max_dirty_pages_pct and innodb_max_dirty_pages_pct_lwm from 0 .. 99 to 0 .. 99.99. Additionally, buffer pool flushing is now initiated when the percentage of dirty pages is “greater than or equal to” innodb_max_dirty_pages_pct. Replication: Log rotation events could cause group_relay_log_pos to be moved forward incorrectly within a group. This meant that, when the transaction was retried, or if the SQL thread was stopped in the middle of a transaction following one or more log rotations (such that the transaction or group spanned multiple relay log files), part or all of the group was silently skipped. This issue has been addressed by correcting a problem in the logic used to avoid touching the coordinates of the SQL thread when updating the log position as part of a relay log rotation whereby it was possible to update the SQL thread's coordinates when not using a multi-threaded slave, even in the middle of a group. Replication: When running the server with --gtid-mode=ON, STOP SLAVE followed by START SLAVE resulted in a mismatch between the information provided by INFORMATION_SCHEMA.INNODB_TEMP_TABLE_INFO and the Slave_open_temp_tables status variable: the INNODB_TEMP_TABLE_INFO table showed that no temporary tables existed, but Slave_open_temp_tables had a nonzero value. Replication: In certain cases, the server mishandled triggers and stored procedures that tried to modify other tables when called by CREATE TABLE ... SELECT. This is now handled correctly as an error. Replication: When used on a table employing a transactional storage engine, a failed TRUNCATE TABLE was still written to the binary log and thus replayed on the slave. This could lead to inconsistency when the master retained data that was removed on the slave. Now in such cases TRUNCATE TABLE is logged only when it executes successfully. Replication: The server did not always handle the auto.cnf file correctly in cases where this file's permissions were incorrect. Replication: When the binary log was rotated due to receipt of a SIGHUP signal, the new binary log did not contain the Previous_gtid_event required for subsequent processing of that binary log's GTID events. Now when SIGHUP is received, steps are taken to insure that the server writes the necessary Previous_gtid_event to the new log before writing any GTID events to the new log.
2014-06-02 09:30:38 +02:00
share/mysql/test/suite/rpl/t/rpl_kill_query-slave.opt
share/mysql/test/suite/rpl/t/rpl_kill_query.test
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/rpl/t/rpl_killed_ddl-master.opt
share/mysql/test/suite/rpl/t/rpl_killed_ddl.test
share/mysql/test/suite/rpl/t/rpl_known_bugs_detection-master.opt
share/mysql/test/suite/rpl/t/rpl_known_bugs_detection.test
share/mysql/test/suite/rpl/t/rpl_lcase_tblnames_rewrite_db-slave.opt
share/mysql/test/suite/rpl/t/rpl_lcase_tblnames_rewrite_db.test
share/mysql/test/suite/rpl/t/rpl_loaddata.test
share/mysql/test/suite/rpl/t/rpl_loaddata_charset.test
share/mysql/test/suite/rpl/t/rpl_loaddata_fatal-slave.opt
share/mysql/test/suite/rpl/t/rpl_loaddata_fatal.test
share/mysql/test/suite/rpl/t/rpl_loaddata_m-master.opt
share/mysql/test/suite/rpl/t/rpl_loaddata_m.test
share/mysql/test/suite/rpl/t/rpl_loaddata_map-master.opt
share/mysql/test/suite/rpl/t/rpl_loaddata_map-slave.opt
share/mysql/test/suite/rpl/t/rpl_loaddata_map.test
share/mysql/test/suite/rpl/t/rpl_loaddata_s-slave.opt
share/mysql/test/suite/rpl/t/rpl_loaddata_s.test
share/mysql/test/suite/rpl/t/rpl_loaddata_simple.test
share/mysql/test/suite/rpl/t/rpl_loaddata_symlink-master.opt
share/mysql/test/suite/rpl/t/rpl_loaddata_symlink-master.sh
share/mysql/test/suite/rpl/t/rpl_loaddata_symlink-slave.opt
share/mysql/test/suite/rpl/t/rpl_loaddata_symlink-slave.sh
share/mysql/test/suite/rpl/t/rpl_loaddata_symlink.test
share/mysql/test/suite/rpl/t/rpl_loaddatalocal.test
share/mysql/test/suite/rpl/t/rpl_loadfile.test
share/mysql/test/suite/rpl/t/rpl_locale.test
share/mysql/test/suite/rpl/t/rpl_log_pos.test
Changes 5.6.15: * Previously, MySQL Server distributions included the MySQL Reference Manual in Info format (the Docs/mysql.info file). Because the license for the manual restricts redistribution, its inclusion in Community packages caused problems for downstream redistributors, such as those who create Linux distributions. Community distributions of MySQL Server no longer include the mysql.info file, to make the repackaging and redistribution process easier (for example, the source tarball and its checksum can be used directly). This change applies to all source and binary Community packaging formats. Commercial (Enterprise) distributions are unchanged. * Incompatible Change: Several statement instruments in the setup_instruments table are used by the Performance Schema during the early stages of statement classification before the exact statement type is known. * The Performance Schema now instruments the read/write lock Delegate::lock * A new CMake option, WITH_ASAN, permits enabling address sanitization for compilers that support it. * The hash function used for metadata locking was modified to reduce overhead. * Bugs Fixed
2013-12-03 21:02:41 +01:00
share/mysql/test/suite/rpl/t/rpl_lost_events_on_rotate.test
Changes 5.6.24: * CMake support was updated to handle CMake version 3.1. * The server now includes its version number when it writes the initial “starting” message to the error log, to make it easier to tell which server instance error log output applies to. This value is the same as that available from the version system variable. * ALTER TABLE did not take advantage of fast alterations that might otherwise apply to the operation to be performed, if the table contained temporal columns found to be in pre-5.6.4 format (TIME, DATETIME, and TIMESTAMP columns without support for fractional seconds precision). * Statement digesting as done previously by the Performance Schema is now done at the SQL level regardless of whether the Performance Schema is compiled in and is available to other aspects of server operation that could benefit from it. The default space available for digesting is 1024 bytes, but can be changed at server startup using the max_digest_length system variable. * Bug fixes.
2015-04-08 12:38:48 +02:00
share/mysql/test/suite/rpl/t/rpl_low_slave_net_time_out.test
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/rpl/t/rpl_manual_change_index_file.test
share/mysql/test/suite/rpl/t/rpl_many_optimize.test
share/mysql/test/suite/rpl/t/rpl_master_connection-master.opt
share/mysql/test/suite/rpl/t/rpl_master_connection-slave.opt
share/mysql/test/suite/rpl/t/rpl_master_connection.test
share/mysql/test/suite/rpl/t/rpl_master_pos_wait.test
share/mysql/test/suite/rpl/t/rpl_migration_crash_safe.test
share/mysql/test/suite/rpl/t/rpl_misc_functions-slave.sh
share/mysql/test/suite/rpl/t/rpl_misc_functions.test
share/mysql/test/suite/rpl/t/rpl_mix_found_rows-master.opt
share/mysql/test/suite/rpl/t/rpl_mix_found_rows.test
share/mysql/test/suite/rpl/t/rpl_mix_insert_delayed.test
Changes 5.6.29: * InnoDB: A new InnoDB configuration option, innodb_tmpdir, allows you to configure a separate temporary file directory for online ALTER TABLE operations. This option was introduced to help avoid tmpdir overflows that could occur as a result of large temporary files created during online ALTER TABLE operations. innodb_tmpdir is a SESSION variable and can be configured dynamically using a SET statement. * yaSSL was upgraded to version 2.3.9. This upgrade corrects an issue in which yaSSL handled only cases of zero or one leading zeros for the key agreement instead of potentially any number, which in rare cases could cause connections to fail when using DHE cipher suites. * The Valgrind function signature in mysql-test/valgrind.supp was upgraded for Valgrind 3.11. * Bugs Fixed
2016-02-28 09:58:03 +01:00
share/mysql/test/suite/rpl/t/rpl_mix_missing_data_on_slave.cnf
share/mysql/test/suite/rpl/t/rpl_mix_missing_data_on_slave.test
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/rpl/t/rpl_mixed_binlog_max_cache_size.test
share/mysql/test/suite/rpl/t/rpl_mixed_bit_pk.test
share/mysql/test/suite/rpl/t/rpl_mixed_ddl_dml.test
share/mysql/test/suite/rpl/t/rpl_mixed_drop_create_temp_table.test
share/mysql/test/suite/rpl/t/rpl_mixed_implicit_commit_binlog-master.opt
share/mysql/test/suite/rpl/t/rpl_mixed_implicit_commit_binlog-slave.opt
share/mysql/test/suite/rpl/t/rpl_mixed_implicit_commit_binlog.test
share/mysql/test/suite/rpl/t/rpl_mixed_mixing_engines.test
share/mysql/test/suite/rpl/t/rpl_mixed_row_innodb-master.opt
share/mysql/test/suite/rpl/t/rpl_mts_debug-slave.opt
share/mysql/test/suite/rpl/t/rpl_mts_debug.test
Changes 5.6.22: * Noisy compiler warnings on FreeBSD 10 were silenced. * CMake workarounds for older Mac OS X and XCode versions were removed. On Mac OS X, compilation always uses Clang, even for 32-bit builds. * Previously, the MYSQL_MAINTAINER_MODE CMake option was turned on by default for debug builds and off for release builds, and MYSQL_MAINTAINER_MODE caused -Werror to be enabled when building with GCC. This made it cumbersome to enable -Werror under certain conditions, such as when compiling with Clang. * Build support was modified to produce the same warnings for Clang as for gcc. * CMake configuration for the Clang compiler sets more appropriate flags for building on Linux. Specifically, -g -fno-omit-frame-pointer -fno-strict-aliasing is now added. * Bugs fixed.
2014-12-02 13:40:09 +01:00
share/mysql/test/suite/rpl/t/rpl_mts_execute_partial_trx_with_auto_pos_off-slave.opt
share/mysql/test/suite/rpl/t/rpl_mts_execute_partial_trx_with_auto_pos_off.test
share/mysql/test/suite/rpl/t/rpl_mts_execute_partial_trx_with_auto_pos_on-slave.opt
share/mysql/test/suite/rpl/t/rpl_mts_execute_partial_trx_with_auto_pos_on.test
Changes 5.6.21: The --skip-innodb option is now deprecated and its use results in a warning. It will be removed in a future MySQL release. This also applies to its synonyms (--innodb=OFF, --disable-innodb, and so forth). MySQL Enterprise Edition now includes a set of encryption functions based on the OpenSSL library that expose OpenSSL capabilities at the SQL level. Replication: The new variable simplified_binlog_gtid_recovery can be used to change the way binary log files are searched for previous GTIDs during recovery, speeding up the process when a large number of binary log files exist. Internally, spatial data types such as Geometry are represented as BLOB values, so when invoked with the --hex-blob option, mysqldump now displays spatial values in hex. Bugs Fixed...
2014-10-01 10:34:23 +02:00
share/mysql/test/suite/rpl/t/rpl_mts_gtids_restart_slave_io_lost_trx-slave.opt
share/mysql/test/suite/rpl/t/rpl_mts_gtids_restart_slave_io_lost_trx.test
Changes 5.6.22: * Noisy compiler warnings on FreeBSD 10 were silenced. * CMake workarounds for older Mac OS X and XCode versions were removed. On Mac OS X, compilation always uses Clang, even for 32-bit builds. * Previously, the MYSQL_MAINTAINER_MODE CMake option was turned on by default for debug builds and off for release builds, and MYSQL_MAINTAINER_MODE caused -Werror to be enabled when building with GCC. This made it cumbersome to enable -Werror under certain conditions, such as when compiling with Clang. * Build support was modified to produce the same warnings for Clang as for gcc. * CMake configuration for the Clang compiler sets more appropriate flags for building on Linux. Specifically, -g -fno-omit-frame-pointer -fno-strict-aliasing is now added. * Bugs fixed.
2014-12-02 13:40:09 +01:00
share/mysql/test/suite/rpl/t/rpl_mts_slave_hang_with_partial_trx-slave.opt
share/mysql/test/suite/rpl/t/rpl_mts_slave_hang_with_partial_trx.test
Changes 5.6.26: * Security Fix: Due to the LogJam issue (https://weakdh.org/), OpenSSL has changed the Diffie-Hellman key length parameters for openssl-1.0.1n and up. * Replication: When using a multi-threaded slave, each worker thread has its own queue of transactions to process. In previous MySQL versions, STOP SLAVE waited for all workers to process their entire queue. This logic has been changed so that STOP SLAVE first finds the newest transaction that was committed by any worker thread. Then, it waits for all workers to complete transactions older than that. Newer transactions are not processed. The new logic allows STOP SLAVE to complete faster in case some worker queues contain multiple transactions. * Previously, the max_digest_length system variable controlled the maximum digest length for all server functions that computed statement digests. However, whereas the Performance Schema may need to maintain many digest values, other server functions such as MySQL Enterprise Firewall need only one digest per session. Increasing the max_digest_length value has little impact on total memory requirements for those functions, but can increase Performance Schema memory requirements significantly. To enable configuring digest length separately for the Performance Schema, its digest length is now controlled by the new performance_schema_max_digest_length system variable. * Previously, changes to the validate_password plugin dictionary file (named by the validate_password_dictionary_file system variable) while the server was running required a restart for the server to recognize the changes. Now validate_password_dictionary_file can be set at runtime and assigning a value causes the named file to be read without a restart. In addition, two new status variables are available. validate_password_dictionary_file_last_parsed indicates when the dictionary file was last read, and validate_password_dictionary_file_words_count indicates how many words it contains. * Bugs fixed
2015-07-30 16:39:18 +02:00
share/mysql/test/suite/rpl/t/rpl_mts_stop_slave-slave.opt
share/mysql/test/suite/rpl/t/rpl_mts_stop_slave.test
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/rpl/t/rpl_multi_delete-slave.opt
share/mysql/test/suite/rpl/t/rpl_multi_delete.test
share/mysql/test/suite/rpl/t/rpl_multi_delete2-slave.opt
share/mysql/test/suite/rpl/t/rpl_multi_delete2.test
share/mysql/test/suite/rpl/t/rpl_multi_engine.test
share/mysql/test/suite/rpl/t/rpl_multi_update.test
share/mysql/test/suite/rpl/t/rpl_multi_update2-slave.opt
share/mysql/test/suite/rpl/t/rpl_multi_update2.test
share/mysql/test/suite/rpl/t/rpl_multi_update3.test
share/mysql/test/suite/rpl/t/rpl_multi_update4-slave.opt
share/mysql/test/suite/rpl/t/rpl_multi_update4.test
share/mysql/test/suite/rpl/t/rpl_mysql_upgrade.test
share/mysql/test/suite/rpl/t/rpl_mysqlbinlog_gtid_on.test
share/mysql/test/suite/rpl/t/rpl_name_const.test
share/mysql/test/suite/rpl/t/rpl_non_direct_mixed_mixing_engines.test
share/mysql/test/suite/rpl/t/rpl_non_direct_row_mixing_engines.test
share/mysql/test/suite/rpl/t/rpl_non_direct_stm_mixing_engines.test
share/mysql/test/suite/rpl/t/rpl_nondeterministic_functions.test
share/mysql/test/suite/rpl/t/rpl_not_null_innodb.test
share/mysql/test/suite/rpl/t/rpl_not_null_myisam.test
share/mysql/test/suite/rpl/t/rpl_optimize.test
share/mysql/test/suite/rpl/t/rpl_packet-master.opt
share/mysql/test/suite/rpl/t/rpl_packet-slave.opt
share/mysql/test/suite/rpl/t/rpl_packet.test
share/mysql/test/suite/rpl/t/rpl_parallel-master.opt
share/mysql/test/suite/rpl/t/rpl_parallel-slave.opt
share/mysql/test/suite/rpl/t/rpl_parallel.test
share/mysql/test/suite/rpl/t/rpl_parallel_change_master-slave.opt
share/mysql/test/suite/rpl/t/rpl_parallel_change_master.test
share/mysql/test/suite/rpl/t/rpl_parallel_conf_limits-slave.opt
share/mysql/test/suite/rpl/t/rpl_parallel_conf_limits.test
share/mysql/test/suite/rpl/t/rpl_parallel_conflicts-slave.opt
share/mysql/test/suite/rpl/t/rpl_parallel_conflicts.test
share/mysql/test/suite/rpl/t/rpl_parallel_ddl-slave.opt
share/mysql/test/suite/rpl/t/rpl_parallel_ddl.test
share/mysql/test/suite/rpl/t/rpl_parallel_innodb-master.opt
share/mysql/test/suite/rpl/t/rpl_parallel_innodb-slave.opt
share/mysql/test/suite/rpl/t/rpl_parallel_innodb.test
share/mysql/test/suite/rpl/t/rpl_parallel_load_data-slave.opt
share/mysql/test/suite/rpl/t/rpl_parallel_load_data.test
share/mysql/test/suite/rpl/t/rpl_parallel_multi_db-master.opt
share/mysql/test/suite/rpl/t/rpl_parallel_multi_db-slave.opt
share/mysql/test/suite/rpl/t/rpl_parallel_multi_db.test
share/mysql/test/suite/rpl/t/rpl_parallel_seconds_behind_master-slave.opt
share/mysql/test/suite/rpl/t/rpl_parallel_seconds_behind_master.test
share/mysql/test/suite/rpl/t/rpl_parallel_show_binlog_events_purge_logs.test
share/mysql/test/suite/rpl/t/rpl_parallel_start_stop-slave.opt
share/mysql/test/suite/rpl/t/rpl_parallel_start_stop.test
share/mysql/test/suite/rpl/t/rpl_parallel_switch_sequential-slave.opt
share/mysql/test/suite/rpl/t/rpl_parallel_switch_sequential.test
share/mysql/test/suite/rpl/t/rpl_parallel_temp_query-slave.opt
share/mysql/test/suite/rpl/t/rpl_parallel_temp_query.test
Changes 5.6.20: Security Fix: The linked OpenSSL library for the MySQL 5.6 Commercial Server has been updated from version 1.0.1g to version 1.0.1h. Versions of OpenSSL prior to and including 1.0.1g are reported to be vulnerable to CVE-2014-0224. This change does not affect the Oracle-produced MySQL Community build of MySQL Server 5.6, which uses the yaSSL library instead. DTrace Support MySQL now includes DTrace support on Oracle Linux 6 or higher with UEK kernel. If DTrace is present, server builds will detect it with no special CMake options required. For information about using DTrace on MySQL, see Tracing mysqld Using DTrace. InnoDB Notes Important Change: Redo log writes for large, externally stored BLOB fields could overwrite the most recent checkpoint. The 5.6.20 patch limits the size of redo log BLOB writes to 10% of the redo log file size. The 5.7.5 patch addresses the bug without imposing a limitation. For MySQL 5.5, the bug remains a known limitation. As a result of the redo log BLOB write limit introduced for MySQL 5.6, innodb_log_file_size should be set to a value greater than 10 times the largest BLOB data size found in the rows of your tables plus the length of other variable length fields (VARCHAR, VARBINARY, and TEXT type fields). Failing to do so could result in “Row size too large” errors. No action is required if your innodb_log_file_size setting is already sufficiently large or your tables contain no BLOB data. Functionality Added or Changed Replication: The new system variable binlog_impossible_mode controls what happens if the server cannot write to the binary log, for example, due to a file error. For backward compatibility, the default for binlog_impossible_mode is IGNORE_ERROR, meaning the server logs the error, halts logging, and continues updates to the database. Setting this variable to ABORT_SERVER makes the server halt logging and shut down if it cannot write to the binary log. CMake support was updated to handle CMake version 3. New Debian7, Ubuntu12.04, and Ubuntu14.04 distribution support that was introduced with 5.6.17 now comes with the platform-specific packaging source placed under the packaging directory, in the deb-precise, deb-wheezy, and deb-trusty directories. Support for LinuxThreads has been removed from the source code. LinuxThreads was superseded by NPTL in Linux 2.6. By default, mysql_install_db creates a my.cnf file in the installation base directory using a template. This may be undesireable for some deployments. To enable this behavior to be suppressed, mysql_install_db now supports a --keep-my-cnf option to preserve any existing my.cnf file and not create a new my.cnf file. The mysqlhotcopy utility is now deprecated and will be removed in a future version of MySQL. Among the reasons for this: It works only for the MyISAM and ARCHIVE storage engines; it works on Unix but not Windows. Alternatives include mysqldump and MySQL Enterprise Backup. The timed_mutexes system variable has no effect and is deprecated. Bugs Fixed
2014-08-10 17:11:57 +02:00
share/mysql/test/suite/rpl/t/rpl_parallel_worker_error.test
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/rpl/t/rpl_partition_archive.test
share/mysql/test/suite/rpl/t/rpl_partition_innodb-master.opt
share/mysql/test/suite/rpl/t/rpl_partition_innodb.test
share/mysql/test/suite/rpl/t/rpl_partition_memory.test
share/mysql/test/suite/rpl/t/rpl_partition_myisam.test
share/mysql/test/suite/rpl/t/rpl_plugin_load-master.opt
share/mysql/test/suite/rpl/t/rpl_plugin_load-slave.opt
share/mysql/test/suite/rpl/t/rpl_plugin_load.test
share/mysql/test/suite/rpl/t/rpl_ps.test
share/mysql/test/suite/rpl/t/rpl_rbr_to_sbr.test
share/mysql/test/suite/rpl/t/rpl_read_old_relay_log_info.test
share/mysql/test/suite/rpl/t/rpl_read_only.test
Changes 5.6.22: * Noisy compiler warnings on FreeBSD 10 were silenced. * CMake workarounds for older Mac OS X and XCode versions were removed. On Mac OS X, compilation always uses Clang, even for 32-bit builds. * Previously, the MYSQL_MAINTAINER_MODE CMake option was turned on by default for debug builds and off for release builds, and MYSQL_MAINTAINER_MODE caused -Werror to be enabled when building with GCC. This made it cumbersome to enable -Werror under certain conditions, such as when compiling with Clang. * Build support was modified to produce the same warnings for Clang as for gcc. * CMake configuration for the Clang compiler sets more appropriate flags for building on Linux. Specifically, -g -fno-omit-frame-pointer -fno-strict-aliasing is now added. * Bugs fixed.
2014-12-02 13:40:09 +01:00
share/mysql/test/suite/rpl/t/rpl_recovery_empty_sqlthd_pos-slave.opt
share/mysql/test/suite/rpl/t/rpl_recovery_empty_sqlthd_pos.test
share/mysql/test/suite/rpl/t/rpl_recovery_replicate_same_server_id-slave.opt
share/mysql/test/suite/rpl/t/rpl_recovery_replicate_same_server_id.test
Changes 5.6.27: * InnoDB: The new innodb_numa_interleave read-only configuration option allows you to enable the NUMA interleave memory policy for allocation of the InnoDB buffer pool. When innodb_numa_interleave is enabled, the NUMA memory policy is set to MPOL_INTERLEAVE for the mysqld process. After the InnoDB buffer pool is allocated, the NUMA memory policy is set back to MPOL_DEFAULT. This option is only available on NUMA-enabled systems. * yaSSL was upgraded to version 2.3.8. * RPM .spec files were updated so that MySQL Server builds from source RPM packages will include the proper files to take advantage of operating system NUMA capabilities. This introduces a runtime dependency on libnuma.so.1. RPM and yum detect this and refuse to install if that library is not installed. * InnoDB: Reloading a table that was evicted while empty caused an AUTO_INCREMENT value to be reset. * InnoDB: Memory allocation sanity checks were added to the memcached code. * InnoDB: A memcached flush_all command raised an assertion. A function that starts a transaction was called from within assertion code. * InnoDB: A data corruption occurred on ARM64. GCC builtins did not issue the correct fences when setting or unsetting the lock word. * InnoDB: Server shutdown was delayed waiting for the purge thread to exit. To avoid this problem, the number of calls to trx_purge() was reduced, and the trx_purge() batch size was reduced to 20. * InnoDB: In READ COMMITTED mode, a REPLACE operation on a unique secondary index resulted in a constraint violation. * InnoDB: The IBUF_BITMAP_FREE bit indicated that there was more free space in the leaf page than was actually available. * InnoDB: Setting lower_case_table_names=0 on a case-insensitive file system could result in a hang condition when running an INSERT INTO ... SELECT ... FROM tbl_name operation with the wrong tbl_name letter case. An error message is now printed and the server exits when attempting to start the server with --lower_case_table_names=0 on a case-insensitive file system. * InnoDB: The server failed to start with an innodb_force_recovery setting greater than 3. InnoDB was set to read-only mode before redo logs were applied. * InnoDB: The trx_sys_read_pertable_file_format_id() function reported the wrong file format. * Partitioning: CREATE TABLE statements that used an invalid function in a subpartitioning expression did not always fail gracefully as expected. * Partitioning: Error handling for failed partitioning-related ALTER TABLE operations against non-partitioned tables was not performed correctly * Partitioning: ALTER TABLE when executed from a stored procedure did not always work correctly with tables partitioned by RANGE. * Replication: Repeatedly checking for ERR_LOCK_WAIT_TIMEOUT (as done, for example by repeatedly executing SHOW SLAVE STATUS) during a prolonged write lock on a table led to an assert. * Replication: If statement based logging was in use, when updating multiple tables in a single statement, a single transaction could be logged as two different transactions. This was due to the binary logging process not properly identifying statements which were operating over transactional tables. The fix ensures that they are correctly identified, even if such statements do not change the contents of the tables.
2015-10-03 14:46:13 +02:00
share/mysql/test/suite/rpl/t/rpl_relay_log_recovery_positions.test
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/rpl/t/rpl_relay_space_innodb.test
share/mysql/test/suite/rpl/t/rpl_relay_space_myisam.test
share/mysql/test/suite/rpl/t/rpl_relayrotate-slave.opt
share/mysql/test/suite/rpl/t/rpl_relayrotate.test
share/mysql/test/suite/rpl/t/rpl_relayspace-slave.opt
share/mysql/test/suite/rpl/t/rpl_relayspace.test
share/mysql/test/suite/rpl/t/rpl_replicate_do-slave.opt
share/mysql/test/suite/rpl/t/rpl_replicate_do.test
Changes 5.6.17: Functionality Added or Changed Incompatible Change: The AES_ENCRYPT() and AES_DECRYPT() functions now permit control of the block encryption mode and take an optional initialization vector argument: The new block_encryption_mode system variable controls the mode for block-based encryption algorithms. Its default value is aes-128-ecb, which signifies encryption using a key length of 128 bits and ECB mode. An optional init_vector argument provides an initialization vector for encryption modes that require it: AES_ENCRYPT(str,key_str[,init_vector]) AES_DECRYPT(crypt_str,key_str[,init_vector]) A random string of bytes to use for the initialization vector can be produced by calling the new RANDOM_BYTES() function. For more information, see Encryption and Compression Functions. These changes make statements that use AES_ENCRYPT() or AES_DECRYPT() unsafe for statement-based replication and they cannot be stored in the query cache. Queries that use RANDOM_BYTES() are unsafe for statement-based replication and cannot be stored in the query cache. Incompatible Change: The ERROR_FOR_DIVISION_BY_ZERO, NO_ZERO_DATE, and NO_ZERO_IN_DATE SQL modes now are deprecated and setting the sql_mode value to include any of them generates a warning. In MySQL 5.7, these modes do nothing. Instead, their effects are included in the effects of strict SQL mode (STRICT_ALL_TABLES or STRICT_TRANS_TABLES). The motivation for the change in MySQL 5.7 is to reduce the number of SQL modes with an effect dependent on strict mode and make them part of strict mode itself. To make advance preparation for an upgrade to MySQL 5.7, see SQL Mode Changes in MySQL 5.7. That discussion provides guidelines to assess whether your applications will be affected by the SQL mode changes in MySQL 5.7. InnoDB: MySQL now supports rebuilding regular and partitioned InnoDB tables using online DDL (ALGORITHM=INPLACE) for the following operations: OPTIMIZE TABLE ALTER TABLE ... FORCE ALTER TABLE ... ENGINE=INNODB (when run on an InnoDB table) Online DDL support reduces table rebuild time and permits concurrent DML, which helps reduce user application downtime. For additional information, see Overview of Online DDL. On Solaris, mysql_config --libs now includes -R/path/to/library so that libraries can be found at runtime. mysql_install_db provides a more informative diagnostic message when required Perl modules are missing. The IGNORE clause for ALTER TABLE is now deprecated and will be removed in a future version of MySQL. ALTER IGNORE TABLE causes problems for replication, prevents online ALTER TABLE for unique index creation, and causes problems with foreign keys (rows removed in the parent table). Bugs Fixed
2014-03-31 12:32:13 +02:00
share/mysql/test/suite/rpl/t/rpl_replicate_event_after_sync_stage.test
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/rpl/t/rpl_replicate_ignore_db-slave.opt
share/mysql/test/suite/rpl/t/rpl_replicate_ignore_db.test
share/mysql/test/suite/rpl/t/rpl_replicate_rewrite_db.test
share/mysql/test/suite/rpl/t/rpl_report-slave.opt
share/mysql/test/suite/rpl/t/rpl_report.test
share/mysql/test/suite/rpl/t/rpl_report_port-master.opt
share/mysql/test/suite/rpl/t/rpl_report_port.test
share/mysql/test/suite/rpl/t/rpl_rewrite_db_filter-master.opt
share/mysql/test/suite/rpl/t/rpl_rewrite_db_filter-slave.opt
share/mysql/test/suite/rpl/t/rpl_rewrite_db_filter.test
share/mysql/test/suite/rpl/t/rpl_rewrt_db-slave.opt
share/mysql/test/suite/rpl/t/rpl_rewrt_db.test
Changes 5.6.21: The --skip-innodb option is now deprecated and its use results in a warning. It will be removed in a future MySQL release. This also applies to its synonyms (--innodb=OFF, --disable-innodb, and so forth). MySQL Enterprise Edition now includes a set of encryption functions based on the OpenSSL library that expose OpenSSL capabilities at the SQL level. Replication: The new variable simplified_binlog_gtid_recovery can be used to change the way binary log files are searched for previous GTIDs during recovery, speeding up the process when a large number of binary log files exist. Internally, spatial data types such as Geometry are represented as BLOB values, so when invoked with the --hex-blob option, mysqldump now displays spatial values in hex. Bugs Fixed...
2014-10-01 10:34:23 +02:00
share/mysql/test/suite/rpl/t/rpl_rotate_gtid.test
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/rpl/t/rpl_rotate_logs.cnf
share/mysql/test/suite/rpl/t/rpl_rotate_logs.test
share/mysql/test/suite/rpl/t/rpl_rotate_purge_deadlock-master.opt
share/mysql/test/suite/rpl/t/rpl_rotate_purge_deadlock.test
Changes 5.6.19: Functionality Added or Changed The obsolete and unmaintained charset2html utility has been removed from MySQL distributions. The mysqlbug, mysql_waitpid, and mysql_zap utilities have been deprecated and will be removed in MySQL 5.7. Bugs Fixed InnoDB: After upgrading from 5.6.10 to MySQL versions up to and including MySQL 5.6.18, InnoDB would attempt to rename obsolete full-text search auxiliary tables on server startup, resulting in an assertion failure. InnoDB: For each insert, memset would be called three times to allocate memory for system fields. To reduce CPU usage, the three memset calls are now combined into a single call. InnoDB: Enabling the InnoDB Table Monitor would result in a ib_table->stat_initialized assertion failure. InnoDB: Setting innodb_max_dirty_pages_pct=0 would leave 1% of dirty pages unflushed. Buffer pool flushing is initiated when the percentage of dirty pages is greater innodb_max_dirty_pages_pct. The internal variables that store the innodb_max_dirty_pages_pct value and the percentage of dirty pages (buf_get_modified_ratio_pct and srv_max_buf_pool_modified_pct) were defined as unsigned integer data types, which meant that a innodb_max_dirty_pages_pct value of 0 required a dirty pages percentage of 1 or greater to initiate buffer pool flushing. To address this problem, the buf_get_modified_ratio_pct and srv_max_buf_pool_modified_pct internal variables are redefined as double data types, which changes the range value for innodb_max_dirty_pages_pct and innodb_max_dirty_pages_pct_lwm from 0 .. 99 to 0 .. 99.99. Additionally, buffer pool flushing is now initiated when the percentage of dirty pages is “greater than or equal to” innodb_max_dirty_pages_pct. Replication: Log rotation events could cause group_relay_log_pos to be moved forward incorrectly within a group. This meant that, when the transaction was retried, or if the SQL thread was stopped in the middle of a transaction following one or more log rotations (such that the transaction or group spanned multiple relay log files), part or all of the group was silently skipped. This issue has been addressed by correcting a problem in the logic used to avoid touching the coordinates of the SQL thread when updating the log position as part of a relay log rotation whereby it was possible to update the SQL thread's coordinates when not using a multi-threaded slave, even in the middle of a group. Replication: When running the server with --gtid-mode=ON, STOP SLAVE followed by START SLAVE resulted in a mismatch between the information provided by INFORMATION_SCHEMA.INNODB_TEMP_TABLE_INFO and the Slave_open_temp_tables status variable: the INNODB_TEMP_TABLE_INFO table showed that no temporary tables existed, but Slave_open_temp_tables had a nonzero value. Replication: In certain cases, the server mishandled triggers and stored procedures that tried to modify other tables when called by CREATE TABLE ... SELECT. This is now handled correctly as an error. Replication: When used on a table employing a transactional storage engine, a failed TRUNCATE TABLE was still written to the binary log and thus replayed on the slave. This could lead to inconsistency when the master retained data that was removed on the slave. Now in such cases TRUNCATE TABLE is logged only when it executes successfully. Replication: The server did not always handle the auto.cnf file correctly in cases where this file's permissions were incorrect. Replication: When the binary log was rotated due to receipt of a SIGHUP signal, the new binary log did not contain the Previous_gtid_event required for subsequent processing of that binary log's GTID events. Now when SIGHUP is received, steps are taken to insure that the server writes the necessary Previous_gtid_event to the new log before writing any GTID events to the new log.
2014-06-02 09:30:38 +02:00
share/mysql/test/suite/rpl/t/rpl_rotate_row_trans.test
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/rpl/t/rpl_row_001.test
share/mysql/test/suite/rpl/t/rpl_row_4_bytes-master.opt
share/mysql/test/suite/rpl/t/rpl_row_4_bytes.test
share/mysql/test/suite/rpl/t/rpl_row_NOW.test
share/mysql/test/suite/rpl/t/rpl_row_USER.test
share/mysql/test/suite/rpl/t/rpl_row_UUID.test
share/mysql/test/suite/rpl/t/rpl_row_basic_11bugs-master.opt
share/mysql/test/suite/rpl/t/rpl_row_basic_11bugs.test
share/mysql/test/suite/rpl/t/rpl_row_basic_2myisam.test
share/mysql/test/suite/rpl/t/rpl_row_basic_3innodb.test
share/mysql/test/suite/rpl/t/rpl_row_basic_8partition.test
share/mysql/test/suite/rpl/t/rpl_row_basic_allow_batching.test
share/mysql/test/suite/rpl/t/rpl_row_binlog_max_cache_size.test
share/mysql/test/suite/rpl/t/rpl_row_blob_innodb.test
share/mysql/test/suite/rpl/t/rpl_row_blob_myisam.test
share/mysql/test/suite/rpl/t/rpl_row_colSize.test
share/mysql/test/suite/rpl/t/rpl_row_conflicts.test
Changes 5.6.19: Functionality Added or Changed The obsolete and unmaintained charset2html utility has been removed from MySQL distributions. The mysqlbug, mysql_waitpid, and mysql_zap utilities have been deprecated and will be removed in MySQL 5.7. Bugs Fixed InnoDB: After upgrading from 5.6.10 to MySQL versions up to and including MySQL 5.6.18, InnoDB would attempt to rename obsolete full-text search auxiliary tables on server startup, resulting in an assertion failure. InnoDB: For each insert, memset would be called three times to allocate memory for system fields. To reduce CPU usage, the three memset calls are now combined into a single call. InnoDB: Enabling the InnoDB Table Monitor would result in a ib_table->stat_initialized assertion failure. InnoDB: Setting innodb_max_dirty_pages_pct=0 would leave 1% of dirty pages unflushed. Buffer pool flushing is initiated when the percentage of dirty pages is greater innodb_max_dirty_pages_pct. The internal variables that store the innodb_max_dirty_pages_pct value and the percentage of dirty pages (buf_get_modified_ratio_pct and srv_max_buf_pool_modified_pct) were defined as unsigned integer data types, which meant that a innodb_max_dirty_pages_pct value of 0 required a dirty pages percentage of 1 or greater to initiate buffer pool flushing. To address this problem, the buf_get_modified_ratio_pct and srv_max_buf_pool_modified_pct internal variables are redefined as double data types, which changes the range value for innodb_max_dirty_pages_pct and innodb_max_dirty_pages_pct_lwm from 0 .. 99 to 0 .. 99.99. Additionally, buffer pool flushing is now initiated when the percentage of dirty pages is “greater than or equal to” innodb_max_dirty_pages_pct. Replication: Log rotation events could cause group_relay_log_pos to be moved forward incorrectly within a group. This meant that, when the transaction was retried, or if the SQL thread was stopped in the middle of a transaction following one or more log rotations (such that the transaction or group spanned multiple relay log files), part or all of the group was silently skipped. This issue has been addressed by correcting a problem in the logic used to avoid touching the coordinates of the SQL thread when updating the log position as part of a relay log rotation whereby it was possible to update the SQL thread's coordinates when not using a multi-threaded slave, even in the middle of a group. Replication: When running the server with --gtid-mode=ON, STOP SLAVE followed by START SLAVE resulted in a mismatch between the information provided by INFORMATION_SCHEMA.INNODB_TEMP_TABLE_INFO and the Slave_open_temp_tables status variable: the INNODB_TEMP_TABLE_INFO table showed that no temporary tables existed, but Slave_open_temp_tables had a nonzero value. Replication: In certain cases, the server mishandled triggers and stored procedures that tried to modify other tables when called by CREATE TABLE ... SELECT. This is now handled correctly as an error. Replication: When used on a table employing a transactional storage engine, a failed TRUNCATE TABLE was still written to the binary log and thus replayed on the slave. This could lead to inconsistency when the master retained data that was removed on the slave. Now in such cases TRUNCATE TABLE is logged only when it executes successfully. Replication: The server did not always handle the auto.cnf file correctly in cases where this file's permissions were incorrect. Replication: When the binary log was rotated due to receipt of a SIGHUP signal, the new binary log did not contain the Previous_gtid_event required for subsequent processing of that binary log's GTID events. Now when SIGHUP is received, steps are taken to insure that the server writes the necessary Previous_gtid_event to the new log before writing any GTID events to the new log.
2014-06-02 09:30:38 +02:00
share/mysql/test/suite/rpl/t/rpl_row_corrupt-master.opt
share/mysql/test/suite/rpl/t/rpl_row_corrupt-slave.opt
share/mysql/test/suite/rpl/t/rpl_row_corrupt.test
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/rpl/t/rpl_row_corruption-slave.opt
share/mysql/test/suite/rpl/t/rpl_row_corruption.test
share/mysql/test/suite/rpl/t/rpl_row_crash_safe-slave.opt
share/mysql/test/suite/rpl/t/rpl_row_crash_safe.test
Changes 5.6.19: Functionality Added or Changed The obsolete and unmaintained charset2html utility has been removed from MySQL distributions. The mysqlbug, mysql_waitpid, and mysql_zap utilities have been deprecated and will be removed in MySQL 5.7. Bugs Fixed InnoDB: After upgrading from 5.6.10 to MySQL versions up to and including MySQL 5.6.18, InnoDB would attempt to rename obsolete full-text search auxiliary tables on server startup, resulting in an assertion failure. InnoDB: For each insert, memset would be called three times to allocate memory for system fields. To reduce CPU usage, the three memset calls are now combined into a single call. InnoDB: Enabling the InnoDB Table Monitor would result in a ib_table->stat_initialized assertion failure. InnoDB: Setting innodb_max_dirty_pages_pct=0 would leave 1% of dirty pages unflushed. Buffer pool flushing is initiated when the percentage of dirty pages is greater innodb_max_dirty_pages_pct. The internal variables that store the innodb_max_dirty_pages_pct value and the percentage of dirty pages (buf_get_modified_ratio_pct and srv_max_buf_pool_modified_pct) were defined as unsigned integer data types, which meant that a innodb_max_dirty_pages_pct value of 0 required a dirty pages percentage of 1 or greater to initiate buffer pool flushing. To address this problem, the buf_get_modified_ratio_pct and srv_max_buf_pool_modified_pct internal variables are redefined as double data types, which changes the range value for innodb_max_dirty_pages_pct and innodb_max_dirty_pages_pct_lwm from 0 .. 99 to 0 .. 99.99. Additionally, buffer pool flushing is now initiated when the percentage of dirty pages is “greater than or equal to” innodb_max_dirty_pages_pct. Replication: Log rotation events could cause group_relay_log_pos to be moved forward incorrectly within a group. This meant that, when the transaction was retried, or if the SQL thread was stopped in the middle of a transaction following one or more log rotations (such that the transaction or group spanned multiple relay log files), part or all of the group was silently skipped. This issue has been addressed by correcting a problem in the logic used to avoid touching the coordinates of the SQL thread when updating the log position as part of a relay log rotation whereby it was possible to update the SQL thread's coordinates when not using a multi-threaded slave, even in the middle of a group. Replication: When running the server with --gtid-mode=ON, STOP SLAVE followed by START SLAVE resulted in a mismatch between the information provided by INFORMATION_SCHEMA.INNODB_TEMP_TABLE_INFO and the Slave_open_temp_tables status variable: the INNODB_TEMP_TABLE_INFO table showed that no temporary tables existed, but Slave_open_temp_tables had a nonzero value. Replication: In certain cases, the server mishandled triggers and stored procedures that tried to modify other tables when called by CREATE TABLE ... SELECT. This is now handled correctly as an error. Replication: When used on a table employing a transactional storage engine, a failed TRUNCATE TABLE was still written to the binary log and thus replayed on the slave. This could lead to inconsistency when the master retained data that was removed on the slave. Now in such cases TRUNCATE TABLE is logged only when it executes successfully. Replication: The server did not always handle the auto.cnf file correctly in cases where this file's permissions were incorrect. Replication: When the binary log was rotated due to receipt of a SIGHUP signal, the new binary log did not contain the Previous_gtid_event required for subsequent processing of that binary log's GTID events. Now when SIGHUP is received, steps are taken to insure that the server writes the necessary Previous_gtid_event to the new log before writing any GTID events to the new log.
2014-06-02 09:30:38 +02:00
share/mysql/test/suite/rpl/t/rpl_row_create_select.test
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/rpl/t/rpl_row_create_table.test
share/mysql/test/suite/rpl/t/rpl_row_delayed_ins.test
share/mysql/test/suite/rpl/t/rpl_row_drop.test
share/mysql/test/suite/rpl/t/rpl_row_drop_create_temp_table.test
share/mysql/test/suite/rpl/t/rpl_row_err_daisychain-master.opt
share/mysql/test/suite/rpl/t/rpl_row_err_daisychain-slave.opt
share/mysql/test/suite/rpl/t/rpl_row_event_max_size-master.opt
share/mysql/test/suite/rpl/t/rpl_row_event_max_size-slave.opt
share/mysql/test/suite/rpl/t/rpl_row_event_max_size.test
share/mysql/test/suite/rpl/t/rpl_row_find_row.test
share/mysql/test/suite/rpl/t/rpl_row_flsh_tbls.test
share/mysql/test/suite/rpl/t/rpl_row_func001.test
share/mysql/test/suite/rpl/t/rpl_row_func002.test
share/mysql/test/suite/rpl/t/rpl_row_func003.test
share/mysql/test/suite/rpl/t/rpl_row_hash_scan.test
share/mysql/test/suite/rpl/t/rpl_row_hash_scan_sanity.test
share/mysql/test/suite/rpl/t/rpl_row_idempotency.test
share/mysql/test/suite/rpl/t/rpl_row_ignorable_event-master.opt
share/mysql/test/suite/rpl/t/rpl_row_ignorable_event-slave.opt
share/mysql/test/suite/rpl/t/rpl_row_ignorable_event.test
share/mysql/test/suite/rpl/t/rpl_row_img.cnf
share/mysql/test/suite/rpl/t/rpl_row_img_blobs.cnf
share/mysql/test/suite/rpl/t/rpl_row_img_blobs.test
share/mysql/test/suite/rpl/t/rpl_row_img_eng_full.cnf
share/mysql/test/suite/rpl/t/rpl_row_img_eng_full.test
share/mysql/test/suite/rpl/t/rpl_row_img_eng_min.cnf
share/mysql/test/suite/rpl/t/rpl_row_img_eng_min.test
share/mysql/test/suite/rpl/t/rpl_row_img_eng_noblob.cnf
share/mysql/test/suite/rpl/t/rpl_row_img_eng_noblob.test
share/mysql/test/suite/rpl/t/rpl_row_img_idx_full.cnf
share/mysql/test/suite/rpl/t/rpl_row_img_idx_full.test
share/mysql/test/suite/rpl/t/rpl_row_img_idx_min.cnf
share/mysql/test/suite/rpl/t/rpl_row_img_idx_min.test
share/mysql/test/suite/rpl/t/rpl_row_img_idx_noblob.cnf
share/mysql/test/suite/rpl/t/rpl_row_img_idx_noblob.test
share/mysql/test/suite/rpl/t/rpl_row_img_misc.test
share/mysql/test/suite/rpl/t/rpl_row_img_sanity.test
share/mysql/test/suite/rpl/t/rpl_row_implicit_commit_binlog-master.opt
share/mysql/test/suite/rpl/t/rpl_row_implicit_commit_binlog-slave.opt
share/mysql/test/suite/rpl/t/rpl_row_implicit_commit_binlog.test
share/mysql/test/suite/rpl/t/rpl_row_inexist_tbl.test
share/mysql/test/suite/rpl/t/rpl_row_insert_delayed.test
share/mysql/test/suite/rpl/t/rpl_row_lcase_tblnames-slave.opt
share/mysql/test/suite/rpl/t/rpl_row_lcase_tblnames.test
share/mysql/test/suite/rpl/t/rpl_row_loaddata_concurrent.test
share/mysql/test/suite/rpl/t/rpl_row_log-master.opt
share/mysql/test/suite/rpl/t/rpl_row_log-slave.opt
share/mysql/test/suite/rpl/t/rpl_row_log.test
share/mysql/test/suite/rpl/t/rpl_row_log_innodb-master.opt
share/mysql/test/suite/rpl/t/rpl_row_log_innodb.test
share/mysql/test/suite/rpl/t/rpl_row_max_relay_size.test
share/mysql/test/suite/rpl/t/rpl_row_merge_engine.test
share/mysql/test/suite/rpl/t/rpl_row_mixing_engines.test
share/mysql/test/suite/rpl/t/rpl_row_mts_crash_safe-slave.opt
share/mysql/test/suite/rpl/t/rpl_row_mts_crash_safe.test
share/mysql/test/suite/rpl/t/rpl_row_mts_rec_crash_safe-slave.opt
share/mysql/test/suite/rpl/t/rpl_row_mts_rec_crash_safe.test
share/mysql/test/suite/rpl/t/rpl_row_mts_show_relaylog_events.test
share/mysql/test/suite/rpl/t/rpl_row_mysqlbinlog-master.opt
share/mysql/test/suite/rpl/t/rpl_row_mysqlbinlog.test
share/mysql/test/suite/rpl/t/rpl_row_rec_comp_innodb.test
share/mysql/test/suite/rpl/t/rpl_row_rec_comp_myisam.test
share/mysql/test/suite/rpl/t/rpl_row_record_find_myisam.test
share/mysql/test/suite/rpl/t/rpl_row_reset_slave.test
Changes 5.6.27: * InnoDB: The new innodb_numa_interleave read-only configuration option allows you to enable the NUMA interleave memory policy for allocation of the InnoDB buffer pool. When innodb_numa_interleave is enabled, the NUMA memory policy is set to MPOL_INTERLEAVE for the mysqld process. After the InnoDB buffer pool is allocated, the NUMA memory policy is set back to MPOL_DEFAULT. This option is only available on NUMA-enabled systems. * yaSSL was upgraded to version 2.3.8. * RPM .spec files were updated so that MySQL Server builds from source RPM packages will include the proper files to take advantage of operating system NUMA capabilities. This introduces a runtime dependency on libnuma.so.1. RPM and yum detect this and refuse to install if that library is not installed. * InnoDB: Reloading a table that was evicted while empty caused an AUTO_INCREMENT value to be reset. * InnoDB: Memory allocation sanity checks were added to the memcached code. * InnoDB: A memcached flush_all command raised an assertion. A function that starts a transaction was called from within assertion code. * InnoDB: A data corruption occurred on ARM64. GCC builtins did not issue the correct fences when setting or unsetting the lock word. * InnoDB: Server shutdown was delayed waiting for the purge thread to exit. To avoid this problem, the number of calls to trx_purge() was reduced, and the trx_purge() batch size was reduced to 20. * InnoDB: In READ COMMITTED mode, a REPLACE operation on a unique secondary index resulted in a constraint violation. * InnoDB: The IBUF_BITMAP_FREE bit indicated that there was more free space in the leaf page than was actually available. * InnoDB: Setting lower_case_table_names=0 on a case-insensitive file system could result in a hang condition when running an INSERT INTO ... SELECT ... FROM tbl_name operation with the wrong tbl_name letter case. An error message is now printed and the server exits when attempting to start the server with --lower_case_table_names=0 on a case-insensitive file system. * InnoDB: The server failed to start with an innodb_force_recovery setting greater than 3. InnoDB was set to read-only mode before redo logs were applied. * InnoDB: The trx_sys_read_pertable_file_format_id() function reported the wrong file format. * Partitioning: CREATE TABLE statements that used an invalid function in a subpartitioning expression did not always fail gracefully as expected. * Partitioning: Error handling for failed partitioning-related ALTER TABLE operations against non-partitioned tables was not performed correctly * Partitioning: ALTER TABLE when executed from a stored procedure did not always work correctly with tables partitioned by RANGE. * Replication: Repeatedly checking for ERR_LOCK_WAIT_TIMEOUT (as done, for example by repeatedly executing SHOW SLAVE STATUS) during a prolonged write lock on a table led to an assert. * Replication: If statement based logging was in use, when updating multiple tables in a single statement, a single transaction could be logged as two different transactions. This was due to the binary logging process not properly identifying statements which were operating over transactional tables. The fix ensures that they are correctly identified, even if such statements do not change the contents of the tables.
2015-10-03 14:46:13 +02:00
share/mysql/test/suite/rpl/t/rpl_row_rollback_to_savepoint.test
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/rpl/t/rpl_row_show_relaylog_events.test
share/mysql/test/suite/rpl/t/rpl_row_sp001.test
share/mysql/test/suite/rpl/t/rpl_row_sp002_innodb.test
share/mysql/test/suite/rpl/t/rpl_row_sp003.test
share/mysql/test/suite/rpl/t/rpl_row_sp005.test
share/mysql/test/suite/rpl/t/rpl_row_sp006_InnoDB.test
share/mysql/test/suite/rpl/t/rpl_row_sp007_innodb.test
share/mysql/test/suite/rpl/t/rpl_row_sp008.test
share/mysql/test/suite/rpl/t/rpl_row_sp009.test
share/mysql/test/suite/rpl/t/rpl_row_sp010.test
share/mysql/test/suite/rpl/t/rpl_row_sp011-master.opt
share/mysql/test/suite/rpl/t/rpl_row_sp011.test
share/mysql/test/suite/rpl/t/rpl_row_sp012.test
share/mysql/test/suite/rpl/t/rpl_row_tabledefs_2myisam.test
share/mysql/test/suite/rpl/t/rpl_row_tabledefs_3innodb.test
share/mysql/test/suite/rpl/t/rpl_row_tbl_metadata.test
share/mysql/test/suite/rpl/t/rpl_row_trig001.test
share/mysql/test/suite/rpl/t/rpl_row_trig002.test
share/mysql/test/suite/rpl/t/rpl_row_trig003.test
share/mysql/test/suite/rpl/t/rpl_row_trig004.test
share/mysql/test/suite/rpl/t/rpl_row_trunc_temp.test
share/mysql/test/suite/rpl/t/rpl_row_unsafe_funcs.test
share/mysql/test/suite/rpl/t/rpl_row_until.test
share/mysql/test/suite/rpl/t/rpl_row_utf16.test
share/mysql/test/suite/rpl/t/rpl_row_utf32.test
share/mysql/test/suite/rpl/t/rpl_row_view01.test
share/mysql/test/suite/rpl/t/rpl_row_wide_table.test
share/mysql/test/suite/rpl/t/rpl_savepoint.test
Changes 5.6.23: * The linked OpenSSL library for the MySQL Commercial Server has been updated from version 1.0.1j to version 1.0.1k. * Support for the SSL 2.0 and SSL 3.0 protocols has been disabled because they provide weak encryption. * yaSSL was upgraded to version 2.3.7. * The valid date range of the SSL certificates in mysql-test/std_data has been extended to the year 2029. * Bugs Fixed
2015-02-07 20:23:40 +01:00
share/mysql/test/suite/rpl/t/rpl_sbm_previous_gtid_event-slave.opt
share/mysql/test/suite/rpl/t/rpl_sbm_previous_gtid_event.test
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/rpl/t/rpl_seconds_behind_master.test
share/mysql/test/suite/rpl/t/rpl_semi_sync-master.opt
share/mysql/test/suite/rpl/t/rpl_semi_sync-slave.opt
share/mysql/test/suite/rpl/t/rpl_semi_sync.test
Changes 5.6.12: * mysql_upgrade now verifies that the server version matches the version against which it was compiled, and exits if there is a mismatch. In addiion, a --version-check option permits specifying whether to enable version checking (the default), or disable checking if given as --skip-version-checking. * Bugs Fixed
2013-06-04 20:17:25 +02:00
share/mysql/test/suite/rpl/t/rpl_semi_sync_deadlock-master.opt
share/mysql/test/suite/rpl/t/rpl_semi_sync_deadlock-slave.opt
share/mysql/test/suite/rpl/t/rpl_semi_sync_deadlock.test
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/rpl/t/rpl_semi_sync_event-master.opt
share/mysql/test/suite/rpl/t/rpl_semi_sync_event-slave.opt
share/mysql/test/suite/rpl/t/rpl_semi_sync_event.test
Changes 5.6.21: The --skip-innodb option is now deprecated and its use results in a warning. It will be removed in a future MySQL release. This also applies to its synonyms (--innodb=OFF, --disable-innodb, and so forth). MySQL Enterprise Edition now includes a set of encryption functions based on the OpenSSL library that expose OpenSSL capabilities at the SQL level. Replication: The new variable simplified_binlog_gtid_recovery can be used to change the way binary log files are searched for previous GTIDs during recovery, speeding up the process when a large number of binary log files exist. Internally, spatial data types such as Geometry are represented as BLOB values, so when invoked with the --hex-blob option, mysqldump now displays spatial values in hex. Bugs Fixed...
2014-10-01 10:34:23 +02:00
share/mysql/test/suite/rpl/t/rpl_semi_sync_future_logpos-master.opt
share/mysql/test/suite/rpl/t/rpl_semi_sync_future_logpos-slave.opt
share/mysql/test/suite/rpl/t/rpl_semi_sync_future_logpos.test
Changes 5.6.12: * mysql_upgrade now verifies that the server version matches the version against which it was compiled, and exits if there is a mismatch. In addiion, a --version-check option permits specifying whether to enable version checking (the default), or disable checking if given as --skip-version-checking. * Bugs Fixed
2013-06-04 20:17:25 +02:00
share/mysql/test/suite/rpl/t/rpl_semi_sync_group_commit_deadlock-master.opt
share/mysql/test/suite/rpl/t/rpl_semi_sync_group_commit_deadlock-slave.opt
share/mysql/test/suite/rpl/t/rpl_semi_sync_group_commit_deadlock.test
share/mysql/test/suite/rpl/t/rpl_semi_sync_non_group_commit_deadlock-master.opt
share/mysql/test/suite/rpl/t/rpl_semi_sync_non_group_commit_deadlock-slave.opt
share/mysql/test/suite/rpl/t/rpl_semi_sync_non_group_commit_deadlock.test
Changes 5.6.21: The --skip-innodb option is now deprecated and its use results in a warning. It will be removed in a future MySQL release. This also applies to its synonyms (--innodb=OFF, --disable-innodb, and so forth). MySQL Enterprise Edition now includes a set of encryption functions based on the OpenSSL library that expose OpenSSL capabilities at the SQL level. Replication: The new variable simplified_binlog_gtid_recovery can be used to change the way binary log files are searched for previous GTIDs during recovery, speeding up the process when a large number of binary log files exist. Internally, spatial data types such as Geometry are represented as BLOB values, so when invoked with the --hex-blob option, mysqldump now displays spatial values in hex. Bugs Fixed...
2014-10-01 10:34:23 +02:00
share/mysql/test/suite/rpl/t/rpl_semi_sync_shutdown_hang-master.opt
share/mysql/test/suite/rpl/t/rpl_semi_sync_shutdown_hang-slave.opt
share/mysql/test/suite/rpl/t/rpl_semi_sync_shutdown_hang.test
Changes 5.6.20: Security Fix: The linked OpenSSL library for the MySQL 5.6 Commercial Server has been updated from version 1.0.1g to version 1.0.1h. Versions of OpenSSL prior to and including 1.0.1g are reported to be vulnerable to CVE-2014-0224. This change does not affect the Oracle-produced MySQL Community build of MySQL Server 5.6, which uses the yaSSL library instead. DTrace Support MySQL now includes DTrace support on Oracle Linux 6 or higher with UEK kernel. If DTrace is present, server builds will detect it with no special CMake options required. For information about using DTrace on MySQL, see Tracing mysqld Using DTrace. InnoDB Notes Important Change: Redo log writes for large, externally stored BLOB fields could overwrite the most recent checkpoint. The 5.6.20 patch limits the size of redo log BLOB writes to 10% of the redo log file size. The 5.7.5 patch addresses the bug without imposing a limitation. For MySQL 5.5, the bug remains a known limitation. As a result of the redo log BLOB write limit introduced for MySQL 5.6, innodb_log_file_size should be set to a value greater than 10 times the largest BLOB data size found in the rows of your tables plus the length of other variable length fields (VARCHAR, VARBINARY, and TEXT type fields). Failing to do so could result in “Row size too large” errors. No action is required if your innodb_log_file_size setting is already sufficiently large or your tables contain no BLOB data. Functionality Added or Changed Replication: The new system variable binlog_impossible_mode controls what happens if the server cannot write to the binary log, for example, due to a file error. For backward compatibility, the default for binlog_impossible_mode is IGNORE_ERROR, meaning the server logs the error, halts logging, and continues updates to the database. Setting this variable to ABORT_SERVER makes the server halt logging and shut down if it cannot write to the binary log. CMake support was updated to handle CMake version 3. New Debian7, Ubuntu12.04, and Ubuntu14.04 distribution support that was introduced with 5.6.17 now comes with the platform-specific packaging source placed under the packaging directory, in the deb-precise, deb-wheezy, and deb-trusty directories. Support for LinuxThreads has been removed from the source code. LinuxThreads was superseded by NPTL in Linux 2.6. By default, mysql_install_db creates a my.cnf file in the installation base directory using a template. This may be undesireable for some deployments. To enable this behavior to be suppressed, mysql_install_db now supports a --keep-my-cnf option to preserve any existing my.cnf file and not create a new my.cnf file. The mysqlhotcopy utility is now deprecated and will be removed in a future version of MySQL. Among the reasons for this: It works only for the MyISAM and ARCHIVE storage engines; it works on Unix but not Windows. Alternatives include mysqldump and MySQL Enterprise Backup. The timed_mutexes system variable has no effect and is deprecated. Bugs Fixed
2014-08-10 17:11:57 +02:00
share/mysql/test/suite/rpl/t/rpl_semi_sync_uninstall_plugin-master.opt
share/mysql/test/suite/rpl/t/rpl_semi_sync_uninstall_plugin-slave.opt
share/mysql/test/suite/rpl/t/rpl_semi_sync_uninstall_plugin.test
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/rpl/t/rpl_sequential-master.opt
share/mysql/test/suite/rpl/t/rpl_sequential-slave.opt
share/mysql/test/suite/rpl/t/rpl_sequential.test
share/mysql/test/suite/rpl/t/rpl_server_id1.test
Changes 5.6.17: Functionality Added or Changed Incompatible Change: The AES_ENCRYPT() and AES_DECRYPT() functions now permit control of the block encryption mode and take an optional initialization vector argument: The new block_encryption_mode system variable controls the mode for block-based encryption algorithms. Its default value is aes-128-ecb, which signifies encryption using a key length of 128 bits and ECB mode. An optional init_vector argument provides an initialization vector for encryption modes that require it: AES_ENCRYPT(str,key_str[,init_vector]) AES_DECRYPT(crypt_str,key_str[,init_vector]) A random string of bytes to use for the initialization vector can be produced by calling the new RANDOM_BYTES() function. For more information, see Encryption and Compression Functions. These changes make statements that use AES_ENCRYPT() or AES_DECRYPT() unsafe for statement-based replication and they cannot be stored in the query cache. Queries that use RANDOM_BYTES() are unsafe for statement-based replication and cannot be stored in the query cache. Incompatible Change: The ERROR_FOR_DIVISION_BY_ZERO, NO_ZERO_DATE, and NO_ZERO_IN_DATE SQL modes now are deprecated and setting the sql_mode value to include any of them generates a warning. In MySQL 5.7, these modes do nothing. Instead, their effects are included in the effects of strict SQL mode (STRICT_ALL_TABLES or STRICT_TRANS_TABLES). The motivation for the change in MySQL 5.7 is to reduce the number of SQL modes with an effect dependent on strict mode and make them part of strict mode itself. To make advance preparation for an upgrade to MySQL 5.7, see SQL Mode Changes in MySQL 5.7. That discussion provides guidelines to assess whether your applications will be affected by the SQL mode changes in MySQL 5.7. InnoDB: MySQL now supports rebuilding regular and partitioned InnoDB tables using online DDL (ALGORITHM=INPLACE) for the following operations: OPTIMIZE TABLE ALTER TABLE ... FORCE ALTER TABLE ... ENGINE=INNODB (when run on an InnoDB table) Online DDL support reduces table rebuild time and permits concurrent DML, which helps reduce user application downtime. For additional information, see Overview of Online DDL. On Solaris, mysql_config --libs now includes -R/path/to/library so that libraries can be found at runtime. mysql_install_db provides a more informative diagnostic message when required Perl modules are missing. The IGNORE clause for ALTER TABLE is now deprecated and will be removed in a future version of MySQL. ALTER IGNORE TABLE causes problems for replication, prevents online ALTER TABLE for unique index creation, and causes problems with foreign keys (rows removed in the parent table). Bugs Fixed
2014-03-31 12:32:13 +02:00
share/mysql/test/suite/rpl/t/rpl_server_id2-master.opt
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/rpl/t/rpl_server_id2-slave.opt
share/mysql/test/suite/rpl/t/rpl_server_id2.test
Changes 5.6.17: Functionality Added or Changed Incompatible Change: The AES_ENCRYPT() and AES_DECRYPT() functions now permit control of the block encryption mode and take an optional initialization vector argument: The new block_encryption_mode system variable controls the mode for block-based encryption algorithms. Its default value is aes-128-ecb, which signifies encryption using a key length of 128 bits and ECB mode. An optional init_vector argument provides an initialization vector for encryption modes that require it: AES_ENCRYPT(str,key_str[,init_vector]) AES_DECRYPT(crypt_str,key_str[,init_vector]) A random string of bytes to use for the initialization vector can be produced by calling the new RANDOM_BYTES() function. For more information, see Encryption and Compression Functions. These changes make statements that use AES_ENCRYPT() or AES_DECRYPT() unsafe for statement-based replication and they cannot be stored in the query cache. Queries that use RANDOM_BYTES() are unsafe for statement-based replication and cannot be stored in the query cache. Incompatible Change: The ERROR_FOR_DIVISION_BY_ZERO, NO_ZERO_DATE, and NO_ZERO_IN_DATE SQL modes now are deprecated and setting the sql_mode value to include any of them generates a warning. In MySQL 5.7, these modes do nothing. Instead, their effects are included in the effects of strict SQL mode (STRICT_ALL_TABLES or STRICT_TRANS_TABLES). The motivation for the change in MySQL 5.7 is to reduce the number of SQL modes with an effect dependent on strict mode and make them part of strict mode itself. To make advance preparation for an upgrade to MySQL 5.7, see SQL Mode Changes in MySQL 5.7. That discussion provides guidelines to assess whether your applications will be affected by the SQL mode changes in MySQL 5.7. InnoDB: MySQL now supports rebuilding regular and partitioned InnoDB tables using online DDL (ALGORITHM=INPLACE) for the following operations: OPTIMIZE TABLE ALTER TABLE ... FORCE ALTER TABLE ... ENGINE=INNODB (when run on an InnoDB table) Online DDL support reduces table rebuild time and permits concurrent DML, which helps reduce user application downtime. For additional information, see Overview of Online DDL. On Solaris, mysql_config --libs now includes -R/path/to/library so that libraries can be found at runtime. mysql_install_db provides a more informative diagnostic message when required Perl modules are missing. The IGNORE clause for ALTER TABLE is now deprecated and will be removed in a future version of MySQL. ALTER IGNORE TABLE causes problems for replication, prevents online ALTER TABLE for unique index creation, and causes problems with foreign keys (rows removed in the parent table). Bugs Fixed
2014-03-31 12:32:13 +02:00
share/mysql/test/suite/rpl/t/rpl_server_id_ignore-master.opt
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/rpl/t/rpl_server_id_ignore-slave.opt
share/mysql/test/suite/rpl/t/rpl_server_id_ignore.test
share/mysql/test/suite/rpl/t/rpl_server_uuid.cnf
share/mysql/test/suite/rpl/t/rpl_server_uuid.test
share/mysql/test/suite/rpl/t/rpl_session_var.test
share/mysql/test/suite/rpl/t/rpl_set_charset.test
share/mysql/test/suite/rpl/t/rpl_set_null_innodb.test
share/mysql/test/suite/rpl/t/rpl_set_null_myisam.test
share/mysql/test/suite/rpl/t/rpl_show_errors.test
share/mysql/test/suite/rpl/t/rpl_show_master_info_file-master.opt
share/mysql/test/suite/rpl/t/rpl_show_master_info_file.test
share/mysql/test/suite/rpl/t/rpl_show_slave_hosts.cnf
share/mysql/test/suite/rpl/t/rpl_show_slave_hosts.test
share/mysql/test/suite/rpl/t/rpl_show_slave_running.test
Changes 5.6.23: * The linked OpenSSL library for the MySQL Commercial Server has been updated from version 1.0.1j to version 1.0.1k. * Support for the SSL 2.0 and SSL 3.0 protocols has been disabled because they provide weak encryption. * yaSSL was upgraded to version 2.3.7. * The valid date range of the SSL certificates in mysql-test/std_data has been extended to the year 2029. * Bugs Fixed
2015-02-07 20:23:40 +01:00
share/mysql/test/suite/rpl/t/rpl_show_slave_status_deadlock.test
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/rpl/t/rpl_skip_ddl_errors_cli-slave.opt
share/mysql/test/suite/rpl/t/rpl_skip_ddl_errors_cli.test
share/mysql/test/suite/rpl/t/rpl_skip_error-slave.opt
share/mysql/test/suite/rpl/t/rpl_skip_error.test
share/mysql/test/suite/rpl/t/rpl_skip_incident-master.opt
share/mysql/test/suite/rpl/t/rpl_skip_incident-slave.opt
share/mysql/test/suite/rpl/t/rpl_skip_incident.test
Changes 5.6.17: Functionality Added or Changed Incompatible Change: The AES_ENCRYPT() and AES_DECRYPT() functions now permit control of the block encryption mode and take an optional initialization vector argument: The new block_encryption_mode system variable controls the mode for block-based encryption algorithms. Its default value is aes-128-ecb, which signifies encryption using a key length of 128 bits and ECB mode. An optional init_vector argument provides an initialization vector for encryption modes that require it: AES_ENCRYPT(str,key_str[,init_vector]) AES_DECRYPT(crypt_str,key_str[,init_vector]) A random string of bytes to use for the initialization vector can be produced by calling the new RANDOM_BYTES() function. For more information, see Encryption and Compression Functions. These changes make statements that use AES_ENCRYPT() or AES_DECRYPT() unsafe for statement-based replication and they cannot be stored in the query cache. Queries that use RANDOM_BYTES() are unsafe for statement-based replication and cannot be stored in the query cache. Incompatible Change: The ERROR_FOR_DIVISION_BY_ZERO, NO_ZERO_DATE, and NO_ZERO_IN_DATE SQL modes now are deprecated and setting the sql_mode value to include any of them generates a warning. In MySQL 5.7, these modes do nothing. Instead, their effects are included in the effects of strict SQL mode (STRICT_ALL_TABLES or STRICT_TRANS_TABLES). The motivation for the change in MySQL 5.7 is to reduce the number of SQL modes with an effect dependent on strict mode and make them part of strict mode itself. To make advance preparation for an upgrade to MySQL 5.7, see SQL Mode Changes in MySQL 5.7. That discussion provides guidelines to assess whether your applications will be affected by the SQL mode changes in MySQL 5.7. InnoDB: MySQL now supports rebuilding regular and partitioned InnoDB tables using online DDL (ALGORITHM=INPLACE) for the following operations: OPTIMIZE TABLE ALTER TABLE ... FORCE ALTER TABLE ... ENGINE=INNODB (when run on an InnoDB table) Online DDL support reduces table rebuild time and permits concurrent DML, which helps reduce user application downtime. For additional information, see Overview of Online DDL. On Solaris, mysql_config --libs now includes -R/path/to/library so that libraries can be found at runtime. mysql_install_db provides a more informative diagnostic message when required Perl modules are missing. The IGNORE clause for ALTER TABLE is now deprecated and will be removed in a future version of MySQL. ALTER IGNORE TABLE causes problems for replication, prevents online ALTER TABLE for unique index creation, and causes problems with foreign keys (rows removed in the parent table). Bugs Fixed
2014-03-31 12:32:13 +02:00
share/mysql/test/suite/rpl/t/rpl_skip_slave_err_warnings-slave.opt
share/mysql/test/suite/rpl/t/rpl_skip_slave_err_warnings.test
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/rpl/t/rpl_slave_grp_exec.test
share/mysql/test/suite/rpl/t/rpl_slave_load_in.test
share/mysql/test/suite/rpl/t/rpl_slave_load_remove_tmpfile.test
share/mysql/test/suite/rpl/t/rpl_slave_load_tmpdir_not_exist-master.opt
share/mysql/test/suite/rpl/t/rpl_slave_load_tmpdir_not_exist-slave.opt
share/mysql/test/suite/rpl/t/rpl_slave_load_tmpdir_not_exist.test
share/mysql/test/suite/rpl/t/rpl_slave_skip.test
share/mysql/test/suite/rpl/t/rpl_slave_start.test
share/mysql/test/suite/rpl/t/rpl_slave_status.test
share/mysql/test/suite/rpl/t/rpl_slow_query_log-slave.opt
share/mysql/test/suite/rpl/t/rpl_slow_query_log.test
share/mysql/test/suite/rpl/t/rpl_sp-master.opt
share/mysql/test/suite/rpl/t/rpl_sp-slave.opt
share/mysql/test/suite/rpl/t/rpl_sp.test
share/mysql/test/suite/rpl/t/rpl_sp004.test
share/mysql/test/suite/rpl/t/rpl_sp_effects-master.opt
share/mysql/test/suite/rpl/t/rpl_sp_effects-slave.opt
share/mysql/test/suite/rpl/t/rpl_sp_effects.test
Changes 5.6.24: * CMake support was updated to handle CMake version 3.1. * The server now includes its version number when it writes the initial “starting” message to the error log, to make it easier to tell which server instance error log output applies to. This value is the same as that available from the version system variable. * ALTER TABLE did not take advantage of fast alterations that might otherwise apply to the operation to be performed, if the table contained temporal columns found to be in pre-5.6.4 format (TIME, DATETIME, and TIMESTAMP columns without support for fractional seconds precision). * Statement digesting as done previously by the Performance Schema is now done at the SQL level regardless of whether the Performance Schema is compiled in and is available to other aspects of server operation that could benefit from it. The default space available for digesting is 1024 bytes, but can be changed at server startup using the max_digest_length system variable. * Bug fixes.
2015-04-08 12:38:48 +02:00
share/mysql/test/suite/rpl/t/rpl_sp_privileges.test
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/rpl/t/rpl_spec_variables-slave.opt
share/mysql/test/suite/rpl/t/rpl_spec_variables.test
Changes 5.6.24: * CMake support was updated to handle CMake version 3.1. * The server now includes its version number when it writes the initial “starting” message to the error log, to make it easier to tell which server instance error log output applies to. This value is the same as that available from the version system variable. * ALTER TABLE did not take advantage of fast alterations that might otherwise apply to the operation to be performed, if the table contained temporal columns found to be in pre-5.6.4 format (TIME, DATETIME, and TIMESTAMP columns without support for fractional seconds precision). * Statement digesting as done previously by the Performance Schema is now done at the SQL level regardless of whether the Performance Schema is compiled in and is available to other aspects of server operation that could benefit from it. The default space available for digesting is 1024 bytes, but can be changed at server startup using the max_digest_length system variable. * Bug fixes.
2015-04-08 12:38:48 +02:00
share/mysql/test/suite/rpl/t/rpl_special_charset-master.opt
share/mysql/test/suite/rpl/t/rpl_special_charset-slave.opt
share/mysql/test/suite/rpl/t/rpl_special_charset.test
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/rpl/t/rpl_sporadic_master-master.opt
share/mysql/test/suite/rpl/t/rpl_sporadic_master.test
Changes 5.6.21: The --skip-innodb option is now deprecated and its use results in a warning. It will be removed in a future MySQL release. This also applies to its synonyms (--innodb=OFF, --disable-innodb, and so forth). MySQL Enterprise Edition now includes a set of encryption functions based on the OpenSSL library that expose OpenSSL capabilities at the SQL level. Replication: The new variable simplified_binlog_gtid_recovery can be used to change the way binary log files are searched for previous GTIDs during recovery, speeding up the process when a large number of binary log files exist. Internally, spatial data types such as Geometry are represented as BLOB values, so when invoked with the --hex-blob option, mysqldump now displays spatial values in hex. Bugs Fixed...
2014-10-01 10:34:23 +02:00
share/mysql/test/suite/rpl/t/rpl_sql_thread_killed_waiting_commit_lock-slave.opt
share/mysql/test/suite/rpl/t/rpl_sql_thread_killed_waiting_commit_lock.test
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/rpl/t/rpl_ssl.test
share/mysql/test/suite/rpl/t/rpl_ssl1.test
share/mysql/test/suite/rpl/t/rpl_stm_000001.test
share/mysql/test/suite/rpl/t/rpl_stm_EE_err2.test
share/mysql/test/suite/rpl/t/rpl_stm_auto_increment_bug33029.test
share/mysql/test/suite/rpl/t/rpl_stm_binlog_max_cache_size.test
share/mysql/test/suite/rpl/t/rpl_stm_conflicts.test
share/mysql/test/suite/rpl/t/rpl_stm_drop_create_temp_table.test
share/mysql/test/suite/rpl/t/rpl_stm_flsh_tbls.test
share/mysql/test/suite/rpl/t/rpl_stm_found_rows.test
Changes 5.6.27: * InnoDB: The new innodb_numa_interleave read-only configuration option allows you to enable the NUMA interleave memory policy for allocation of the InnoDB buffer pool. When innodb_numa_interleave is enabled, the NUMA memory policy is set to MPOL_INTERLEAVE for the mysqld process. After the InnoDB buffer pool is allocated, the NUMA memory policy is set back to MPOL_DEFAULT. This option is only available on NUMA-enabled systems. * yaSSL was upgraded to version 2.3.8. * RPM .spec files were updated so that MySQL Server builds from source RPM packages will include the proper files to take advantage of operating system NUMA capabilities. This introduces a runtime dependency on libnuma.so.1. RPM and yum detect this and refuse to install if that library is not installed. * InnoDB: Reloading a table that was evicted while empty caused an AUTO_INCREMENT value to be reset. * InnoDB: Memory allocation sanity checks were added to the memcached code. * InnoDB: A memcached flush_all command raised an assertion. A function that starts a transaction was called from within assertion code. * InnoDB: A data corruption occurred on ARM64. GCC builtins did not issue the correct fences when setting or unsetting the lock word. * InnoDB: Server shutdown was delayed waiting for the purge thread to exit. To avoid this problem, the number of calls to trx_purge() was reduced, and the trx_purge() batch size was reduced to 20. * InnoDB: In READ COMMITTED mode, a REPLACE operation on a unique secondary index resulted in a constraint violation. * InnoDB: The IBUF_BITMAP_FREE bit indicated that there was more free space in the leaf page than was actually available. * InnoDB: Setting lower_case_table_names=0 on a case-insensitive file system could result in a hang condition when running an INSERT INTO ... SELECT ... FROM tbl_name operation with the wrong tbl_name letter case. An error message is now printed and the server exits when attempting to start the server with --lower_case_table_names=0 on a case-insensitive file system. * InnoDB: The server failed to start with an innodb_force_recovery setting greater than 3. InnoDB was set to read-only mode before redo logs were applied. * InnoDB: The trx_sys_read_pertable_file_format_id() function reported the wrong file format. * Partitioning: CREATE TABLE statements that used an invalid function in a subpartitioning expression did not always fail gracefully as expected. * Partitioning: Error handling for failed partitioning-related ALTER TABLE operations against non-partitioned tables was not performed correctly * Partitioning: ALTER TABLE when executed from a stored procedure did not always work correctly with tables partitioned by RANGE. * Replication: Repeatedly checking for ERR_LOCK_WAIT_TIMEOUT (as done, for example by repeatedly executing SHOW SLAVE STATUS) during a prolonged write lock on a table led to an assert. * Replication: If statement based logging was in use, when updating multiple tables in a single statement, a single transaction could be logged as two different transactions. This was due to the binary logging process not properly identifying statements which were operating over transactional tables. The fix ensures that they are correctly identified, even if such statements do not change the contents of the tables.
2015-10-03 14:46:13 +02:00
share/mysql/test/suite/rpl/t/rpl_stm_ignore-slave.opt
share/mysql/test/suite/rpl/t/rpl_stm_ignore.test
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/rpl/t/rpl_stm_implicit_commit_binlog-master.opt
share/mysql/test/suite/rpl/t/rpl_stm_implicit_commit_binlog-slave.opt
share/mysql/test/suite/rpl/t/rpl_stm_implicit_commit_binlog.test
share/mysql/test/suite/rpl/t/rpl_stm_innodb.test
share/mysql/test/suite/rpl/t/rpl_stm_insert_delayed.test
share/mysql/test/suite/rpl/t/rpl_stm_lcase_tblnames-slave.opt
share/mysql/test/suite/rpl/t/rpl_stm_lcase_tblnames.test
share/mysql/test/suite/rpl/t/rpl_stm_loaddata_concurrent.test
share/mysql/test/suite/rpl/t/rpl_stm_loadfile.test
share/mysql/test/suite/rpl/t/rpl_stm_log-master.opt
share/mysql/test/suite/rpl/t/rpl_stm_log-slave.opt
share/mysql/test/suite/rpl/t/rpl_stm_log.test
share/mysql/test/suite/rpl/t/rpl_stm_max_relay_size.test
share/mysql/test/suite/rpl/t/rpl_stm_mix_mts_show_relaylog_events.test
Changes 5.6.27: * InnoDB: The new innodb_numa_interleave read-only configuration option allows you to enable the NUMA interleave memory policy for allocation of the InnoDB buffer pool. When innodb_numa_interleave is enabled, the NUMA memory policy is set to MPOL_INTERLEAVE for the mysqld process. After the InnoDB buffer pool is allocated, the NUMA memory policy is set back to MPOL_DEFAULT. This option is only available on NUMA-enabled systems. * yaSSL was upgraded to version 2.3.8. * RPM .spec files were updated so that MySQL Server builds from source RPM packages will include the proper files to take advantage of operating system NUMA capabilities. This introduces a runtime dependency on libnuma.so.1. RPM and yum detect this and refuse to install if that library is not installed. * InnoDB: Reloading a table that was evicted while empty caused an AUTO_INCREMENT value to be reset. * InnoDB: Memory allocation sanity checks were added to the memcached code. * InnoDB: A memcached flush_all command raised an assertion. A function that starts a transaction was called from within assertion code. * InnoDB: A data corruption occurred on ARM64. GCC builtins did not issue the correct fences when setting or unsetting the lock word. * InnoDB: Server shutdown was delayed waiting for the purge thread to exit. To avoid this problem, the number of calls to trx_purge() was reduced, and the trx_purge() batch size was reduced to 20. * InnoDB: In READ COMMITTED mode, a REPLACE operation on a unique secondary index resulted in a constraint violation. * InnoDB: The IBUF_BITMAP_FREE bit indicated that there was more free space in the leaf page than was actually available. * InnoDB: Setting lower_case_table_names=0 on a case-insensitive file system could result in a hang condition when running an INSERT INTO ... SELECT ... FROM tbl_name operation with the wrong tbl_name letter case. An error message is now printed and the server exits when attempting to start the server with --lower_case_table_names=0 on a case-insensitive file system. * InnoDB: The server failed to start with an innodb_force_recovery setting greater than 3. InnoDB was set to read-only mode before redo logs were applied. * InnoDB: The trx_sys_read_pertable_file_format_id() function reported the wrong file format. * Partitioning: CREATE TABLE statements that used an invalid function in a subpartitioning expression did not always fail gracefully as expected. * Partitioning: Error handling for failed partitioning-related ALTER TABLE operations against non-partitioned tables was not performed correctly * Partitioning: ALTER TABLE when executed from a stored procedure did not always work correctly with tables partitioned by RANGE. * Replication: Repeatedly checking for ERR_LOCK_WAIT_TIMEOUT (as done, for example by repeatedly executing SHOW SLAVE STATUS) during a prolonged write lock on a table led to an assert. * Replication: If statement based logging was in use, when updating multiple tables in a single statement, a single transaction could be logged as two different transactions. This was due to the binary logging process not properly identifying statements which were operating over transactional tables. The fix ensures that they are correctly identified, even if such statements do not change the contents of the tables.
2015-10-03 14:46:13 +02:00
share/mysql/test/suite/rpl/t/rpl_stm_mix_rollback_to_savepoint.test
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/rpl/t/rpl_stm_mix_show_relaylog_events.test
share/mysql/test/suite/rpl/t/rpl_stm_mixed_crash_safe-slave.opt
share/mysql/test/suite/rpl/t/rpl_stm_mixed_crash_safe.test
Changes 5.6.11: 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. 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. mysql_config_editor now supports --port and --socket options for specifying TCP/IP port number and Unix socket file name. 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. The only supported value for the innodb_mirrored_log_groups system variable is 1, so this variable is now deprecated. Setting it to 1 at startup results in a warning. Setting it to a value other than 1 at startup results in an error and the server exits. This variable will be removed in a future release.
2013-04-20 10:06:01 +02:00
share/mysql/test/suite/rpl/t/rpl_stm_mixed_mts_crash_safe-slave.opt
share/mysql/test/suite/rpl/t/rpl_stm_mixed_mts_crash_safe.test
share/mysql/test/suite/rpl/t/rpl_stm_mixed_mts_rec_crash_safe-slave.opt
share/mysql/test/suite/rpl/t/rpl_stm_mixed_mts_rec_crash_safe.test
share/mysql/test/suite/rpl/t/rpl_stm_mixed_mts_rec_crash_safe_checksum-master.opt
share/mysql/test/suite/rpl/t/rpl_stm_mixed_mts_rec_crash_safe_checksum-slave.opt
share/mysql/test/suite/rpl/t/rpl_stm_mixed_mts_rec_crash_safe_checksum.test
share/mysql/test/suite/rpl/t/rpl_stm_mixed_mts_rec_crash_safe_small-slave.opt
share/mysql/test/suite/rpl/t/rpl_stm_mixed_mts_rec_crash_safe_small.test
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/rpl/t/rpl_stm_mixing_engines.test
share/mysql/test/suite/rpl/t/rpl_stm_multi_query.test
share/mysql/test/suite/rpl/t/rpl_stm_no_op.test
share/mysql/test/suite/rpl/t/rpl_stm_relay_ign_space-slave.opt
share/mysql/test/suite/rpl/t/rpl_stm_relay_ign_space.test
share/mysql/test/suite/rpl/t/rpl_stm_reset_slave.test
share/mysql/test/suite/rpl/t/rpl_stm_sql_mode.test
share/mysql/test/suite/rpl/t/rpl_stm_start_stop_slave.test
share/mysql/test/suite/rpl/t/rpl_stm_stop_middle_group.test
share/mysql/test/suite/rpl/t/rpl_stm_until.test
Changes 5.6.21: The --skip-innodb option is now deprecated and its use results in a warning. It will be removed in a future MySQL release. This also applies to its synonyms (--innodb=OFF, --disable-innodb, and so forth). MySQL Enterprise Edition now includes a set of encryption functions based on the OpenSSL library that expose OpenSSL capabilities at the SQL level. Replication: The new variable simplified_binlog_gtid_recovery can be used to change the way binary log files are searched for previous GTIDs during recovery, speeding up the process when a large number of binary log files exist. Internally, spatial data types such as Geometry are represented as BLOB values, so when invoked with the --hex-blob option, mysqldump now displays spatial values in hex. Bugs Fixed...
2014-10-01 10:34:23 +02:00
share/mysql/test/suite/rpl/t/rpl_stm_until_pos_middle_gtid.test
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/rpl/t/rpl_stm_user_variables.test
share/mysql/test/suite/rpl/t/rpl_stop_slave.test
share/mysql/test/suite/rpl/t/rpl_switch_stm_row_mixed-master.opt
share/mysql/test/suite/rpl/t/rpl_switch_stm_row_mixed.test
share/mysql/test/suite/rpl/t/rpl_sync-master.opt
share/mysql/test/suite/rpl/t/rpl_sync-slave.opt
share/mysql/test/suite/rpl/t/rpl_sync.test
share/mysql/test/suite/rpl/t/rpl_temp_table.test
share/mysql/test/suite/rpl/t/rpl_temp_table_mix_row.test
share/mysql/test/suite/rpl/t/rpl_temporal_fractional.test
share/mysql/test/suite/rpl/t/rpl_temporary.test
Changes 5.6.27: * InnoDB: The new innodb_numa_interleave read-only configuration option allows you to enable the NUMA interleave memory policy for allocation of the InnoDB buffer pool. When innodb_numa_interleave is enabled, the NUMA memory policy is set to MPOL_INTERLEAVE for the mysqld process. After the InnoDB buffer pool is allocated, the NUMA memory policy is set back to MPOL_DEFAULT. This option is only available on NUMA-enabled systems. * yaSSL was upgraded to version 2.3.8. * RPM .spec files were updated so that MySQL Server builds from source RPM packages will include the proper files to take advantage of operating system NUMA capabilities. This introduces a runtime dependency on libnuma.so.1. RPM and yum detect this and refuse to install if that library is not installed. * InnoDB: Reloading a table that was evicted while empty caused an AUTO_INCREMENT value to be reset. * InnoDB: Memory allocation sanity checks were added to the memcached code. * InnoDB: A memcached flush_all command raised an assertion. A function that starts a transaction was called from within assertion code. * InnoDB: A data corruption occurred on ARM64. GCC builtins did not issue the correct fences when setting or unsetting the lock word. * InnoDB: Server shutdown was delayed waiting for the purge thread to exit. To avoid this problem, the number of calls to trx_purge() was reduced, and the trx_purge() batch size was reduced to 20. * InnoDB: In READ COMMITTED mode, a REPLACE operation on a unique secondary index resulted in a constraint violation. * InnoDB: The IBUF_BITMAP_FREE bit indicated that there was more free space in the leaf page than was actually available. * InnoDB: Setting lower_case_table_names=0 on a case-insensitive file system could result in a hang condition when running an INSERT INTO ... SELECT ... FROM tbl_name operation with the wrong tbl_name letter case. An error message is now printed and the server exits when attempting to start the server with --lower_case_table_names=0 on a case-insensitive file system. * InnoDB: The server failed to start with an innodb_force_recovery setting greater than 3. InnoDB was set to read-only mode before redo logs were applied. * InnoDB: The trx_sys_read_pertable_file_format_id() function reported the wrong file format. * Partitioning: CREATE TABLE statements that used an invalid function in a subpartitioning expression did not always fail gracefully as expected. * Partitioning: Error handling for failed partitioning-related ALTER TABLE operations against non-partitioned tables was not performed correctly * Partitioning: ALTER TABLE when executed from a stored procedure did not always work correctly with tables partitioned by RANGE. * Replication: Repeatedly checking for ERR_LOCK_WAIT_TIMEOUT (as done, for example by repeatedly executing SHOW SLAVE STATUS) during a prolonged write lock on a table led to an assert. * Replication: If statement based logging was in use, when updating multiple tables in a single statement, a single transaction could be logged as two different transactions. This was due to the binary logging process not properly identifying statements which were operating over transactional tables. The fix ensures that they are correctly identified, even if such statements do not change the contents of the tables.
2015-10-03 14:46:13 +02:00
share/mysql/test/suite/rpl/t/rpl_temporary_error_table_repository.test
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/rpl/t/rpl_temporary_errors-slave.opt
share/mysql/test/suite/rpl/t/rpl_temporary_errors.test
share/mysql/test/suite/rpl/t/rpl_test_framework.cnf
share/mysql/test/suite/rpl/t/rpl_test_framework.test
Changes 5.6.20: Security Fix: The linked OpenSSL library for the MySQL 5.6 Commercial Server has been updated from version 1.0.1g to version 1.0.1h. Versions of OpenSSL prior to and including 1.0.1g are reported to be vulnerable to CVE-2014-0224. This change does not affect the Oracle-produced MySQL Community build of MySQL Server 5.6, which uses the yaSSL library instead. DTrace Support MySQL now includes DTrace support on Oracle Linux 6 or higher with UEK kernel. If DTrace is present, server builds will detect it with no special CMake options required. For information about using DTrace on MySQL, see Tracing mysqld Using DTrace. InnoDB Notes Important Change: Redo log writes for large, externally stored BLOB fields could overwrite the most recent checkpoint. The 5.6.20 patch limits the size of redo log BLOB writes to 10% of the redo log file size. The 5.7.5 patch addresses the bug without imposing a limitation. For MySQL 5.5, the bug remains a known limitation. As a result of the redo log BLOB write limit introduced for MySQL 5.6, innodb_log_file_size should be set to a value greater than 10 times the largest BLOB data size found in the rows of your tables plus the length of other variable length fields (VARCHAR, VARBINARY, and TEXT type fields). Failing to do so could result in “Row size too large” errors. No action is required if your innodb_log_file_size setting is already sufficiently large or your tables contain no BLOB data. Functionality Added or Changed Replication: The new system variable binlog_impossible_mode controls what happens if the server cannot write to the binary log, for example, due to a file error. For backward compatibility, the default for binlog_impossible_mode is IGNORE_ERROR, meaning the server logs the error, halts logging, and continues updates to the database. Setting this variable to ABORT_SERVER makes the server halt logging and shut down if it cannot write to the binary log. CMake support was updated to handle CMake version 3. New Debian7, Ubuntu12.04, and Ubuntu14.04 distribution support that was introduced with 5.6.17 now comes with the platform-specific packaging source placed under the packaging directory, in the deb-precise, deb-wheezy, and deb-trusty directories. Support for LinuxThreads has been removed from the source code. LinuxThreads was superseded by NPTL in Linux 2.6. By default, mysql_install_db creates a my.cnf file in the installation base directory using a template. This may be undesireable for some deployments. To enable this behavior to be suppressed, mysql_install_db now supports a --keep-my-cnf option to preserve any existing my.cnf file and not create a new my.cnf file. The mysqlhotcopy utility is now deprecated and will be removed in a future version of MySQL. Among the reasons for this: It works only for the MyISAM and ARCHIVE storage engines; it works on Unix but not Windows. Alternatives include mysqldump and MySQL Enterprise Backup. The timed_mutexes system variable has no effect and is deprecated. Bugs Fixed
2014-08-10 17:11:57 +02:00
share/mysql/test/suite/rpl/t/rpl_timestamp_upgrage_55.test
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/rpl/t/rpl_timezone-master.opt
share/mysql/test/suite/rpl/t/rpl_timezone-slave.opt
share/mysql/test/suite/rpl/t/rpl_timezone.test
share/mysql/test/suite/rpl/t/rpl_tmp_table_and_DDL.test
share/mysql/test/suite/rpl/t/rpl_trigger.test
share/mysql/test/suite/rpl/t/rpl_trunc_temp.test
share/mysql/test/suite/rpl/t/rpl_truncate_2myisam.test
share/mysql/test/suite/rpl/t/rpl_truncate_3innodb.test
share/mysql/test/suite/rpl/t/rpl_typeconv-master.opt
share/mysql/test/suite/rpl/t/rpl_typeconv-slave.opt
share/mysql/test/suite/rpl/t/rpl_typeconv.test
share/mysql/test/suite/rpl/t/rpl_typeconv_innodb.test
share/mysql/test/suite/rpl/t/rpl_udf-master.opt
share/mysql/test/suite/rpl/t/rpl_udf-slave.opt
share/mysql/test/suite/rpl/t/rpl_udf.test
Changes 5.6.23: * The linked OpenSSL library for the MySQL Commercial Server has been updated from version 1.0.1j to version 1.0.1k. * Support for the SSL 2.0 and SSL 3.0 protocols has been disabled because they provide weak encryption. * yaSSL was upgraded to version 2.3.7. * The valid date range of the SSL certificates in mysql-test/std_data has been extended to the year 2029. * Bugs Fixed
2015-02-07 20:23:40 +01:00
share/mysql/test/suite/rpl/t/rpl_unknown_ignorable_event.test
Changes 5.6.29: * InnoDB: A new InnoDB configuration option, innodb_tmpdir, allows you to configure a separate temporary file directory for online ALTER TABLE operations. This option was introduced to help avoid tmpdir overflows that could occur as a result of large temporary files created during online ALTER TABLE operations. innodb_tmpdir is a SESSION variable and can be configured dynamically using a SET statement. * yaSSL was upgraded to version 2.3.9. This upgrade corrects an issue in which yaSSL handled only cases of zero or one leading zeros for the key agreement instead of potentially any number, which in rare cases could cause connections to fail when using DHE cipher suites. * The Valgrind function signature in mysql-test/valgrind.supp was upgraded for Valgrind 3.11. * Bugs Fixed
2016-02-28 09:58:03 +01:00
share/mysql/test/suite/rpl/t/rpl_unsafe_statements.test
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/rpl/t/rpl_user.test
share/mysql/test/suite/rpl/t/rpl_user_variables.test
share/mysql/test/suite/rpl/t/rpl_variables.test
share/mysql/test/suite/rpl/t/rpl_variables_stm.test
share/mysql/test/suite/rpl/t/rpl_view.test
share/mysql/test/suite/rpl/t/rpl_view_multi.test
share/mysql/test/suite/rpl_ndb/my.cnf
share/mysql/test/suite/rpl_ndb/r/rpl_ndb_UUID.result
share/mysql/test/suite/rpl_ndb/r/rpl_ndb_blob2.result
share/mysql/test/suite/rpl_ndb/r/rpl_ndb_commit_afterflush.result
share/mysql/test/suite/rpl_ndb/r/rpl_ndb_ddl.result
share/mysql/test/suite/rpl_ndb/r/rpl_ndb_delete_nowhere.result
share/mysql/test/suite/rpl_ndb/r/rpl_ndb_dist_priv.result
share/mysql/test/suite/rpl_ndb/r/rpl_ndb_extra_col_master.result
share/mysql/test/suite/rpl_ndb/r/rpl_ndb_extra_col_slave.result
share/mysql/test/suite/rpl_ndb/r/rpl_ndb_func003.result
share/mysql/test/suite/rpl_ndb/r/rpl_ndb_insert_ignore.result
share/mysql/test/suite/rpl_ndb/r/rpl_ndb_mixed_implicit_commit_binlog.result
share/mysql/test/suite/rpl_ndb/r/rpl_ndb_multi_update2.result
share/mysql/test/suite/rpl_ndb/r/rpl_ndb_multi_update3.result
share/mysql/test/suite/rpl_ndb/r/rpl_ndb_relayrotate.result
share/mysql/test/suite/rpl_ndb/r/rpl_ndb_row_001.result
share/mysql/test/suite/rpl_ndb/r/rpl_ndb_row_basic.result
share/mysql/test/suite/rpl_ndb/r/rpl_ndb_row_implicit_commit_binlog.result
share/mysql/test/suite/rpl_ndb/r/rpl_ndb_set_null.result
share/mysql/test/suite/rpl_ndb/r/rpl_ndb_sp003.result
share/mysql/test/suite/rpl_ndb/r/rpl_ndb_sp006.result
share/mysql/test/suite/rpl_ndb/r/rpl_ndb_trig004.result
share/mysql/test/suite/rpl_ndb/r/rpl_ndb_typeconv_all.result
share/mysql/test/suite/rpl_ndb/r/rpl_ndb_typeconv_lossy.result
share/mysql/test/suite/rpl_ndb/r/rpl_ndb_typeconv_nonlossy.result
share/mysql/test/suite/rpl_ndb/r/rpl_ndb_typeconv_strict.result
share/mysql/test/suite/rpl_ndb/t/check_conversions.inc
share/mysql/test/suite/rpl_ndb/t/disabled.def
share/mysql/test/suite/rpl_ndb/t/rpl_ndb_UUID.test
share/mysql/test/suite/rpl_ndb/t/rpl_ndb_blob2.test
share/mysql/test/suite/rpl_ndb/t/rpl_ndb_commit_afterflush.test
share/mysql/test/suite/rpl_ndb/t/rpl_ndb_ddl.test
share/mysql/test/suite/rpl_ndb/t/rpl_ndb_delete_nowhere.test
share/mysql/test/suite/rpl_ndb/t/rpl_ndb_dist_priv.test
share/mysql/test/suite/rpl_ndb/t/rpl_ndb_extra_col_master.test
share/mysql/test/suite/rpl_ndb/t/rpl_ndb_extra_col_slave.test
share/mysql/test/suite/rpl_ndb/t/rpl_ndb_func003.test
share/mysql/test/suite/rpl_ndb/t/rpl_ndb_insert_ignore.test
share/mysql/test/suite/rpl_ndb/t/rpl_ndb_mixed_implicit_commit_binlog.test
share/mysql/test/suite/rpl_ndb/t/rpl_ndb_multi_update2.test
share/mysql/test/suite/rpl_ndb/t/rpl_ndb_multi_update3.test
share/mysql/test/suite/rpl_ndb/t/rpl_ndb_relayrotate.test
share/mysql/test/suite/rpl_ndb/t/rpl_ndb_row_001.test
share/mysql/test/suite/rpl_ndb/t/rpl_ndb_row_basic.test
share/mysql/test/suite/rpl_ndb/t/rpl_ndb_row_implicit_commit_binlog.test
share/mysql/test/suite/rpl_ndb/t/rpl_ndb_set_null.test
share/mysql/test/suite/rpl_ndb/t/rpl_ndb_sp003.test
share/mysql/test/suite/rpl_ndb/t/rpl_ndb_sp006.test
share/mysql/test/suite/rpl_ndb/t/rpl_ndb_stm_innodb-slave.opt
share/mysql/test/suite/rpl_ndb/t/rpl_ndb_trig004.test
share/mysql/test/suite/rpl_ndb/t/rpl_ndb_typeconv_all.test
share/mysql/test/suite/rpl_ndb/t/rpl_ndb_typeconv_lossy.test
share/mysql/test/suite/rpl_ndb/t/rpl_ndb_typeconv_nonlossy.test
share/mysql/test/suite/rpl_ndb/t/rpl_ndb_typeconv_strict.test
share/mysql/test/suite/stress/include/ddl.cln
share/mysql/test/suite/stress/include/ddl.pre
share/mysql/test/suite/stress/include/ddl1.inc
share/mysql/test/suite/stress/include/ddl2.inc
share/mysql/test/suite/stress/include/ddl3.inc
share/mysql/test/suite/stress/include/ddl4.inc
share/mysql/test/suite/stress/include/ddl5.inc
share/mysql/test/suite/stress/include/ddl6.inc
share/mysql/test/suite/stress/include/ddl7.inc
share/mysql/test/suite/stress/include/ddl8.inc
share/mysql/test/suite/stress/r/ddl_archive.result
share/mysql/test/suite/stress/r/ddl_csv.result
share/mysql/test/suite/stress/r/ddl_innodb.result
share/mysql/test/suite/stress/r/ddl_memory.result
share/mysql/test/suite/stress/r/ddl_myisam.result
share/mysql/test/suite/stress/t/ddl_archive.test
share/mysql/test/suite/stress/t/ddl_csv.test
share/mysql/test/suite/stress/t/ddl_innodb.test
share/mysql/test/suite/stress/t/ddl_memory.test
share/mysql/test/suite/stress/t/ddl_myisam.test
share/mysql/test/suite/stress/t/wrapper.test
share/mysql/test/suite/sys_vars/inc/autocommit_func2.inc
share/mysql/test/suite/sys_vars/inc/bin_relay_log_basename_index.inc
share/mysql/test/suite/sys_vars/inc/binlog_cache_size_basic.inc
share/mysql/test/suite/sys_vars/inc/binlog_stmt_cache_size_basic.inc
share/mysql/test/suite/sys_vars/inc/bulk_insert_buffer_size_basic.inc
share/mysql/test/suite/sys_vars/inc/charset_basic.inc
share/mysql/test/suite/sys_vars/inc/collation_basic.inc
share/mysql/test/suite/sys_vars/inc/delayed_insert_limit_basic.inc
share/mysql/test/suite/sys_vars/inc/delayed_queue_size_basic.inc
share/mysql/test/suite/sys_vars/inc/join_buffer_size_basic.inc
share/mysql/test/suite/sys_vars/inc/key_cache_age_threshold_basic.inc
share/mysql/test/suite/sys_vars/inc/log_warnings_basic.inc
share/mysql/test/suite/sys_vars/inc/max_connect_errors_basic.inc
share/mysql/test/suite/sys_vars/inc/max_seeks_for_key_basic.inc
share/mysql/test/suite/sys_vars/inc/max_tmp_tables_basic.inc
share/mysql/test/suite/sys_vars/inc/max_write_lock_count_basic.inc
share/mysql/test/suite/sys_vars/inc/min_examined_row_limit_basic.inc
share/mysql/test/suite/sys_vars/inc/multi_range_count_basic.inc
share/mysql/test/suite/sys_vars/inc/myisam_max_sort_file_size_basic.inc
share/mysql/test/suite/sys_vars/inc/myisam_repair_threads_basic.inc
share/mysql/test/suite/sys_vars/inc/myisam_sort_buffer_size_basic.inc
share/mysql/test/suite/sys_vars/inc/net_retry_count_basic.inc
share/mysql/test/suite/sys_vars/inc/query_alloc_block_size_basic.inc
share/mysql/test/suite/sys_vars/inc/query_cache_limit_basic.inc
share/mysql/test/suite/sys_vars/inc/query_cache_min_res_unit_basic.inc
share/mysql/test/suite/sys_vars/inc/query_cache_size_basic.inc
share/mysql/test/suite/sys_vars/inc/range_alloc_block_size_basic.inc
share/mysql/test/suite/sys_vars/inc/slave_transaction_retries_basic.inc
share/mysql/test/suite/sys_vars/inc/sort_buffer_size_basic.inc
share/mysql/test/suite/sys_vars/r/all_vars.result
share/mysql/test/suite/sys_vars/r/auto_increment_increment_basic.result
share/mysql/test/suite/sys_vars/r/auto_increment_increment_func.result
share/mysql/test/suite/sys_vars/r/auto_increment_offset_basic.result
share/mysql/test/suite/sys_vars/r/auto_increment_offset_func.result
share/mysql/test/suite/sys_vars/r/autocommit_basic.result
share/mysql/test/suite/sys_vars/r/autocommit_func.result
share/mysql/test/suite/sys_vars/r/autocommit_func2.result
share/mysql/test/suite/sys_vars/r/autocommit_func3.result
share/mysql/test/suite/sys_vars/r/autocommit_func4.result
share/mysql/test/suite/sys_vars/r/autocommit_func5.result
share/mysql/test/suite/sys_vars/r/automatic_sp_privileges_basic.result
share/mysql/test/suite/sys_vars/r/automatic_sp_privileges_func.result
Changes 5.6.24: * CMake support was updated to handle CMake version 3.1. * The server now includes its version number when it writes the initial “starting” message to the error log, to make it easier to tell which server instance error log output applies to. This value is the same as that available from the version system variable. * ALTER TABLE did not take advantage of fast alterations that might otherwise apply to the operation to be performed, if the table contained temporal columns found to be in pre-5.6.4 format (TIME, DATETIME, and TIMESTAMP columns without support for fractional seconds precision). * Statement digesting as done previously by the Performance Schema is now done at the SQL level regardless of whether the Performance Schema is compiled in and is available to other aspects of server operation that could benefit from it. The default space available for digesting is 1024 bytes, but can be changed at server startup using the max_digest_length system variable. * Bug fixes.
2015-04-08 12:38:48 +02:00
share/mysql/test/suite/sys_vars/r/avoid_temporal_upgrade_basic.result
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/sys_vars/r/back_log_basic.result
share/mysql/test/suite/sys_vars/r/basedir_basic.result
share/mysql/test/suite/sys_vars/r/big_tables_basic.result
share/mysql/test/suite/sys_vars/r/bind_address_basic.result
share/mysql/test/suite/sys_vars/r/binlog_cache_size_basic_32.result
share/mysql/test/suite/sys_vars/r/binlog_cache_size_basic_64.result
share/mysql/test/suite/sys_vars/r/binlog_checksum_basic.result
share/mysql/test/suite/sys_vars/r/binlog_direct_non_transactional_updates_basic.result
Changes 5.6.22: * Noisy compiler warnings on FreeBSD 10 were silenced. * CMake workarounds for older Mac OS X and XCode versions were removed. On Mac OS X, compilation always uses Clang, even for 32-bit builds. * Previously, the MYSQL_MAINTAINER_MODE CMake option was turned on by default for debug builds and off for release builds, and MYSQL_MAINTAINER_MODE caused -Werror to be enabled when building with GCC. This made it cumbersome to enable -Werror under certain conditions, such as when compiling with Clang. * Build support was modified to produce the same warnings for Clang as for gcc. * CMake configuration for the Clang compiler sets more appropriate flags for building on Linux. Specifically, -g -fno-omit-frame-pointer -fno-strict-aliasing is now added. * Bugs fixed.
2014-12-02 13:40:09 +01:00
share/mysql/test/suite/sys_vars/r/binlog_error_action_basic.result
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/sys_vars/r/binlog_format_basic.result
Changes 5.6.23: * The linked OpenSSL library for the MySQL Commercial Server has been updated from version 1.0.1j to version 1.0.1k. * Support for the SSL 2.0 and SSL 3.0 protocols has been disabled because they provide weak encryption. * yaSSL was upgraded to version 2.3.7. * The valid date range of the SSL certificates in mysql-test/std_data has been extended to the year 2029. * Bugs Fixed
2015-02-07 20:23:40 +01:00
share/mysql/test/suite/sys_vars/r/binlog_gtid_simple_recovery_basic.result
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/sys_vars/r/binlog_max_flush_queue_time_basic.result
share/mysql/test/suite/sys_vars/r/binlog_order_commits_basic.result
share/mysql/test/suite/sys_vars/r/binlog_row_image_basic.result
share/mysql/test/suite/sys_vars/r/binlog_rows_query_log_events_basic.result
share/mysql/test/suite/sys_vars/r/binlog_stmt_cache_size_basic_32.result
share/mysql/test/suite/sys_vars/r/binlog_stmt_cache_size_basic_64.result
Changes 5.6.20: Security Fix: The linked OpenSSL library for the MySQL 5.6 Commercial Server has been updated from version 1.0.1g to version 1.0.1h. Versions of OpenSSL prior to and including 1.0.1g are reported to be vulnerable to CVE-2014-0224. This change does not affect the Oracle-produced MySQL Community build of MySQL Server 5.6, which uses the yaSSL library instead. DTrace Support MySQL now includes DTrace support on Oracle Linux 6 or higher with UEK kernel. If DTrace is present, server builds will detect it with no special CMake options required. For information about using DTrace on MySQL, see Tracing mysqld Using DTrace. InnoDB Notes Important Change: Redo log writes for large, externally stored BLOB fields could overwrite the most recent checkpoint. The 5.6.20 patch limits the size of redo log BLOB writes to 10% of the redo log file size. The 5.7.5 patch addresses the bug without imposing a limitation. For MySQL 5.5, the bug remains a known limitation. As a result of the redo log BLOB write limit introduced for MySQL 5.6, innodb_log_file_size should be set to a value greater than 10 times the largest BLOB data size found in the rows of your tables plus the length of other variable length fields (VARCHAR, VARBINARY, and TEXT type fields). Failing to do so could result in “Row size too large” errors. No action is required if your innodb_log_file_size setting is already sufficiently large or your tables contain no BLOB data. Functionality Added or Changed Replication: The new system variable binlog_impossible_mode controls what happens if the server cannot write to the binary log, for example, due to a file error. For backward compatibility, the default for binlog_impossible_mode is IGNORE_ERROR, meaning the server logs the error, halts logging, and continues updates to the database. Setting this variable to ABORT_SERVER makes the server halt logging and shut down if it cannot write to the binary log. CMake support was updated to handle CMake version 3. New Debian7, Ubuntu12.04, and Ubuntu14.04 distribution support that was introduced with 5.6.17 now comes with the platform-specific packaging source placed under the packaging directory, in the deb-precise, deb-wheezy, and deb-trusty directories. Support for LinuxThreads has been removed from the source code. LinuxThreads was superseded by NPTL in Linux 2.6. By default, mysql_install_db creates a my.cnf file in the installation base directory using a template. This may be undesireable for some deployments. To enable this behavior to be suppressed, mysql_install_db now supports a --keep-my-cnf option to preserve any existing my.cnf file and not create a new my.cnf file. The mysqlhotcopy utility is now deprecated and will be removed in a future version of MySQL. Among the reasons for this: It works only for the MyISAM and ARCHIVE storage engines; it works on Unix but not Windows. Alternatives include mysqldump and MySQL Enterprise Backup. The timed_mutexes system variable has no effect and is deprecated. Bugs Fixed
2014-08-10 17:11:57 +02:00
share/mysql/test/suite/sys_vars/r/binlogging_impossible_mode_basic.result
Changes 5.6.17: Functionality Added or Changed Incompatible Change: The AES_ENCRYPT() and AES_DECRYPT() functions now permit control of the block encryption mode and take an optional initialization vector argument: The new block_encryption_mode system variable controls the mode for block-based encryption algorithms. Its default value is aes-128-ecb, which signifies encryption using a key length of 128 bits and ECB mode. An optional init_vector argument provides an initialization vector for encryption modes that require it: AES_ENCRYPT(str,key_str[,init_vector]) AES_DECRYPT(crypt_str,key_str[,init_vector]) A random string of bytes to use for the initialization vector can be produced by calling the new RANDOM_BYTES() function. For more information, see Encryption and Compression Functions. These changes make statements that use AES_ENCRYPT() or AES_DECRYPT() unsafe for statement-based replication and they cannot be stored in the query cache. Queries that use RANDOM_BYTES() are unsafe for statement-based replication and cannot be stored in the query cache. Incompatible Change: The ERROR_FOR_DIVISION_BY_ZERO, NO_ZERO_DATE, and NO_ZERO_IN_DATE SQL modes now are deprecated and setting the sql_mode value to include any of them generates a warning. In MySQL 5.7, these modes do nothing. Instead, their effects are included in the effects of strict SQL mode (STRICT_ALL_TABLES or STRICT_TRANS_TABLES). The motivation for the change in MySQL 5.7 is to reduce the number of SQL modes with an effect dependent on strict mode and make them part of strict mode itself. To make advance preparation for an upgrade to MySQL 5.7, see SQL Mode Changes in MySQL 5.7. That discussion provides guidelines to assess whether your applications will be affected by the SQL mode changes in MySQL 5.7. InnoDB: MySQL now supports rebuilding regular and partitioned InnoDB tables using online DDL (ALGORITHM=INPLACE) for the following operations: OPTIMIZE TABLE ALTER TABLE ... FORCE ALTER TABLE ... ENGINE=INNODB (when run on an InnoDB table) Online DDL support reduces table rebuild time and permits concurrent DML, which helps reduce user application downtime. For additional information, see Overview of Online DDL. On Solaris, mysql_config --libs now includes -R/path/to/library so that libraries can be found at runtime. mysql_install_db provides a more informative diagnostic message when required Perl modules are missing. The IGNORE clause for ALTER TABLE is now deprecated and will be removed in a future version of MySQL. ALTER IGNORE TABLE causes problems for replication, prevents online ALTER TABLE for unique index creation, and causes problems with foreign keys (rows removed in the parent table). Bugs Fixed
2014-03-31 12:32:13 +02:00
share/mysql/test/suite/sys_vars/r/block_encryption_mode_basic.result
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/sys_vars/r/bulk_insert_buffer_size_basic_32.result
share/mysql/test/suite/sys_vars/r/bulk_insert_buffer_size_basic_64.result
share/mysql/test/suite/sys_vars/r/character_set_client_basic.result
share/mysql/test/suite/sys_vars/r/character_set_client_func.result
share/mysql/test/suite/sys_vars/r/character_set_connection_basic.result
share/mysql/test/suite/sys_vars/r/character_set_connection_func.result
share/mysql/test/suite/sys_vars/r/character_set_database_basic.result
share/mysql/test/suite/sys_vars/r/character_set_database_func.result
share/mysql/test/suite/sys_vars/r/character_set_filesystem_basic.result
share/mysql/test/suite/sys_vars/r/character_set_results_basic.result
share/mysql/test/suite/sys_vars/r/character_set_results_func.result
share/mysql/test/suite/sys_vars/r/character_set_server_basic.result
share/mysql/test/suite/sys_vars/r/character_set_server_func.result
share/mysql/test/suite/sys_vars/r/character_set_system_basic.result
share/mysql/test/suite/sys_vars/r/character_sets_dir_basic.result
share/mysql/test/suite/sys_vars/r/collation_connection_basic.result
share/mysql/test/suite/sys_vars/r/collation_connection_func.result
share/mysql/test/suite/sys_vars/r/collation_database_basic.result
share/mysql/test/suite/sys_vars/r/collation_database_func.result
share/mysql/test/suite/sys_vars/r/collation_server_basic.result
share/mysql/test/suite/sys_vars/r/collation_server_func.result
share/mysql/test/suite/sys_vars/r/completion_type_basic.result
share/mysql/test/suite/sys_vars/r/completion_type_func.result
share/mysql/test/suite/sys_vars/r/concurrent_insert_basic.result
share/mysql/test/suite/sys_vars/r/concurrent_insert_func.result
share/mysql/test/suite/sys_vars/r/connect_timeout_basic.result
share/mysql/test/suite/sys_vars/r/core_file_basic.result
share/mysql/test/suite/sys_vars/r/datadir_basic.result
share/mysql/test/suite/sys_vars/r/date_format_basic.result
share/mysql/test/suite/sys_vars/r/datetime_format_basic.result
share/mysql/test/suite/sys_vars/r/debug_basic.result
share/mysql/test/suite/sys_vars/r/debug_sync_basic.result
share/mysql/test/suite/sys_vars/r/default_storage_engine_basic.result
share/mysql/test/suite/sys_vars/r/default_tmp_storage_engine_basic.result
share/mysql/test/suite/sys_vars/r/default_week_format_basic.result
share/mysql/test/suite/sys_vars/r/default_week_format_func.result
share/mysql/test/suite/sys_vars/r/delay_key_write_basic.result
share/mysql/test/suite/sys_vars/r/delay_key_write_func.result
share/mysql/test/suite/sys_vars/r/delayed_insert_limit_basic_32.result
share/mysql/test/suite/sys_vars/r/delayed_insert_limit_basic_64.result
share/mysql/test/suite/sys_vars/r/delayed_insert_limit_func.result
share/mysql/test/suite/sys_vars/r/delayed_insert_timeout_basic.result
share/mysql/test/suite/sys_vars/r/delayed_queue_size_basic_32.result
share/mysql/test/suite/sys_vars/r/delayed_queue_size_basic_64.result
share/mysql/test/suite/sys_vars/r/disconnect_on_expired_password_basic.result
share/mysql/test/suite/sys_vars/r/div_precision_increment_basic.result
share/mysql/test/suite/sys_vars/r/div_precision_increment_func.result
share/mysql/test/suite/sys_vars/r/end_markers_in_json_basic.result
share/mysql/test/suite/sys_vars/r/enforce_gtid_consistency_basic.result
share/mysql/test/suite/sys_vars/r/eq_range_index_dive_limit_basic.result
share/mysql/test/suite/sys_vars/r/error_count_basic.result
share/mysql/test/suite/sys_vars/r/event_scheduler_basic.result
share/mysql/test/suite/sys_vars/r/expire_logs_days_basic.result
share/mysql/test/suite/sys_vars/r/explicit_defaults_for_timestamp_basic.result
share/mysql/test/suite/sys_vars/r/external_user_basic.result
share/mysql/test/suite/sys_vars/r/flush_basic.result
share/mysql/test/suite/sys_vars/r/flush_time_basic.result
share/mysql/test/suite/sys_vars/r/foreign_key_checks_basic.result
share/mysql/test/suite/sys_vars/r/foreign_key_checks_func.result
share/mysql/test/suite/sys_vars/r/ft_boolean_syntax_basic.result
share/mysql/test/suite/sys_vars/r/ft_boolean_syntax_func.result
share/mysql/test/suite/sys_vars/r/ft_max_word_len_basic.result
share/mysql/test/suite/sys_vars/r/ft_min_word_len_basic.result
share/mysql/test/suite/sys_vars/r/ft_query_expansion_limit_basic.result
share/mysql/test/suite/sys_vars/r/ft_stopword_file_basic.result
share/mysql/test/suite/sys_vars/r/general_log_basic.result
share/mysql/test/suite/sys_vars/r/general_log_file_basic.result
share/mysql/test/suite/sys_vars/r/general_log_file_func.result
share/mysql/test/suite/sys_vars/r/general_log_func.result
share/mysql/test/suite/sys_vars/r/group_concat_max_len_basic.result
share/mysql/test/suite/sys_vars/r/group_concat_max_len_func.result
share/mysql/test/suite/sys_vars/r/gtid_executed_basic.result
share/mysql/test/suite/sys_vars/r/gtid_mode_basic.result
share/mysql/test/suite/sys_vars/r/gtid_next_basic.result
share/mysql/test/suite/sys_vars/r/gtid_owned_basic.result
share/mysql/test/suite/sys_vars/r/gtid_purged_basic.result
share/mysql/test/suite/sys_vars/r/have_compress_basic.result
share/mysql/test/suite/sys_vars/r/have_crypt_basic.result
share/mysql/test/suite/sys_vars/r/have_dynamic_loading_basic.result
share/mysql/test/suite/sys_vars/r/have_geometry_basic.result
share/mysql/test/suite/sys_vars/r/have_openssl_basic.result
share/mysql/test/suite/sys_vars/r/have_profiling_basic.result
share/mysql/test/suite/sys_vars/r/have_query_cache_basic.result
share/mysql/test/suite/sys_vars/r/have_rtree_keys_basic.result
share/mysql/test/suite/sys_vars/r/have_ssl_basic.result
share/mysql/test/suite/sys_vars/r/have_symlink_basic.result
share/mysql/test/suite/sys_vars/r/host_cache_size_basic.result
share/mysql/test/suite/sys_vars/r/hostname_basic.result
share/mysql/test/suite/sys_vars/r/identity_basic.result
share/mysql/test/suite/sys_vars/r/identity_func.result
share/mysql/test/suite/sys_vars/r/ignore_builtin_innodb_basic.result
share/mysql/test/suite/sys_vars/r/ignore_db_dirs_basic.result
share/mysql/test/suite/sys_vars/r/init_connect_basic.result
share/mysql/test/suite/sys_vars/r/init_file_basic.result
share/mysql/test/suite/sys_vars/r/init_slave_basic.result
share/mysql/test/suite/sys_vars/r/innodb_adaptive_flushing_basic.result
share/mysql/test/suite/sys_vars/r/innodb_adaptive_flushing_lwm_basic.result
share/mysql/test/suite/sys_vars/r/innodb_adaptive_hash_index_basic.result
share/mysql/test/suite/sys_vars/r/innodb_adaptive_max_sleep_delay_basic.result
share/mysql/test/suite/sys_vars/r/innodb_additional_mem_pool_size_basic.result
share/mysql/test/suite/sys_vars/r/innodb_api_bk_commit_interval_basic.result
share/mysql/test/suite/sys_vars/r/innodb_api_disable_rowlock_basic.result
share/mysql/test/suite/sys_vars/r/innodb_api_enable_binlog_basic.result
share/mysql/test/suite/sys_vars/r/innodb_api_enable_mdl_basic.result
share/mysql/test/suite/sys_vars/r/innodb_api_trx_level_basic.result
share/mysql/test/suite/sys_vars/r/innodb_autoextend_increment_basic.result
share/mysql/test/suite/sys_vars/r/innodb_autoinc_lock_mode_basic.result
share/mysql/test/suite/sys_vars/r/innodb_autoinc_lock_mode_func.result
Changes 5.6.16: Functionality Added or Changed * InnoDB: New global configuration parameters, innodb_status_output and innodb_status_output_locks, allow you to dynamically enable and disable the standard InnoDB Monitor and InnoDB Lock Monitor for periodic output. Enabling and disabling monitors for periodic output by creating and dropping specially named tables is deprecated and may be removed in a future release. * Previously, ALTER TABLE in MySQL 5.6 could alter a table such that the result had temporal columns in both 5.5 and 5.6 format. Now ALTER TABLE upgrades old temporal columns to 5.6 format for ADD COLUMN, CHANGE COLUMN, MODIFY COLUMN, ADD INDEX, and FORCE operations. This conversion cannot be done using the INPLACE algorithm, so specifying ALGORITHM=INPLACE in these cases results in an error. * CMake now supports a -DTMPDIR=dir_name option to specify the default tmpdir value. If unspecified, the value defaults to P_tmpdir in <stdio.h>. Bugs Fixed * InnoDB; Replication: Using the InnoDB memcached plugin (see InnoDB Integration with memcached) with innodb_api_enable_binlog set to 1 caused the server to leak memory. * InnoDB: A boolean mode full-text search query would result in a memory access violation during parsing. * InnoDB: When new indexes are added by an ALTER TABLE operation, instead of only saving table-level statistics and statistics for the new indexes, InnoDB would save statistics for the entire table, including the table's other indexes. This behavior slowed ALTER TABLE performance. * InnoDB: Due to a parser error, full-text search queries that include a sub-expression could return the wrong result. * InnoDB: The innochecksum tool did not use a Windows-specific API to retrieve file size information, which resulted in an incorrect error message (Error: ibdata1 cannot be found) when the MySQL 5.6 innochecksum 2GB file size limit was exceeded. innochecksum now provides support for files larger than 2GB in both MySQL 5.6 and MySQL 5.7. * InnoDB: Due to a regression introduced by the fix for Bug17371537, memory was not allocated for the default memcached engine when using the default memcached engine as the backstore for data instead of InnoDB. * InnoDB: InnoDB would report an incorrect operating system error code after failing to initialize. * InnoDB: Manipulating a table after discarding its tablespace using ALTER TABLE ... DISCARD TABLESPACE could result in a serious error. * InnoDB: Persistent optimizer statistics would cause stalls due to latch contention. * InnoDB: MATCH() ... AGAINST queries that use a long string as an argument for AGAINST() could result in an error when run on an InnoDB table with a full-text search index. * InnoDB: An InnoDB full-text search failure would occur due to an “unended” token. The string and string length should be passed for string comparison. * InnoDB: In debug builds, a merge insert buffer during a page read would cause a memory access violation. * InnoDB: Truncating a memcached InnoDB table while memcached is performing DML operations would result in a serious error. * InnoDB: In sync0rw.ic, rw_lock_x_lock_func_nowait would needlessly call os_thread_get_curr_id. * InnoDB: Attempting to rename a table to a missing database would result in a serious error. more...
2014-02-13 08:49:56 +01:00
share/mysql/test/suite/sys_vars/r/innodb_buf_flush_list_now_basic.result
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/sys_vars/r/innodb_buffer_pool_dump_at_shutdown_basic.result
share/mysql/test/suite/sys_vars/r/innodb_buffer_pool_dump_now_basic.result
Changes 5.6.11: 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. 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. mysql_config_editor now supports --port and --socket options for specifying TCP/IP port number and Unix socket file name. 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. The only supported value for the innodb_mirrored_log_groups system variable is 1, so this variable is now deprecated. Setting it to 1 at startup results in a warning. Setting it to a value other than 1 at startup results in an error and the server exits. This variable will be removed in a future release.
2013-04-20 10:06:01 +02:00
share/mysql/test/suite/sys_vars/r/innodb_buffer_pool_evict_basic.result
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/sys_vars/r/innodb_buffer_pool_filename_basic.result
share/mysql/test/suite/sys_vars/r/innodb_buffer_pool_instances_basic.result
share/mysql/test/suite/sys_vars/r/innodb_buffer_pool_load_abort_basic.result
share/mysql/test/suite/sys_vars/r/innodb_buffer_pool_load_at_startup_basic.result
share/mysql/test/suite/sys_vars/r/innodb_buffer_pool_load_now_basic.result
share/mysql/test/suite/sys_vars/r/innodb_buffer_pool_size_basic.result
share/mysql/test/suite/sys_vars/r/innodb_change_buffer_max_size_basic.result
share/mysql/test/suite/sys_vars/r/innodb_change_buffering_basic.result
share/mysql/test/suite/sys_vars/r/innodb_change_buffering_debug_basic.result
share/mysql/test/suite/sys_vars/r/innodb_checksum_algorithm_basic.result
share/mysql/test/suite/sys_vars/r/innodb_checksums_basic.result
share/mysql/test/suite/sys_vars/r/innodb_cmp_per_index_enabled_basic.result
share/mysql/test/suite/sys_vars/r/innodb_commit_concurrency_basic.result
share/mysql/test/suite/sys_vars/r/innodb_compression_failure_threshold_pct_basic.result
share/mysql/test/suite/sys_vars/r/innodb_compression_level_basic.result
share/mysql/test/suite/sys_vars/r/innodb_compression_pad_pct_max_basic.result
share/mysql/test/suite/sys_vars/r/innodb_concurrency_tickets_basic.result
share/mysql/test/suite/sys_vars/r/innodb_data_file_path_basic.result
share/mysql/test/suite/sys_vars/r/innodb_data_home_dir_basic.result
share/mysql/test/suite/sys_vars/r/innodb_disable_background_merge_basic.result
share/mysql/test/suite/sys_vars/r/innodb_disable_sort_file_cache_basic.result
share/mysql/test/suite/sys_vars/r/innodb_doublewrite_basic.result
share/mysql/test/suite/sys_vars/r/innodb_doublewrite_batch_size_basic.result
share/mysql/test/suite/sys_vars/r/innodb_fast_shutdown_basic.result
Changes 5.6.17: Functionality Added or Changed Incompatible Change: The AES_ENCRYPT() and AES_DECRYPT() functions now permit control of the block encryption mode and take an optional initialization vector argument: The new block_encryption_mode system variable controls the mode for block-based encryption algorithms. Its default value is aes-128-ecb, which signifies encryption using a key length of 128 bits and ECB mode. An optional init_vector argument provides an initialization vector for encryption modes that require it: AES_ENCRYPT(str,key_str[,init_vector]) AES_DECRYPT(crypt_str,key_str[,init_vector]) A random string of bytes to use for the initialization vector can be produced by calling the new RANDOM_BYTES() function. For more information, see Encryption and Compression Functions. These changes make statements that use AES_ENCRYPT() or AES_DECRYPT() unsafe for statement-based replication and they cannot be stored in the query cache. Queries that use RANDOM_BYTES() are unsafe for statement-based replication and cannot be stored in the query cache. Incompatible Change: The ERROR_FOR_DIVISION_BY_ZERO, NO_ZERO_DATE, and NO_ZERO_IN_DATE SQL modes now are deprecated and setting the sql_mode value to include any of them generates a warning. In MySQL 5.7, these modes do nothing. Instead, their effects are included in the effects of strict SQL mode (STRICT_ALL_TABLES or STRICT_TRANS_TABLES). The motivation for the change in MySQL 5.7 is to reduce the number of SQL modes with an effect dependent on strict mode and make them part of strict mode itself. To make advance preparation for an upgrade to MySQL 5.7, see SQL Mode Changes in MySQL 5.7. That discussion provides guidelines to assess whether your applications will be affected by the SQL mode changes in MySQL 5.7. InnoDB: MySQL now supports rebuilding regular and partitioned InnoDB tables using online DDL (ALGORITHM=INPLACE) for the following operations: OPTIMIZE TABLE ALTER TABLE ... FORCE ALTER TABLE ... ENGINE=INNODB (when run on an InnoDB table) Online DDL support reduces table rebuild time and permits concurrent DML, which helps reduce user application downtime. For additional information, see Overview of Online DDL. On Solaris, mysql_config --libs now includes -R/path/to/library so that libraries can be found at runtime. mysql_install_db provides a more informative diagnostic message when required Perl modules are missing. The IGNORE clause for ALTER TABLE is now deprecated and will be removed in a future version of MySQL. ALTER IGNORE TABLE causes problems for replication, prevents online ALTER TABLE for unique index creation, and causes problems with foreign keys (rows removed in the parent table). Bugs Fixed
2014-03-31 12:32:13 +02:00
share/mysql/test/suite/sys_vars/r/innodb_fil_make_page_dirty_debug_basic.result
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/sys_vars/r/innodb_file_format_basic.result
share/mysql/test/suite/sys_vars/r/innodb_file_format_check_basic.result
share/mysql/test/suite/sys_vars/r/innodb_file_format_max_basic.result
share/mysql/test/suite/sys_vars/r/innodb_file_io_threads_basic.result
share/mysql/test/suite/sys_vars/r/innodb_file_per_table_basic.result
share/mysql/test/suite/sys_vars/r/innodb_flush_log_at_timeout_basic.result
share/mysql/test/suite/sys_vars/r/innodb_flush_log_at_trx_commit_basic.result
share/mysql/test/suite/sys_vars/r/innodb_flush_method_basic.result
share/mysql/test/suite/sys_vars/r/innodb_flush_neighbors_basic.result
share/mysql/test/suite/sys_vars/r/innodb_flushing_avg_loops_basic.result
share/mysql/test/suite/sys_vars/r/innodb_force_load_corrupted_basic.result
share/mysql/test/suite/sys_vars/r/innodb_force_recovery_basic.result
share/mysql/test/suite/sys_vars/r/innodb_force_recovery_crash_basic.result
share/mysql/test/suite/sys_vars/r/innodb_ft_aux_table_basic.result
share/mysql/test/suite/sys_vars/r/innodb_ft_cache_size_basic.result
share/mysql/test/suite/sys_vars/r/innodb_ft_enable_diag_print_basic.result
share/mysql/test/suite/sys_vars/r/innodb_ft_enable_stopword_basic.result
share/mysql/test/suite/sys_vars/r/innodb_ft_max_token_size_basic.result
share/mysql/test/suite/sys_vars/r/innodb_ft_min_token_size_basic.result
share/mysql/test/suite/sys_vars/r/innodb_ft_num_word_optimize_basic.result
Changes 5.6.13: * Important Change; Replication: By default, when promoting integers from a smaller type on the master to a larger type on the slave (for example, from a SMALLINT column on the master to a BIGINT column on the slave), the promoted values are treated as though they are signed. Now in such cases it is possible to modify or override this behavior using one or both of ALL_SIGNED, ALL_UNSIGNED in the set of values specified for the slave_type_conversions server system variable. For more information, see Row-based replication: attribute promotion and demotion, as well as the description of the variable. * Previously, program options could be specified in full or as any unambiguous prefix. For example, the --compress option could be given to mysqldump as --compr, but not as --comp because the latter is ambiguous. Option prefixes now are deprecated. They can cause problems when new options are implemented for programs. A prefix that is currently unambiguous might become ambiguous in the future. If an unambiguous prefix is given, a warning now occurs to provide feedback. For example: Warning: Using unique option prefix compr instead of compress is deprecated and will be removed in a future release. Please use the full name instead. Option prefixes are no longer supported in MySQL 5.7; only full options are accepted. * The C API libmysqlclient shared-library .so files now have version 18.1.0 (up from version 18.0.0 used in MySQL 5.5). * In batch mode, mysql formatted result status messages such as “"Query OK, 1 row affected"” but did not print them. Now these messages are not formatted. * Bugs Fixed
2013-07-31 11:51:38 +02:00
share/mysql/test/suite/sys_vars/r/innodb_ft_result_cache_limit_basic.result
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/sys_vars/r/innodb_ft_server_stopword_table_basic.result
share/mysql/test/suite/sys_vars/r/innodb_ft_sort_pll_degree_basic.result
Changes 5.6.13: * Important Change; Replication: By default, when promoting integers from a smaller type on the master to a larger type on the slave (for example, from a SMALLINT column on the master to a BIGINT column on the slave), the promoted values are treated as though they are signed. Now in such cases it is possible to modify or override this behavior using one or both of ALL_SIGNED, ALL_UNSIGNED in the set of values specified for the slave_type_conversions server system variable. For more information, see Row-based replication: attribute promotion and demotion, as well as the description of the variable. * Previously, program options could be specified in full or as any unambiguous prefix. For example, the --compress option could be given to mysqldump as --compr, but not as --comp because the latter is ambiguous. Option prefixes now are deprecated. They can cause problems when new options are implemented for programs. A prefix that is currently unambiguous might become ambiguous in the future. If an unambiguous prefix is given, a warning now occurs to provide feedback. For example: Warning: Using unique option prefix compr instead of compress is deprecated and will be removed in a future release. Please use the full name instead. Option prefixes are no longer supported in MySQL 5.7; only full options are accepted. * The C API libmysqlclient shared-library .so files now have version 18.1.0 (up from version 18.0.0 used in MySQL 5.5). * In batch mode, mysql formatted result status messages such as “"Query OK, 1 row affected"” but did not print them. Now these messages are not formatted. * Bugs Fixed
2013-07-31 11:51:38 +02:00
share/mysql/test/suite/sys_vars/r/innodb_ft_total_cache_size_basic.result
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/sys_vars/r/innodb_ft_user_stopword_table_basic.result
share/mysql/test/suite/sys_vars/r/innodb_io_capacity_basic.result
share/mysql/test/suite/sys_vars/r/innodb_io_capacity_max_basic.result
share/mysql/test/suite/sys_vars/r/innodb_large_prefix_basic.result
share/mysql/test/suite/sys_vars/r/innodb_limit_optimistic_insert_debug_basic.result
share/mysql/test/suite/sys_vars/r/innodb_lock_wait_timeout_basic.result
share/mysql/test/suite/sys_vars/r/innodb_locks_unsafe_for_binlog_basic.result
share/mysql/test/suite/sys_vars/r/innodb_log_buffer_size_basic.result
Changes 5.6.12: * mysql_upgrade now verifies that the server version matches the version against which it was compiled, and exits if there is a mismatch. In addiion, a --version-check option permits specifying whether to enable version checking (the default), or disable checking if given as --skip-version-checking. * Bugs Fixed
2013-06-04 20:17:25 +02:00
share/mysql/test/suite/sys_vars/r/innodb_log_checkpoint_now_basic.result
Changes 5.6.11: 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. 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. mysql_config_editor now supports --port and --socket options for specifying TCP/IP port number and Unix socket file name. 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. The only supported value for the innodb_mirrored_log_groups system variable is 1, so this variable is now deprecated. Setting it to 1 at startup results in a warning. Setting it to a value other than 1 at startup results in an error and the server exits. This variable will be removed in a future release.
2013-04-20 10:06:01 +02:00
share/mysql/test/suite/sys_vars/r/innodb_log_compressed_pages_basic.result
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/sys_vars/r/innodb_log_file_size_basic.result
share/mysql/test/suite/sys_vars/r/innodb_log_files_in_group_basic.result
share/mysql/test/suite/sys_vars/r/innodb_log_group_home_dir_basic.result
share/mysql/test/suite/sys_vars/r/innodb_lru_scan_depth_basic.result
share/mysql/test/suite/sys_vars/r/innodb_max_dirty_pages_pct_basic.result
share/mysql/test/suite/sys_vars/r/innodb_max_dirty_pages_pct_func.result
share/mysql/test/suite/sys_vars/r/innodb_max_dirty_pages_pct_lwm_basic.result
share/mysql/test/suite/sys_vars/r/innodb_max_purge_lag_basic.result
share/mysql/test/suite/sys_vars/r/innodb_max_purge_lag_delay_basic.result
share/mysql/test/suite/sys_vars/r/innodb_mirrored_log_groups_basic.result
share/mysql/test/suite/sys_vars/r/innodb_monitor_disable_basic.result
share/mysql/test/suite/sys_vars/r/innodb_monitor_enable_basic.result
share/mysql/test/suite/sys_vars/r/innodb_monitor_reset_all_basic.result
share/mysql/test/suite/sys_vars/r/innodb_monitor_reset_basic.result
Changes 5.6.27: * InnoDB: The new innodb_numa_interleave read-only configuration option allows you to enable the NUMA interleave memory policy for allocation of the InnoDB buffer pool. When innodb_numa_interleave is enabled, the NUMA memory policy is set to MPOL_INTERLEAVE for the mysqld process. After the InnoDB buffer pool is allocated, the NUMA memory policy is set back to MPOL_DEFAULT. This option is only available on NUMA-enabled systems. * yaSSL was upgraded to version 2.3.8. * RPM .spec files were updated so that MySQL Server builds from source RPM packages will include the proper files to take advantage of operating system NUMA capabilities. This introduces a runtime dependency on libnuma.so.1. RPM and yum detect this and refuse to install if that library is not installed. * InnoDB: Reloading a table that was evicted while empty caused an AUTO_INCREMENT value to be reset. * InnoDB: Memory allocation sanity checks were added to the memcached code. * InnoDB: A memcached flush_all command raised an assertion. A function that starts a transaction was called from within assertion code. * InnoDB: A data corruption occurred on ARM64. GCC builtins did not issue the correct fences when setting or unsetting the lock word. * InnoDB: Server shutdown was delayed waiting for the purge thread to exit. To avoid this problem, the number of calls to trx_purge() was reduced, and the trx_purge() batch size was reduced to 20. * InnoDB: In READ COMMITTED mode, a REPLACE operation on a unique secondary index resulted in a constraint violation. * InnoDB: The IBUF_BITMAP_FREE bit indicated that there was more free space in the leaf page than was actually available. * InnoDB: Setting lower_case_table_names=0 on a case-insensitive file system could result in a hang condition when running an INSERT INTO ... SELECT ... FROM tbl_name operation with the wrong tbl_name letter case. An error message is now printed and the server exits when attempting to start the server with --lower_case_table_names=0 on a case-insensitive file system. * InnoDB: The server failed to start with an innodb_force_recovery setting greater than 3. InnoDB was set to read-only mode before redo logs were applied. * InnoDB: The trx_sys_read_pertable_file_format_id() function reported the wrong file format. * Partitioning: CREATE TABLE statements that used an invalid function in a subpartitioning expression did not always fail gracefully as expected. * Partitioning: Error handling for failed partitioning-related ALTER TABLE operations against non-partitioned tables was not performed correctly * Partitioning: ALTER TABLE when executed from a stored procedure did not always work correctly with tables partitioned by RANGE. * Replication: Repeatedly checking for ERR_LOCK_WAIT_TIMEOUT (as done, for example by repeatedly executing SHOW SLAVE STATUS) during a prolonged write lock on a table led to an assert. * Replication: If statement based logging was in use, when updating multiple tables in a single statement, a single transaction could be logged as two different transactions. This was due to the binary logging process not properly identifying statements which were operating over transactional tables. The fix ensures that they are correctly identified, even if such statements do not change the contents of the tables.
2015-10-03 14:46:13 +02:00
share/mysql/test/suite/sys_vars/r/innodb_numa_interleave_basic.result
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/sys_vars/r/innodb_old_blocks_pct_basic.result
share/mysql/test/suite/sys_vars/r/innodb_old_blocks_time_basic.result
share/mysql/test/suite/sys_vars/r/innodb_online_alter_log_max_size_basic.result
share/mysql/test/suite/sys_vars/r/innodb_open_files_basic.result
share/mysql/test/suite/sys_vars/r/innodb_optimize_fulltext_only_basic.result
share/mysql/test/suite/sys_vars/r/innodb_page_hash_locks_basic.result
share/mysql/test/suite/sys_vars/r/innodb_page_size_basic.result
share/mysql/test/suite/sys_vars/r/innodb_print_all_deadlocks_basic.result
share/mysql/test/suite/sys_vars/r/innodb_purge_batch_size_basic.result
share/mysql/test/suite/sys_vars/r/innodb_purge_run_now_basic.result
share/mysql/test/suite/sys_vars/r/innodb_purge_stop_now_basic.result
share/mysql/test/suite/sys_vars/r/innodb_purge_threads_basic.result
share/mysql/test/suite/sys_vars/r/innodb_random_read_ahead_basic.result
share/mysql/test/suite/sys_vars/r/innodb_read_ahead_threshold_basic.result
share/mysql/test/suite/sys_vars/r/innodb_read_io_threads_basic.result
share/mysql/test/suite/sys_vars/r/innodb_read_only_basic.result
share/mysql/test/suite/sys_vars/r/innodb_replication_delay_basic.result
share/mysql/test/suite/sys_vars/r/innodb_rollback_on_timeout_basic.result
share/mysql/test/suite/sys_vars/r/innodb_rollback_segments_basic.result
Changes 5.6.17: Functionality Added or Changed Incompatible Change: The AES_ENCRYPT() and AES_DECRYPT() functions now permit control of the block encryption mode and take an optional initialization vector argument: The new block_encryption_mode system variable controls the mode for block-based encryption algorithms. Its default value is aes-128-ecb, which signifies encryption using a key length of 128 bits and ECB mode. An optional init_vector argument provides an initialization vector for encryption modes that require it: AES_ENCRYPT(str,key_str[,init_vector]) AES_DECRYPT(crypt_str,key_str[,init_vector]) A random string of bytes to use for the initialization vector can be produced by calling the new RANDOM_BYTES() function. For more information, see Encryption and Compression Functions. These changes make statements that use AES_ENCRYPT() or AES_DECRYPT() unsafe for statement-based replication and they cannot be stored in the query cache. Queries that use RANDOM_BYTES() are unsafe for statement-based replication and cannot be stored in the query cache. Incompatible Change: The ERROR_FOR_DIVISION_BY_ZERO, NO_ZERO_DATE, and NO_ZERO_IN_DATE SQL modes now are deprecated and setting the sql_mode value to include any of them generates a warning. In MySQL 5.7, these modes do nothing. Instead, their effects are included in the effects of strict SQL mode (STRICT_ALL_TABLES or STRICT_TRANS_TABLES). The motivation for the change in MySQL 5.7 is to reduce the number of SQL modes with an effect dependent on strict mode and make them part of strict mode itself. To make advance preparation for an upgrade to MySQL 5.7, see SQL Mode Changes in MySQL 5.7. That discussion provides guidelines to assess whether your applications will be affected by the SQL mode changes in MySQL 5.7. InnoDB: MySQL now supports rebuilding regular and partitioned InnoDB tables using online DDL (ALGORITHM=INPLACE) for the following operations: OPTIMIZE TABLE ALTER TABLE ... FORCE ALTER TABLE ... ENGINE=INNODB (when run on an InnoDB table) Online DDL support reduces table rebuild time and permits concurrent DML, which helps reduce user application downtime. For additional information, see Overview of Online DDL. On Solaris, mysql_config --libs now includes -R/path/to/library so that libraries can be found at runtime. mysql_install_db provides a more informative diagnostic message when required Perl modules are missing. The IGNORE clause for ALTER TABLE is now deprecated and will be removed in a future version of MySQL. ALTER IGNORE TABLE causes problems for replication, prevents online ALTER TABLE for unique index creation, and causes problems with foreign keys (rows removed in the parent table). Bugs Fixed
2014-03-31 12:32:13 +02:00
share/mysql/test/suite/sys_vars/r/innodb_saved_page_number_debug_basic.result
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/sys_vars/r/innodb_sort_buffer_size_basic.result
share/mysql/test/suite/sys_vars/r/innodb_spin_wait_delay_basic.result
share/mysql/test/suite/sys_vars/r/innodb_stats_auto_recalc_basic.result
share/mysql/test/suite/sys_vars/r/innodb_stats_method_basic.result
share/mysql/test/suite/sys_vars/r/innodb_stats_on_metadata_basic.result
share/mysql/test/suite/sys_vars/r/innodb_stats_persistent_basic.result
share/mysql/test/suite/sys_vars/r/innodb_stats_persistent_sample_pages_basic.result
share/mysql/test/suite/sys_vars/r/innodb_stats_sample_pages_basic.result
share/mysql/test/suite/sys_vars/r/innodb_stats_transient_sample_pages_basic.result
Changes 5.6.16: Functionality Added or Changed * InnoDB: New global configuration parameters, innodb_status_output and innodb_status_output_locks, allow you to dynamically enable and disable the standard InnoDB Monitor and InnoDB Lock Monitor for periodic output. Enabling and disabling monitors for periodic output by creating and dropping specially named tables is deprecated and may be removed in a future release. * Previously, ALTER TABLE in MySQL 5.6 could alter a table such that the result had temporal columns in both 5.5 and 5.6 format. Now ALTER TABLE upgrades old temporal columns to 5.6 format for ADD COLUMN, CHANGE COLUMN, MODIFY COLUMN, ADD INDEX, and FORCE operations. This conversion cannot be done using the INPLACE algorithm, so specifying ALGORITHM=INPLACE in these cases results in an error. * CMake now supports a -DTMPDIR=dir_name option to specify the default tmpdir value. If unspecified, the value defaults to P_tmpdir in <stdio.h>. Bugs Fixed * InnoDB; Replication: Using the InnoDB memcached plugin (see InnoDB Integration with memcached) with innodb_api_enable_binlog set to 1 caused the server to leak memory. * InnoDB: A boolean mode full-text search query would result in a memory access violation during parsing. * InnoDB: When new indexes are added by an ALTER TABLE operation, instead of only saving table-level statistics and statistics for the new indexes, InnoDB would save statistics for the entire table, including the table's other indexes. This behavior slowed ALTER TABLE performance. * InnoDB: Due to a parser error, full-text search queries that include a sub-expression could return the wrong result. * InnoDB: The innochecksum tool did not use a Windows-specific API to retrieve file size information, which resulted in an incorrect error message (Error: ibdata1 cannot be found) when the MySQL 5.6 innochecksum 2GB file size limit was exceeded. innochecksum now provides support for files larger than 2GB in both MySQL 5.6 and MySQL 5.7. * InnoDB: Due to a regression introduced by the fix for Bug17371537, memory was not allocated for the default memcached engine when using the default memcached engine as the backstore for data instead of InnoDB. * InnoDB: InnoDB would report an incorrect operating system error code after failing to initialize. * InnoDB: Manipulating a table after discarding its tablespace using ALTER TABLE ... DISCARD TABLESPACE could result in a serious error. * InnoDB: Persistent optimizer statistics would cause stalls due to latch contention. * InnoDB: MATCH() ... AGAINST queries that use a long string as an argument for AGAINST() could result in an error when run on an InnoDB table with a full-text search index. * InnoDB: An InnoDB full-text search failure would occur due to an “unended” token. The string and string length should be passed for string comparison. * InnoDB: In debug builds, a merge insert buffer during a page read would cause a memory access violation. * InnoDB: Truncating a memcached InnoDB table while memcached is performing DML operations would result in a serious error. * InnoDB: In sync0rw.ic, rw_lock_x_lock_func_nowait would needlessly call os_thread_get_curr_id. * InnoDB: Attempting to rename a table to a missing database would result in a serious error. more...
2014-02-13 08:49:56 +01:00
share/mysql/test/suite/sys_vars/r/innodb_status_output_basic.result
share/mysql/test/suite/sys_vars/r/innodb_status_output_locks_basic.result
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/sys_vars/r/innodb_strict_mode_basic.result
share/mysql/test/suite/sys_vars/r/innodb_support_xa_basic.result
share/mysql/test/suite/sys_vars/r/innodb_support_xa_func.result
share/mysql/test/suite/sys_vars/r/innodb_sync_array_size_basic.result
share/mysql/test/suite/sys_vars/r/innodb_sync_spin_loops_basic.result
share/mysql/test/suite/sys_vars/r/innodb_table_locks_basic.result
share/mysql/test/suite/sys_vars/r/innodb_table_locks_func.result
share/mysql/test/suite/sys_vars/r/innodb_thread_concurrency_basic.result
share/mysql/test/suite/sys_vars/r/innodb_thread_sleep_delay_basic.result
Changes 5.6.29: * InnoDB: A new InnoDB configuration option, innodb_tmpdir, allows you to configure a separate temporary file directory for online ALTER TABLE operations. This option was introduced to help avoid tmpdir overflows that could occur as a result of large temporary files created during online ALTER TABLE operations. innodb_tmpdir is a SESSION variable and can be configured dynamically using a SET statement. * yaSSL was upgraded to version 2.3.9. This upgrade corrects an issue in which yaSSL handled only cases of zero or one leading zeros for the key agreement instead of potentially any number, which in rare cases could cause connections to fail when using DHE cipher suites. * The Valgrind function signature in mysql-test/valgrind.supp was upgraded for Valgrind 3.11. * Bugs Fixed
2016-02-28 09:58:03 +01:00
share/mysql/test/suite/sys_vars/r/innodb_tmpdir_basic.result
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/sys_vars/r/innodb_trx_purge_view_update_only_debug_basic.result
share/mysql/test/suite/sys_vars/r/innodb_trx_rseg_n_slots_debug_basic.result
share/mysql/test/suite/sys_vars/r/innodb_undo_directory_basic.result
share/mysql/test/suite/sys_vars/r/innodb_undo_logs_basic.result
share/mysql/test/suite/sys_vars/r/innodb_undo_tablespaces_basic.result
share/mysql/test/suite/sys_vars/r/innodb_use_native_aio_basic.result
share/mysql/test/suite/sys_vars/r/innodb_use_sys_malloc_basic.result
share/mysql/test/suite/sys_vars/r/innodb_version_basic.result
share/mysql/test/suite/sys_vars/r/innodb_write_io_threads_basic.result
share/mysql/test/suite/sys_vars/r/insert_id_basic.result
share/mysql/test/suite/sys_vars/r/insert_id_func.result
share/mysql/test/suite/sys_vars/r/interactive_timeout_basic.result
share/mysql/test/suite/sys_vars/r/interactive_timeout_func.result
share/mysql/test/suite/sys_vars/r/join_buffer_size_basic_32.result
share/mysql/test/suite/sys_vars/r/join_buffer_size_basic_64.result
share/mysql/test/suite/sys_vars/r/keep_files_on_create_basic.result
share/mysql/test/suite/sys_vars/r/key_buffer_size_basic.result
share/mysql/test/suite/sys_vars/r/key_buffer_size_func.result
share/mysql/test/suite/sys_vars/r/key_cache_age_threshold_basic_32.result
share/mysql/test/suite/sys_vars/r/key_cache_age_threshold_basic_64.result
share/mysql/test/suite/sys_vars/r/key_cache_block_size_basic.result
share/mysql/test/suite/sys_vars/r/key_cache_division_limit_basic.result
share/mysql/test/suite/sys_vars/r/large_files_support_basic.result
share/mysql/test/suite/sys_vars/r/large_page_size_basic.result
share/mysql/test/suite/sys_vars/r/large_pages_basic.result
share/mysql/test/suite/sys_vars/r/last_insert_id_basic.result
share/mysql/test/suite/sys_vars/r/last_insert_id_func.result
share/mysql/test/suite/sys_vars/r/lc_messages_basic.result
share/mysql/test/suite/sys_vars/r/lc_messages_dir_basic.result
share/mysql/test/suite/sys_vars/r/lc_time_names_basic.result
share/mysql/test/suite/sys_vars/r/lc_time_names_func.result
share/mysql/test/suite/sys_vars/r/license_basic.result
share/mysql/test/suite/sys_vars/r/local_infile_basic.result
share/mysql/test/suite/sys_vars/r/local_infile_func.result
share/mysql/test/suite/sys_vars/r/lock_wait_timeout_basic.result
share/mysql/test/suite/sys_vars/r/locked_in_memory_basic.result
share/mysql/test/suite/sys_vars/r/log_bin_basename_basic.result
share/mysql/test/suite/sys_vars/r/log_bin_basic.result
share/mysql/test/suite/sys_vars/r/log_bin_index_basic.result
share/mysql/test/suite/sys_vars/r/log_bin_trust_function_creators_basic.result
share/mysql/test/suite/sys_vars/r/log_bin_trust_function_creators_func.result
share/mysql/test/suite/sys_vars/r/log_bin_use_v1_row_events_basic.result
share/mysql/test/suite/sys_vars/r/log_error_basic.result
share/mysql/test/suite/sys_vars/r/log_error_func.result
share/mysql/test/suite/sys_vars/r/log_error_func2.result
share/mysql/test/suite/sys_vars/r/log_error_func3.result
share/mysql/test/suite/sys_vars/r/log_output_basic.result
share/mysql/test/suite/sys_vars/r/log_output_func.result
share/mysql/test/suite/sys_vars/r/log_queries_not_using_indexes_basic.result
share/mysql/test/suite/sys_vars/r/log_slave_updates_basic.result
Changes 5.6.11: 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. 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. mysql_config_editor now supports --port and --socket options for specifying TCP/IP port number and Unix socket file name. 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. The only supported value for the innodb_mirrored_log_groups system variable is 1, so this variable is now deprecated. Setting it to 1 at startup results in a warning. Setting it to a value other than 1 at startup results in an error and the server exits. This variable will be removed in a future release.
2013-04-20 10:06:01 +02:00
share/mysql/test/suite/sys_vars/r/log_slow_admin_statements_basic.result
share/mysql/test/suite/sys_vars/r/log_slow_admin_statements_func.result
share/mysql/test/suite/sys_vars/r/log_slow_slave_statements_basic.result
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/sys_vars/r/log_throttle_queries_not_using_indexes_basic.result
share/mysql/test/suite/sys_vars/r/log_warnings_basic_32.result
share/mysql/test/suite/sys_vars/r/log_warnings_basic_64.result
share/mysql/test/suite/sys_vars/r/long_query_time_basic.result
share/mysql/test/suite/sys_vars/r/low_priority_updates_basic.result
share/mysql/test/suite/sys_vars/r/lower_case_file_system_basic.result
share/mysql/test/suite/sys_vars/r/lower_case_table_names_basic.result
share/mysql/test/suite/sys_vars/r/master_info_repository_basic.result
share/mysql/test/suite/sys_vars/r/master_verify_checksum_basic.result
share/mysql/test/suite/sys_vars/r/max_allowed_packet_basic.result
share/mysql/test/suite/sys_vars/r/max_allowed_packet_func.result
share/mysql/test/suite/sys_vars/r/max_binlog_cache_size_basic.result
share/mysql/test/suite/sys_vars/r/max_binlog_cache_size_func.result
share/mysql/test/suite/sys_vars/r/max_binlog_size_basic.result
share/mysql/test/suite/sys_vars/r/max_binlog_stmt_cache_size_basic.result
share/mysql/test/suite/sys_vars/r/max_connect_errors_basic_32.result
share/mysql/test/suite/sys_vars/r/max_connect_errors_basic_64.result
share/mysql/test/suite/sys_vars/r/max_connections_basic.result
share/mysql/test/suite/sys_vars/r/max_delayed_threads_basic.result
Changes 5.6.24: * CMake support was updated to handle CMake version 3.1. * The server now includes its version number when it writes the initial “starting” message to the error log, to make it easier to tell which server instance error log output applies to. This value is the same as that available from the version system variable. * ALTER TABLE did not take advantage of fast alterations that might otherwise apply to the operation to be performed, if the table contained temporal columns found to be in pre-5.6.4 format (TIME, DATETIME, and TIMESTAMP columns without support for fractional seconds precision). * Statement digesting as done previously by the Performance Schema is now done at the SQL level regardless of whether the Performance Schema is compiled in and is available to other aspects of server operation that could benefit from it. The default space available for digesting is 1024 bytes, but can be changed at server startup using the max_digest_length system variable. * Bug fixes.
2015-04-08 12:38:48 +02:00
share/mysql/test/suite/sys_vars/r/max_digest_length_basic.result
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/sys_vars/r/max_error_count_basic.result
share/mysql/test/suite/sys_vars/r/max_heap_table_size_basic.result
share/mysql/test/suite/sys_vars/r/max_insert_delayed_threads_basic.result
share/mysql/test/suite/sys_vars/r/max_join_size_basic.result
share/mysql/test/suite/sys_vars/r/max_join_size_func.result
share/mysql/test/suite/sys_vars/r/max_length_for_sort_data_basic.result
share/mysql/test/suite/sys_vars/r/max_prepared_stmt_count_basic.result
share/mysql/test/suite/sys_vars/r/max_prepared_stmt_count_func.result
share/mysql/test/suite/sys_vars/r/max_relay_log_size_basic.result
share/mysql/test/suite/sys_vars/r/max_seeks_for_key_basic_32.result
share/mysql/test/suite/sys_vars/r/max_seeks_for_key_basic_64.result
share/mysql/test/suite/sys_vars/r/max_seeks_for_key_func.result
share/mysql/test/suite/sys_vars/r/max_sort_length_basic.result
share/mysql/test/suite/sys_vars/r/max_sort_length_func.result
share/mysql/test/suite/sys_vars/r/max_sp_recursion_depth_basic.result
share/mysql/test/suite/sys_vars/r/max_sp_recursion_depth_func.result
share/mysql/test/suite/sys_vars/r/max_tmp_tables_basic_32.result
share/mysql/test/suite/sys_vars/r/max_tmp_tables_basic_64.result
share/mysql/test/suite/sys_vars/r/max_user_connections_basic.result
share/mysql/test/suite/sys_vars/r/max_user_connections_func.result
share/mysql/test/suite/sys_vars/r/max_write_lock_count_basic_32.result
share/mysql/test/suite/sys_vars/r/max_write_lock_count_basic_64.result
share/mysql/test/suite/sys_vars/r/maximum_basic.result
share/mysql/test/suite/sys_vars/r/metadata_locks_cache_size_basic.result
share/mysql/test/suite/sys_vars/r/metadata_locks_hash_instances_basic.result
share/mysql/test/suite/sys_vars/r/min_examined_row_limit_basic_32.result
share/mysql/test/suite/sys_vars/r/min_examined_row_limit_basic_64.result
share/mysql/test/suite/sys_vars/r/multi_range_count_basic_32.result
share/mysql/test/suite/sys_vars/r/multi_range_count_basic_64.result
share/mysql/test/suite/sys_vars/r/myisam_data_pointer_size_basic.result
share/mysql/test/suite/sys_vars/r/myisam_data_pointer_size_func.result
share/mysql/test/suite/sys_vars/r/myisam_max_sort_file_size_basic_32.result
share/mysql/test/suite/sys_vars/r/myisam_max_sort_file_size_basic_64.result
share/mysql/test/suite/sys_vars/r/myisam_mmap_size_basic.result
share/mysql/test/suite/sys_vars/r/myisam_recover_options_basic.result
share/mysql/test/suite/sys_vars/r/myisam_repair_threads_basic_32.result
share/mysql/test/suite/sys_vars/r/myisam_repair_threads_basic_64.result
share/mysql/test/suite/sys_vars/r/myisam_sort_buffer_size_basic_32.result
share/mysql/test/suite/sys_vars/r/myisam_sort_buffer_size_basic_64.result
share/mysql/test/suite/sys_vars/r/myisam_stats_method_basic.result
share/mysql/test/suite/sys_vars/r/myisam_stats_method_func.result
share/mysql/test/suite/sys_vars/r/myisam_use_mmap_basic.result
share/mysql/test/suite/sys_vars/r/named_pipe_basic.result
share/mysql/test/suite/sys_vars/r/net_buffer_length_basic.result
share/mysql/test/suite/sys_vars/r/net_read_timeout_basic.result
share/mysql/test/suite/sys_vars/r/net_retry_count_basic_32.result
share/mysql/test/suite/sys_vars/r/net_retry_count_basic_64.result
share/mysql/test/suite/sys_vars/r/net_write_timeout_basic.result
share/mysql/test/suite/sys_vars/r/new_basic.result
share/mysql/test/suite/sys_vars/r/old_alter_table_basic.result
share/mysql/test/suite/sys_vars/r/old_basic.result
share/mysql/test/suite/sys_vars/r/old_passwords_basic.result
share/mysql/test/suite/sys_vars/r/old_passwords_func.result
share/mysql/test/suite/sys_vars/r/open_files_limit_basic.result
share/mysql/test/suite/sys_vars/r/optimizer_prune_level_basic.result
share/mysql/test/suite/sys_vars/r/optimizer_search_depth_basic.result
share/mysql/test/suite/sys_vars/r/optimizer_switch_basic.result
share/mysql/test/suite/sys_vars/r/optimizer_trace_basic.result
share/mysql/test/suite/sys_vars/r/optimizer_trace_features_basic.result
share/mysql/test/suite/sys_vars/r/optimizer_trace_limit_basic.result
share/mysql/test/suite/sys_vars/r/optimizer_trace_max_mem_size_basic.result
share/mysql/test/suite/sys_vars/r/optimizer_trace_offset_basic.result
share/mysql/test/suite/sys_vars/r/optimizer_trace_offset_max.result
share/mysql/test/suite/sys_vars/r/performance_schema_basic.result
share/mysql/test/suite/sys_vars/r/pfs_accounts_size_basic.result
share/mysql/test/suite/sys_vars/r/pfs_digests_size_basic.result
share/mysql/test/suite/sys_vars/r/pfs_events_stages_h_size_basic.result
share/mysql/test/suite/sys_vars/r/pfs_events_stages_hl_size_basic.result
share/mysql/test/suite/sys_vars/r/pfs_events_statements_h_size_basic.result
share/mysql/test/suite/sys_vars/r/pfs_events_statements_hl_size_basic.result
share/mysql/test/suite/sys_vars/r/pfs_events_waits_h_size_basic.result
share/mysql/test/suite/sys_vars/r/pfs_events_waits_hl_size_basic.result
share/mysql/test/suite/sys_vars/r/pfs_hosts_size_basic.result
share/mysql/test/suite/sys_vars/r/pfs_max_cond_classes_basic.result
share/mysql/test/suite/sys_vars/r/pfs_max_cond_instances_basic.result
Changes 5.6.26: * Security Fix: Due to the LogJam issue (https://weakdh.org/), OpenSSL has changed the Diffie-Hellman key length parameters for openssl-1.0.1n and up. * Replication: When using a multi-threaded slave, each worker thread has its own queue of transactions to process. In previous MySQL versions, STOP SLAVE waited for all workers to process their entire queue. This logic has been changed so that STOP SLAVE first finds the newest transaction that was committed by any worker thread. Then, it waits for all workers to complete transactions older than that. Newer transactions are not processed. The new logic allows STOP SLAVE to complete faster in case some worker queues contain multiple transactions. * Previously, the max_digest_length system variable controlled the maximum digest length for all server functions that computed statement digests. However, whereas the Performance Schema may need to maintain many digest values, other server functions such as MySQL Enterprise Firewall need only one digest per session. Increasing the max_digest_length value has little impact on total memory requirements for those functions, but can increase Performance Schema memory requirements significantly. To enable configuring digest length separately for the Performance Schema, its digest length is now controlled by the new performance_schema_max_digest_length system variable. * Previously, changes to the validate_password plugin dictionary file (named by the validate_password_dictionary_file system variable) while the server was running required a restart for the server to recognize the changes. Now validate_password_dictionary_file can be set at runtime and assigning a value causes the named file to be read without a restart. In addition, two new status variables are available. validate_password_dictionary_file_last_parsed indicates when the dictionary file was last read, and validate_password_dictionary_file_words_count indicates how many words it contains. * Bugs fixed
2015-07-30 16:39:18 +02:00
share/mysql/test/suite/sys_vars/r/pfs_max_digest_length_basic.result
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/sys_vars/r/pfs_max_file_classes_basic.result
share/mysql/test/suite/sys_vars/r/pfs_max_file_handles_basic.result
share/mysql/test/suite/sys_vars/r/pfs_max_file_instances_basic.result
share/mysql/test/suite/sys_vars/r/pfs_max_mutex_classes_basic.result
share/mysql/test/suite/sys_vars/r/pfs_max_mutex_instances_basic.result
share/mysql/test/suite/sys_vars/r/pfs_max_rwlock_classes_basic.result
share/mysql/test/suite/sys_vars/r/pfs_max_rwlock_instances_basic.result
share/mysql/test/suite/sys_vars/r/pfs_max_socket_classes_basic.result
share/mysql/test/suite/sys_vars/r/pfs_max_socket_instances_basic.result
share/mysql/test/suite/sys_vars/r/pfs_max_stage_classes_basic.result
share/mysql/test/suite/sys_vars/r/pfs_max_statement_classes_basic.result
share/mysql/test/suite/sys_vars/r/pfs_max_table_handles_basic.result
share/mysql/test/suite/sys_vars/r/pfs_max_table_instances_basic.result
share/mysql/test/suite/sys_vars/r/pfs_max_thread_classes_basic.result
share/mysql/test/suite/sys_vars/r/pfs_max_thread_instances_basic.result
share/mysql/test/suite/sys_vars/r/pfs_session_connect_attrs_size_basic.result
share/mysql/test/suite/sys_vars/r/pfs_setup_actors_size_basic.result
share/mysql/test/suite/sys_vars/r/pfs_setup_objects_size_basic.result
share/mysql/test/suite/sys_vars/r/pfs_users_size_basic.result
share/mysql/test/suite/sys_vars/r/pid_file_basic.result
share/mysql/test/suite/sys_vars/r/plugin_dir_basic.result
share/mysql/test/suite/sys_vars/r/port_basic.result
share/mysql/test/suite/sys_vars/r/preload_buffer_size_basic.result
share/mysql/test/suite/sys_vars/r/profiling_basic.result
share/mysql/test/suite/sys_vars/r/profiling_h_size_basic.result
share/mysql/test/suite/sys_vars/r/protocol_version_basic.result
share/mysql/test/suite/sys_vars/r/proxy_user_basic.result
share/mysql/test/suite/sys_vars/r/pseudo_slave_mode_basic.result
share/mysql/test/suite/sys_vars/r/pseudo_thread_id_basic.result
share/mysql/test/suite/sys_vars/r/query_alloc_block_size_basic_32.result
share/mysql/test/suite/sys_vars/r/query_alloc_block_size_basic_64.result
share/mysql/test/suite/sys_vars/r/query_cache_limit_basic_32.result
share/mysql/test/suite/sys_vars/r/query_cache_limit_basic_64.result
share/mysql/test/suite/sys_vars/r/query_cache_limit_func.result
share/mysql/test/suite/sys_vars/r/query_cache_min_res_unit_basic_32.result
share/mysql/test/suite/sys_vars/r/query_cache_min_res_unit_basic_64.result
share/mysql/test/suite/sys_vars/r/query_cache_size_basic_32.result
share/mysql/test/suite/sys_vars/r/query_cache_size_basic_64.result
share/mysql/test/suite/sys_vars/r/query_cache_type_basic.result
share/mysql/test/suite/sys_vars/r/query_cache_type_func.result
share/mysql/test/suite/sys_vars/r/query_cache_wlock_invalidate_basic.result
share/mysql/test/suite/sys_vars/r/query_cache_wlock_invalidate_func.result
share/mysql/test/suite/sys_vars/r/query_prealloc_size_basic.result
share/mysql/test/suite/sys_vars/r/query_prealloc_size_func.result
share/mysql/test/suite/sys_vars/r/rand_seed1_basic.result
share/mysql/test/suite/sys_vars/r/rand_seed2_basic.result
share/mysql/test/suite/sys_vars/r/range_alloc_block_size_basic_32.result
share/mysql/test/suite/sys_vars/r/range_alloc_block_size_basic_64.result
share/mysql/test/suite/sys_vars/r/read_buffer_size_basic.result
share/mysql/test/suite/sys_vars/r/read_only_basic.result
share/mysql/test/suite/sys_vars/r/read_only_func.result
share/mysql/test/suite/sys_vars/r/read_rnd_buffer_size_basic.result
share/mysql/test/suite/sys_vars/r/relay_log_basename_basic.result
share/mysql/test/suite/sys_vars/r/relay_log_basic.result
share/mysql/test/suite/sys_vars/r/relay_log_index_basic.result
share/mysql/test/suite/sys_vars/r/relay_log_info_file_basic.result
share/mysql/test/suite/sys_vars/r/relay_log_info_repository_basic.result
share/mysql/test/suite/sys_vars/r/relay_log_purge_basic.result
share/mysql/test/suite/sys_vars/r/relay_log_recovery_basic.result
share/mysql/test/suite/sys_vars/r/relay_log_space_limit_basic.result
share/mysql/test/suite/sys_vars/r/report_host_basic.result
share/mysql/test/suite/sys_vars/r/report_password_basic.result
share/mysql/test/suite/sys_vars/r/report_port_basic.result
share/mysql/test/suite/sys_vars/r/report_user_basic.result
share/mysql/test/suite/sys_vars/r/rpl_init_slave_func.result
share/mysql/test/suite/sys_vars/r/rpl_max_binlog_size_func.result
share/mysql/test/suite/sys_vars/r/rpl_recovery_rank_basic_32.result
share/mysql/test/suite/sys_vars/r/rpl_recovery_rank_basic_64.result
share/mysql/test/suite/sys_vars/r/rpl_semi_sync_master_enabled_basic.result
share/mysql/test/suite/sys_vars/r/rpl_semi_sync_master_timeout_basic.result
share/mysql/test/suite/sys_vars/r/rpl_semi_sync_master_trace_level_basic.result
share/mysql/test/suite/sys_vars/r/rpl_semi_sync_master_wait_no_slave_basic.result
share/mysql/test/suite/sys_vars/r/rpl_semi_sync_slave_enabled_basic.result
share/mysql/test/suite/sys_vars/r/rpl_semi_sync_slave_trace_level_basic.result
Changes 5.6.13: * Important Change; Replication: By default, when promoting integers from a smaller type on the master to a larger type on the slave (for example, from a SMALLINT column on the master to a BIGINT column on the slave), the promoted values are treated as though they are signed. Now in such cases it is possible to modify or override this behavior using one or both of ALL_SIGNED, ALL_UNSIGNED in the set of values specified for the slave_type_conversions server system variable. For more information, see Row-based replication: attribute promotion and demotion, as well as the description of the variable. * Previously, program options could be specified in full or as any unambiguous prefix. For example, the --compress option could be given to mysqldump as --compr, but not as --comp because the latter is ambiguous. Option prefixes now are deprecated. They can cause problems when new options are implemented for programs. A prefix that is currently unambiguous might become ambiguous in the future. If an unambiguous prefix is given, a warning now occurs to provide feedback. For example: Warning: Using unique option prefix compr instead of compress is deprecated and will be removed in a future release. Please use the full name instead. Option prefixes are no longer supported in MySQL 5.7; only full options are accepted. * The C API libmysqlclient shared-library .so files now have version 18.1.0 (up from version 18.0.0 used in MySQL 5.5). * In batch mode, mysql formatted result status messages such as “"Query OK, 1 row affected"” but did not print them. Now these messages are not formatted. * Bugs Fixed
2013-07-31 11:51:38 +02:00
share/mysql/test/suite/sys_vars/r/rpl_stop_slave_timeout_basic.result
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/sys_vars/r/secure_auth_basic.result
share/mysql/test/suite/sys_vars/r/secure_auth_func.result
share/mysql/test/suite/sys_vars/r/secure_file_priv.result
share/mysql/test/suite/sys_vars/r/secure_file_priv2.result
share/mysql/test/suite/sys_vars/r/secure_file_priv_basic.result
share/mysql/test/suite/sys_vars/r/server_id_basic.result
share/mysql/test/suite/sys_vars/r/server_id_bits_basic.result
share/mysql/test/suite/sys_vars/r/server_uuid_basic.result
share/mysql/test/suite/sys_vars/r/sha256_password_private_key_path_basic.result
share/mysql/test/suite/sys_vars/r/sha256_password_public_key_path_basic.result
share/mysql/test/suite/sys_vars/r/shared_memory_base_name_basic.result
share/mysql/test/suite/sys_vars/r/shared_memory_basic.result
Changes 5.6.24: * CMake support was updated to handle CMake version 3.1. * The server now includes its version number when it writes the initial “starting” message to the error log, to make it easier to tell which server instance error log output applies to. This value is the same as that available from the version system variable. * ALTER TABLE did not take advantage of fast alterations that might otherwise apply to the operation to be performed, if the table contained temporal columns found to be in pre-5.6.4 format (TIME, DATETIME, and TIMESTAMP columns without support for fractional seconds precision). * Statement digesting as done previously by the Performance Schema is now done at the SQL level regardless of whether the Performance Schema is compiled in and is available to other aspects of server operation that could benefit from it. The default space available for digesting is 1024 bytes, but can be changed at server startup using the max_digest_length system variable. * Bug fixes.
2015-04-08 12:38:48 +02:00
share/mysql/test/suite/sys_vars/r/show_old_temporals_basic.result
Changes 5.6.21: The --skip-innodb option is now deprecated and its use results in a warning. It will be removed in a future MySQL release. This also applies to its synonyms (--innodb=OFF, --disable-innodb, and so forth). MySQL Enterprise Edition now includes a set of encryption functions based on the OpenSSL library that expose OpenSSL capabilities at the SQL level. Replication: The new variable simplified_binlog_gtid_recovery can be used to change the way binary log files are searched for previous GTIDs during recovery, speeding up the process when a large number of binary log files exist. Internally, spatial data types such as Geometry are represented as BLOB values, so when invoked with the --hex-blob option, mysqldump now displays spatial values in hex. Bugs Fixed...
2014-10-01 10:34:23 +02:00
share/mysql/test/suite/sys_vars/r/simplified_binlog_gtid_recovery_basic.result
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/sys_vars/r/skip_external_locking_basic.result
share/mysql/test/suite/sys_vars/r/skip_name_resolve_basic.result
share/mysql/test/suite/sys_vars/r/skip_networking_basic.result
share/mysql/test/suite/sys_vars/r/skip_show_database_basic.result
share/mysql/test/suite/sys_vars/r/slave_allow_batching_basic.result
share/mysql/test/suite/sys_vars/r/slave_checkpoint_group_basic.result
share/mysql/test/suite/sys_vars/r/slave_checkpoint_period_basic.result
share/mysql/test/suite/sys_vars/r/slave_compressed_protocol_basic.result
share/mysql/test/suite/sys_vars/r/slave_exec_mode_basic.result
share/mysql/test/suite/sys_vars/r/slave_load_tmpdir_basic.result
share/mysql/test/suite/sys_vars/r/slave_max_allowed_packet_basic.result
share/mysql/test/suite/sys_vars/r/slave_net_timeout_basic.result
share/mysql/test/suite/sys_vars/r/slave_parallel_workers_basic.result
share/mysql/test/suite/sys_vars/r/slave_pending_jobs_size_max_basic.result
share/mysql/test/suite/sys_vars/r/slave_rows_search_algorithms_basic.result
share/mysql/test/suite/sys_vars/r/slave_skip_errors_basic.result
share/mysql/test/suite/sys_vars/r/slave_sql_verify_checksum_basic.result
share/mysql/test/suite/sys_vars/r/slave_transaction_retries_basic_32.result
share/mysql/test/suite/sys_vars/r/slave_transaction_retries_basic_64.result
share/mysql/test/suite/sys_vars/r/slave_type_conversions_basic.result
share/mysql/test/suite/sys_vars/r/slow_launch_time_basic.result
share/mysql/test/suite/sys_vars/r/slow_launch_time_func.result
share/mysql/test/suite/sys_vars/r/slow_query_log_basic.result
share/mysql/test/suite/sys_vars/r/slow_query_log_file_basic.result
share/mysql/test/suite/sys_vars/r/slow_query_log_file_func.result
share/mysql/test/suite/sys_vars/r/slow_query_log_func.result
share/mysql/test/suite/sys_vars/r/socket_basic.result
share/mysql/test/suite/sys_vars/r/sort_buffer_size_basic_32.result
share/mysql/test/suite/sys_vars/r/sort_buffer_size_basic_64.result
share/mysql/test/suite/sys_vars/r/sql_auto_is_null_basic.result
share/mysql/test/suite/sys_vars/r/sql_big_selects_basic.result
share/mysql/test/suite/sys_vars/r/sql_big_selects_func.result
share/mysql/test/suite/sys_vars/r/sql_buffer_result_basic.result
share/mysql/test/suite/sys_vars/r/sql_buffer_result_func.result
share/mysql/test/suite/sys_vars/r/sql_log_bin_basic.result
share/mysql/test/suite/sys_vars/r/sql_log_off_basic.result
share/mysql/test/suite/sys_vars/r/sql_log_off_func.result
share/mysql/test/suite/sys_vars/r/sql_low_priority_updates_func.result
share/mysql/test/suite/sys_vars/r/sql_mode_basic.result
share/mysql/test/suite/sys_vars/r/sql_mode_func.result
share/mysql/test/suite/sys_vars/r/sql_notes_basic.result
share/mysql/test/suite/sys_vars/r/sql_notes_func.result
share/mysql/test/suite/sys_vars/r/sql_quote_show_create_basic.result
share/mysql/test/suite/sys_vars/r/sql_quote_show_create_func.result
share/mysql/test/suite/sys_vars/r/sql_safe_updates_basic.result
share/mysql/test/suite/sys_vars/r/sql_safe_updates_func.result
share/mysql/test/suite/sys_vars/r/sql_select_limit_basic.result
share/mysql/test/suite/sys_vars/r/sql_select_limit_func.result
share/mysql/test/suite/sys_vars/r/sql_slave_skip_counter_basic.result
share/mysql/test/suite/sys_vars/r/sql_warnings_basic.result
share/mysql/test/suite/sys_vars/r/sql_warnings_func.result
share/mysql/test/suite/sys_vars/r/ssl_ca_basic.result
share/mysql/test/suite/sys_vars/r/ssl_capath_basic.result
share/mysql/test/suite/sys_vars/r/ssl_cert_basic.result
share/mysql/test/suite/sys_vars/r/ssl_cipher_basic.result
share/mysql/test/suite/sys_vars/r/ssl_crl_basic.result
share/mysql/test/suite/sys_vars/r/ssl_crlpath_basic.result
share/mysql/test/suite/sys_vars/r/ssl_key_basic.result
share/mysql/test/suite/sys_vars/r/storage_engine_basic.result
share/mysql/test/suite/sys_vars/r/stored_program_cache_basic.result
share/mysql/test/suite/sys_vars/r/sync_binlog_basic.result
share/mysql/test/suite/sys_vars/r/sync_frm_basic.result
share/mysql/test/suite/sys_vars/r/sync_master_info_basic.result
share/mysql/test/suite/sys_vars/r/sync_relay_log_basic.result
share/mysql/test/suite/sys_vars/r/sync_relay_log_info_basic.result
share/mysql/test/suite/sys_vars/r/system_time_zone_basic.result
share/mysql/test/suite/sys_vars/r/table_definition_cache_basic.result
share/mysql/test/suite/sys_vars/r/table_open_cache_basic.result
share/mysql/test/suite/sys_vars/r/table_open_cache_instances_basic.result
share/mysql/test/suite/sys_vars/r/thread_cache_size_basic.result
share/mysql/test/suite/sys_vars/r/thread_cache_size_func.result
share/mysql/test/suite/sys_vars/r/thread_concurrency_basic.result
share/mysql/test/suite/sys_vars/r/thread_handling_basic.result
share/mysql/test/suite/sys_vars/r/thread_stack_basic.result
share/mysql/test/suite/sys_vars/r/time_format_basic.result
share/mysql/test/suite/sys_vars/r/time_zone_basic.result
share/mysql/test/suite/sys_vars/r/time_zone_func.result
share/mysql/test/suite/sys_vars/r/timed_mutexes_basic.result
share/mysql/test/suite/sys_vars/r/timestamp_basic.result
share/mysql/test/suite/sys_vars/r/timestamp_func.result
share/mysql/test/suite/sys_vars/r/timestamp_sysdate_is_now_func.result
share/mysql/test/suite/sys_vars/r/tmp_table_size_basic.result
share/mysql/test/suite/sys_vars/r/tmpdir_basic.result
Changes 5.6.24: * CMake support was updated to handle CMake version 3.1. * The server now includes its version number when it writes the initial “starting” message to the error log, to make it easier to tell which server instance error log output applies to. This value is the same as that available from the version system variable. * ALTER TABLE did not take advantage of fast alterations that might otherwise apply to the operation to be performed, if the table contained temporal columns found to be in pre-5.6.4 format (TIME, DATETIME, and TIMESTAMP columns without support for fractional seconds precision). * Statement digesting as done previously by the Performance Schema is now done at the SQL level regardless of whether the Performance Schema is compiled in and is available to other aspects of server operation that could benefit from it. The default space available for digesting is 1024 bytes, but can be changed at server startup using the max_digest_length system variable. * Bug fixes.
2015-04-08 12:38:48 +02:00
share/mysql/test/suite/sys_vars/r/transaction_alloc_block_size_basic.result
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/sys_vars/r/transaction_allow_batching_basic.result
Changes 5.6.24: * CMake support was updated to handle CMake version 3.1. * The server now includes its version number when it writes the initial “starting” message to the error log, to make it easier to tell which server instance error log output applies to. This value is the same as that available from the version system variable. * ALTER TABLE did not take advantage of fast alterations that might otherwise apply to the operation to be performed, if the table contained temporal columns found to be in pre-5.6.4 format (TIME, DATETIME, and TIMESTAMP columns without support for fractional seconds precision). * Statement digesting as done previously by the Performance Schema is now done at the SQL level regardless of whether the Performance Schema is compiled in and is available to other aspects of server operation that could benefit from it. The default space available for digesting is 1024 bytes, but can be changed at server startup using the max_digest_length system variable. * Bug fixes.
2015-04-08 12:38:48 +02:00
share/mysql/test/suite/sys_vars/r/transaction_prealloc_size_basic.result
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/sys_vars/r/tx_isolation_basic.result
share/mysql/test/suite/sys_vars/r/tx_isolation_func.result
share/mysql/test/suite/sys_vars/r/tx_read_only_basic.result
share/mysql/test/suite/sys_vars/r/unique_checks_basic.result
share/mysql/test/suite/sys_vars/r/updatable_views_with_limit_basic.result
share/mysql/test/suite/sys_vars/r/updatable_views_with_limit_func.result
share/mysql/test/suite/sys_vars/r/version_basic.result
share/mysql/test/suite/sys_vars/r/version_comment_basic.result
share/mysql/test/suite/sys_vars/r/version_compile_machine_basic.result
share/mysql/test/suite/sys_vars/r/version_compile_os_basic.result
share/mysql/test/suite/sys_vars/r/wait_timeout_basic.result
share/mysql/test/suite/sys_vars/r/wait_timeout_func.result
share/mysql/test/suite/sys_vars/r/warning_count_basic.result
share/mysql/test/suite/sys_vars/t/all_vars-master.opt
share/mysql/test/suite/sys_vars/t/all_vars.test
share/mysql/test/suite/sys_vars/t/auto_increment_increment_basic.test
share/mysql/test/suite/sys_vars/t/auto_increment_increment_func.test
share/mysql/test/suite/sys_vars/t/auto_increment_offset_basic.test
share/mysql/test/suite/sys_vars/t/auto_increment_offset_func.test
share/mysql/test/suite/sys_vars/t/autocommit_basic.test
share/mysql/test/suite/sys_vars/t/autocommit_func.test
share/mysql/test/suite/sys_vars/t/autocommit_func2-master.opt
share/mysql/test/suite/sys_vars/t/autocommit_func2.test
share/mysql/test/suite/sys_vars/t/autocommit_func3-master.opt
share/mysql/test/suite/sys_vars/t/autocommit_func3.test
share/mysql/test/suite/sys_vars/t/autocommit_func4-master.opt
share/mysql/test/suite/sys_vars/t/autocommit_func4.test
share/mysql/test/suite/sys_vars/t/autocommit_func5-master.opt
share/mysql/test/suite/sys_vars/t/autocommit_func5.test
share/mysql/test/suite/sys_vars/t/automatic_sp_privileges_basic.test
share/mysql/test/suite/sys_vars/t/automatic_sp_privileges_func.test
Changes 5.6.24: * CMake support was updated to handle CMake version 3.1. * The server now includes its version number when it writes the initial “starting” message to the error log, to make it easier to tell which server instance error log output applies to. This value is the same as that available from the version system variable. * ALTER TABLE did not take advantage of fast alterations that might otherwise apply to the operation to be performed, if the table contained temporal columns found to be in pre-5.6.4 format (TIME, DATETIME, and TIMESTAMP columns without support for fractional seconds precision). * Statement digesting as done previously by the Performance Schema is now done at the SQL level regardless of whether the Performance Schema is compiled in and is available to other aspects of server operation that could benefit from it. The default space available for digesting is 1024 bytes, but can be changed at server startup using the max_digest_length system variable. * Bug fixes.
2015-04-08 12:38:48 +02:00
share/mysql/test/suite/sys_vars/t/avoid_temporal_upgrade_basic.test
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/sys_vars/t/back_log_basic.test
share/mysql/test/suite/sys_vars/t/basedir_basic.test
share/mysql/test/suite/sys_vars/t/big_tables_basic.test
share/mysql/test/suite/sys_vars/t/bind_address_basic.test
share/mysql/test/suite/sys_vars/t/binlog_cache_size_basic_32.test
share/mysql/test/suite/sys_vars/t/binlog_cache_size_basic_64.test
share/mysql/test/suite/sys_vars/t/binlog_checksum_basic.test
share/mysql/test/suite/sys_vars/t/binlog_direct_non_transactional_updates_basic.test
Changes 5.6.22: * Noisy compiler warnings on FreeBSD 10 were silenced. * CMake workarounds for older Mac OS X and XCode versions were removed. On Mac OS X, compilation always uses Clang, even for 32-bit builds. * Previously, the MYSQL_MAINTAINER_MODE CMake option was turned on by default for debug builds and off for release builds, and MYSQL_MAINTAINER_MODE caused -Werror to be enabled when building with GCC. This made it cumbersome to enable -Werror under certain conditions, such as when compiling with Clang. * Build support was modified to produce the same warnings for Clang as for gcc. * CMake configuration for the Clang compiler sets more appropriate flags for building on Linux. Specifically, -g -fno-omit-frame-pointer -fno-strict-aliasing is now added. * Bugs fixed.
2014-12-02 13:40:09 +01:00
share/mysql/test/suite/sys_vars/t/binlog_error_action_basic.test
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/sys_vars/t/binlog_format_basic.test
Changes 5.6.23: * The linked OpenSSL library for the MySQL Commercial Server has been updated from version 1.0.1j to version 1.0.1k. * Support for the SSL 2.0 and SSL 3.0 protocols has been disabled because they provide weak encryption. * yaSSL was upgraded to version 2.3.7. * The valid date range of the SSL certificates in mysql-test/std_data has been extended to the year 2029. * Bugs Fixed
2015-02-07 20:23:40 +01:00
share/mysql/test/suite/sys_vars/t/binlog_gtid_simple_recovery_basic.test
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/sys_vars/t/binlog_max_flush_queue_time_basic.test
share/mysql/test/suite/sys_vars/t/binlog_order_commits_basic.test
share/mysql/test/suite/sys_vars/t/binlog_row_image_basic.test
share/mysql/test/suite/sys_vars/t/binlog_rows_query_log_events_basic.test
share/mysql/test/suite/sys_vars/t/binlog_stmt_cache_size_basic_32.test
share/mysql/test/suite/sys_vars/t/binlog_stmt_cache_size_basic_64.test
Changes 5.6.20: Security Fix: The linked OpenSSL library for the MySQL 5.6 Commercial Server has been updated from version 1.0.1g to version 1.0.1h. Versions of OpenSSL prior to and including 1.0.1g are reported to be vulnerable to CVE-2014-0224. This change does not affect the Oracle-produced MySQL Community build of MySQL Server 5.6, which uses the yaSSL library instead. DTrace Support MySQL now includes DTrace support on Oracle Linux 6 or higher with UEK kernel. If DTrace is present, server builds will detect it with no special CMake options required. For information about using DTrace on MySQL, see Tracing mysqld Using DTrace. InnoDB Notes Important Change: Redo log writes for large, externally stored BLOB fields could overwrite the most recent checkpoint. The 5.6.20 patch limits the size of redo log BLOB writes to 10% of the redo log file size. The 5.7.5 patch addresses the bug without imposing a limitation. For MySQL 5.5, the bug remains a known limitation. As a result of the redo log BLOB write limit introduced for MySQL 5.6, innodb_log_file_size should be set to a value greater than 10 times the largest BLOB data size found in the rows of your tables plus the length of other variable length fields (VARCHAR, VARBINARY, and TEXT type fields). Failing to do so could result in “Row size too large” errors. No action is required if your innodb_log_file_size setting is already sufficiently large or your tables contain no BLOB data. Functionality Added or Changed Replication: The new system variable binlog_impossible_mode controls what happens if the server cannot write to the binary log, for example, due to a file error. For backward compatibility, the default for binlog_impossible_mode is IGNORE_ERROR, meaning the server logs the error, halts logging, and continues updates to the database. Setting this variable to ABORT_SERVER makes the server halt logging and shut down if it cannot write to the binary log. CMake support was updated to handle CMake version 3. New Debian7, Ubuntu12.04, and Ubuntu14.04 distribution support that was introduced with 5.6.17 now comes with the platform-specific packaging source placed under the packaging directory, in the deb-precise, deb-wheezy, and deb-trusty directories. Support for LinuxThreads has been removed from the source code. LinuxThreads was superseded by NPTL in Linux 2.6. By default, mysql_install_db creates a my.cnf file in the installation base directory using a template. This may be undesireable for some deployments. To enable this behavior to be suppressed, mysql_install_db now supports a --keep-my-cnf option to preserve any existing my.cnf file and not create a new my.cnf file. The mysqlhotcopy utility is now deprecated and will be removed in a future version of MySQL. Among the reasons for this: It works only for the MyISAM and ARCHIVE storage engines; it works on Unix but not Windows. Alternatives include mysqldump and MySQL Enterprise Backup. The timed_mutexes system variable has no effect and is deprecated. Bugs Fixed
2014-08-10 17:11:57 +02:00
share/mysql/test/suite/sys_vars/t/binlogging_impossible_mode_basic.test
Changes 5.6.17: Functionality Added or Changed Incompatible Change: The AES_ENCRYPT() and AES_DECRYPT() functions now permit control of the block encryption mode and take an optional initialization vector argument: The new block_encryption_mode system variable controls the mode for block-based encryption algorithms. Its default value is aes-128-ecb, which signifies encryption using a key length of 128 bits and ECB mode. An optional init_vector argument provides an initialization vector for encryption modes that require it: AES_ENCRYPT(str,key_str[,init_vector]) AES_DECRYPT(crypt_str,key_str[,init_vector]) A random string of bytes to use for the initialization vector can be produced by calling the new RANDOM_BYTES() function. For more information, see Encryption and Compression Functions. These changes make statements that use AES_ENCRYPT() or AES_DECRYPT() unsafe for statement-based replication and they cannot be stored in the query cache. Queries that use RANDOM_BYTES() are unsafe for statement-based replication and cannot be stored in the query cache. Incompatible Change: The ERROR_FOR_DIVISION_BY_ZERO, NO_ZERO_DATE, and NO_ZERO_IN_DATE SQL modes now are deprecated and setting the sql_mode value to include any of them generates a warning. In MySQL 5.7, these modes do nothing. Instead, their effects are included in the effects of strict SQL mode (STRICT_ALL_TABLES or STRICT_TRANS_TABLES). The motivation for the change in MySQL 5.7 is to reduce the number of SQL modes with an effect dependent on strict mode and make them part of strict mode itself. To make advance preparation for an upgrade to MySQL 5.7, see SQL Mode Changes in MySQL 5.7. That discussion provides guidelines to assess whether your applications will be affected by the SQL mode changes in MySQL 5.7. InnoDB: MySQL now supports rebuilding regular and partitioned InnoDB tables using online DDL (ALGORITHM=INPLACE) for the following operations: OPTIMIZE TABLE ALTER TABLE ... FORCE ALTER TABLE ... ENGINE=INNODB (when run on an InnoDB table) Online DDL support reduces table rebuild time and permits concurrent DML, which helps reduce user application downtime. For additional information, see Overview of Online DDL. On Solaris, mysql_config --libs now includes -R/path/to/library so that libraries can be found at runtime. mysql_install_db provides a more informative diagnostic message when required Perl modules are missing. The IGNORE clause for ALTER TABLE is now deprecated and will be removed in a future version of MySQL. ALTER IGNORE TABLE causes problems for replication, prevents online ALTER TABLE for unique index creation, and causes problems with foreign keys (rows removed in the parent table). Bugs Fixed
2014-03-31 12:32:13 +02:00
share/mysql/test/suite/sys_vars/t/block_encryption_mode_basic.test
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/sys_vars/t/bulk_insert_buffer_size_basic_32.test
share/mysql/test/suite/sys_vars/t/bulk_insert_buffer_size_basic_64.test
share/mysql/test/suite/sys_vars/t/character_set_client_basic.test
share/mysql/test/suite/sys_vars/t/character_set_client_func.test
share/mysql/test/suite/sys_vars/t/character_set_connection_basic.test
share/mysql/test/suite/sys_vars/t/character_set_connection_func.test
share/mysql/test/suite/sys_vars/t/character_set_database_basic.test
share/mysql/test/suite/sys_vars/t/character_set_database_func.test
share/mysql/test/suite/sys_vars/t/character_set_filesystem_basic.test
share/mysql/test/suite/sys_vars/t/character_set_filesystem_func-master.opt
share/mysql/test/suite/sys_vars/t/character_set_results_basic.test
share/mysql/test/suite/sys_vars/t/character_set_results_func.test
share/mysql/test/suite/sys_vars/t/character_set_server_basic.test
share/mysql/test/suite/sys_vars/t/character_set_server_func.test
share/mysql/test/suite/sys_vars/t/character_set_system_basic.test
share/mysql/test/suite/sys_vars/t/character_sets_dir_basic.test
share/mysql/test/suite/sys_vars/t/collation_connection_basic.test
share/mysql/test/suite/sys_vars/t/collation_connection_func.test
share/mysql/test/suite/sys_vars/t/collation_database_basic.test
share/mysql/test/suite/sys_vars/t/collation_database_func.test
share/mysql/test/suite/sys_vars/t/collation_server_basic.test
share/mysql/test/suite/sys_vars/t/collation_server_func.test
share/mysql/test/suite/sys_vars/t/completion_type_basic.test
share/mysql/test/suite/sys_vars/t/completion_type_func.test
share/mysql/test/suite/sys_vars/t/concurrent_insert_basic.test
share/mysql/test/suite/sys_vars/t/concurrent_insert_func.test
share/mysql/test/suite/sys_vars/t/connect_timeout_basic.test
share/mysql/test/suite/sys_vars/t/core_file_basic-master.opt
share/mysql/test/suite/sys_vars/t/core_file_basic.test
share/mysql/test/suite/sys_vars/t/datadir_basic.test
share/mysql/test/suite/sys_vars/t/date_format_basic.test
share/mysql/test/suite/sys_vars/t/datetime_format_basic.test
share/mysql/test/suite/sys_vars/t/debug_basic.test
share/mysql/test/suite/sys_vars/t/debug_sync_basic.test
share/mysql/test/suite/sys_vars/t/default_storage_engine_basic.test
share/mysql/test/suite/sys_vars/t/default_tmp_storage_engine_basic.test
share/mysql/test/suite/sys_vars/t/default_week_format_basic.test
share/mysql/test/suite/sys_vars/t/default_week_format_func.test
share/mysql/test/suite/sys_vars/t/delay_key_write_basic.test
share/mysql/test/suite/sys_vars/t/delay_key_write_func-master.opt
share/mysql/test/suite/sys_vars/t/delay_key_write_func.test
share/mysql/test/suite/sys_vars/t/delayed_insert_limit_basic_32.test
share/mysql/test/suite/sys_vars/t/delayed_insert_limit_basic_64.test
share/mysql/test/suite/sys_vars/t/delayed_insert_limit_func.test
share/mysql/test/suite/sys_vars/t/delayed_insert_timeout_basic.test
share/mysql/test/suite/sys_vars/t/delayed_queue_size_basic_32.test
share/mysql/test/suite/sys_vars/t/delayed_queue_size_basic_64.test
share/mysql/test/suite/sys_vars/t/disabled.def
share/mysql/test/suite/sys_vars/t/disconnect_on_expired_password_basic.test
share/mysql/test/suite/sys_vars/t/div_precision_increment_basic.test
share/mysql/test/suite/sys_vars/t/div_precision_increment_func.test
share/mysql/test/suite/sys_vars/t/end_markers_in_json_basic.test
share/mysql/test/suite/sys_vars/t/enforce_gtid_consistency_basic.test
share/mysql/test/suite/sys_vars/t/eq_range_index_dive_limit_basic.test
share/mysql/test/suite/sys_vars/t/error_count_basic.test
share/mysql/test/suite/sys_vars/t/event_scheduler_basic.test
share/mysql/test/suite/sys_vars/t/expire_logs_days_basic.test
share/mysql/test/suite/sys_vars/t/explicit_defaults_for_timestamp_basic.test
share/mysql/test/suite/sys_vars/t/external_user_basic.test
share/mysql/test/suite/sys_vars/t/flush_basic.test
share/mysql/test/suite/sys_vars/t/flush_time_basic.test
share/mysql/test/suite/sys_vars/t/foreign_key_checks_basic.test
share/mysql/test/suite/sys_vars/t/foreign_key_checks_func.test
share/mysql/test/suite/sys_vars/t/ft_boolean_syntax_basic.test
share/mysql/test/suite/sys_vars/t/ft_boolean_syntax_func.test
share/mysql/test/suite/sys_vars/t/ft_max_word_len_basic.test
share/mysql/test/suite/sys_vars/t/ft_min_word_len_basic.test
share/mysql/test/suite/sys_vars/t/ft_query_expansion_limit_basic.test
share/mysql/test/suite/sys_vars/t/ft_stopword_file_basic.test
share/mysql/test/suite/sys_vars/t/general_log_basic.test
share/mysql/test/suite/sys_vars/t/general_log_file_basic-master.opt
share/mysql/test/suite/sys_vars/t/general_log_file_basic.test
share/mysql/test/suite/sys_vars/t/general_log_file_func-master.opt
share/mysql/test/suite/sys_vars/t/general_log_file_func.test
share/mysql/test/suite/sys_vars/t/general_log_func.test
share/mysql/test/suite/sys_vars/t/group_concat_max_len_basic.test
share/mysql/test/suite/sys_vars/t/group_concat_max_len_func.test
share/mysql/test/suite/sys_vars/t/gtid_executed_basic.test
share/mysql/test/suite/sys_vars/t/gtid_mode_basic.test
share/mysql/test/suite/sys_vars/t/gtid_next_basic.test
share/mysql/test/suite/sys_vars/t/gtid_owned_basic.test
share/mysql/test/suite/sys_vars/t/gtid_purged_basic.test
share/mysql/test/suite/sys_vars/t/have_compress_basic.test
share/mysql/test/suite/sys_vars/t/have_crypt_basic.test
share/mysql/test/suite/sys_vars/t/have_dynamic_loading_basic.test
share/mysql/test/suite/sys_vars/t/have_geometry_basic.test
share/mysql/test/suite/sys_vars/t/have_openssl_basic.test
share/mysql/test/suite/sys_vars/t/have_profiling_basic.test
share/mysql/test/suite/sys_vars/t/have_query_cache_basic.test
share/mysql/test/suite/sys_vars/t/have_rtree_keys_basic.test
share/mysql/test/suite/sys_vars/t/have_ssl_basic.test
share/mysql/test/suite/sys_vars/t/have_symlink_basic.test
share/mysql/test/suite/sys_vars/t/host_cache_size_basic-master.opt
share/mysql/test/suite/sys_vars/t/host_cache_size_basic.test
share/mysql/test/suite/sys_vars/t/hostname_basic.test
share/mysql/test/suite/sys_vars/t/identity_basic.test
share/mysql/test/suite/sys_vars/t/identity_func-master.opt
share/mysql/test/suite/sys_vars/t/identity_func.test
share/mysql/test/suite/sys_vars/t/ignore_builtin_innodb_basic.test
share/mysql/test/suite/sys_vars/t/ignore_db_dirs_basic-master.opt
share/mysql/test/suite/sys_vars/t/ignore_db_dirs_basic.test
share/mysql/test/suite/sys_vars/t/init_connect_basic.test
share/mysql/test/suite/sys_vars/t/init_file_basic.test
share/mysql/test/suite/sys_vars/t/init_slave_basic.test
share/mysql/test/suite/sys_vars/t/innodb_adaptive_flushing_basic.test
share/mysql/test/suite/sys_vars/t/innodb_adaptive_flushing_lwm_basic.test
share/mysql/test/suite/sys_vars/t/innodb_adaptive_hash_index_basic.test
share/mysql/test/suite/sys_vars/t/innodb_adaptive_max_sleep_delay_basic.test
share/mysql/test/suite/sys_vars/t/innodb_additional_mem_pool_size_basic.test
share/mysql/test/suite/sys_vars/t/innodb_api_bk_commit_interval_basic.test
share/mysql/test/suite/sys_vars/t/innodb_api_disable_rowlock_basic.test
share/mysql/test/suite/sys_vars/t/innodb_api_enable_binlog_basic.test
share/mysql/test/suite/sys_vars/t/innodb_api_enable_mdl_basic.test
share/mysql/test/suite/sys_vars/t/innodb_api_trx_level_basic.test
share/mysql/test/suite/sys_vars/t/innodb_autoextend_increment_basic.test
share/mysql/test/suite/sys_vars/t/innodb_autoinc_lock_mode_basic.test
share/mysql/test/suite/sys_vars/t/innodb_autoinc_lock_mode_func-master.opt
share/mysql/test/suite/sys_vars/t/innodb_autoinc_lock_mode_func.test
Changes 5.6.16: Functionality Added or Changed * InnoDB: New global configuration parameters, innodb_status_output and innodb_status_output_locks, allow you to dynamically enable and disable the standard InnoDB Monitor and InnoDB Lock Monitor for periodic output. Enabling and disabling monitors for periodic output by creating and dropping specially named tables is deprecated and may be removed in a future release. * Previously, ALTER TABLE in MySQL 5.6 could alter a table such that the result had temporal columns in both 5.5 and 5.6 format. Now ALTER TABLE upgrades old temporal columns to 5.6 format for ADD COLUMN, CHANGE COLUMN, MODIFY COLUMN, ADD INDEX, and FORCE operations. This conversion cannot be done using the INPLACE algorithm, so specifying ALGORITHM=INPLACE in these cases results in an error. * CMake now supports a -DTMPDIR=dir_name option to specify the default tmpdir value. If unspecified, the value defaults to P_tmpdir in <stdio.h>. Bugs Fixed * InnoDB; Replication: Using the InnoDB memcached plugin (see InnoDB Integration with memcached) with innodb_api_enable_binlog set to 1 caused the server to leak memory. * InnoDB: A boolean mode full-text search query would result in a memory access violation during parsing. * InnoDB: When new indexes are added by an ALTER TABLE operation, instead of only saving table-level statistics and statistics for the new indexes, InnoDB would save statistics for the entire table, including the table's other indexes. This behavior slowed ALTER TABLE performance. * InnoDB: Due to a parser error, full-text search queries that include a sub-expression could return the wrong result. * InnoDB: The innochecksum tool did not use a Windows-specific API to retrieve file size information, which resulted in an incorrect error message (Error: ibdata1 cannot be found) when the MySQL 5.6 innochecksum 2GB file size limit was exceeded. innochecksum now provides support for files larger than 2GB in both MySQL 5.6 and MySQL 5.7. * InnoDB: Due to a regression introduced by the fix for Bug17371537, memory was not allocated for the default memcached engine when using the default memcached engine as the backstore for data instead of InnoDB. * InnoDB: InnoDB would report an incorrect operating system error code after failing to initialize. * InnoDB: Manipulating a table after discarding its tablespace using ALTER TABLE ... DISCARD TABLESPACE could result in a serious error. * InnoDB: Persistent optimizer statistics would cause stalls due to latch contention. * InnoDB: MATCH() ... AGAINST queries that use a long string as an argument for AGAINST() could result in an error when run on an InnoDB table with a full-text search index. * InnoDB: An InnoDB full-text search failure would occur due to an “unended” token. The string and string length should be passed for string comparison. * InnoDB: In debug builds, a merge insert buffer during a page read would cause a memory access violation. * InnoDB: Truncating a memcached InnoDB table while memcached is performing DML operations would result in a serious error. * InnoDB: In sync0rw.ic, rw_lock_x_lock_func_nowait would needlessly call os_thread_get_curr_id. * InnoDB: Attempting to rename a table to a missing database would result in a serious error. more...
2014-02-13 08:49:56 +01:00
share/mysql/test/suite/sys_vars/t/innodb_buf_flush_list_now_basic.test
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/sys_vars/t/innodb_buffer_pool_dump_at_shutdown_basic.test
share/mysql/test/suite/sys_vars/t/innodb_buffer_pool_dump_now_basic.test
Changes 5.6.11: 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. 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. mysql_config_editor now supports --port and --socket options for specifying TCP/IP port number and Unix socket file name. 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. The only supported value for the innodb_mirrored_log_groups system variable is 1, so this variable is now deprecated. Setting it to 1 at startup results in a warning. Setting it to a value other than 1 at startup results in an error and the server exits. This variable will be removed in a future release.
2013-04-20 10:06:01 +02:00
share/mysql/test/suite/sys_vars/t/innodb_buffer_pool_evict_basic.test
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/sys_vars/t/innodb_buffer_pool_filename_basic-master.opt
share/mysql/test/suite/sys_vars/t/innodb_buffer_pool_filename_basic.test
share/mysql/test/suite/sys_vars/t/innodb_buffer_pool_instances_basic.test
share/mysql/test/suite/sys_vars/t/innodb_buffer_pool_load_abort_basic.test
share/mysql/test/suite/sys_vars/t/innodb_buffer_pool_load_at_startup_basic.test
share/mysql/test/suite/sys_vars/t/innodb_buffer_pool_load_now_basic.test
share/mysql/test/suite/sys_vars/t/innodb_buffer_pool_size_basic.test
share/mysql/test/suite/sys_vars/t/innodb_change_buffer_max_size_basic.test
share/mysql/test/suite/sys_vars/t/innodb_change_buffering_basic.test
share/mysql/test/suite/sys_vars/t/innodb_change_buffering_debug_basic.test
share/mysql/test/suite/sys_vars/t/innodb_checksum_algorithm_basic.test
share/mysql/test/suite/sys_vars/t/innodb_checksums_basic.test
share/mysql/test/suite/sys_vars/t/innodb_cmp_per_index_enabled_basic.test
share/mysql/test/suite/sys_vars/t/innodb_commit_concurrency_basic.test
share/mysql/test/suite/sys_vars/t/innodb_compression_failure_threshold_pct_basic.test
share/mysql/test/suite/sys_vars/t/innodb_compression_level_basic.test
share/mysql/test/suite/sys_vars/t/innodb_compression_pad_pct_max_basic.test
share/mysql/test/suite/sys_vars/t/innodb_concurrency_tickets_basic.test
share/mysql/test/suite/sys_vars/t/innodb_data_file_path_basic.test
share/mysql/test/suite/sys_vars/t/innodb_data_home_dir_basic.test
share/mysql/test/suite/sys_vars/t/innodb_disable_background_merge_basic.test
share/mysql/test/suite/sys_vars/t/innodb_disable_sort_file_cache_basic.test
share/mysql/test/suite/sys_vars/t/innodb_doublewrite_basic.test
share/mysql/test/suite/sys_vars/t/innodb_doublewrite_batch_size_basic.test
share/mysql/test/suite/sys_vars/t/innodb_fast_shutdown_basic.test
Changes 5.6.17: Functionality Added or Changed Incompatible Change: The AES_ENCRYPT() and AES_DECRYPT() functions now permit control of the block encryption mode and take an optional initialization vector argument: The new block_encryption_mode system variable controls the mode for block-based encryption algorithms. Its default value is aes-128-ecb, which signifies encryption using a key length of 128 bits and ECB mode. An optional init_vector argument provides an initialization vector for encryption modes that require it: AES_ENCRYPT(str,key_str[,init_vector]) AES_DECRYPT(crypt_str,key_str[,init_vector]) A random string of bytes to use for the initialization vector can be produced by calling the new RANDOM_BYTES() function. For more information, see Encryption and Compression Functions. These changes make statements that use AES_ENCRYPT() or AES_DECRYPT() unsafe for statement-based replication and they cannot be stored in the query cache. Queries that use RANDOM_BYTES() are unsafe for statement-based replication and cannot be stored in the query cache. Incompatible Change: The ERROR_FOR_DIVISION_BY_ZERO, NO_ZERO_DATE, and NO_ZERO_IN_DATE SQL modes now are deprecated and setting the sql_mode value to include any of them generates a warning. In MySQL 5.7, these modes do nothing. Instead, their effects are included in the effects of strict SQL mode (STRICT_ALL_TABLES or STRICT_TRANS_TABLES). The motivation for the change in MySQL 5.7 is to reduce the number of SQL modes with an effect dependent on strict mode and make them part of strict mode itself. To make advance preparation for an upgrade to MySQL 5.7, see SQL Mode Changes in MySQL 5.7. That discussion provides guidelines to assess whether your applications will be affected by the SQL mode changes in MySQL 5.7. InnoDB: MySQL now supports rebuilding regular and partitioned InnoDB tables using online DDL (ALGORITHM=INPLACE) for the following operations: OPTIMIZE TABLE ALTER TABLE ... FORCE ALTER TABLE ... ENGINE=INNODB (when run on an InnoDB table) Online DDL support reduces table rebuild time and permits concurrent DML, which helps reduce user application downtime. For additional information, see Overview of Online DDL. On Solaris, mysql_config --libs now includes -R/path/to/library so that libraries can be found at runtime. mysql_install_db provides a more informative diagnostic message when required Perl modules are missing. The IGNORE clause for ALTER TABLE is now deprecated and will be removed in a future version of MySQL. ALTER IGNORE TABLE causes problems for replication, prevents online ALTER TABLE for unique index creation, and causes problems with foreign keys (rows removed in the parent table). Bugs Fixed
2014-03-31 12:32:13 +02:00
share/mysql/test/suite/sys_vars/t/innodb_fil_make_page_dirty_debug_basic.test
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/sys_vars/t/innodb_file_format_basic.test
share/mysql/test/suite/sys_vars/t/innodb_file_format_check_basic.test
share/mysql/test/suite/sys_vars/t/innodb_file_format_max_basic-master.opt
share/mysql/test/suite/sys_vars/t/innodb_file_format_max_basic.test
share/mysql/test/suite/sys_vars/t/innodb_file_io_threads_basic.test
share/mysql/test/suite/sys_vars/t/innodb_file_per_table_basic-master.opt
share/mysql/test/suite/sys_vars/t/innodb_file_per_table_basic.test
share/mysql/test/suite/sys_vars/t/innodb_flush_log_at_timeout_basic.test
share/mysql/test/suite/sys_vars/t/innodb_flush_log_at_trx_commit_basic.test
share/mysql/test/suite/sys_vars/t/innodb_flush_method_basic.test
share/mysql/test/suite/sys_vars/t/innodb_flush_neighbors_basic.test
share/mysql/test/suite/sys_vars/t/innodb_flushing_avg_loops_basic.test
share/mysql/test/suite/sys_vars/t/innodb_force_load_corrupted_basic.test
share/mysql/test/suite/sys_vars/t/innodb_force_recovery_basic.test
share/mysql/test/suite/sys_vars/t/innodb_force_recovery_crash_basic.test
share/mysql/test/suite/sys_vars/t/innodb_ft_aux_table_basic.test
share/mysql/test/suite/sys_vars/t/innodb_ft_cache_size_basic.test
share/mysql/test/suite/sys_vars/t/innodb_ft_enable_diag_print_basic.test
share/mysql/test/suite/sys_vars/t/innodb_ft_enable_stopword_basic.test
share/mysql/test/suite/sys_vars/t/innodb_ft_max_token_size_basic.test
share/mysql/test/suite/sys_vars/t/innodb_ft_min_token_size_basic.test
share/mysql/test/suite/sys_vars/t/innodb_ft_num_word_optimize_basic.test
Changes 5.6.13: * Important Change; Replication: By default, when promoting integers from a smaller type on the master to a larger type on the slave (for example, from a SMALLINT column on the master to a BIGINT column on the slave), the promoted values are treated as though they are signed. Now in such cases it is possible to modify or override this behavior using one or both of ALL_SIGNED, ALL_UNSIGNED in the set of values specified for the slave_type_conversions server system variable. For more information, see Row-based replication: attribute promotion and demotion, as well as the description of the variable. * Previously, program options could be specified in full or as any unambiguous prefix. For example, the --compress option could be given to mysqldump as --compr, but not as --comp because the latter is ambiguous. Option prefixes now are deprecated. They can cause problems when new options are implemented for programs. A prefix that is currently unambiguous might become ambiguous in the future. If an unambiguous prefix is given, a warning now occurs to provide feedback. For example: Warning: Using unique option prefix compr instead of compress is deprecated and will be removed in a future release. Please use the full name instead. Option prefixes are no longer supported in MySQL 5.7; only full options are accepted. * The C API libmysqlclient shared-library .so files now have version 18.1.0 (up from version 18.0.0 used in MySQL 5.5). * In batch mode, mysql formatted result status messages such as “"Query OK, 1 row affected"” but did not print them. Now these messages are not formatted. * Bugs Fixed
2013-07-31 11:51:38 +02:00
share/mysql/test/suite/sys_vars/t/innodb_ft_result_cache_limit_basic.test
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/sys_vars/t/innodb_ft_server_stopword_table_basic.test
share/mysql/test/suite/sys_vars/t/innodb_ft_sort_pll_degree_basic.test
Changes 5.6.13: * Important Change; Replication: By default, when promoting integers from a smaller type on the master to a larger type on the slave (for example, from a SMALLINT column on the master to a BIGINT column on the slave), the promoted values are treated as though they are signed. Now in such cases it is possible to modify or override this behavior using one or both of ALL_SIGNED, ALL_UNSIGNED in the set of values specified for the slave_type_conversions server system variable. For more information, see Row-based replication: attribute promotion and demotion, as well as the description of the variable. * Previously, program options could be specified in full or as any unambiguous prefix. For example, the --compress option could be given to mysqldump as --compr, but not as --comp because the latter is ambiguous. Option prefixes now are deprecated. They can cause problems when new options are implemented for programs. A prefix that is currently unambiguous might become ambiguous in the future. If an unambiguous prefix is given, a warning now occurs to provide feedback. For example: Warning: Using unique option prefix compr instead of compress is deprecated and will be removed in a future release. Please use the full name instead. Option prefixes are no longer supported in MySQL 5.7; only full options are accepted. * The C API libmysqlclient shared-library .so files now have version 18.1.0 (up from version 18.0.0 used in MySQL 5.5). * In batch mode, mysql formatted result status messages such as “"Query OK, 1 row affected"” but did not print them. Now these messages are not formatted. * Bugs Fixed
2013-07-31 11:51:38 +02:00
share/mysql/test/suite/sys_vars/t/innodb_ft_total_cache_size_basic.test
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/sys_vars/t/innodb_ft_user_stopword_table_basic.test
share/mysql/test/suite/sys_vars/t/innodb_io_capacity_basic.test
share/mysql/test/suite/sys_vars/t/innodb_io_capacity_max_basic.test
share/mysql/test/suite/sys_vars/t/innodb_large_prefix_basic.test
share/mysql/test/suite/sys_vars/t/innodb_limit_optimistic_insert_debug_basic.test
share/mysql/test/suite/sys_vars/t/innodb_lock_wait_timeout_basic.test
share/mysql/test/suite/sys_vars/t/innodb_locks_unsafe_for_binlog_basic.test
share/mysql/test/suite/sys_vars/t/innodb_log_buffer_size_basic.test
Changes 5.6.12: * mysql_upgrade now verifies that the server version matches the version against which it was compiled, and exits if there is a mismatch. In addiion, a --version-check option permits specifying whether to enable version checking (the default), or disable checking if given as --skip-version-checking. * Bugs Fixed
2013-06-04 20:17:25 +02:00
share/mysql/test/suite/sys_vars/t/innodb_log_checkpoint_now_basic.test
Changes 5.6.11: 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. 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. mysql_config_editor now supports --port and --socket options for specifying TCP/IP port number and Unix socket file name. 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. The only supported value for the innodb_mirrored_log_groups system variable is 1, so this variable is now deprecated. Setting it to 1 at startup results in a warning. Setting it to a value other than 1 at startup results in an error and the server exits. This variable will be removed in a future release.
2013-04-20 10:06:01 +02:00
share/mysql/test/suite/sys_vars/t/innodb_log_compressed_pages_basic.test
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/sys_vars/t/innodb_log_file_size_basic.test
share/mysql/test/suite/sys_vars/t/innodb_log_files_in_group_basic.test
share/mysql/test/suite/sys_vars/t/innodb_log_group_home_dir_basic.test
share/mysql/test/suite/sys_vars/t/innodb_lru_scan_depth_basic.test
share/mysql/test/suite/sys_vars/t/innodb_max_dirty_pages_pct_basic.test
share/mysql/test/suite/sys_vars/t/innodb_max_dirty_pages_pct_func.test
share/mysql/test/suite/sys_vars/t/innodb_max_dirty_pages_pct_lwm_basic.test
share/mysql/test/suite/sys_vars/t/innodb_max_purge_lag_basic.test
share/mysql/test/suite/sys_vars/t/innodb_max_purge_lag_delay_basic.test
share/mysql/test/suite/sys_vars/t/innodb_mirrored_log_groups_basic.test
share/mysql/test/suite/sys_vars/t/innodb_monitor_disable_basic.test
share/mysql/test/suite/sys_vars/t/innodb_monitor_enable_basic.test
share/mysql/test/suite/sys_vars/t/innodb_monitor_reset_all_basic.test
share/mysql/test/suite/sys_vars/t/innodb_monitor_reset_basic.test
Changes 5.6.27: * InnoDB: The new innodb_numa_interleave read-only configuration option allows you to enable the NUMA interleave memory policy for allocation of the InnoDB buffer pool. When innodb_numa_interleave is enabled, the NUMA memory policy is set to MPOL_INTERLEAVE for the mysqld process. After the InnoDB buffer pool is allocated, the NUMA memory policy is set back to MPOL_DEFAULT. This option is only available on NUMA-enabled systems. * yaSSL was upgraded to version 2.3.8. * RPM .spec files were updated so that MySQL Server builds from source RPM packages will include the proper files to take advantage of operating system NUMA capabilities. This introduces a runtime dependency on libnuma.so.1. RPM and yum detect this and refuse to install if that library is not installed. * InnoDB: Reloading a table that was evicted while empty caused an AUTO_INCREMENT value to be reset. * InnoDB: Memory allocation sanity checks were added to the memcached code. * InnoDB: A memcached flush_all command raised an assertion. A function that starts a transaction was called from within assertion code. * InnoDB: A data corruption occurred on ARM64. GCC builtins did not issue the correct fences when setting or unsetting the lock word. * InnoDB: Server shutdown was delayed waiting for the purge thread to exit. To avoid this problem, the number of calls to trx_purge() was reduced, and the trx_purge() batch size was reduced to 20. * InnoDB: In READ COMMITTED mode, a REPLACE operation on a unique secondary index resulted in a constraint violation. * InnoDB: The IBUF_BITMAP_FREE bit indicated that there was more free space in the leaf page than was actually available. * InnoDB: Setting lower_case_table_names=0 on a case-insensitive file system could result in a hang condition when running an INSERT INTO ... SELECT ... FROM tbl_name operation with the wrong tbl_name letter case. An error message is now printed and the server exits when attempting to start the server with --lower_case_table_names=0 on a case-insensitive file system. * InnoDB: The server failed to start with an innodb_force_recovery setting greater than 3. InnoDB was set to read-only mode before redo logs were applied. * InnoDB: The trx_sys_read_pertable_file_format_id() function reported the wrong file format. * Partitioning: CREATE TABLE statements that used an invalid function in a subpartitioning expression did not always fail gracefully as expected. * Partitioning: Error handling for failed partitioning-related ALTER TABLE operations against non-partitioned tables was not performed correctly * Partitioning: ALTER TABLE when executed from a stored procedure did not always work correctly with tables partitioned by RANGE. * Replication: Repeatedly checking for ERR_LOCK_WAIT_TIMEOUT (as done, for example by repeatedly executing SHOW SLAVE STATUS) during a prolonged write lock on a table led to an assert. * Replication: If statement based logging was in use, when updating multiple tables in a single statement, a single transaction could be logged as two different transactions. This was due to the binary logging process not properly identifying statements which were operating over transactional tables. The fix ensures that they are correctly identified, even if such statements do not change the contents of the tables.
2015-10-03 14:46:13 +02:00
share/mysql/test/suite/sys_vars/t/innodb_numa_interleave_basic.test
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/sys_vars/t/innodb_old_blocks_pct_basic.test
share/mysql/test/suite/sys_vars/t/innodb_old_blocks_time_basic.test
share/mysql/test/suite/sys_vars/t/innodb_online_alter_log_max_size_basic.test
share/mysql/test/suite/sys_vars/t/innodb_open_files_basic.test
share/mysql/test/suite/sys_vars/t/innodb_optimize_fulltext_only_basic.test
share/mysql/test/suite/sys_vars/t/innodb_page_hash_locks_basic.test
share/mysql/test/suite/sys_vars/t/innodb_page_size_basic.test
share/mysql/test/suite/sys_vars/t/innodb_print_all_deadlocks_basic.test
share/mysql/test/suite/sys_vars/t/innodb_purge_batch_size_basic.test
share/mysql/test/suite/sys_vars/t/innodb_purge_run_now_basic.test
share/mysql/test/suite/sys_vars/t/innodb_purge_stop_now_basic.test
share/mysql/test/suite/sys_vars/t/innodb_purge_threads_basic.test
share/mysql/test/suite/sys_vars/t/innodb_random_read_ahead_basic.test
share/mysql/test/suite/sys_vars/t/innodb_read_ahead_threshold_basic.test
share/mysql/test/suite/sys_vars/t/innodb_read_io_threads_basic.test
share/mysql/test/suite/sys_vars/t/innodb_read_only_basic.test
share/mysql/test/suite/sys_vars/t/innodb_replication_delay_basic.test
share/mysql/test/suite/sys_vars/t/innodb_rollback_on_timeout_basic.test
share/mysql/test/suite/sys_vars/t/innodb_rollback_segments_basic.test
Changes 5.6.17: Functionality Added or Changed Incompatible Change: The AES_ENCRYPT() and AES_DECRYPT() functions now permit control of the block encryption mode and take an optional initialization vector argument: The new block_encryption_mode system variable controls the mode for block-based encryption algorithms. Its default value is aes-128-ecb, which signifies encryption using a key length of 128 bits and ECB mode. An optional init_vector argument provides an initialization vector for encryption modes that require it: AES_ENCRYPT(str,key_str[,init_vector]) AES_DECRYPT(crypt_str,key_str[,init_vector]) A random string of bytes to use for the initialization vector can be produced by calling the new RANDOM_BYTES() function. For more information, see Encryption and Compression Functions. These changes make statements that use AES_ENCRYPT() or AES_DECRYPT() unsafe for statement-based replication and they cannot be stored in the query cache. Queries that use RANDOM_BYTES() are unsafe for statement-based replication and cannot be stored in the query cache. Incompatible Change: The ERROR_FOR_DIVISION_BY_ZERO, NO_ZERO_DATE, and NO_ZERO_IN_DATE SQL modes now are deprecated and setting the sql_mode value to include any of them generates a warning. In MySQL 5.7, these modes do nothing. Instead, their effects are included in the effects of strict SQL mode (STRICT_ALL_TABLES or STRICT_TRANS_TABLES). The motivation for the change in MySQL 5.7 is to reduce the number of SQL modes with an effect dependent on strict mode and make them part of strict mode itself. To make advance preparation for an upgrade to MySQL 5.7, see SQL Mode Changes in MySQL 5.7. That discussion provides guidelines to assess whether your applications will be affected by the SQL mode changes in MySQL 5.7. InnoDB: MySQL now supports rebuilding regular and partitioned InnoDB tables using online DDL (ALGORITHM=INPLACE) for the following operations: OPTIMIZE TABLE ALTER TABLE ... FORCE ALTER TABLE ... ENGINE=INNODB (when run on an InnoDB table) Online DDL support reduces table rebuild time and permits concurrent DML, which helps reduce user application downtime. For additional information, see Overview of Online DDL. On Solaris, mysql_config --libs now includes -R/path/to/library so that libraries can be found at runtime. mysql_install_db provides a more informative diagnostic message when required Perl modules are missing. The IGNORE clause for ALTER TABLE is now deprecated and will be removed in a future version of MySQL. ALTER IGNORE TABLE causes problems for replication, prevents online ALTER TABLE for unique index creation, and causes problems with foreign keys (rows removed in the parent table). Bugs Fixed
2014-03-31 12:32:13 +02:00
share/mysql/test/suite/sys_vars/t/innodb_saved_page_number_debug_basic.test
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/sys_vars/t/innodb_sort_buffer_size_basic.test
share/mysql/test/suite/sys_vars/t/innodb_spin_wait_delay_basic.test
share/mysql/test/suite/sys_vars/t/innodb_stats_auto_recalc_basic.test
share/mysql/test/suite/sys_vars/t/innodb_stats_method_basic.test
share/mysql/test/suite/sys_vars/t/innodb_stats_on_metadata_basic.test
share/mysql/test/suite/sys_vars/t/innodb_stats_persistent_basic.test
share/mysql/test/suite/sys_vars/t/innodb_stats_persistent_sample_pages_basic.test
share/mysql/test/suite/sys_vars/t/innodb_stats_sample_pages_basic.test
share/mysql/test/suite/sys_vars/t/innodb_stats_transient_sample_pages_basic.test
Changes 5.6.16: Functionality Added or Changed * InnoDB: New global configuration parameters, innodb_status_output and innodb_status_output_locks, allow you to dynamically enable and disable the standard InnoDB Monitor and InnoDB Lock Monitor for periodic output. Enabling and disabling monitors for periodic output by creating and dropping specially named tables is deprecated and may be removed in a future release. * Previously, ALTER TABLE in MySQL 5.6 could alter a table such that the result had temporal columns in both 5.5 and 5.6 format. Now ALTER TABLE upgrades old temporal columns to 5.6 format for ADD COLUMN, CHANGE COLUMN, MODIFY COLUMN, ADD INDEX, and FORCE operations. This conversion cannot be done using the INPLACE algorithm, so specifying ALGORITHM=INPLACE in these cases results in an error. * CMake now supports a -DTMPDIR=dir_name option to specify the default tmpdir value. If unspecified, the value defaults to P_tmpdir in <stdio.h>. Bugs Fixed * InnoDB; Replication: Using the InnoDB memcached plugin (see InnoDB Integration with memcached) with innodb_api_enable_binlog set to 1 caused the server to leak memory. * InnoDB: A boolean mode full-text search query would result in a memory access violation during parsing. * InnoDB: When new indexes are added by an ALTER TABLE operation, instead of only saving table-level statistics and statistics for the new indexes, InnoDB would save statistics for the entire table, including the table's other indexes. This behavior slowed ALTER TABLE performance. * InnoDB: Due to a parser error, full-text search queries that include a sub-expression could return the wrong result. * InnoDB: The innochecksum tool did not use a Windows-specific API to retrieve file size information, which resulted in an incorrect error message (Error: ibdata1 cannot be found) when the MySQL 5.6 innochecksum 2GB file size limit was exceeded. innochecksum now provides support for files larger than 2GB in both MySQL 5.6 and MySQL 5.7. * InnoDB: Due to a regression introduced by the fix for Bug17371537, memory was not allocated for the default memcached engine when using the default memcached engine as the backstore for data instead of InnoDB. * InnoDB: InnoDB would report an incorrect operating system error code after failing to initialize. * InnoDB: Manipulating a table after discarding its tablespace using ALTER TABLE ... DISCARD TABLESPACE could result in a serious error. * InnoDB: Persistent optimizer statistics would cause stalls due to latch contention. * InnoDB: MATCH() ... AGAINST queries that use a long string as an argument for AGAINST() could result in an error when run on an InnoDB table with a full-text search index. * InnoDB: An InnoDB full-text search failure would occur due to an “unended” token. The string and string length should be passed for string comparison. * InnoDB: In debug builds, a merge insert buffer during a page read would cause a memory access violation. * InnoDB: Truncating a memcached InnoDB table while memcached is performing DML operations would result in a serious error. * InnoDB: In sync0rw.ic, rw_lock_x_lock_func_nowait would needlessly call os_thread_get_curr_id. * InnoDB: Attempting to rename a table to a missing database would result in a serious error. more...
2014-02-13 08:49:56 +01:00
share/mysql/test/suite/sys_vars/t/innodb_status_output_basic.test
share/mysql/test/suite/sys_vars/t/innodb_status_output_locks_basic.test
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/sys_vars/t/innodb_strict_mode_basic.test
share/mysql/test/suite/sys_vars/t/innodb_support_xa_basic.test
share/mysql/test/suite/sys_vars/t/innodb_support_xa_func.test
share/mysql/test/suite/sys_vars/t/innodb_sync_array_size_basic.test
share/mysql/test/suite/sys_vars/t/innodb_sync_spin_loops_basic.test
share/mysql/test/suite/sys_vars/t/innodb_table_locks_basic.test
share/mysql/test/suite/sys_vars/t/innodb_table_locks_func.test
share/mysql/test/suite/sys_vars/t/innodb_thread_concurrency_basic.test
share/mysql/test/suite/sys_vars/t/innodb_thread_sleep_delay_basic.test
Changes 5.6.29: * InnoDB: A new InnoDB configuration option, innodb_tmpdir, allows you to configure a separate temporary file directory for online ALTER TABLE operations. This option was introduced to help avoid tmpdir overflows that could occur as a result of large temporary files created during online ALTER TABLE operations. innodb_tmpdir is a SESSION variable and can be configured dynamically using a SET statement. * yaSSL was upgraded to version 2.3.9. This upgrade corrects an issue in which yaSSL handled only cases of zero or one leading zeros for the key agreement instead of potentially any number, which in rare cases could cause connections to fail when using DHE cipher suites. * The Valgrind function signature in mysql-test/valgrind.supp was upgraded for Valgrind 3.11. * Bugs Fixed
2016-02-28 09:58:03 +01:00
share/mysql/test/suite/sys_vars/t/innodb_tmpdir_basic.test
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/sys_vars/t/innodb_trx_purge_view_update_only_debug_basic.test
share/mysql/test/suite/sys_vars/t/innodb_trx_rseg_n_slots_debug_basic.test
share/mysql/test/suite/sys_vars/t/innodb_undo_directory_basic.test
share/mysql/test/suite/sys_vars/t/innodb_undo_logs_basic.test
share/mysql/test/suite/sys_vars/t/innodb_undo_tablespaces_basic.test
share/mysql/test/suite/sys_vars/t/innodb_use_native_aio_basic.test
share/mysql/test/suite/sys_vars/t/innodb_use_sys_malloc_basic.test
share/mysql/test/suite/sys_vars/t/innodb_version_basic.test
share/mysql/test/suite/sys_vars/t/innodb_write_io_threads_basic.test
share/mysql/test/suite/sys_vars/t/insert_id_basic.test
share/mysql/test/suite/sys_vars/t/insert_id_func.test
share/mysql/test/suite/sys_vars/t/interactive_timeout_basic.test
share/mysql/test/suite/sys_vars/t/interactive_timeout_func.test
share/mysql/test/suite/sys_vars/t/join_buffer_size_basic_32.test
share/mysql/test/suite/sys_vars/t/join_buffer_size_basic_64.test
share/mysql/test/suite/sys_vars/t/keep_files_on_create_basic.test
share/mysql/test/suite/sys_vars/t/key_buffer_size_basic.test
share/mysql/test/suite/sys_vars/t/key_buffer_size_func.test
share/mysql/test/suite/sys_vars/t/key_cache_age_threshold_basic_32.test
share/mysql/test/suite/sys_vars/t/key_cache_age_threshold_basic_64.test
share/mysql/test/suite/sys_vars/t/key_cache_block_size_basic.test
share/mysql/test/suite/sys_vars/t/key_cache_division_limit_basic.test
share/mysql/test/suite/sys_vars/t/large_files_support_basic.test
share/mysql/test/suite/sys_vars/t/large_page_size_basic.test
share/mysql/test/suite/sys_vars/t/large_pages_basic.test
share/mysql/test/suite/sys_vars/t/last_insert_id_basic.test
share/mysql/test/suite/sys_vars/t/last_insert_id_func-master.opt
share/mysql/test/suite/sys_vars/t/last_insert_id_func.test
share/mysql/test/suite/sys_vars/t/lc_messages_basic.test
share/mysql/test/suite/sys_vars/t/lc_messages_dir_basic.test
share/mysql/test/suite/sys_vars/t/lc_time_names_basic.test
share/mysql/test/suite/sys_vars/t/lc_time_names_func.test
share/mysql/test/suite/sys_vars/t/license_basic.test
share/mysql/test/suite/sys_vars/t/local_infile_basic.test
share/mysql/test/suite/sys_vars/t/local_infile_func.test
share/mysql/test/suite/sys_vars/t/lock_wait_timeout_basic.test
share/mysql/test/suite/sys_vars/t/locked_in_memory_basic.test
share/mysql/test/suite/sys_vars/t/log_bin_basename_basic.test
share/mysql/test/suite/sys_vars/t/log_bin_basic.test
share/mysql/test/suite/sys_vars/t/log_bin_index_basic.test
share/mysql/test/suite/sys_vars/t/log_bin_trust_function_creators_basic.test
share/mysql/test/suite/sys_vars/t/log_bin_trust_function_creators_func.test
share/mysql/test/suite/sys_vars/t/log_bin_use_v1_row_events_basic.test
share/mysql/test/suite/sys_vars/t/log_error_basic.test
share/mysql/test/suite/sys_vars/t/log_error_func.cnf
share/mysql/test/suite/sys_vars/t/log_error_func.test
share/mysql/test/suite/sys_vars/t/log_error_func2.cnf
share/mysql/test/suite/sys_vars/t/log_error_func2.test
share/mysql/test/suite/sys_vars/t/log_error_func3.test
share/mysql/test/suite/sys_vars/t/log_output_basic.test
share/mysql/test/suite/sys_vars/t/log_output_func.test
share/mysql/test/suite/sys_vars/t/log_queries_not_using_indexes_basic.test
share/mysql/test/suite/sys_vars/t/log_slave_updates_basic.test
Changes 5.6.11: 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. 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. mysql_config_editor now supports --port and --socket options for specifying TCP/IP port number and Unix socket file name. 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. The only supported value for the innodb_mirrored_log_groups system variable is 1, so this variable is now deprecated. Setting it to 1 at startup results in a warning. Setting it to a value other than 1 at startup results in an error and the server exits. This variable will be removed in a future release.
2013-04-20 10:06:01 +02:00
share/mysql/test/suite/sys_vars/t/log_slow_admin_statements_basic.test
share/mysql/test/suite/sys_vars/t/log_slow_admin_statements_func.test
share/mysql/test/suite/sys_vars/t/log_slow_slave_statements_basic.test
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/sys_vars/t/log_throttle_queries_not_using_indexes_basic.test
share/mysql/test/suite/sys_vars/t/log_warnings_basic_32.test
share/mysql/test/suite/sys_vars/t/log_warnings_basic_64.test
share/mysql/test/suite/sys_vars/t/long_query_time_basic.test
share/mysql/test/suite/sys_vars/t/low_priority_updates_basic.test
share/mysql/test/suite/sys_vars/t/lower_case_file_system_basic.test
share/mysql/test/suite/sys_vars/t/lower_case_table_names_basic.test
share/mysql/test/suite/sys_vars/t/master_info_repository_basic.test
share/mysql/test/suite/sys_vars/t/master_verify_checksum_basic.test
share/mysql/test/suite/sys_vars/t/max_allowed_packet_basic.test
share/mysql/test/suite/sys_vars/t/max_allowed_packet_func.test
share/mysql/test/suite/sys_vars/t/max_binlog_cache_size_basic.test
share/mysql/test/suite/sys_vars/t/max_binlog_size_basic.test
share/mysql/test/suite/sys_vars/t/max_binlog_stmt_cache_size_basic.test
share/mysql/test/suite/sys_vars/t/max_connect_errors_basic_32.test
share/mysql/test/suite/sys_vars/t/max_connect_errors_basic_64.test
share/mysql/test/suite/sys_vars/t/max_connections_basic.test
share/mysql/test/suite/sys_vars/t/max_delayed_threads_basic.test
Changes 5.6.24: * CMake support was updated to handle CMake version 3.1. * The server now includes its version number when it writes the initial “starting” message to the error log, to make it easier to tell which server instance error log output applies to. This value is the same as that available from the version system variable. * ALTER TABLE did not take advantage of fast alterations that might otherwise apply to the operation to be performed, if the table contained temporal columns found to be in pre-5.6.4 format (TIME, DATETIME, and TIMESTAMP columns without support for fractional seconds precision). * Statement digesting as done previously by the Performance Schema is now done at the SQL level regardless of whether the Performance Schema is compiled in and is available to other aspects of server operation that could benefit from it. The default space available for digesting is 1024 bytes, but can be changed at server startup using the max_digest_length system variable. * Bug fixes.
2015-04-08 12:38:48 +02:00
share/mysql/test/suite/sys_vars/t/max_digest_length_basic-master.opt
share/mysql/test/suite/sys_vars/t/max_digest_length_basic.test
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/sys_vars/t/max_error_count_basic.test
share/mysql/test/suite/sys_vars/t/max_heap_table_size_basic.test
share/mysql/test/suite/sys_vars/t/max_insert_delayed_threads_basic.test
share/mysql/test/suite/sys_vars/t/max_join_size_basic.test
share/mysql/test/suite/sys_vars/t/max_join_size_func.test
share/mysql/test/suite/sys_vars/t/max_length_for_sort_data_basic.test
share/mysql/test/suite/sys_vars/t/max_prepared_stmt_count_basic.test
share/mysql/test/suite/sys_vars/t/max_prepared_stmt_count_func.test
share/mysql/test/suite/sys_vars/t/max_relay_log_size_basic.test
share/mysql/test/suite/sys_vars/t/max_seeks_for_key_basic_32.test
share/mysql/test/suite/sys_vars/t/max_seeks_for_key_basic_64.test
share/mysql/test/suite/sys_vars/t/max_seeks_for_key_func.test
share/mysql/test/suite/sys_vars/t/max_sort_length_basic.test
share/mysql/test/suite/sys_vars/t/max_sort_length_func.test
share/mysql/test/suite/sys_vars/t/max_sp_recursion_depth_basic.test
share/mysql/test/suite/sys_vars/t/max_sp_recursion_depth_func-master.opt
share/mysql/test/suite/sys_vars/t/max_sp_recursion_depth_func.test
share/mysql/test/suite/sys_vars/t/max_tmp_tables_basic_32.test
share/mysql/test/suite/sys_vars/t/max_tmp_tables_basic_64.test
share/mysql/test/suite/sys_vars/t/max_user_connections_basic.test
share/mysql/test/suite/sys_vars/t/max_user_connections_func.test
share/mysql/test/suite/sys_vars/t/max_write_lock_count_basic_32.test
share/mysql/test/suite/sys_vars/t/max_write_lock_count_basic_64.test
share/mysql/test/suite/sys_vars/t/maximum_basic-master.opt
share/mysql/test/suite/sys_vars/t/maximum_basic.test
share/mysql/test/suite/sys_vars/t/metadata_locks_cache_size_basic-master.opt
share/mysql/test/suite/sys_vars/t/metadata_locks_cache_size_basic.test
share/mysql/test/suite/sys_vars/t/metadata_locks_hash_instances_basic.test
share/mysql/test/suite/sys_vars/t/min_examined_row_limit_basic_32.test
share/mysql/test/suite/sys_vars/t/min_examined_row_limit_basic_64.test
share/mysql/test/suite/sys_vars/t/multi_range_count_basic_32.test
share/mysql/test/suite/sys_vars/t/multi_range_count_basic_64.test
share/mysql/test/suite/sys_vars/t/myisam_data_pointer_size_basic.test
share/mysql/test/suite/sys_vars/t/myisam_data_pointer_size_func.test
share/mysql/test/suite/sys_vars/t/myisam_max_sort_file_size_basic_32.test
share/mysql/test/suite/sys_vars/t/myisam_max_sort_file_size_basic_64.test
share/mysql/test/suite/sys_vars/t/myisam_mmap_size_basic.test
share/mysql/test/suite/sys_vars/t/myisam_recover_options_basic.test
share/mysql/test/suite/sys_vars/t/myisam_repair_threads_basic_32.test
share/mysql/test/suite/sys_vars/t/myisam_repair_threads_basic_64.test
share/mysql/test/suite/sys_vars/t/myisam_sort_buffer_size_basic_32.test
share/mysql/test/suite/sys_vars/t/myisam_sort_buffer_size_basic_64.test
share/mysql/test/suite/sys_vars/t/myisam_stats_method_basic.test
share/mysql/test/suite/sys_vars/t/myisam_stats_method_func.test
share/mysql/test/suite/sys_vars/t/myisam_use_mmap_basic.test
share/mysql/test/suite/sys_vars/t/named_pipe_basic.test
share/mysql/test/suite/sys_vars/t/net_buffer_length_basic.test
share/mysql/test/suite/sys_vars/t/net_read_timeout_basic.test
share/mysql/test/suite/sys_vars/t/net_retry_count_basic_32.test
share/mysql/test/suite/sys_vars/t/net_retry_count_basic_64.test
share/mysql/test/suite/sys_vars/t/net_write_timeout_basic.test
share/mysql/test/suite/sys_vars/t/new_basic.test
share/mysql/test/suite/sys_vars/t/old_alter_table_basic.test
share/mysql/test/suite/sys_vars/t/old_basic.test
share/mysql/test/suite/sys_vars/t/old_passwords_basic.test
share/mysql/test/suite/sys_vars/t/old_passwords_func.test
share/mysql/test/suite/sys_vars/t/open_files_limit_basic.test
share/mysql/test/suite/sys_vars/t/optimizer_prune_level_basic.test
share/mysql/test/suite/sys_vars/t/optimizer_search_depth_basic.test
share/mysql/test/suite/sys_vars/t/optimizer_switch_basic.test
share/mysql/test/suite/sys_vars/t/optimizer_trace_basic.test
share/mysql/test/suite/sys_vars/t/optimizer_trace_features_basic.test
share/mysql/test/suite/sys_vars/t/optimizer_trace_limit_basic.test
share/mysql/test/suite/sys_vars/t/optimizer_trace_max_mem_size_basic.test
share/mysql/test/suite/sys_vars/t/optimizer_trace_offset_basic.test
share/mysql/test/suite/sys_vars/t/optimizer_trace_offset_max-master.opt
share/mysql/test/suite/sys_vars/t/optimizer_trace_offset_max.test
share/mysql/test/suite/sys_vars/t/performance_schema_basic-master.opt
share/mysql/test/suite/sys_vars/t/performance_schema_basic.test
share/mysql/test/suite/sys_vars/t/pfs_accounts_size_basic-master.opt
share/mysql/test/suite/sys_vars/t/pfs_accounts_size_basic.test
share/mysql/test/suite/sys_vars/t/pfs_digests_size_basic-master.opt
share/mysql/test/suite/sys_vars/t/pfs_digests_size_basic.test
share/mysql/test/suite/sys_vars/t/pfs_events_stages_h_size_basic-master.opt
share/mysql/test/suite/sys_vars/t/pfs_events_stages_h_size_basic.test
share/mysql/test/suite/sys_vars/t/pfs_events_stages_hl_size_basic-master.opt
share/mysql/test/suite/sys_vars/t/pfs_events_stages_hl_size_basic.test
share/mysql/test/suite/sys_vars/t/pfs_events_statements_h_size_basic-master.opt
share/mysql/test/suite/sys_vars/t/pfs_events_statements_h_size_basic.test
share/mysql/test/suite/sys_vars/t/pfs_events_statements_hl_size_basic-master.opt
share/mysql/test/suite/sys_vars/t/pfs_events_statements_hl_size_basic.test
share/mysql/test/suite/sys_vars/t/pfs_events_waits_h_size_basic-master.opt
share/mysql/test/suite/sys_vars/t/pfs_events_waits_h_size_basic.test
share/mysql/test/suite/sys_vars/t/pfs_events_waits_hl_size_basic-master.opt
share/mysql/test/suite/sys_vars/t/pfs_events_waits_hl_size_basic.test
share/mysql/test/suite/sys_vars/t/pfs_hosts_size_basic-master.opt
share/mysql/test/suite/sys_vars/t/pfs_hosts_size_basic.test
share/mysql/test/suite/sys_vars/t/pfs_max_cond_classes_basic-master.opt
share/mysql/test/suite/sys_vars/t/pfs_max_cond_classes_basic.test
share/mysql/test/suite/sys_vars/t/pfs_max_cond_instances_basic-master.opt
share/mysql/test/suite/sys_vars/t/pfs_max_cond_instances_basic.test
Changes 5.6.26: * Security Fix: Due to the LogJam issue (https://weakdh.org/), OpenSSL has changed the Diffie-Hellman key length parameters for openssl-1.0.1n and up. * Replication: When using a multi-threaded slave, each worker thread has its own queue of transactions to process. In previous MySQL versions, STOP SLAVE waited for all workers to process their entire queue. This logic has been changed so that STOP SLAVE first finds the newest transaction that was committed by any worker thread. Then, it waits for all workers to complete transactions older than that. Newer transactions are not processed. The new logic allows STOP SLAVE to complete faster in case some worker queues contain multiple transactions. * Previously, the max_digest_length system variable controlled the maximum digest length for all server functions that computed statement digests. However, whereas the Performance Schema may need to maintain many digest values, other server functions such as MySQL Enterprise Firewall need only one digest per session. Increasing the max_digest_length value has little impact on total memory requirements for those functions, but can increase Performance Schema memory requirements significantly. To enable configuring digest length separately for the Performance Schema, its digest length is now controlled by the new performance_schema_max_digest_length system variable. * Previously, changes to the validate_password plugin dictionary file (named by the validate_password_dictionary_file system variable) while the server was running required a restart for the server to recognize the changes. Now validate_password_dictionary_file can be set at runtime and assigning a value causes the named file to be read without a restart. In addition, two new status variables are available. validate_password_dictionary_file_last_parsed indicates when the dictionary file was last read, and validate_password_dictionary_file_words_count indicates how many words it contains. * Bugs fixed
2015-07-30 16:39:18 +02:00
share/mysql/test/suite/sys_vars/t/pfs_max_digest_length_basic-master.opt
share/mysql/test/suite/sys_vars/t/pfs_max_digest_length_basic.test
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/sys_vars/t/pfs_max_file_classes_basic-master.opt
share/mysql/test/suite/sys_vars/t/pfs_max_file_classes_basic.test
share/mysql/test/suite/sys_vars/t/pfs_max_file_handles_basic-master.opt
share/mysql/test/suite/sys_vars/t/pfs_max_file_handles_basic.test
share/mysql/test/suite/sys_vars/t/pfs_max_file_instances_basic-master.opt
share/mysql/test/suite/sys_vars/t/pfs_max_file_instances_basic.test
share/mysql/test/suite/sys_vars/t/pfs_max_mutex_classes_basic-master.opt
share/mysql/test/suite/sys_vars/t/pfs_max_mutex_classes_basic.test
share/mysql/test/suite/sys_vars/t/pfs_max_mutex_instances_basic-master.opt
share/mysql/test/suite/sys_vars/t/pfs_max_mutex_instances_basic.test
share/mysql/test/suite/sys_vars/t/pfs_max_rwlock_classes_basic-master.opt
share/mysql/test/suite/sys_vars/t/pfs_max_rwlock_classes_basic.test
share/mysql/test/suite/sys_vars/t/pfs_max_rwlock_instances_basic-master.opt
share/mysql/test/suite/sys_vars/t/pfs_max_rwlock_instances_basic.test
share/mysql/test/suite/sys_vars/t/pfs_max_socket_classes_basic-master.opt
share/mysql/test/suite/sys_vars/t/pfs_max_socket_classes_basic.test
share/mysql/test/suite/sys_vars/t/pfs_max_socket_instances_basic-master.opt
share/mysql/test/suite/sys_vars/t/pfs_max_socket_instances_basic.test
share/mysql/test/suite/sys_vars/t/pfs_max_stage_classes_basic-master.opt
share/mysql/test/suite/sys_vars/t/pfs_max_stage_classes_basic.test
share/mysql/test/suite/sys_vars/t/pfs_max_statement_classes_basic-master.opt
share/mysql/test/suite/sys_vars/t/pfs_max_statement_classes_basic.test
share/mysql/test/suite/sys_vars/t/pfs_max_table_handles_basic-master.opt
share/mysql/test/suite/sys_vars/t/pfs_max_table_handles_basic.test
share/mysql/test/suite/sys_vars/t/pfs_max_table_instances_basic-master.opt
share/mysql/test/suite/sys_vars/t/pfs_max_table_instances_basic.test
share/mysql/test/suite/sys_vars/t/pfs_max_thread_classes_basic-master.opt
share/mysql/test/suite/sys_vars/t/pfs_max_thread_classes_basic.test
share/mysql/test/suite/sys_vars/t/pfs_max_thread_instances_basic-master.opt
share/mysql/test/suite/sys_vars/t/pfs_max_thread_instances_basic.test
share/mysql/test/suite/sys_vars/t/pfs_session_connect_attrs_size_basic-master.opt
share/mysql/test/suite/sys_vars/t/pfs_session_connect_attrs_size_basic.test
share/mysql/test/suite/sys_vars/t/pfs_setup_actors_size_basic-master.opt
share/mysql/test/suite/sys_vars/t/pfs_setup_actors_size_basic.test
share/mysql/test/suite/sys_vars/t/pfs_setup_objects_size_basic-master.opt
share/mysql/test/suite/sys_vars/t/pfs_setup_objects_size_basic.test
share/mysql/test/suite/sys_vars/t/pfs_users_size_basic-master.opt
share/mysql/test/suite/sys_vars/t/pfs_users_size_basic.test
share/mysql/test/suite/sys_vars/t/pid_file_basic.test
share/mysql/test/suite/sys_vars/t/plugin_dir_basic-master.opt
share/mysql/test/suite/sys_vars/t/plugin_dir_basic.test
share/mysql/test/suite/sys_vars/t/port_basic.test
share/mysql/test/suite/sys_vars/t/preload_buffer_size_basic.test
share/mysql/test/suite/sys_vars/t/profiling_basic.test
share/mysql/test/suite/sys_vars/t/profiling_h_size_basic.test
share/mysql/test/suite/sys_vars/t/protocol_version_basic.test
share/mysql/test/suite/sys_vars/t/proxy_user_basic.test
share/mysql/test/suite/sys_vars/t/pseudo_slave_mode_basic.test
share/mysql/test/suite/sys_vars/t/pseudo_thread_id_basic.test
share/mysql/test/suite/sys_vars/t/query_alloc_block_size_basic_32.test
share/mysql/test/suite/sys_vars/t/query_alloc_block_size_basic_64.test
share/mysql/test/suite/sys_vars/t/query_cache_limit_basic_32.test
share/mysql/test/suite/sys_vars/t/query_cache_limit_basic_64.test
share/mysql/test/suite/sys_vars/t/query_cache_limit_func-master.opt
share/mysql/test/suite/sys_vars/t/query_cache_limit_func.test
share/mysql/test/suite/sys_vars/t/query_cache_min_res_unit_basic_32.test
share/mysql/test/suite/sys_vars/t/query_cache_min_res_unit_basic_64.test
share/mysql/test/suite/sys_vars/t/query_cache_size_basic_32.test
share/mysql/test/suite/sys_vars/t/query_cache_size_basic_64.test
share/mysql/test/suite/sys_vars/t/query_cache_type_basic-master.opt
share/mysql/test/suite/sys_vars/t/query_cache_type_basic.test
share/mysql/test/suite/sys_vars/t/query_cache_type_func-master.opt
share/mysql/test/suite/sys_vars/t/query_cache_type_func.test
share/mysql/test/suite/sys_vars/t/query_cache_wlock_invalidate_basic.test
share/mysql/test/suite/sys_vars/t/query_cache_wlock_invalidate_func-master.opt
share/mysql/test/suite/sys_vars/t/query_cache_wlock_invalidate_func.test
share/mysql/test/suite/sys_vars/t/query_prealloc_size_basic.test
share/mysql/test/suite/sys_vars/t/query_prealloc_size_func.test
share/mysql/test/suite/sys_vars/t/rand_seed1_basic.test
share/mysql/test/suite/sys_vars/t/rand_seed2_basic.test
share/mysql/test/suite/sys_vars/t/range_alloc_block_size_basic_32.test
share/mysql/test/suite/sys_vars/t/range_alloc_block_size_basic_64.test
share/mysql/test/suite/sys_vars/t/read_buffer_size_basic.test
share/mysql/test/suite/sys_vars/t/read_only_basic.test
share/mysql/test/suite/sys_vars/t/read_only_func.test
share/mysql/test/suite/sys_vars/t/read_rnd_buffer_size_basic.test
share/mysql/test/suite/sys_vars/t/relay_log_basename_basic.test
share/mysql/test/suite/sys_vars/t/relay_log_basic.test
share/mysql/test/suite/sys_vars/t/relay_log_index_basic.test
share/mysql/test/suite/sys_vars/t/relay_log_info_file_basic.test
share/mysql/test/suite/sys_vars/t/relay_log_info_repository_basic.test
share/mysql/test/suite/sys_vars/t/relay_log_purge_basic.test
share/mysql/test/suite/sys_vars/t/relay_log_recovery_basic.test
share/mysql/test/suite/sys_vars/t/relay_log_space_limit_basic.test
share/mysql/test/suite/sys_vars/t/report_host_basic.test
share/mysql/test/suite/sys_vars/t/report_password_basic.test
share/mysql/test/suite/sys_vars/t/report_port_basic.test
share/mysql/test/suite/sys_vars/t/report_user_basic.test
share/mysql/test/suite/sys_vars/t/rpl_init_slave_func.test
share/mysql/test/suite/sys_vars/t/rpl_max_binlog_size_func-master.opt
share/mysql/test/suite/sys_vars/t/rpl_max_binlog_size_func.test
share/mysql/test/suite/sys_vars/t/rpl_semi_sync_master_enabled_basic-master.opt
share/mysql/test/suite/sys_vars/t/rpl_semi_sync_master_enabled_basic.test
share/mysql/test/suite/sys_vars/t/rpl_semi_sync_master_timeout_basic-master.opt
share/mysql/test/suite/sys_vars/t/rpl_semi_sync_master_timeout_basic.test
share/mysql/test/suite/sys_vars/t/rpl_semi_sync_master_trace_level_basic-master.opt
share/mysql/test/suite/sys_vars/t/rpl_semi_sync_master_trace_level_basic.test
share/mysql/test/suite/sys_vars/t/rpl_semi_sync_master_wait_no_slave_basic-master.opt
share/mysql/test/suite/sys_vars/t/rpl_semi_sync_master_wait_no_slave_basic.test
share/mysql/test/suite/sys_vars/t/rpl_semi_sync_slave_enabled_basic-master.opt
share/mysql/test/suite/sys_vars/t/rpl_semi_sync_slave_enabled_basic.test
share/mysql/test/suite/sys_vars/t/rpl_semi_sync_slave_trace_level_basic-master.opt
share/mysql/test/suite/sys_vars/t/rpl_semi_sync_slave_trace_level_basic.test
Changes 5.6.13: * Important Change; Replication: By default, when promoting integers from a smaller type on the master to a larger type on the slave (for example, from a SMALLINT column on the master to a BIGINT column on the slave), the promoted values are treated as though they are signed. Now in such cases it is possible to modify or override this behavior using one or both of ALL_SIGNED, ALL_UNSIGNED in the set of values specified for the slave_type_conversions server system variable. For more information, see Row-based replication: attribute promotion and demotion, as well as the description of the variable. * Previously, program options could be specified in full or as any unambiguous prefix. For example, the --compress option could be given to mysqldump as --compr, but not as --comp because the latter is ambiguous. Option prefixes now are deprecated. They can cause problems when new options are implemented for programs. A prefix that is currently unambiguous might become ambiguous in the future. If an unambiguous prefix is given, a warning now occurs to provide feedback. For example: Warning: Using unique option prefix compr instead of compress is deprecated and will be removed in a future release. Please use the full name instead. Option prefixes are no longer supported in MySQL 5.7; only full options are accepted. * The C API libmysqlclient shared-library .so files now have version 18.1.0 (up from version 18.0.0 used in MySQL 5.5). * In batch mode, mysql formatted result status messages such as “"Query OK, 1 row affected"” but did not print them. Now these messages are not formatted. * Bugs Fixed
2013-07-31 11:51:38 +02:00
share/mysql/test/suite/sys_vars/t/rpl_stop_slave_timeout_basic.test
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/sys_vars/t/secure_auth_basic.test
share/mysql/test/suite/sys_vars/t/secure_auth_func-master.opt
share/mysql/test/suite/sys_vars/t/secure_auth_func.test
share/mysql/test/suite/sys_vars/t/secure_file_priv-master.opt
share/mysql/test/suite/sys_vars/t/secure_file_priv.test
share/mysql/test/suite/sys_vars/t/secure_file_priv2-master.opt
share/mysql/test/suite/sys_vars/t/secure_file_priv2.test
share/mysql/test/suite/sys_vars/t/secure_file_priv_basic.test
share/mysql/test/suite/sys_vars/t/server_id_basic.test
share/mysql/test/suite/sys_vars/t/server_id_bits_basic.test
share/mysql/test/suite/sys_vars/t/server_uuid_basic.test
share/mysql/test/suite/sys_vars/t/sha256_password_private_key_path_basic.test
share/mysql/test/suite/sys_vars/t/sha256_password_public_key_path_basic.test
share/mysql/test/suite/sys_vars/t/shared_memory_base_name_basic.test
share/mysql/test/suite/sys_vars/t/shared_memory_basic.test
Changes 5.6.24: * CMake support was updated to handle CMake version 3.1. * The server now includes its version number when it writes the initial “starting” message to the error log, to make it easier to tell which server instance error log output applies to. This value is the same as that available from the version system variable. * ALTER TABLE did not take advantage of fast alterations that might otherwise apply to the operation to be performed, if the table contained temporal columns found to be in pre-5.6.4 format (TIME, DATETIME, and TIMESTAMP columns without support for fractional seconds precision). * Statement digesting as done previously by the Performance Schema is now done at the SQL level regardless of whether the Performance Schema is compiled in and is available to other aspects of server operation that could benefit from it. The default space available for digesting is 1024 bytes, but can be changed at server startup using the max_digest_length system variable. * Bug fixes.
2015-04-08 12:38:48 +02:00
share/mysql/test/suite/sys_vars/t/show_old_temporals_basic.test
Changes 5.6.21: The --skip-innodb option is now deprecated and its use results in a warning. It will be removed in a future MySQL release. This also applies to its synonyms (--innodb=OFF, --disable-innodb, and so forth). MySQL Enterprise Edition now includes a set of encryption functions based on the OpenSSL library that expose OpenSSL capabilities at the SQL level. Replication: The new variable simplified_binlog_gtid_recovery can be used to change the way binary log files are searched for previous GTIDs during recovery, speeding up the process when a large number of binary log files exist. Internally, spatial data types such as Geometry are represented as BLOB values, so when invoked with the --hex-blob option, mysqldump now displays spatial values in hex. Bugs Fixed...
2014-10-01 10:34:23 +02:00
share/mysql/test/suite/sys_vars/t/simplified_binlog_gtid_recovery_basic.test
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/sys_vars/t/skip_external_locking_basic.test
share/mysql/test/suite/sys_vars/t/skip_name_resolve_basic-master.opt
share/mysql/test/suite/sys_vars/t/skip_name_resolve_basic.test
share/mysql/test/suite/sys_vars/t/skip_networking_basic.test
share/mysql/test/suite/sys_vars/t/skip_show_database_basic.test
share/mysql/test/suite/sys_vars/t/slave_allow_batching_basic.test
share/mysql/test/suite/sys_vars/t/slave_checkpoint_group_basic.test
share/mysql/test/suite/sys_vars/t/slave_checkpoint_period_basic.test
share/mysql/test/suite/sys_vars/t/slave_compressed_protocol_basic.test
share/mysql/test/suite/sys_vars/t/slave_exec_mode_basic.test
share/mysql/test/suite/sys_vars/t/slave_load_tmpdir_basic.test
share/mysql/test/suite/sys_vars/t/slave_max_allowed_packet_basic.test
share/mysql/test/suite/sys_vars/t/slave_net_timeout_basic.test
share/mysql/test/suite/sys_vars/t/slave_parallel_workers_basic.test
share/mysql/test/suite/sys_vars/t/slave_pending_jobs_size_max_basic.test
share/mysql/test/suite/sys_vars/t/slave_rows_search_algorithms_basic.test
share/mysql/test/suite/sys_vars/t/slave_skip_errors_basic.test
share/mysql/test/suite/sys_vars/t/slave_sql_verify_checksum_basic.test
share/mysql/test/suite/sys_vars/t/slave_transaction_retries_basic_32.test
share/mysql/test/suite/sys_vars/t/slave_transaction_retries_basic_64.test
share/mysql/test/suite/sys_vars/t/slave_type_conversions_basic.test
share/mysql/test/suite/sys_vars/t/slow_launch_time_basic.test
share/mysql/test/suite/sys_vars/t/slow_launch_time_func-master.opt
share/mysql/test/suite/sys_vars/t/slow_launch_time_func.test
share/mysql/test/suite/sys_vars/t/slow_query_log_basic.test
share/mysql/test/suite/sys_vars/t/slow_query_log_file_basic-master.opt
share/mysql/test/suite/sys_vars/t/slow_query_log_file_basic.test
share/mysql/test/suite/sys_vars/t/slow_query_log_file_func-master.opt
share/mysql/test/suite/sys_vars/t/slow_query_log_file_func.test
share/mysql/test/suite/sys_vars/t/slow_query_log_func.test
share/mysql/test/suite/sys_vars/t/socket_basic.test
share/mysql/test/suite/sys_vars/t/sort_buffer_size_basic_32.test
share/mysql/test/suite/sys_vars/t/sort_buffer_size_basic_64.test
share/mysql/test/suite/sys_vars/t/sql_auto_is_null_basic.test
share/mysql/test/suite/sys_vars/t/sql_big_selects_basic.test
share/mysql/test/suite/sys_vars/t/sql_big_selects_func.test
share/mysql/test/suite/sys_vars/t/sql_buffer_result_basic.test
share/mysql/test/suite/sys_vars/t/sql_buffer_result_func.test
share/mysql/test/suite/sys_vars/t/sql_log_bin_basic.test
share/mysql/test/suite/sys_vars/t/sql_log_off_basic.test
share/mysql/test/suite/sys_vars/t/sql_log_off_func.test
share/mysql/test/suite/sys_vars/t/sql_low_priority_updates_func.test
share/mysql/test/suite/sys_vars/t/sql_mode_basic.test
share/mysql/test/suite/sys_vars/t/sql_mode_func.test
share/mysql/test/suite/sys_vars/t/sql_notes_basic.test
share/mysql/test/suite/sys_vars/t/sql_notes_func.test
share/mysql/test/suite/sys_vars/t/sql_quote_show_create_basic.test
share/mysql/test/suite/sys_vars/t/sql_quote_show_create_func.test
share/mysql/test/suite/sys_vars/t/sql_safe_updates_basic.test
share/mysql/test/suite/sys_vars/t/sql_safe_updates_func.test
share/mysql/test/suite/sys_vars/t/sql_select_limit_basic.test
share/mysql/test/suite/sys_vars/t/sql_select_limit_func.test
share/mysql/test/suite/sys_vars/t/sql_slave_skip_counter_basic.test
share/mysql/test/suite/sys_vars/t/sql_warnings_basic.test
share/mysql/test/suite/sys_vars/t/sql_warnings_func.test
share/mysql/test/suite/sys_vars/t/ssl_ca_basic.test
share/mysql/test/suite/sys_vars/t/ssl_capath_basic.test
share/mysql/test/suite/sys_vars/t/ssl_cert_basic.test
share/mysql/test/suite/sys_vars/t/ssl_cipher_basic.test
share/mysql/test/suite/sys_vars/t/ssl_crl_basic.test
share/mysql/test/suite/sys_vars/t/ssl_crlpath_basic.test
share/mysql/test/suite/sys_vars/t/ssl_key_basic.test
share/mysql/test/suite/sys_vars/t/storage_engine_basic-master.opt
share/mysql/test/suite/sys_vars/t/storage_engine_basic.test
share/mysql/test/suite/sys_vars/t/stored_program_cache_basic.test
share/mysql/test/suite/sys_vars/t/sync_binlog_basic.test
share/mysql/test/suite/sys_vars/t/sync_frm_basic.test
share/mysql/test/suite/sys_vars/t/sync_master_info_basic.test
share/mysql/test/suite/sys_vars/t/sync_relay_log_basic.test
share/mysql/test/suite/sys_vars/t/sync_relay_log_info_basic.test
share/mysql/test/suite/sys_vars/t/system_time_zone_basic.test
share/mysql/test/suite/sys_vars/t/table_definition_cache_basic.test
share/mysql/test/suite/sys_vars/t/table_open_cache_basic.test
share/mysql/test/suite/sys_vars/t/table_open_cache_instances_basic.test
share/mysql/test/suite/sys_vars/t/thread_cache_size_basic.test
share/mysql/test/suite/sys_vars/t/thread_cache_size_func-master.opt
share/mysql/test/suite/sys_vars/t/thread_cache_size_func.test
share/mysql/test/suite/sys_vars/t/thread_concurrency_basic.test
share/mysql/test/suite/sys_vars/t/thread_handling_basic.test
share/mysql/test/suite/sys_vars/t/thread_stack_basic.test
share/mysql/test/suite/sys_vars/t/time_format_basic.test
share/mysql/test/suite/sys_vars/t/time_zone_basic.test
share/mysql/test/suite/sys_vars/t/time_zone_func.test
share/mysql/test/suite/sys_vars/t/timed_mutexes_basic.test
share/mysql/test/suite/sys_vars/t/timestamp_basic.test
share/mysql/test/suite/sys_vars/t/timestamp_func.test
share/mysql/test/suite/sys_vars/t/timestamp_sysdate_is_now_func-master.opt
share/mysql/test/suite/sys_vars/t/timestamp_sysdate_is_now_func.test
share/mysql/test/suite/sys_vars/t/tmp_table_size_basic.test
share/mysql/test/suite/sys_vars/t/tmpdir_basic.test
Changes 5.6.24: * CMake support was updated to handle CMake version 3.1. * The server now includes its version number when it writes the initial “starting” message to the error log, to make it easier to tell which server instance error log output applies to. This value is the same as that available from the version system variable. * ALTER TABLE did not take advantage of fast alterations that might otherwise apply to the operation to be performed, if the table contained temporal columns found to be in pre-5.6.4 format (TIME, DATETIME, and TIMESTAMP columns without support for fractional seconds precision). * Statement digesting as done previously by the Performance Schema is now done at the SQL level regardless of whether the Performance Schema is compiled in and is available to other aspects of server operation that could benefit from it. The default space available for digesting is 1024 bytes, but can be changed at server startup using the max_digest_length system variable. * Bug fixes.
2015-04-08 12:38:48 +02:00
share/mysql/test/suite/sys_vars/t/transaction_alloc_block_size_basic.test
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/sys_vars/t/transaction_allow_batching_basic.test
Changes 5.6.24: * CMake support was updated to handle CMake version 3.1. * The server now includes its version number when it writes the initial “starting” message to the error log, to make it easier to tell which server instance error log output applies to. This value is the same as that available from the version system variable. * ALTER TABLE did not take advantage of fast alterations that might otherwise apply to the operation to be performed, if the table contained temporal columns found to be in pre-5.6.4 format (TIME, DATETIME, and TIMESTAMP columns without support for fractional seconds precision). * Statement digesting as done previously by the Performance Schema is now done at the SQL level regardless of whether the Performance Schema is compiled in and is available to other aspects of server operation that could benefit from it. The default space available for digesting is 1024 bytes, but can be changed at server startup using the max_digest_length system variable. * Bug fixes.
2015-04-08 12:38:48 +02:00
share/mysql/test/suite/sys_vars/t/transaction_prealloc_size_basic.test
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/suite/sys_vars/t/tx_isolation_basic.test
share/mysql/test/suite/sys_vars/t/tx_isolation_func-master.opt
share/mysql/test/suite/sys_vars/t/tx_isolation_func.test
share/mysql/test/suite/sys_vars/t/tx_read_only_basic.test
share/mysql/test/suite/sys_vars/t/unique_checks_basic.test
share/mysql/test/suite/sys_vars/t/updatable_views_with_limit_basic.test
share/mysql/test/suite/sys_vars/t/updatable_views_with_limit_func.test
share/mysql/test/suite/sys_vars/t/version_basic.test
share/mysql/test/suite/sys_vars/t/version_comment_basic.test
share/mysql/test/suite/sys_vars/t/version_compile_machine_basic.test
share/mysql/test/suite/sys_vars/t/version_compile_os_basic.test
share/mysql/test/suite/sys_vars/t/wait_timeout_basic.test
share/mysql/test/suite/sys_vars/t/wait_timeout_func.test
share/mysql/test/suite/sys_vars/t/warning_count_basic.test
share/mysql/test/t/1st.test
share/mysql/test/t/alias.test
share/mysql/test/t/almost_full.test
share/mysql/test/t/alter_table-big.test
share/mysql/test/t/alter_table.test
share/mysql/test/t/analyze.test
share/mysql/test/t/ansi.test
share/mysql/test/t/archive-big.test
share/mysql/test/t/archive.test
share/mysql/test/t/archive_bitfield.test
share/mysql/test/t/archive_debug.test
share/mysql/test/t/archive_gis.test
share/mysql/test/t/archive_no_symlink-master.opt
share/mysql/test/t/archive_no_symlink.test
share/mysql/test/t/archive_plugin-master.opt
share/mysql/test/t/archive_plugin.test
share/mysql/test/t/archive_symlink.test
share/mysql/test/t/audit_plugin-master.opt
share/mysql/test/t/audit_plugin.test
share/mysql/test/t/auth_rpl-master.opt
share/mysql/test/t/auth_rpl-slave.opt
share/mysql/test/t/auth_rpl.test
share/mysql/test/t/auto_increment.test
share/mysql/test/t/bench_count_distinct.test
share/mysql/test/t/bigint.test
share/mysql/test/t/binary.test
share/mysql/test/t/blackhole.test
share/mysql/test/t/blackhole_plugin-master.opt
share/mysql/test/t/blackhole_plugin.test
share/mysql/test/t/bool.test
share/mysql/test/t/bootstrap-master.opt
share/mysql/test/t/bootstrap.test
share/mysql/test/t/bug12427262.test
share/mysql/test/t/bug12969156-master.opt
share/mysql/test/t/bug12969156.test
Changes 5.6.20: Security Fix: The linked OpenSSL library for the MySQL 5.6 Commercial Server has been updated from version 1.0.1g to version 1.0.1h. Versions of OpenSSL prior to and including 1.0.1g are reported to be vulnerable to CVE-2014-0224. This change does not affect the Oracle-produced MySQL Community build of MySQL Server 5.6, which uses the yaSSL library instead. DTrace Support MySQL now includes DTrace support on Oracle Linux 6 or higher with UEK kernel. If DTrace is present, server builds will detect it with no special CMake options required. For information about using DTrace on MySQL, see Tracing mysqld Using DTrace. InnoDB Notes Important Change: Redo log writes for large, externally stored BLOB fields could overwrite the most recent checkpoint. The 5.6.20 patch limits the size of redo log BLOB writes to 10% of the redo log file size. The 5.7.5 patch addresses the bug without imposing a limitation. For MySQL 5.5, the bug remains a known limitation. As a result of the redo log BLOB write limit introduced for MySQL 5.6, innodb_log_file_size should be set to a value greater than 10 times the largest BLOB data size found in the rows of your tables plus the length of other variable length fields (VARCHAR, VARBINARY, and TEXT type fields). Failing to do so could result in “Row size too large” errors. No action is required if your innodb_log_file_size setting is already sufficiently large or your tables contain no BLOB data. Functionality Added or Changed Replication: The new system variable binlog_impossible_mode controls what happens if the server cannot write to the binary log, for example, due to a file error. For backward compatibility, the default for binlog_impossible_mode is IGNORE_ERROR, meaning the server logs the error, halts logging, and continues updates to the database. Setting this variable to ABORT_SERVER makes the server halt logging and shut down if it cannot write to the binary log. CMake support was updated to handle CMake version 3. New Debian7, Ubuntu12.04, and Ubuntu14.04 distribution support that was introduced with 5.6.17 now comes with the platform-specific packaging source placed under the packaging directory, in the deb-precise, deb-wheezy, and deb-trusty directories. Support for LinuxThreads has been removed from the source code. LinuxThreads was superseded by NPTL in Linux 2.6. By default, mysql_install_db creates a my.cnf file in the installation base directory using a template. This may be undesireable for some deployments. To enable this behavior to be suppressed, mysql_install_db now supports a --keep-my-cnf option to preserve any existing my.cnf file and not create a new my.cnf file. The mysqlhotcopy utility is now deprecated and will be removed in a future version of MySQL. Among the reasons for this: It works only for the MyISAM and ARCHIVE storage engines; it works on Unix but not Windows. Alternatives include mysqldump and MySQL Enterprise Backup. The timed_mutexes system variable has no effect and is deprecated. Bugs Fixed
2014-08-10 17:11:57 +02:00
share/mysql/test/t/bug17076131-master.opt
share/mysql/test/t/bug17076131.test
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/t/bug33509-master.opt
share/mysql/test/t/bug33509.test
share/mysql/test/t/bug39022.test
share/mysql/test/t/bug46080-master.opt
share/mysql/test/t/bug46080.test
share/mysql/test/t/bug46261-master.opt
share/mysql/test/t/bug46261.test
share/mysql/test/t/bug46760-master.opt
share/mysql/test/t/bug46760.test
share/mysql/test/t/bug47671-master.opt
share/mysql/test/t/bug47671.test
share/mysql/test/t/bug58669-master.opt
share/mysql/test/t/bug58669.test
share/mysql/test/t/bulk_replace.test
share/mysql/test/t/cache_innodb-master.opt
share/mysql/test/t/cache_innodb.test
share/mysql/test/t/case.test
share/mysql/test/t/cast.test
share/mysql/test/t/change_user-master.opt
share/mysql/test/t/change_user.test
share/mysql/test/t/check.test
Changes 5.6.19: Functionality Added or Changed The obsolete and unmaintained charset2html utility has been removed from MySQL distributions. The mysqlbug, mysql_waitpid, and mysql_zap utilities have been deprecated and will be removed in MySQL 5.7. Bugs Fixed InnoDB: After upgrading from 5.6.10 to MySQL versions up to and including MySQL 5.6.18, InnoDB would attempt to rename obsolete full-text search auxiliary tables on server startup, resulting in an assertion failure. InnoDB: For each insert, memset would be called three times to allocate memory for system fields. To reduce CPU usage, the three memset calls are now combined into a single call. InnoDB: Enabling the InnoDB Table Monitor would result in a ib_table->stat_initialized assertion failure. InnoDB: Setting innodb_max_dirty_pages_pct=0 would leave 1% of dirty pages unflushed. Buffer pool flushing is initiated when the percentage of dirty pages is greater innodb_max_dirty_pages_pct. The internal variables that store the innodb_max_dirty_pages_pct value and the percentage of dirty pages (buf_get_modified_ratio_pct and srv_max_buf_pool_modified_pct) were defined as unsigned integer data types, which meant that a innodb_max_dirty_pages_pct value of 0 required a dirty pages percentage of 1 or greater to initiate buffer pool flushing. To address this problem, the buf_get_modified_ratio_pct and srv_max_buf_pool_modified_pct internal variables are redefined as double data types, which changes the range value for innodb_max_dirty_pages_pct and innodb_max_dirty_pages_pct_lwm from 0 .. 99 to 0 .. 99.99. Additionally, buffer pool flushing is now initiated when the percentage of dirty pages is “greater than or equal to” innodb_max_dirty_pages_pct. Replication: Log rotation events could cause group_relay_log_pos to be moved forward incorrectly within a group. This meant that, when the transaction was retried, or if the SQL thread was stopped in the middle of a transaction following one or more log rotations (such that the transaction or group spanned multiple relay log files), part or all of the group was silently skipped. This issue has been addressed by correcting a problem in the logic used to avoid touching the coordinates of the SQL thread when updating the log position as part of a relay log rotation whereby it was possible to update the SQL thread's coordinates when not using a multi-threaded slave, even in the middle of a group. Replication: When running the server with --gtid-mode=ON, STOP SLAVE followed by START SLAVE resulted in a mismatch between the information provided by INFORMATION_SCHEMA.INNODB_TEMP_TABLE_INFO and the Slave_open_temp_tables status variable: the INNODB_TEMP_TABLE_INFO table showed that no temporary tables existed, but Slave_open_temp_tables had a nonzero value. Replication: In certain cases, the server mishandled triggers and stored procedures that tried to modify other tables when called by CREATE TABLE ... SELECT. This is now handled correctly as an error. Replication: When used on a table employing a transactional storage engine, a failed TRUNCATE TABLE was still written to the binary log and thus replayed on the slave. This could lead to inconsistency when the master retained data that was removed on the slave. Now in such cases TRUNCATE TABLE is logged only when it executes successfully. Replication: The server did not always handle the auto.cnf file correctly in cases where this file's permissions were incorrect. Replication: When the binary log was rotated due to receipt of a SIGHUP signal, the new binary log did not contain the Previous_gtid_event required for subsequent processing of that binary log's GTID events. Now when SIGHUP is received, steps are taken to insure that the server writes the necessary Previous_gtid_event to the new log before writing any GTID events to the new log.
2014-06-02 09:30:38 +02:00
share/mysql/test/t/check_auto_permission.test
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/t/client_xml.test
share/mysql/test/t/comment_column.test
share/mysql/test/t/comment_column2.test
share/mysql/test/t/comment_index.test
share/mysql/test/t/comment_table.test
share/mysql/test/t/comments.test
share/mysql/test/t/commit.test
share/mysql/test/t/commit_1innodb.test
share/mysql/test/t/compare.test
share/mysql/test/t/compress.test
share/mysql/test/t/concurrent_innodb_safelog-master.opt
share/mysql/test/t/concurrent_innodb_safelog.test
share/mysql/test/t/concurrent_innodb_unsafelog-master.opt
share/mysql/test/t/concurrent_innodb_unsafelog.test
share/mysql/test/t/connect.test
Changes 5.6.29: * InnoDB: A new InnoDB configuration option, innodb_tmpdir, allows you to configure a separate temporary file directory for online ALTER TABLE operations. This option was introduced to help avoid tmpdir overflows that could occur as a result of large temporary files created during online ALTER TABLE operations. innodb_tmpdir is a SESSION variable and can be configured dynamically using a SET statement. * yaSSL was upgraded to version 2.3.9. This upgrade corrects an issue in which yaSSL handled only cases of zero or one leading zeros for the key agreement instead of potentially any number, which in rare cases could cause connections to fail when using DHE cipher suites. * The Valgrind function signature in mysql-test/valgrind.supp was upgraded for Valgrind 3.11. * Bugs Fixed
2016-02-28 09:58:03 +01:00
share/mysql/test/t/connect_debug.test
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/t/consistent_snapshot.test
share/mysql/test/t/constraints.test
share/mysql/test/t/count_distinct.test
share/mysql/test/t/count_distinct2-master.opt
share/mysql/test/t/count_distinct2.test
share/mysql/test/t/count_distinct3.test
share/mysql/test/t/create-big.test
share/mysql/test/t/create.test
share/mysql/test/t/create_not_windows.test
share/mysql/test/t/create_select_tmp.test
share/mysql/test/t/csv.test
share/mysql/test/t/csv_alter_table.test
share/mysql/test/t/csv_not_null.test
share/mysql/test/t/ctype_ascii.test
share/mysql/test/t/ctype_big5.test
share/mysql/test/t/ctype_binary.test
share/mysql/test/t/ctype_collate.test
share/mysql/test/t/ctype_cp1250_ch.test
share/mysql/test/t/ctype_cp1251.test
Changes 5.6.21: The --skip-innodb option is now deprecated and its use results in a warning. It will be removed in a future MySQL release. This also applies to its synonyms (--innodb=OFF, --disable-innodb, and so forth). MySQL Enterprise Edition now includes a set of encryption functions based on the OpenSSL library that expose OpenSSL capabilities at the SQL level. Replication: The new variable simplified_binlog_gtid_recovery can be used to change the way binary log files are searched for previous GTIDs during recovery, speeding up the process when a large number of binary log files exist. Internally, spatial data types such as Geometry are represented as BLOB values, so when invoked with the --hex-blob option, mysqldump now displays spatial values in hex. Bugs Fixed...
2014-10-01 10:34:23 +02:00
share/mysql/test/t/ctype_cp932.test
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/t/ctype_cp932_binlog_row.test
share/mysql/test/t/ctype_cp932_binlog_stm.test
share/mysql/test/t/ctype_create.test
share/mysql/test/t/ctype_errors.test
share/mysql/test/t/ctype_eucjpms.test
share/mysql/test/t/ctype_euckr.test
share/mysql/test/t/ctype_filename.test
share/mysql/test/t/ctype_filesystem-master.opt
share/mysql/test/t/ctype_filesystem.test
share/mysql/test/t/ctype_gb2312.test
share/mysql/test/t/ctype_gbk.test
share/mysql/test/t/ctype_gbk_binlog.test
share/mysql/test/t/ctype_hebrew.test
share/mysql/test/t/ctype_latin1.test
share/mysql/test/t/ctype_latin1_de-master.opt
share/mysql/test/t/ctype_latin1_de.test
share/mysql/test/t/ctype_latin2.test
share/mysql/test/t/ctype_latin2_ch.test
share/mysql/test/t/ctype_ldml-master.opt
share/mysql/test/t/ctype_ldml.test
share/mysql/test/t/ctype_like_range.test
share/mysql/test/t/ctype_many.test
share/mysql/test/t/ctype_mb.test
share/mysql/test/t/ctype_recoding.test
share/mysql/test/t/ctype_sjis.test
share/mysql/test/t/ctype_tis620.test
share/mysql/test/t/ctype_uca.test
share/mysql/test/t/ctype_ucs.test
share/mysql/test/t/ctype_ucs2_def-master.opt
share/mysql/test/t/ctype_ucs2_def.test
share/mysql/test/t/ctype_ujis.test
share/mysql/test/t/ctype_ujis_ucs2.test
share/mysql/test/t/ctype_utf16.test
share/mysql/test/t/ctype_utf16_def-master.opt
share/mysql/test/t/ctype_utf16_def.test
share/mysql/test/t/ctype_utf16_uca.test
share/mysql/test/t/ctype_utf16le.test
share/mysql/test/t/ctype_utf32.test
share/mysql/test/t/ctype_utf32_uca.test
share/mysql/test/t/ctype_utf8-master.opt
share/mysql/test/t/ctype_utf8.test
share/mysql/test/t/ctype_utf8mb4-master.opt
share/mysql/test/t/ctype_utf8mb4.test
share/mysql/test/t/ctype_utf8mb4_heap.test
share/mysql/test/t/ctype_utf8mb4_innodb-master.opt
share/mysql/test/t/ctype_utf8mb4_innodb.test
share/mysql/test/t/ctype_utf8mb4_myisam.test
share/mysql/test/t/ctype_utf8mb4_uca.test
share/mysql/test/t/date_formats-master.opt
share/mysql/test/t/date_formats.test
share/mysql/test/t/ddl_i18n_koi8r.test
share/mysql/test/t/ddl_i18n_utf8.test
share/mysql/test/t/deadlock_innodb.test
share/mysql/test/t/debug_sync.test
share/mysql/test/t/debug_sync2-master.opt
share/mysql/test/t/debug_sync2.test
share/mysql/test/t/default.test
share/mysql/test/t/delayed.test
share/mysql/test/t/delete.test
share/mysql/test/t/deprecated_features.test
share/mysql/test/t/derived.test
share/mysql/test/t/dirty_close.test
share/mysql/test/t/disabled.def
share/mysql/test/t/disabled_replication-master.opt
share/mysql/test/t/disabled_replication.test
share/mysql/test/t/disconnect_on_expired_password_default.test
share/mysql/test/t/disconnect_on_expired_password_off-master.opt
share/mysql/test/t/disconnect_on_expired_password_off.test
share/mysql/test/t/distinct.test
share/mysql/test/t/drop-no_root.test
share/mysql/test/t/drop.test
share/mysql/test/t/drop_debug.test
share/mysql/test/t/ds_mrr-big.test
Changes 5.6.20: Security Fix: The linked OpenSSL library for the MySQL 5.6 Commercial Server has been updated from version 1.0.1g to version 1.0.1h. Versions of OpenSSL prior to and including 1.0.1g are reported to be vulnerable to CVE-2014-0224. This change does not affect the Oracle-produced MySQL Community build of MySQL Server 5.6, which uses the yaSSL library instead. DTrace Support MySQL now includes DTrace support on Oracle Linux 6 or higher with UEK kernel. If DTrace is present, server builds will detect it with no special CMake options required. For information about using DTrace on MySQL, see Tracing mysqld Using DTrace. InnoDB Notes Important Change: Redo log writes for large, externally stored BLOB fields could overwrite the most recent checkpoint. The 5.6.20 patch limits the size of redo log BLOB writes to 10% of the redo log file size. The 5.7.5 patch addresses the bug without imposing a limitation. For MySQL 5.5, the bug remains a known limitation. As a result of the redo log BLOB write limit introduced for MySQL 5.6, innodb_log_file_size should be set to a value greater than 10 times the largest BLOB data size found in the rows of your tables plus the length of other variable length fields (VARCHAR, VARBINARY, and TEXT type fields). Failing to do so could result in “Row size too large” errors. No action is required if your innodb_log_file_size setting is already sufficiently large or your tables contain no BLOB data. Functionality Added or Changed Replication: The new system variable binlog_impossible_mode controls what happens if the server cannot write to the binary log, for example, due to a file error. For backward compatibility, the default for binlog_impossible_mode is IGNORE_ERROR, meaning the server logs the error, halts logging, and continues updates to the database. Setting this variable to ABORT_SERVER makes the server halt logging and shut down if it cannot write to the binary log. CMake support was updated to handle CMake version 3. New Debian7, Ubuntu12.04, and Ubuntu14.04 distribution support that was introduced with 5.6.17 now comes with the platform-specific packaging source placed under the packaging directory, in the deb-precise, deb-wheezy, and deb-trusty directories. Support for LinuxThreads has been removed from the source code. LinuxThreads was superseded by NPTL in Linux 2.6. By default, mysql_install_db creates a my.cnf file in the installation base directory using a template. This may be undesireable for some deployments. To enable this behavior to be suppressed, mysql_install_db now supports a --keep-my-cnf option to preserve any existing my.cnf file and not create a new my.cnf file. The mysqlhotcopy utility is now deprecated and will be removed in a future version of MySQL. Among the reasons for this: It works only for the MyISAM and ARCHIVE storage engines; it works on Unix but not Windows. Alternatives include mysqldump and MySQL Enterprise Backup. The timed_mutexes system variable has no effect and is deprecated. Bugs Fixed
2014-08-10 17:11:57 +02:00
share/mysql/test/t/dynamic_tracing.test
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/t/empty_table.test
Changes 5.6.28: MySQL Server RPM packages now contain a conflict indicator for MySQL Connector C, such that an error occurs when installing MySQL Server if MySQL Connector C is also installed. To install MySQL Server, remove any MySQL Connector C packages first. mysql_upgrade now attempts to print more informative errors than FATAL ERROR: Upgrade failed. These client programs now support the --enable-cleartext-plugin option: mysqlcheck, mysqldump, mysqlimport, mysqlshow. This option enables the mysql_clear_password cleartext authentication plugin. (See The Cleartext Client-Side Authentication Plugin.) Support for building with Solaris Studio 5.13 was added. Performance Schema digests in DIGEST_TEXT columns have ... appended to the end to indicate when statements exceed the maximum statement size and were truncated. This is also now done for statement text values in SQL_TEXT columns. Bugs Fixed
2015-12-08 09:49:50 +01:00
share/mysql/test/t/enable_cleartext_plugin-master.opt
share/mysql/test/t/enable_cleartext_plugin.test
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/t/endspace.test
share/mysql/test/t/eq_range_idx_stat.test
share/mysql/test/t/error_simulation.test
share/mysql/test/t/errors.test
share/mysql/test/t/events_1.test
share/mysql/test/t/events_2.test
share/mysql/test/t/events_bugs-master.opt
share/mysql/test/t/events_bugs.test
share/mysql/test/t/events_embedded.test
share/mysql/test/t/events_grant.test
share/mysql/test/t/events_logs_tests-master.opt
share/mysql/test/t/events_logs_tests.test
share/mysql/test/t/events_microsec.test
share/mysql/test/t/events_restart-master.opt
share/mysql/test/t/events_restart.test
share/mysql/test/t/events_scheduling.test
share/mysql/test/t/events_stress.test
share/mysql/test/t/events_time_zone.test
share/mysql/test/t/events_trans.test
share/mysql/test/t/events_trans_notembedded.test
share/mysql/test/t/execution_constants.test
share/mysql/test/t/explain.test
share/mysql/test/t/explain_json_all.test
share/mysql/test/t/explain_json_none.test
share/mysql/test/t/file_contents.test
share/mysql/test/t/filesort_debug.test
share/mysql/test/t/fix_priv_tables.test
share/mysql/test/t/flush.test
share/mysql/test/t/flush2-master.opt
share/mysql/test/t/flush2.test
share/mysql/test/t/flush_block_commit.test
share/mysql/test/t/flush_block_commit_notembedded.test
share/mysql/test/t/flush_read_lock.test
share/mysql/test/t/flush_read_lock_kill.test
share/mysql/test/t/flush_table.test
share/mysql/test/t/foreign_key.test
share/mysql/test/t/fulltext.test
share/mysql/test/t/fulltext2.test
share/mysql/test/t/fulltext3.test
share/mysql/test/t/fulltext_cache.test
share/mysql/test/t/fulltext_distinct.test
share/mysql/test/t/fulltext_left_join.test
share/mysql/test/t/fulltext_multi.test
share/mysql/test/t/fulltext_order_by.test
share/mysql/test/t/fulltext_plugin-master.opt
share/mysql/test/t/fulltext_plugin.test
share/mysql/test/t/fulltext_update.test
share/mysql/test/t/fulltext_var.test
Changes 5.6.17: Functionality Added or Changed Incompatible Change: The AES_ENCRYPT() and AES_DECRYPT() functions now permit control of the block encryption mode and take an optional initialization vector argument: The new block_encryption_mode system variable controls the mode for block-based encryption algorithms. Its default value is aes-128-ecb, which signifies encryption using a key length of 128 bits and ECB mode. An optional init_vector argument provides an initialization vector for encryption modes that require it: AES_ENCRYPT(str,key_str[,init_vector]) AES_DECRYPT(crypt_str,key_str[,init_vector]) A random string of bytes to use for the initialization vector can be produced by calling the new RANDOM_BYTES() function. For more information, see Encryption and Compression Functions. These changes make statements that use AES_ENCRYPT() or AES_DECRYPT() unsafe for statement-based replication and they cannot be stored in the query cache. Queries that use RANDOM_BYTES() are unsafe for statement-based replication and cannot be stored in the query cache. Incompatible Change: The ERROR_FOR_DIVISION_BY_ZERO, NO_ZERO_DATE, and NO_ZERO_IN_DATE SQL modes now are deprecated and setting the sql_mode value to include any of them generates a warning. In MySQL 5.7, these modes do nothing. Instead, their effects are included in the effects of strict SQL mode (STRICT_ALL_TABLES or STRICT_TRANS_TABLES). The motivation for the change in MySQL 5.7 is to reduce the number of SQL modes with an effect dependent on strict mode and make them part of strict mode itself. To make advance preparation for an upgrade to MySQL 5.7, see SQL Mode Changes in MySQL 5.7. That discussion provides guidelines to assess whether your applications will be affected by the SQL mode changes in MySQL 5.7. InnoDB: MySQL now supports rebuilding regular and partitioned InnoDB tables using online DDL (ALGORITHM=INPLACE) for the following operations: OPTIMIZE TABLE ALTER TABLE ... FORCE ALTER TABLE ... ENGINE=INNODB (when run on an InnoDB table) Online DDL support reduces table rebuild time and permits concurrent DML, which helps reduce user application downtime. For additional information, see Overview of Online DDL. On Solaris, mysql_config --libs now includes -R/path/to/library so that libraries can be found at runtime. mysql_install_db provides a more informative diagnostic message when required Perl modules are missing. The IGNORE clause for ALTER TABLE is now deprecated and will be removed in a future version of MySQL. ALTER IGNORE TABLE causes problems for replication, prevents online ALTER TABLE for unique index creation, and causes problems with foreign keys (rows removed in the parent table). Bugs Fixed
2014-03-31 12:32:13 +02:00
share/mysql/test/t/func_aes.test
share/mysql/test/t/func_aes_cfb1.test
share/mysql/test/t/func_aes_cfb128.test
share/mysql/test/t/func_aes_cfb8.test
share/mysql/test/t/func_aes_misc.test
share/mysql/test/t/func_aes_ofb.test
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/t/func_analyse.test
share/mysql/test/t/func_compress.test
share/mysql/test/t/func_concat.test
share/mysql/test/t/func_crypt.test
share/mysql/test/t/func_date_add.test
share/mysql/test/t/func_default.test
share/mysql/test/t/func_des_encrypt.test
share/mysql/test/t/func_digest.test
share/mysql/test/t/func_encrypt-master.opt
share/mysql/test/t/func_encrypt.test
share/mysql/test/t/func_encrypt_nossl.test
share/mysql/test/t/func_encrypt_ucs2.test
share/mysql/test/t/func_equal.test
share/mysql/test/t/func_gconcat.test
share/mysql/test/t/func_group.test
share/mysql/test/t/func_group_innodb.test
share/mysql/test/t/func_group_innodb_16k.test
share/mysql/test/t/func_if.test
share/mysql/test/t/func_in_all.test
share/mysql/test/t/func_in_icp.test
share/mysql/test/t/func_in_icp_mrr.test
share/mysql/test/t/func_in_mrr.test
share/mysql/test/t/func_in_mrr_cost.test
share/mysql/test/t/func_in_none.test
share/mysql/test/t/func_isnull.test
share/mysql/test/t/func_like.test
share/mysql/test/t/func_math.test
share/mysql/test/t/func_misc-master.opt
share/mysql/test/t/func_misc.test
share/mysql/test/t/func_op.test
share/mysql/test/t/func_regexp.test
share/mysql/test/t/func_rollback.test
share/mysql/test/t/func_sapdb.test
share/mysql/test/t/func_set.test
share/mysql/test/t/func_str.test
Changes 5.6.27: * InnoDB: The new innodb_numa_interleave read-only configuration option allows you to enable the NUMA interleave memory policy for allocation of the InnoDB buffer pool. When innodb_numa_interleave is enabled, the NUMA memory policy is set to MPOL_INTERLEAVE for the mysqld process. After the InnoDB buffer pool is allocated, the NUMA memory policy is set back to MPOL_DEFAULT. This option is only available on NUMA-enabled systems. * yaSSL was upgraded to version 2.3.8. * RPM .spec files were updated so that MySQL Server builds from source RPM packages will include the proper files to take advantage of operating system NUMA capabilities. This introduces a runtime dependency on libnuma.so.1. RPM and yum detect this and refuse to install if that library is not installed. * InnoDB: Reloading a table that was evicted while empty caused an AUTO_INCREMENT value to be reset. * InnoDB: Memory allocation sanity checks were added to the memcached code. * InnoDB: A memcached flush_all command raised an assertion. A function that starts a transaction was called from within assertion code. * InnoDB: A data corruption occurred on ARM64. GCC builtins did not issue the correct fences when setting or unsetting the lock word. * InnoDB: Server shutdown was delayed waiting for the purge thread to exit. To avoid this problem, the number of calls to trx_purge() was reduced, and the trx_purge() batch size was reduced to 20. * InnoDB: In READ COMMITTED mode, a REPLACE operation on a unique secondary index resulted in a constraint violation. * InnoDB: The IBUF_BITMAP_FREE bit indicated that there was more free space in the leaf page than was actually available. * InnoDB: Setting lower_case_table_names=0 on a case-insensitive file system could result in a hang condition when running an INSERT INTO ... SELECT ... FROM tbl_name operation with the wrong tbl_name letter case. An error message is now printed and the server exits when attempting to start the server with --lower_case_table_names=0 on a case-insensitive file system. * InnoDB: The server failed to start with an innodb_force_recovery setting greater than 3. InnoDB was set to read-only mode before redo logs were applied. * InnoDB: The trx_sys_read_pertable_file_format_id() function reported the wrong file format. * Partitioning: CREATE TABLE statements that used an invalid function in a subpartitioning expression did not always fail gracefully as expected. * Partitioning: Error handling for failed partitioning-related ALTER TABLE operations against non-partitioned tables was not performed correctly * Partitioning: ALTER TABLE when executed from a stored procedure did not always work correctly with tables partitioned by RANGE. * Replication: Repeatedly checking for ERR_LOCK_WAIT_TIMEOUT (as done, for example by repeatedly executing SHOW SLAVE STATUS) during a prolonged write lock on a table led to an assert. * Replication: If statement based logging was in use, when updating multiple tables in a single statement, a single transaction could be logged as two different transactions. This was due to the binary logging process not properly identifying statements which were operating over transactional tables. The fix ensures that they are correctly identified, even if such statements do not change the contents of the tables.
2015-10-03 14:46:13 +02:00
share/mysql/test/t/func_str_debug.test
share/mysql/test/t/func_str_no_ps.test
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/t/func_system.test
share/mysql/test/t/func_test.test
share/mysql/test/t/func_time.test
share/mysql/test/t/func_timestamp.test
share/mysql/test/t/func_weight_string.test
share/mysql/test/t/function_defaults.test
share/mysql/test/t/function_defaults_notembedded.test
share/mysql/test/t/gcc296.test
share/mysql/test/t/get_diagnostics.test
share/mysql/test/t/gis-debug.test
share/mysql/test/t/gis-precise.test
share/mysql/test/t/gis-rt-precise.test
share/mysql/test/t/gis-rtree.test
share/mysql/test/t/gis.test
share/mysql/test/t/grant.test
share/mysql/test/t/grant2.test
share/mysql/test/t/grant3-master.opt
share/mysql/test/t/grant3.test
share/mysql/test/t/grant4.test
share/mysql/test/t/grant_cache-master.opt
share/mysql/test/t/grant_cache.test
share/mysql/test/t/grant_explain_non_select.test
share/mysql/test/t/grant_lowercase_fs.test
share/mysql/test/t/greedy_optimizer.test
share/mysql/test/t/greedy_search.test
share/mysql/test/t/group_by.test
share/mysql/test/t/group_min_max.test
share/mysql/test/t/group_min_max_innodb.test
share/mysql/test/t/handler_innodb.test
share/mysql/test/t/handler_myisam.test
share/mysql/test/t/handler_read_last.test
share/mysql/test/t/having.test
share/mysql/test/t/heap.test
share/mysql/test/t/heap_auto_increment.test
share/mysql/test/t/heap_btree.test
share/mysql/test/t/heap_hash.test
share/mysql/test/t/help.test
share/mysql/test/t/host_cache_size_functionality.test
share/mysql/test/t/implicit_char_to_num_conversion.test
share/mysql/test/t/implicit_commit-master.opt
share/mysql/test/t/implicit_commit.test
Changes 5.6.12: * mysql_upgrade now verifies that the server version matches the version against which it was compiled, and exits if there is a mismatch. In addiion, a --version-check option permits specifying whether to enable version checking (the default), or disable checking if given as --skip-version-checking. * Bugs Fixed
2013-06-04 20:17:25 +02:00
share/mysql/test/t/index_merge_delete.test
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/t/index_merge_innodb.test
Changes 5.6.12: * mysql_upgrade now verifies that the server version matches the version against which it was compiled, and exits if there is a mismatch. In addiion, a --version-check option permits specifying whether to enable version checking (the default), or disable checking if given as --skip-version-checking. * Bugs Fixed
2013-06-04 20:17:25 +02:00
share/mysql/test/t/index_merge_insert-and-replace.test
share/mysql/test/t/index_merge_intersect_dml.test
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/t/index_merge_myisam.test
Changes 5.6.12: * mysql_upgrade now verifies that the server version matches the version against which it was compiled, and exits if there is a mismatch. In addiion, a --version-check option permits specifying whether to enable version checking (the default), or disable checking if given as --skip-version-checking. * Bugs Fixed
2013-06-04 20:17:25 +02:00
share/mysql/test/t/index_merge_update.test
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/t/information_schema-big.test
share/mysql/test/t/information_schema.test
share/mysql/test/t/information_schema_chmod.test
share/mysql/test/t/information_schema_db.test
share/mysql/test/t/information_schema_inno.test
share/mysql/test/t/information_schema_parameters.test
share/mysql/test/t/information_schema_part.test
share/mysql/test/t/information_schema_routines.test
share/mysql/test/t/init_connect-master.opt
share/mysql/test/t/init_connect.test
share/mysql/test/t/init_file-master.opt
share/mysql/test/t/init_file.test
share/mysql/test/t/innodb_explain_json_non_select_all.test
share/mysql/test/t/innodb_explain_json_non_select_none.test
share/mysql/test/t/innodb_explain_non_select_all.test
share/mysql/test/t/innodb_explain_non_select_none.test
share/mysql/test/t/innodb_icp.test
share/mysql/test/t/innodb_icp_all.test
share/mysql/test/t/innodb_icp_none.test
share/mysql/test/t/innodb_ignore_builtin-master.opt
share/mysql/test/t/innodb_ignore_builtin.test
share/mysql/test/t/innodb_log_file_size_functionality.test
share/mysql/test/t/innodb_mrr-master.opt
share/mysql/test/t/innodb_mrr.test
share/mysql/test/t/innodb_mrr_all-master.opt
share/mysql/test/t/innodb_mrr_all.test
share/mysql/test/t/innodb_mrr_cost-master.opt
share/mysql/test/t/innodb_mrr_cost.test
share/mysql/test/t/innodb_mrr_cost_all-master.opt
share/mysql/test/t/innodb_mrr_cost_all.test
share/mysql/test/t/innodb_mrr_cost_icp-master.opt
share/mysql/test/t/innodb_mrr_cost_icp.test
share/mysql/test/t/innodb_mrr_icp-master.opt
share/mysql/test/t/innodb_mrr_icp.test
share/mysql/test/t/innodb_mrr_none-master.opt
share/mysql/test/t/innodb_mrr_none.test
share/mysql/test/t/innodb_mysql_lock-master.opt
share/mysql/test/t/innodb_mysql_lock.test
share/mysql/test/t/innodb_mysql_lock2.test
share/mysql/test/t/innodb_mysql_sync.test
share/mysql/test/t/innodb_pk_extension_off.test
share/mysql/test/t/innodb_pk_extension_on.test
Changes 5.6.22: * Noisy compiler warnings on FreeBSD 10 were silenced. * CMake workarounds for older Mac OS X and XCode versions were removed. On Mac OS X, compilation always uses Clang, even for 32-bit builds. * Previously, the MYSQL_MAINTAINER_MODE CMake option was turned on by default for debug builds and off for release builds, and MYSQL_MAINTAINER_MODE caused -Werror to be enabled when building with GCC. This made it cumbersome to enable -Werror under certain conditions, such as when compiling with Clang. * Build support was modified to produce the same warnings for Clang as for gcc. * CMake configuration for the Clang compiler sets more appropriate flags for building on Linux. Specifically, -g -fno-omit-frame-pointer -fno-strict-aliasing is now added. * Bugs fixed.
2014-12-02 13:40:09 +01:00
share/mysql/test/t/innodb_recovery_with_upper_case_names-master.opt
share/mysql/test/t/innodb_recovery_with_upper_case_names.test
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/t/insert.test
share/mysql/test/t/insert_notembedded.test
share/mysql/test/t/insert_select.test
share/mysql/test/t/insert_update.test
share/mysql/test/t/ipv4_as_ipv6-master.opt
share/mysql/test/t/ipv4_as_ipv6.test
share/mysql/test/t/ipv6-master.opt
share/mysql/test/t/ipv6.test
share/mysql/test/t/join.test
share/mysql/test/t/join_cache_bka.test
share/mysql/test/t/join_cache_bka_nixbnl.test
share/mysql/test/t/join_cache_bkaunique.test
share/mysql/test/t/join_cache_bnl.test
share/mysql/test/t/join_cache_nojb.test
share/mysql/test/t/join_crash.test
share/mysql/test/t/join_nested.test
share/mysql/test/t/join_nested_bka.test
share/mysql/test/t/join_nested_bka_nixbnl.test
share/mysql/test/t/join_outer.test
share/mysql/test/t/join_outer_bka.test
share/mysql/test/t/join_outer_bka_nixbnl.test
share/mysql/test/t/join_outer_innodb.test
share/mysql/test/t/key.test
share/mysql/test/t/key_cache-master.opt
share/mysql/test/t/key_cache.test
share/mysql/test/t/key_diff.test
share/mysql/test/t/key_primary.test
share/mysql/test/t/keywords.test
share/mysql/test/t/kill.test
share/mysql/test/t/kill_debug.test
share/mysql/test/t/limit.test
share/mysql/test/t/loaddata.test
share/mysql/test/t/loaddata_autocom_innodb.test
share/mysql/test/t/loadxml.test
share/mysql/test/t/locale.test
share/mysql/test/t/lock.test
share/mysql/test/t/lock_multi.test
share/mysql/test/t/lock_multi_bug38499.test
share/mysql/test/t/lock_multi_bug38691.test
share/mysql/test/t/lock_sync-master.opt
share/mysql/test/t/lock_sync.test
share/mysql/test/t/lock_tables_lost_commit-master.opt
share/mysql/test/t/lock_tables_lost_commit.test
Changes 5.6.25: Functionality Added or Changed * MySQL Enterprise Firewall operates on parser states and does not work well together with the query cache, which circumvents the parser. MySQL Enterprise Firewall now checks whether the query cache is enabled. If so, it displays a message that the query cache must be disabled and does not load. * my_print_defaults now masks passwords. To display passwords in cleartext, use the new --show option. * MySQL distributions now include an innodb_stress suite of test cases. Thanks to Mark Callaghan for the contribution. Bugs Fixed * InnoDB; Partitioning: The CREATE_TIME column of the INFORMATION_SCHEMA.TABLES table now shows the correct table creation time for partitioned InnoDB tables. The CREATE_TIME column of the INFORMATION_SCHEMA.PARTITIONS table now shows the correct partition creation time for a partition of partitioned InnoDB tables. The UPDATE_TIME column of the INFORMATION_SCHEMA.TABLES table now shows when a partitioned InnoDB table was last updated by an INSERT, DELETE, or UPDATE. The UPDATE_TIME column of the INFORMATION_SCHEMA.PARTITIONS table now shows when a partition of a partitioned InnoDB table was last updated. * InnoDB: An assertion was raised on shutdown due to XA PREPARE transactions holding explicit locks. * InnoDB: The strict_* forms of innodb_checksum_algorithm settings (strict_none, strict_innodb, and strict_crc32) caused the server to halt when a non-matching checksum was encountered, even though the non-matching checksum was valid. For example, with innodb_checksum_algorithm=strict_crc32, encountering a valid innodb checksum caused the server to halt. Instead of halting the server, a message is now printed to the error log and the page is accepted as valid if it matches an innodb, crc32 or none checksum. * InnoDB: The memcached set command permitted a negative expire time value. Expire time is stored internally as an unsigned integer. A negative value would be converted to a large number and accepted. The maximum expire time value is now restricted to INT_MAX32 to prevent negative expire time values. * InnoDB: Removal of a foreign key object from the data dictionary cache during error handling caused the server to exit. * InnoDB: SHOW ENGINE INNODB STATUS output showed negative reservation and signal count values due to a counter overflow error. * InnoDB: Failure to check the status of a cursor transaction read-only option before reusing the cursor transaction for a write operation resulted in a server exit during a memcached workload. * InnoDB: MDL locks taken by memcached clients caused a MySQL Enterprise Backup FLUSH TABLES WITH READ LOCK operation to hang. * InnoDB: Estimates that were too low for the size of merge chunks in the result sorting algorithm caused a server exit. * InnoDB: For full-text searches, the optimizer could choose an index that does not produce correct relevancy rankings. * Partitioning: When creating a partitioned table, partition-level DATA DIRECTORY or INDEX DIRECTORY option values that contained an excessive number of characters were handled incorrectly. * Partitioning: Executing an ALTER TABLE on a partitioned table on which a write lock was in effect could cause subsequent SQL statements on this table to fail. * Replication: When binary logging was enabled, using stored functions and triggers resulting in a long running procedure that inserted many records caused the memory use to increase rapidly. This was due to memory being allocated per variable. The fix ensures that in such a situation, memory is allocated once and the same memory is reused. * Replication: If an error was encountered while adding a GTID to the received GTID set, the log lock was not being correctly released. This could cause a deadlock. more...
2015-06-01 10:15:05 +02:00
share/mysql/test/t/log_empty_name.opt
share/mysql/test/t/log_empty_name.test
Changes 5.6.21: The --skip-innodb option is now deprecated and its use results in a warning. It will be removed in a future MySQL release. This also applies to its synonyms (--innodb=OFF, --disable-innodb, and so forth). MySQL Enterprise Edition now includes a set of encryption functions based on the OpenSSL library that expose OpenSSL capabilities at the SQL level. Replication: The new variable simplified_binlog_gtid_recovery can be used to change the way binary log files are searched for previous GTIDs during recovery, speeding up the process when a large number of binary log files exist. Internally, spatial data types such as Geometry are represented as BLOB values, so when invoked with the --hex-blob option, mysqldump now displays spatial values in hex. Bugs Fixed...
2014-10-01 10:34:23 +02:00
share/mysql/test/t/log_errchk.test
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/t/log_state-master.opt
share/mysql/test/t/log_state.test
share/mysql/test/t/log_state_bug33693-master.opt
share/mysql/test/t/log_state_bug33693.test
share/mysql/test/t/log_tables-big-master.opt
share/mysql/test/t/log_tables-big.test
share/mysql/test/t/log_tables-master.opt
share/mysql/test/t/log_tables.test
share/mysql/test/t/log_tables_debug.test
share/mysql/test/t/log_tables_upgrade.test
share/mysql/test/t/long_tmpdir-master.opt
share/mysql/test/t/long_tmpdir-master.sh
share/mysql/test/t/long_tmpdir.test
share/mysql/test/t/lowercase_fs_off.test
Changes 5.6.27: * InnoDB: The new innodb_numa_interleave read-only configuration option allows you to enable the NUMA interleave memory policy for allocation of the InnoDB buffer pool. When innodb_numa_interleave is enabled, the NUMA memory policy is set to MPOL_INTERLEAVE for the mysqld process. After the InnoDB buffer pool is allocated, the NUMA memory policy is set back to MPOL_DEFAULT. This option is only available on NUMA-enabled systems. * yaSSL was upgraded to version 2.3.8. * RPM .spec files were updated so that MySQL Server builds from source RPM packages will include the proper files to take advantage of operating system NUMA capabilities. This introduces a runtime dependency on libnuma.so.1. RPM and yum detect this and refuse to install if that library is not installed. * InnoDB: Reloading a table that was evicted while empty caused an AUTO_INCREMENT value to be reset. * InnoDB: Memory allocation sanity checks were added to the memcached code. * InnoDB: A memcached flush_all command raised an assertion. A function that starts a transaction was called from within assertion code. * InnoDB: A data corruption occurred on ARM64. GCC builtins did not issue the correct fences when setting or unsetting the lock word. * InnoDB: Server shutdown was delayed waiting for the purge thread to exit. To avoid this problem, the number of calls to trx_purge() was reduced, and the trx_purge() batch size was reduced to 20. * InnoDB: In READ COMMITTED mode, a REPLACE operation on a unique secondary index resulted in a constraint violation. * InnoDB: The IBUF_BITMAP_FREE bit indicated that there was more free space in the leaf page than was actually available. * InnoDB: Setting lower_case_table_names=0 on a case-insensitive file system could result in a hang condition when running an INSERT INTO ... SELECT ... FROM tbl_name operation with the wrong tbl_name letter case. An error message is now printed and the server exits when attempting to start the server with --lower_case_table_names=0 on a case-insensitive file system. * InnoDB: The server failed to start with an innodb_force_recovery setting greater than 3. InnoDB was set to read-only mode before redo logs were applied. * InnoDB: The trx_sys_read_pertable_file_format_id() function reported the wrong file format. * Partitioning: CREATE TABLE statements that used an invalid function in a subpartitioning expression did not always fail gracefully as expected. * Partitioning: Error handling for failed partitioning-related ALTER TABLE operations against non-partitioned tables was not performed correctly * Partitioning: ALTER TABLE when executed from a stored procedure did not always work correctly with tables partitioned by RANGE. * Replication: Repeatedly checking for ERR_LOCK_WAIT_TIMEOUT (as done, for example by repeatedly executing SHOW SLAVE STATUS) during a prolonged write lock on a table led to an assert. * Replication: If statement based logging was in use, when updating multiple tables in a single statement, a single transaction could be logged as two different transactions. This was due to the binary logging process not properly identifying statements which were operating over transactional tables. The fix ensures that they are correctly identified, even if such statements do not change the contents of the tables.
2015-10-03 14:46:13 +02:00
share/mysql/test/t/lowercase_fs_on.test
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/t/lowercase_mixed_tmpdir-master.opt
share/mysql/test/t/lowercase_mixed_tmpdir-master.sh
share/mysql/test/t/lowercase_mixed_tmpdir.test
share/mysql/test/t/lowercase_mixed_tmpdir_innodb-master.opt
share/mysql/test/t/lowercase_mixed_tmpdir_innodb-master.sh
share/mysql/test/t/lowercase_mixed_tmpdir_innodb.test
share/mysql/test/t/lowercase_table-master.opt
share/mysql/test/t/lowercase_table.test
share/mysql/test/t/lowercase_table2.test
share/mysql/test/t/lowercase_table4-master.opt
share/mysql/test/t/lowercase_table4.test
share/mysql/test/t/lowercase_table_grant-master.opt
share/mysql/test/t/lowercase_table_grant.test
share/mysql/test/t/lowercase_table_qcache-master.opt
share/mysql/test/t/lowercase_table_qcache.test
share/mysql/test/t/lowercase_utf8-master.opt
share/mysql/test/t/lowercase_utf8.test
share/mysql/test/t/lowercase_view-master.opt
share/mysql/test/t/lowercase_view.test
share/mysql/test/t/main.lowercase_table_qcache-master.opt
share/mysql/test/t/mdl_sync-master.opt
share/mysql/test/t/mdl_sync.test
share/mysql/test/t/merge-big.test
share/mysql/test/t/merge.test
share/mysql/test/t/merge_innodb.test
share/mysql/test/t/merge_mmap-master.opt
share/mysql/test/t/merge_mmap.test
share/mysql/test/t/metadata.test
share/mysql/test/t/mix2_myisam-master.opt
share/mysql/test/t/mix2_myisam.test
share/mysql/test/t/mix2_myisam_ucs2.test
share/mysql/test/t/multi_plugin_load-master.opt
share/mysql/test/t/multi_plugin_load.test
share/mysql/test/t/multi_plugin_load_add-master.opt
share/mysql/test/t/multi_plugin_load_add.test
share/mysql/test/t/multi_plugin_load_add2-master.opt
share/mysql/test/t/multi_plugin_load_add2.test
share/mysql/test/t/multi_statement-master.opt
share/mysql/test/t/multi_statement.test
share/mysql/test/t/multi_update-master.opt
share/mysql/test/t/multi_update.test
share/mysql/test/t/multi_update2-master.opt
share/mysql/test/t/multi_update2.test
share/mysql/test/t/multi_update_innodb.test
share/mysql/test/t/multi_update_tiny_hash-master.opt
share/mysql/test/t/multi_update_tiny_hash.test
share/mysql/test/t/myisam-blob-master.opt
share/mysql/test/t/myisam-blob.test
share/mysql/test/t/myisam-system.test
share/mysql/test/t/myisam.test
share/mysql/test/t/myisam_crash_before_flush_keys-master.opt
share/mysql/test/t/myisam_crash_before_flush_keys.test
share/mysql/test/t/myisam_debug.test
share/mysql/test/t/myisam_explain_json_non_select_all.test
share/mysql/test/t/myisam_explain_json_non_select_none.test
share/mysql/test/t/myisam_explain_non_select_all.test
share/mysql/test/t/myisam_explain_non_select_none.test
share/mysql/test/t/myisam_icp.test
share/mysql/test/t/myisam_icp_all.test
share/mysql/test/t/myisam_icp_none.test
share/mysql/test/t/myisam_mrr.test
share/mysql/test/t/myisam_mrr_all.test
share/mysql/test/t/myisam_mrr_cost.test
share/mysql/test/t/myisam_mrr_cost_all.test
share/mysql/test/t/myisam_mrr_cost_icp.test
share/mysql/test/t/myisam_mrr_icp.test
share/mysql/test/t/myisam_mrr_none.test
Changes 5.6.26: * Security Fix: Due to the LogJam issue (https://weakdh.org/), OpenSSL has changed the Diffie-Hellman key length parameters for openssl-1.0.1n and up. * Replication: When using a multi-threaded slave, each worker thread has its own queue of transactions to process. In previous MySQL versions, STOP SLAVE waited for all workers to process their entire queue. This logic has been changed so that STOP SLAVE first finds the newest transaction that was committed by any worker thread. Then, it waits for all workers to complete transactions older than that. Newer transactions are not processed. The new logic allows STOP SLAVE to complete faster in case some worker queues contain multiple transactions. * Previously, the max_digest_length system variable controlled the maximum digest length for all server functions that computed statement digests. However, whereas the Performance Schema may need to maintain many digest values, other server functions such as MySQL Enterprise Firewall need only one digest per session. Increasing the max_digest_length value has little impact on total memory requirements for those functions, but can increase Performance Schema memory requirements significantly. To enable configuring digest length separately for the Performance Schema, its digest length is now controlled by the new performance_schema_max_digest_length system variable. * Previously, changes to the validate_password plugin dictionary file (named by the validate_password_dictionary_file system variable) while the server was running required a restart for the server to recognize the changes. Now validate_password_dictionary_file can be set at runtime and assigning a value causes the named file to be read without a restart. In addition, two new status variables are available. validate_password_dictionary_file_last_parsed indicates when the dictionary file was last read, and validate_password_dictionary_file_words_count indicates how many words it contains. * Bugs fixed
2015-07-30 16:39:18 +02:00
share/mysql/test/t/myisam_recover-master.opt
share/mysql/test/t/myisam_recover.test
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/t/myisam_row_rpl-master.opt
share/mysql/test/t/myisam_row_rpl-slave.opt
share/mysql/test/t/myisam_row_rpl.test
share/mysql/test/t/myisampack.test
share/mysql/test/t/mysql-bug41486.test
share/mysql/test/t/mysql-bug45236.test
share/mysql/test/t/mysql.test
share/mysql/test/t/mysql_binary_mode.test
share/mysql/test/t/mysql_client_test-master.opt
share/mysql/test/t/mysql_client_test.test
share/mysql/test/t/mysql_client_test_embedded.cnf
share/mysql/test/t/mysql_client_test_embedded.test
share/mysql/test/t/mysql_comments.sql
share/mysql/test/t/mysql_comments.test
share/mysql/test/t/mysql_config_editor.test
share/mysql/test/t/mysql_cp932.test
share/mysql/test/t/mysql_delimiter.sql
share/mysql/test/t/mysql_delimiter_19799.sql
share/mysql/test/t/mysql_delimiter_source.sql
share/mysql/test/t/mysql_embedded-master.opt
share/mysql/test/t/mysql_embedded.test
share/mysql/test/t/mysql_embedded_client_test.test
share/mysql/test/t/mysql_locale_posix.test
share/mysql/test/t/mysql_not_windows.test
share/mysql/test/t/mysql_plugin-master.opt
share/mysql/test/t/mysql_plugin.test
share/mysql/test/t/mysql_protocols.test
share/mysql/test/t/mysql_upgrade.test
share/mysql/test/t/mysql_upgrade_ssl.test
share/mysql/test/t/mysqladmin.test
share/mysql/test/t/mysqlbinlog-master.opt
share/mysql/test/t/mysqlbinlog.test
Changes 5.6.20: Security Fix: The linked OpenSSL library for the MySQL 5.6 Commercial Server has been updated from version 1.0.1g to version 1.0.1h. Versions of OpenSSL prior to and including 1.0.1g are reported to be vulnerable to CVE-2014-0224. This change does not affect the Oracle-produced MySQL Community build of MySQL Server 5.6, which uses the yaSSL library instead. DTrace Support MySQL now includes DTrace support on Oracle Linux 6 or higher with UEK kernel. If DTrace is present, server builds will detect it with no special CMake options required. For information about using DTrace on MySQL, see Tracing mysqld Using DTrace. InnoDB Notes Important Change: Redo log writes for large, externally stored BLOB fields could overwrite the most recent checkpoint. The 5.6.20 patch limits the size of redo log BLOB writes to 10% of the redo log file size. The 5.7.5 patch addresses the bug without imposing a limitation. For MySQL 5.5, the bug remains a known limitation. As a result of the redo log BLOB write limit introduced for MySQL 5.6, innodb_log_file_size should be set to a value greater than 10 times the largest BLOB data size found in the rows of your tables plus the length of other variable length fields (VARCHAR, VARBINARY, and TEXT type fields). Failing to do so could result in “Row size too large” errors. No action is required if your innodb_log_file_size setting is already sufficiently large or your tables contain no BLOB data. Functionality Added or Changed Replication: The new system variable binlog_impossible_mode controls what happens if the server cannot write to the binary log, for example, due to a file error. For backward compatibility, the default for binlog_impossible_mode is IGNORE_ERROR, meaning the server logs the error, halts logging, and continues updates to the database. Setting this variable to ABORT_SERVER makes the server halt logging and shut down if it cannot write to the binary log. CMake support was updated to handle CMake version 3. New Debian7, Ubuntu12.04, and Ubuntu14.04 distribution support that was introduced with 5.6.17 now comes with the platform-specific packaging source placed under the packaging directory, in the deb-precise, deb-wheezy, and deb-trusty directories. Support for LinuxThreads has been removed from the source code. LinuxThreads was superseded by NPTL in Linux 2.6. By default, mysql_install_db creates a my.cnf file in the installation base directory using a template. This may be undesireable for some deployments. To enable this behavior to be suppressed, mysql_install_db now supports a --keep-my-cnf option to preserve any existing my.cnf file and not create a new my.cnf file. The mysqlhotcopy utility is now deprecated and will be removed in a future version of MySQL. Among the reasons for this: It works only for the MyISAM and ARCHIVE storage engines; it works on Unix but not Windows. Alternatives include mysqldump and MySQL Enterprise Backup. The timed_mutexes system variable has no effect and is deprecated. Bugs Fixed
2014-08-10 17:11:57 +02:00
share/mysql/test/t/mysqlbinlog_debug.test
Changes 5.6.22: * Noisy compiler warnings on FreeBSD 10 were silenced. * CMake workarounds for older Mac OS X and XCode versions were removed. On Mac OS X, compilation always uses Clang, even for 32-bit builds. * Previously, the MYSQL_MAINTAINER_MODE CMake option was turned on by default for debug builds and off for release builds, and MYSQL_MAINTAINER_MODE caused -Werror to be enabled when building with GCC. This made it cumbersome to enable -Werror under certain conditions, such as when compiling with Clang. * Build support was modified to produce the same warnings for Clang as for gcc. * CMake configuration for the Clang compiler sets more appropriate flags for building on Linux. Specifically, -g -fno-omit-frame-pointer -fno-strict-aliasing is now added. * Bugs fixed.
2014-12-02 13:40:09 +01:00
share/mysql/test/t/mysqlbinlog_mixed_or_statment.test
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/t/mysqlbinlog_raw_mode.test
share/mysql/test/t/mysqlbinlog_raw_mode_win.test
share/mysql/test/t/mysqlbinlog_row_big.test
share/mysql/test/t/mysqlcheck.test
share/mysql/test/t/mysqld--defaults-file.test
share/mysql/test/t/mysqld--help-notwin.test
share/mysql/test/t/mysqld--help-win.test
share/mysql/test/t/mysqldump-compat.opt
share/mysql/test/t/mysqldump-compat.test
share/mysql/test/t/mysqldump-max-master.opt
share/mysql/test/t/mysqldump-max.test
share/mysql/test/t/mysqldump-no-binlog-master.opt
share/mysql/test/t/mysqldump-no-binlog.test
share/mysql/test/t/mysqldump.test
share/mysql/test/t/mysqldump_restore.test
share/mysql/test/t/mysqlhotcopy_archive.test
share/mysql/test/t/mysqlhotcopy_myisam.test
share/mysql/test/t/mysqlimport.test
share/mysql/test/t/mysqlshow.test
share/mysql/test/t/mysqlslap.test
share/mysql/test/t/mysqltest.test
share/mysql/test/t/named_pipe-master.opt
share/mysql/test/t/named_pipe.test
share/mysql/test/t/negation_elimination.test
share/mysql/test/t/no-threads-master.opt
share/mysql/test/t/no-threads.test
share/mysql/test/t/no_binlog.test
share/mysql/test/t/not_embedded_server-master.opt
share/mysql/test/t/not_embedded_server.test
share/mysql/test/t/not_partition.test
share/mysql/test/t/null.test
share/mysql/test/t/null_key_all.test
share/mysql/test/t/null_key_icp.test
share/mysql/test/t/null_key_none.test
share/mysql/test/t/odbc.test
share/mysql/test/t/olap.test
share/mysql/test/t/openssl_1.test
share/mysql/test/t/optimizer_bug12837084.test
share/mysql/test/t/optimizer_debug_sync.test
share/mysql/test/t/optimizer_switch.test
share/mysql/test/t/order_by_all.test
share/mysql/test/t/order_by_icp_mrr.test
share/mysql/test/t/order_by_none.test
share/mysql/test/t/order_by_sortkey.test
share/mysql/test/t/order_fill_sortbuf-master.opt
share/mysql/test/t/order_fill_sortbuf.test
share/mysql/test/t/outfile.test
share/mysql/test/t/outfile_loaddata.test
share/mysql/test/t/overflow.test
share/mysql/test/t/packet.test
share/mysql/test/t/parser.test
share/mysql/test/t/parser_bug21114_innodb.test
share/mysql/test/t/parser_not_embedded.test
share/mysql/test/t/parser_precedence.test
share/mysql/test/t/parser_stack.test
share/mysql/test/t/partition.test
share/mysql/test/t/partition_archive.test
share/mysql/test/t/partition_binlog.test
share/mysql/test/t/partition_binlog_stmt.test
share/mysql/test/t/partition_blackhole.test
share/mysql/test/t/partition_bug18198.test
share/mysql/test/t/partition_cache-master.opt
share/mysql/test/t/partition_cache.test
share/mysql/test/t/partition_charset.test
share/mysql/test/t/partition_column.test
share/mysql/test/t/partition_column_prune.test
share/mysql/test/t/partition_csv.test
share/mysql/test/t/partition_datatype.test
share/mysql/test/t/partition_debug_sync.test
share/mysql/test/t/partition_disabled-master.opt
share/mysql/test/t/partition_disabled.test
share/mysql/test/t/partition_error.test
share/mysql/test/t/partition_exchange.test
share/mysql/test/t/partition_explicit_prune.test
share/mysql/test/t/partition_federated.test
share/mysql/test/t/partition_grant.test
share/mysql/test/t/partition_hash.test
Changes 5.6.17: Functionality Added or Changed Incompatible Change: The AES_ENCRYPT() and AES_DECRYPT() functions now permit control of the block encryption mode and take an optional initialization vector argument: The new block_encryption_mode system variable controls the mode for block-based encryption algorithms. Its default value is aes-128-ecb, which signifies encryption using a key length of 128 bits and ECB mode. An optional init_vector argument provides an initialization vector for encryption modes that require it: AES_ENCRYPT(str,key_str[,init_vector]) AES_DECRYPT(crypt_str,key_str[,init_vector]) A random string of bytes to use for the initialization vector can be produced by calling the new RANDOM_BYTES() function. For more information, see Encryption and Compression Functions. These changes make statements that use AES_ENCRYPT() or AES_DECRYPT() unsafe for statement-based replication and they cannot be stored in the query cache. Queries that use RANDOM_BYTES() are unsafe for statement-based replication and cannot be stored in the query cache. Incompatible Change: The ERROR_FOR_DIVISION_BY_ZERO, NO_ZERO_DATE, and NO_ZERO_IN_DATE SQL modes now are deprecated and setting the sql_mode value to include any of them generates a warning. In MySQL 5.7, these modes do nothing. Instead, their effects are included in the effects of strict SQL mode (STRICT_ALL_TABLES or STRICT_TRANS_TABLES). The motivation for the change in MySQL 5.7 is to reduce the number of SQL modes with an effect dependent on strict mode and make them part of strict mode itself. To make advance preparation for an upgrade to MySQL 5.7, see SQL Mode Changes in MySQL 5.7. That discussion provides guidelines to assess whether your applications will be affected by the SQL mode changes in MySQL 5.7. InnoDB: MySQL now supports rebuilding regular and partitioned InnoDB tables using online DDL (ALGORITHM=INPLACE) for the following operations: OPTIMIZE TABLE ALTER TABLE ... FORCE ALTER TABLE ... ENGINE=INNODB (when run on an InnoDB table) Online DDL support reduces table rebuild time and permits concurrent DML, which helps reduce user application downtime. For additional information, see Overview of Online DDL. On Solaris, mysql_config --libs now includes -R/path/to/library so that libraries can be found at runtime. mysql_install_db provides a more informative diagnostic message when required Perl modules are missing. The IGNORE clause for ALTER TABLE is now deprecated and will be removed in a future version of MySQL. ALTER IGNORE TABLE causes problems for replication, prevents online ALTER TABLE for unique index creation, and causes problems with foreign keys (rows removed in the parent table). Bugs Fixed
2014-03-31 12:32:13 +02:00
share/mysql/test/t/partition_index_innodb.test
share/mysql/test/t/partition_index_myisam.test
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/t/partition_innodb.test
share/mysql/test/t/partition_innodb_plugin.test
share/mysql/test/t/partition_innodb_semi_consistent-master.opt
share/mysql/test/t/partition_innodb_semi_consistent.test
share/mysql/test/t/partition_innodb_stmt.test
share/mysql/test/t/partition_innodb_tablespace.test
share/mysql/test/t/partition_key_cache.test
share/mysql/test/t/partition_list.test
share/mysql/test/t/partition_locking.test
share/mysql/test/t/partition_locking_4.test
share/mysql/test/t/partition_mgm.test
share/mysql/test/t/partition_mgm_err.test
share/mysql/test/t/partition_mgm_err2.test
share/mysql/test/t/partition_myisam.test
share/mysql/test/t/partition_not_blackhole-master.opt
share/mysql/test/t/partition_not_blackhole.test
share/mysql/test/t/partition_not_windows-master.opt
share/mysql/test/t/partition_not_windows.test
share/mysql/test/t/partition_open_files_limit-master.opt
share/mysql/test/t/partition_open_files_limit.test
share/mysql/test/t/partition_order.test
share/mysql/test/t/partition_pruning.test
share/mysql/test/t/partition_range.test
share/mysql/test/t/partition_rename_longfilename.test
share/mysql/test/t/partition_symlink.test
share/mysql/test/t/partition_sync.test
share/mysql/test/t/partition_truncate.test
share/mysql/test/t/partition_utf8.test
share/mysql/test/t/partition_windows.test
share/mysql/test/t/perror-win.test
share/mysql/test/t/perror.test
share/mysql/test/t/plugin-master.opt
share/mysql/test/t/plugin.test
share/mysql/test/t/plugin_auth-master.opt
share/mysql/test/t/plugin_auth.test
share/mysql/test/t/plugin_auth_qa-master.opt
share/mysql/test/t/plugin_auth_qa.test
share/mysql/test/t/plugin_auth_qa_1-master.opt
share/mysql/test/t/plugin_auth_qa_1.test
share/mysql/test/t/plugin_auth_qa_2-master.opt
share/mysql/test/t/plugin_auth_qa_2.test
share/mysql/test/t/plugin_auth_qa_3-master.opt
share/mysql/test/t/plugin_auth_qa_3.test
share/mysql/test/t/plugin_auth_sha256-master.opt
share/mysql/test/t/plugin_auth_sha256.test
share/mysql/test/t/plugin_auth_sha256_2-master.opt
share/mysql/test/t/plugin_auth_sha256_2.test
share/mysql/test/t/plugin_auth_sha256_server_default-master.opt
share/mysql/test/t/plugin_auth_sha256_server_default.test
share/mysql/test/t/plugin_auth_sha256_server_default_tls-master.opt
share/mysql/test/t/plugin_auth_sha256_server_default_tls.test
share/mysql/test/t/plugin_auth_sha256_tls.test
share/mysql/test/t/plugin_load-master.opt
share/mysql/test/t/plugin_load.test
share/mysql/test/t/plugin_load_option-master.opt
share/mysql/test/t/plugin_load_option.test
share/mysql/test/t/plugin_not_embedded-master.opt
share/mysql/test/t/plugin_not_embedded.test
share/mysql/test/t/preload.test
share/mysql/test/t/profiling.test
share/mysql/test/t/ps-master.opt
share/mysql/test/t/ps.test
share/mysql/test/t/ps_10nestset.test
share/mysql/test/t/ps_11bugs.test
share/mysql/test/t/ps_1general.test
share/mysql/test/t/ps_2myisam.test
share/mysql/test/t/ps_3innodb-master.opt
share/mysql/test/t/ps_3innodb.test
share/mysql/test/t/ps_4heap.test
share/mysql/test/t/ps_5merge.test
share/mysql/test/t/ps_ddl.test
share/mysql/test/t/ps_ddl1.test
share/mysql/test/t/ps_grant.test
share/mysql/test/t/ps_not_windows.test
share/mysql/test/t/query_cache-master.opt
share/mysql/test/t/query_cache.test
share/mysql/test/t/query_cache_28249-master.opt
share/mysql/test/t/query_cache_28249.test
share/mysql/test/t/query_cache_debug-master.opt
share/mysql/test/t/query_cache_debug.test
share/mysql/test/t/query_cache_disabled-master.opt
share/mysql/test/t/query_cache_disabled.test
share/mysql/test/t/query_cache_merge-master.opt
share/mysql/test/t/query_cache_merge.test
share/mysql/test/t/query_cache_notembedded-master.opt
share/mysql/test/t/query_cache_notembedded.test
share/mysql/test/t/query_cache_ps_no_prot-master.opt
share/mysql/test/t/query_cache_ps_no_prot.test
share/mysql/test/t/query_cache_ps_ps_prot-master.opt
share/mysql/test/t/query_cache_ps_ps_prot.test
share/mysql/test/t/query_cache_size_functionality.test
share/mysql/test/t/query_cache_type_functionality.test
share/mysql/test/t/query_cache_with_views-master.opt
share/mysql/test/t/query_cache_with_views.test
share/mysql/test/t/range_all.test
share/mysql/test/t/range_icp.test
share/mysql/test/t/range_icp_mrr.test
share/mysql/test/t/range_mrr.test
share/mysql/test/t/range_mrr_cost.test
share/mysql/test/t/range_none.test
share/mysql/test/t/read_many_rows_innodb.test
share/mysql/test/t/read_only.test
share/mysql/test/t/read_only_innodb.test
share/mysql/test/t/rename.test
share/mysql/test/t/renamedb.test
share/mysql/test/t/repair.test
share/mysql/test/t/replace.test
share/mysql/test/t/rewrite_general_log.test
share/mysql/test/t/rewrite_slow_log.test
share/mysql/test/t/rollback.test
share/mysql/test/t/round.test
share/mysql/test/t/row.test
share/mysql/test/t/rowid_order_innodb.test
share/mysql/test/t/rpl_mysqldump_slave.test
share/mysql/test/t/schema.test
share/mysql/test/t/secure_file_priv_win-master.opt
share/mysql/test/t/secure_file_priv_win.test
share/mysql/test/t/select_all.test
share/mysql/test/t/select_all_bka.test
share/mysql/test/t/select_all_bka_nixbnl.test
share/mysql/test/t/select_found.test
share/mysql/test/t/select_icp_mrr.test
share/mysql/test/t/select_icp_mrr_bka.test
share/mysql/test/t/select_icp_mrr_bka_nixbnl.test
share/mysql/test/t/select_none.test
share/mysql/test/t/select_none_bka.test
share/mysql/test/t/select_none_bka_nixbnl.test
share/mysql/test/t/select_safe.test
share/mysql/test/t/server_uuid.test
share/mysql/test/t/server_uuid_embedded.test
share/mysql/test/t/shm-master.opt
share/mysql/test/t/shm.test
share/mysql/test/t/show_check-master.opt
share/mysql/test/t/show_check.test
Changes 5.6.20: Security Fix: The linked OpenSSL library for the MySQL 5.6 Commercial Server has been updated from version 1.0.1g to version 1.0.1h. Versions of OpenSSL prior to and including 1.0.1g are reported to be vulnerable to CVE-2014-0224. This change does not affect the Oracle-produced MySQL Community build of MySQL Server 5.6, which uses the yaSSL library instead. DTrace Support MySQL now includes DTrace support on Oracle Linux 6 or higher with UEK kernel. If DTrace is present, server builds will detect it with no special CMake options required. For information about using DTrace on MySQL, see Tracing mysqld Using DTrace. InnoDB Notes Important Change: Redo log writes for large, externally stored BLOB fields could overwrite the most recent checkpoint. The 5.6.20 patch limits the size of redo log BLOB writes to 10% of the redo log file size. The 5.7.5 patch addresses the bug without imposing a limitation. For MySQL 5.5, the bug remains a known limitation. As a result of the redo log BLOB write limit introduced for MySQL 5.6, innodb_log_file_size should be set to a value greater than 10 times the largest BLOB data size found in the rows of your tables plus the length of other variable length fields (VARCHAR, VARBINARY, and TEXT type fields). Failing to do so could result in “Row size too large” errors. No action is required if your innodb_log_file_size setting is already sufficiently large or your tables contain no BLOB data. Functionality Added or Changed Replication: The new system variable binlog_impossible_mode controls what happens if the server cannot write to the binary log, for example, due to a file error. For backward compatibility, the default for binlog_impossible_mode is IGNORE_ERROR, meaning the server logs the error, halts logging, and continues updates to the database. Setting this variable to ABORT_SERVER makes the server halt logging and shut down if it cannot write to the binary log. CMake support was updated to handle CMake version 3. New Debian7, Ubuntu12.04, and Ubuntu14.04 distribution support that was introduced with 5.6.17 now comes with the platform-specific packaging source placed under the packaging directory, in the deb-precise, deb-wheezy, and deb-trusty directories. Support for LinuxThreads has been removed from the source code. LinuxThreads was superseded by NPTL in Linux 2.6. By default, mysql_install_db creates a my.cnf file in the installation base directory using a template. This may be undesireable for some deployments. To enable this behavior to be suppressed, mysql_install_db now supports a --keep-my-cnf option to preserve any existing my.cnf file and not create a new my.cnf file. The mysqlhotcopy utility is now deprecated and will be removed in a future version of MySQL. Among the reasons for this: It works only for the MyISAM and ARCHIVE storage engines; it works on Unix but not Windows. Alternatives include mysqldump and MySQL Enterprise Backup. The timed_mutexes system variable has no effect and is deprecated. Bugs Fixed
2014-08-10 17:11:57 +02:00
share/mysql/test/t/show_processlist.test
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/t/show_profile.test
share/mysql/test/t/signal.test
share/mysql/test/t/signal_code.test
share/mysql/test/t/signal_demo1.test
share/mysql/test/t/signal_demo2.test
share/mysql/test/t/signal_demo3-master.opt
share/mysql/test/t/signal_demo3.test
share/mysql/test/t/signal_sqlmode.test
share/mysql/test/t/single_delete_update.test
share/mysql/test/t/skip_grants-master.opt
share/mysql/test/t/skip_grants.test
share/mysql/test/t/skip_log_bin-master.opt
share/mysql/test/t/skip_log_bin.test
share/mysql/test/t/skip_name_resolve-master.opt
share/mysql/test/t/skip_name_resolve.test
share/mysql/test/t/sort_buffer_size_functionality.test
share/mysql/test/t/sp-big.test
share/mysql/test/t/sp-bugs.test
share/mysql/test/t/sp-code.test
share/mysql/test/t/sp-destruct.test
share/mysql/test/t/sp-dynamic.test
share/mysql/test/t/sp-error.test
share/mysql/test/t/sp-fib-master.opt
share/mysql/test/t/sp-fib.test
share/mysql/test/t/sp-lock-master.opt
share/mysql/test/t/sp-lock.test
share/mysql/test/t/sp-master.opt
share/mysql/test/t/sp-no-code.test
share/mysql/test/t/sp-prelocking-master.opt
share/mysql/test/t/sp-prelocking.test
share/mysql/test/t/sp-security.test
share/mysql/test/t/sp-threads.test
share/mysql/test/t/sp-ucs2.test
share/mysql/test/t/sp-vars.test
share/mysql/test/t/sp.test
share/mysql/test/t/sp_gis.test
share/mysql/test/t/sp_notembedded-master.opt
share/mysql/test/t/sp_notembedded.test
share/mysql/test/t/sp_stress_case.test
share/mysql/test/t/sp_sync.test
share/mysql/test/t/sp_trans.test
share/mysql/test/t/sp_trans_log.test
share/mysql/test/t/sp_validation.test
share/mysql/test/t/sql_mode.test
share/mysql/test/t/ssl-big.test
Changes 5.6.11: 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. 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. mysql_config_editor now supports --port and --socket options for specifying TCP/IP port number and Unix socket file name. 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. The only supported value for the innodb_mirrored_log_groups system variable is 1, so this variable is now deprecated. Setting it to 1 at startup results in a warning. Setting it to a value other than 1 at startup results in an error and the server exits. This variable will be removed in a future release.
2013-04-20 10:06:01 +02:00
share/mysql/test/t/ssl-sha512-master.opt
share/mysql/test/t/ssl-sha512.test
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/t/ssl.test
share/mysql/test/t/ssl_8k_key-master.opt
share/mysql/test/t/ssl_8k_key.test
share/mysql/test/t/ssl_and_innodb.test
share/mysql/test/t/ssl_cipher-master.opt
share/mysql/test/t/ssl_cipher.test
share/mysql/test/t/ssl_compress.test
share/mysql/test/t/ssl_connect.test
share/mysql/test/t/ssl_crl-master.opt
share/mysql/test/t/ssl_crl.test
share/mysql/test/t/ssl_crl_clients-master.opt
share/mysql/test/t/ssl_crl_clients.test
share/mysql/test/t/ssl_crl_clients_valid-master.opt
share/mysql/test/t/ssl_crl_clients_valid.test
share/mysql/test/t/ssl_crl_crlpath-master.opt
share/mysql/test/t/ssl_crl_crlpath.test
share/mysql/test/t/status-master.opt
share/mysql/test/t/status.test
share/mysql/test/t/status2.test
share/mysql/test/t/status_bug17954.test
Changes 5.6.26: * Security Fix: Due to the LogJam issue (https://weakdh.org/), OpenSSL has changed the Diffie-Hellman key length parameters for openssl-1.0.1n and up. * Replication: When using a multi-threaded slave, each worker thread has its own queue of transactions to process. In previous MySQL versions, STOP SLAVE waited for all workers to process their entire queue. This logic has been changed so that STOP SLAVE first finds the newest transaction that was committed by any worker thread. Then, it waits for all workers to complete transactions older than that. Newer transactions are not processed. The new logic allows STOP SLAVE to complete faster in case some worker queues contain multiple transactions. * Previously, the max_digest_length system variable controlled the maximum digest length for all server functions that computed statement digests. However, whereas the Performance Schema may need to maintain many digest values, other server functions such as MySQL Enterprise Firewall need only one digest per session. Increasing the max_digest_length value has little impact on total memory requirements for those functions, but can increase Performance Schema memory requirements significantly. To enable configuring digest length separately for the Performance Schema, its digest length is now controlled by the new performance_schema_max_digest_length system variable. * Previously, changes to the validate_password plugin dictionary file (named by the validate_password_dictionary_file system variable) while the server was running required a restart for the server to recognize the changes. Now validate_password_dictionary_file can be set at runtime and assigning a value causes the named file to be read without a restart. In addition, two new status variables are available. validate_password_dictionary_file_last_parsed indicates when the dictionary file was last read, and validate_password_dictionary_file_words_count indicates how many words it contains. * Bugs fixed
2015-07-30 16:39:18 +02:00
share/mysql/test/t/status_debug.test
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/t/strict-master.opt
share/mysql/test/t/strict.test
share/mysql/test/t/strict_autoinc_1myisam.test
share/mysql/test/t/strict_autoinc_2innodb.test
share/mysql/test/t/strict_autoinc_3heap.test
share/mysql/test/t/subquery_all.test
share/mysql/test/t/subquery_all_bka.test
share/mysql/test/t/subquery_all_bka_nixbnl.test
share/mysql/test/t/subquery_mat.test
share/mysql/test/t/subquery_mat_all.test
share/mysql/test/t/subquery_mat_none.test
share/mysql/test/t/subquery_nomat_nosj.test
share/mysql/test/t/subquery_nomat_nosj_bka.test
share/mysql/test/t/subquery_nomat_nosj_bka_nixbnl.test
share/mysql/test/t/subquery_none.test
share/mysql/test/t/subquery_none_bka.test
share/mysql/test/t/subquery_none_bka_nixbnl.test
share/mysql/test/t/subquery_sj_all-master.opt
share/mysql/test/t/subquery_sj_all.test
share/mysql/test/t/subquery_sj_all_bka-master.opt
share/mysql/test/t/subquery_sj_all_bka.test
share/mysql/test/t/subquery_sj_all_bka_nixbnl-master.opt
share/mysql/test/t/subquery_sj_all_bka_nixbnl.test
share/mysql/test/t/subquery_sj_all_bkaunique-master.opt
share/mysql/test/t/subquery_sj_all_bkaunique.test
share/mysql/test/t/subquery_sj_dupsweed-master.opt
share/mysql/test/t/subquery_sj_dupsweed.test
share/mysql/test/t/subquery_sj_dupsweed_bka-master.opt
share/mysql/test/t/subquery_sj_dupsweed_bka.test
share/mysql/test/t/subquery_sj_dupsweed_bka_nixbnl-master.opt
share/mysql/test/t/subquery_sj_dupsweed_bka_nixbnl.test
share/mysql/test/t/subquery_sj_dupsweed_bkaunique-master.opt
share/mysql/test/t/subquery_sj_dupsweed_bkaunique.test
share/mysql/test/t/subquery_sj_firstmatch-master.opt
share/mysql/test/t/subquery_sj_firstmatch.test
share/mysql/test/t/subquery_sj_firstmatch_bka-master.opt
share/mysql/test/t/subquery_sj_firstmatch_bka.test
share/mysql/test/t/subquery_sj_firstmatch_bka_nixbnl.test
share/mysql/test/t/subquery_sj_firstmatch_bkaunique.test
share/mysql/test/t/subquery_sj_innodb_all.test
share/mysql/test/t/subquery_sj_innodb_all_bka.test
share/mysql/test/t/subquery_sj_innodb_all_bka_nixbnl.test
share/mysql/test/t/subquery_sj_innodb_all_bkaunique.test
share/mysql/test/t/subquery_sj_innodb_none.test
share/mysql/test/t/subquery_sj_innodb_none_bka.test
share/mysql/test/t/subquery_sj_innodb_none_bka_nixbnl.test
share/mysql/test/t/subquery_sj_innodb_none_bkaunique.test
share/mysql/test/t/subquery_sj_loosescan.test
share/mysql/test/t/subquery_sj_loosescan_bka.test
share/mysql/test/t/subquery_sj_loosescan_bka_nixbnl.test
share/mysql/test/t/subquery_sj_loosescan_bkaunique.test
share/mysql/test/t/subquery_sj_mat.test
share/mysql/test/t/subquery_sj_mat_bka.test
share/mysql/test/t/subquery_sj_mat_bka_nixbnl.test
share/mysql/test/t/subquery_sj_mat_bkaunique.test
share/mysql/test/t/subquery_sj_mat_nosj.test
share/mysql/test/t/subquery_sj_none.test
share/mysql/test/t/subquery_sj_none_bka.test
share/mysql/test/t/subquery_sj_none_bka_nixbnl.test
share/mysql/test/t/subquery_sj_none_bkaunique.test
share/mysql/test/t/subselect_debug.test
share/mysql/test/t/subselect_gis.test
share/mysql/test/t/subselect_innodb.test
share/mysql/test/t/subselect_notembedded-master.opt
share/mysql/test/t/subselect_notembedded.test
share/mysql/test/t/sum_distinct-big.test
share/mysql/test/t/sum_distinct.test
share/mysql/test/t/symlink.test
share/mysql/test/t/symlink_windows.test
share/mysql/test/t/synchronization.test
share/mysql/test/t/sysdate_is_now-master.opt
share/mysql/test/t/sysdate_is_now.test
share/mysql/test/t/system_mysql_db.test
share/mysql/test/t/system_mysql_db_fix30020-master.opt
share/mysql/test/t/system_mysql_db_fix40123-master.opt
share/mysql/test/t/system_mysql_db_fix40123.test
share/mysql/test/t/system_mysql_db_fix50030-master.opt
share/mysql/test/t/system_mysql_db_fix50030.test
share/mysql/test/t/system_mysql_db_fix50117-master.opt
share/mysql/test/t/system_mysql_db_fix50117.test
share/mysql/test/t/system_mysql_db_refs.test
share/mysql/test/t/table_definition_cache_functionality.test
share/mysql/test/t/table_open_cache_functionality.test
share/mysql/test/t/tablelock.test
share/mysql/test/t/tablespace.test
Changes 5.6.23: * The linked OpenSSL library for the MySQL Commercial Server has been updated from version 1.0.1j to version 1.0.1k. * Support for the SSL 2.0 and SSL 3.0 protocols has been disabled because they provide weak encryption. * yaSSL was upgraded to version 2.3.7. * The valid date range of the SSL certificates in mysql-test/std_data has been extended to the year 2029. * Bugs Fixed
2015-02-07 20:23:40 +01:00
share/mysql/test/t/temp_pool-master.opt
share/mysql/test/t/temp_pool.test
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/t/temp_table-master.opt
share/mysql/test/t/temp_table.test
share/mysql/test/t/temporal_literal.test
share/mysql/test/t/timezone-master.opt
share/mysql/test/t/timezone.test
share/mysql/test/t/timezone2.test
share/mysql/test/t/timezone3-master.opt
share/mysql/test/t/timezone3.test
share/mysql/test/t/timezone4-master.opt
share/mysql/test/t/timezone4.test
share/mysql/test/t/timezone_grant.test
share/mysql/test/t/trans_read_only-master.opt
share/mysql/test/t/trans_read_only.test
share/mysql/test/t/trigger-compat.test
share/mysql/test/t/trigger-trans.test
share/mysql/test/t/trigger.test
share/mysql/test/t/trigger_notembedded.test
share/mysql/test/t/truncate.test
share/mysql/test/t/truncate_coverage.test
share/mysql/test/t/type_binary.test
share/mysql/test/t/type_bit.test
share/mysql/test/t/type_bit_innodb.test
share/mysql/test/t/type_blob.test
share/mysql/test/t/type_date.test
share/mysql/test/t/type_datetime.test
share/mysql/test/t/type_decimal.test
share/mysql/test/t/type_enum.test
share/mysql/test/t/type_float.test
share/mysql/test/t/type_nchar.test
share/mysql/test/t/type_newdecimal-big.test
share/mysql/test/t/type_newdecimal.test
share/mysql/test/t/type_ranges.test
share/mysql/test/t/type_set.test
share/mysql/test/t/type_temporal_fractional.test
share/mysql/test/t/type_temporal_upgrade.test
share/mysql/test/t/type_time.test
share/mysql/test/t/type_timestamp-master.opt
share/mysql/test/t/type_timestamp.test
Changes 5.6.11: 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. 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. mysql_config_editor now supports --port and --socket options for specifying TCP/IP port number and Unix socket file name. 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. The only supported value for the innodb_mirrored_log_groups system variable is 1, so this variable is now deprecated. Setting it to 1 at startup results in a warning. Setting it to a value other than 1 at startup results in an error and the server exits. This variable will be removed in a future release.
2013-04-20 10:06:01 +02:00
share/mysql/test/t/type_timestamp_explicit-master.opt
share/mysql/test/t/type_timestamp_explicit.test
Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html
2013-02-13 22:00:01 +01:00
share/mysql/test/t/type_uint.test
share/mysql/test/t/type_varchar.test
share/mysql/test/t/type_year.test
share/mysql/test/t/udf-master.opt
share/mysql/test/t/udf.test
share/mysql/test/t/udf_skip_grants-master.opt
share/mysql/test/t/udf_skip_grants.test
share/mysql/test/t/union-master.opt
share/mysql/test/t/union.test
share/mysql/test/t/unsafe_binlog_innodb-master.opt
share/mysql/test/t/unsafe_binlog_innodb.test
share/mysql/test/t/update.test
share/mysql/test/t/upgrade.test
share/mysql/test/t/user_limits.test
share/mysql/test/t/user_var-binlog.test
share/mysql/test/t/user_var.test
share/mysql/test/t/validate_password_plugin-master.opt
share/mysql/test/t/validate_password_plugin.test
share/mysql/test/t/varbinary.test
share/mysql/test/t/variables-big.test
share/mysql/test/t/variables-master.opt
share/mysql/test/t/variables-notembedded-master.opt
share/mysql/test/t/variables-notembedded.test
share/mysql/test/t/variables.test
share/mysql/test/t/variables_community.test
share/mysql/test/t/variables_debug.test
share/mysql/test/t/view.test
share/mysql/test/t/view_alias.test
share/mysql/test/t/view_grant.test
share/mysql/test/t/wait_timeout.test
share/mysql/test/t/warnings-master.opt
share/mysql/test/t/warnings.test
share/mysql/test/t/warnings_engine_disabled.test
share/mysql/test/t/windows.test
share/mysql/test/t/wl4435_generated.inc
share/mysql/test/t/wl6219-csv.test
share/mysql/test/t/wl6219-innodb.test
share/mysql/test/t/wl6219-memory.test
share/mysql/test/t/wl6219-merge.test
share/mysql/test/t/wl6219-myisam.test
share/mysql/test/t/wl6219-upgrade.test
share/mysql/test/t/wl6301_1_not_windows-master.opt
share/mysql/test/t/wl6301_1_not_windows.test
share/mysql/test/t/wl6301_2_not_windows-master.opt
share/mysql/test/t/wl6301_2_not_windows.test
share/mysql/test/t/wl6301_3-master.opt
share/mysql/test/t/wl6301_3.test
share/mysql/test/t/wl6443_deprecation-master.opt
share/mysql/test/t/wl6443_deprecation.test
share/mysql/test/t/xa.test
share/mysql/test/t/xml.test
share/mysql/test/valgrind.supp
share/mysql/ukrainian/errmsg.sys
Reference in a new issue Copy permalink