pkgsrc/databases/mysql55-server/PLIST

6368 lines
335 KiB
Text
Raw Normal View History

Security Notes * Security Fix: The linked OpenSSL library for the MySQL Commercial Server has been updated to version 1.0.2l. Issues fixed in the new OpenSSL version are described at http://www.openssl.org/news/vulnerabilities.html. This change does not affect the Oracle-produced MySQL Community build of MySQL Server, which uses the yaSSL library instead. Platform-Specific Notes * Linux: The generic Linux build for MySQL 5.6 is now built on Oracle Linux 6 using glibc 2.12. Systems that use the build need to have glibc 2.12 or later installed on them. Functionality Added or Changed * For Windows, MSI installer packages now include a check for the required Visual Studio redistributable package, and produce a message asking the user to install it if it is missing. * The mysql client now supports a --binary-as-hex option that causes display of binary data using hexadecimal notation (0xvalue). Thanks to Daniël van Eeden for the patch. * mysqlaccess now looks for its configuration file only in the SYSCONFDIR directory and /etc. Bugs Fixed * InnoDB: The server allocated memory unnecessarily for an operation that rebuilt the table. * InnoDB: When using an index merge optimizer switch, a SELECT COUNT(*) operation sometimes returned 0. Partitioning code incorrectly performed a memcpy instead of a column copy of columns read by the index, causing the wrong records to be copied. * Replication: A USE statement that followed a SET GTID_NEXT statement sometimes had no effect. * Replication: If the binary log on a master server was rotated and a full disk condition occurred on the partition where the binary log file was being stored, the server could stop unexpectedly. The fix adds a check for the existence of the binary log when the dump thread switches to next binary log file. If the binary log is disabled, all binary logs up to the current active log are transmitted to slave and an error is returned to the receiver thread. * Replication: If a relay log index file named relay log files that did not exist, RESET SLAVE ALL sometimes did not fully clean up properly. * Replication: mysqlbinlog, if invoked with the --raw option, does not flush the output file until the process terminates. But if also invoked with the --stop-never option, the process never terminates, thus nothing is ever written to the output file. Now the output is flushed after each event. * Replication: A memory leak in mysqlbinlog was fixed. The leak happened when processing fake rotate events, or when using --raw and the destination log file could not be created. The leak only occurred when processing events from a remote server. Thanks to Laurynas Biveinis for his contribution to fixing this bug. * Replication: Multi-threaded slaves could not be configured with small queue sizes using slave_pending_jobs_size_max if they ever needed to process transactions larger than that size. Any packet larger than slave_pending_jobs_size_max was rejected with the error ER_MTS_EVENT_BIGGER_PENDING_JOBS_SIZE_MAX, even if the packet was smaller than the limit set by slave_max_allowed_packet. * With this fix, slave_pending_jobs_size_max becomes a soft limit rather than a hard limit. If the size of a packet exceeds slave_pending_jobs_size_max but is less than slave_max_allowed_packet, the transaction is held until all the slave workers have empty queues, and then processed. All subsequent transactions are held until the large transaction has been completed. The queue size for slave workers can therefore be limited while still allowing occasional larger transactions. * mysqldump could write database names in USE statements incorrectly. * If the mysql_stmt_close() C API function was called, it freed memory that later could be accessed if mysql_stmt_error(), mysql_stmt_errno(), or mysql_stmt_sqlstate() was called. To obtain error information after a call to mysql_stmt_close(), call mysql_error(), mysql_errno(), or mysql_sqlstate() instead. * Queries could be cached incorrectly, leading to incorrect query results, under these circumstances: InnoDB table; rows are being inserted but have not yet been committed; a query uses the table as a base table in a derived table; the optimizer chooses to materialize the derived table. * Man pages for a few utilities were missing from Debian/Ubuntu packages. * The field-t unit test failed to run with AddressSanitizer enabled. Thanks to Laurynas Biveinis for the patch. * Debian client packages were missing information about conflicts with native packages. * The Perl path in #! lines at the beginning of Perl scripts has been adjusted to /usr/local/bin/perl for FreeBSD 11. * The server exited abnormally attempting to access invalid memory. * A race condition could occur for CREATE TABLE statements with DATA DIRECTORY or INDEX DIRECTORY clauses. * MySQL compilation in different directories produced different builds to leakage of absolute paths into debug information and __FILE__. * mysqld_failed to start the server if the --datadir option was specified with a relative path name. * With read_only enabled, creation of non-TEMPORARY tables by non-SUPER users was permitted under certain conditions. *Certain stored functions, if used in a query WHERE clause, could be handled using Index Condition Pushdown (which should not happen), resulting in a server exit. * On x86 machines, the uint3korr() macro read 4 bytes of data instead of the intended 3 bytes. * An assertion was raised during a fetch operation by the memcached plugin. * Queries that contained UNION in a subquery and GROUP BY could return incorrect results. * LOAD XML INFILE performance became noticeably slower when the XML file being read contained a great many spaces, such as those introduced by indenting or pretty-printing. Now all leading whitespace is trimmed from each such value before reading it into memory.
2017-07-19 20:48:21 +02:00
@comment $NetBSD: PLIST,v 1.47 2017/07/19 18:48:22 adam Exp $
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
2012-02-16 15:47:01 +01:00
${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
lib/mysql/plugin/ha_archive.so
lib/mysql/plugin/ha_blackhole.so
lib/mysql/plugin/ha_example.so
lib/mysql/plugin/ha_federated.so
${PLIST.sphinx}lib/mysql/plugin/ha_sphinx.so
lib/mysql/plugin/libdaemon_example.so
lib/mysql/plugin/mypluglib.so
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
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/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/config.huge.ini
share/mysql/config.medium.ini
share/mysql/config.small.ini
share/mysql/czech/errmsg.sys
share/mysql/danish/errmsg.sys
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/italian/errmsg.sys
share/mysql/japanese/errmsg.sys
share/mysql/korean/errmsg.sys
share/mysql/magic
share/mysql/my-huge.cnf
share/mysql/my-innodb-heavy-4G.cnf
share/mysql/my-large.cnf
share/mysql/my-medium.cnf
share/mysql/my-small.cnf
share/mysql/mysql-log-rotate
share/mysql/mysql.server
share/mysql/mysqld_multi.server
share/mysql/ndb-config-2-node.ini
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
share/mysql/test/collections/default.experimental
share/mysql/test/collections/default.push
share/mysql/test/collections/default.release
share/mysql/test/collections/default.release.done
share/mysql/test/collections/default.weekly
share/mysql/test/collections/disabled-daily.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
share/mysql/test/extra/binlog_tests/binlog_insert_delayed.test
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/rpl_tests/check_type.inc
share/mysql/test/extra/rpl_tests/create_recursive_construct.inc
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
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_charset.test
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_ddl.test
share/mysql/test/extra/rpl_tests/rpl_deadlock.test
share/mysql/test/extra/rpl_tests/rpl_delete_no_where.test
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_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
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
share/mysql/test/extra/rpl_tests/rpl_loaddata.test
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_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_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_ndb_2multi_basic.test
share/mysql/test/extra/rpl_tests/rpl_ndb_2multi_eng.test
share/mysql/test/extra/rpl_tests/rpl_ndb_apply_status.test
share/mysql/test/extra/rpl_tests/rpl_not_null.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
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_func003.test
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
share/mysql/test/extra/rpl_tests/rpl_stop_middle_group.test
share/mysql/test/extra/rpl_tests/rpl_stop_slave.test
share/mysql/test/extra/rpl_tests/rpl_sv_relay_space.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/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/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
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_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_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/ctype_8bit.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_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_regex.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_ndbd.cnf
share/mysql/test/include/delete_anonymous_users.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/file_does_not_exist.inc
share/mysql/test/include/force_restart.inc
share/mysql/test/include/force_restart_if_skipped.inc
share/mysql/test/include/get_relay_log_pos.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/handler.inc
share/mysql/test/include/have_32bit.inc
share/mysql/test/include/have_64bit.inc
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_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_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_insensitive_fs.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
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_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_gb2312.inc
share/mysql/test/include/have_gbk.inc
share/mysql/test/include/have_geometry.inc
share/mysql/test/include/have_innodb.inc
share/mysql/test/include/have_ipv4_mapped.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_lowercase0.inc
share/mysql/test/include/have_lowercase1.inc
share/mysql/test/include/have_lowercase2.inc
share/mysql/test/include/have_multi_ndb.inc
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
share/mysql/test/include/have_outfile.inc
share/mysql/test/include/have_partition.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_semisync_plugin.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.5.34: * 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.5 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. * 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: 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: InnoDB would rename a user-defined foreign key constraint containing the string “_ibfk_” in its name, resulting in a duplicate constraint. * InnoDB: Rolling back an INSERT after a failed BLOB write would result in an assertion failure. The assertion has been modified to allow NULL BLOB pointers if an error occurs during a BLOB write. * InnoDB: A regression introduced with the fix for Bug 11762038 would cause InnoDB to raise an incorrect error message. The message stated that, “InnoDB cannot delete/update rows with cascading foreign key constraints that exceed max depth of 20”. The error message would occur when killing connections reading from InnoDB tables that did not have foreign key constraints. * InnoDB: The documentation incorrectly stated that START TRANSACTION WITH CONSISTENT SNAPSHOT provides a consistent snapshot only if the current isolation level is REPEATABLE READ or SERIALIZABLE. START TRANSACTION WITH CONSISTENT SNAPSHOT only works with REPEATABLE READ. All other isolation levels are ignored. The documentation has been revised and a warning is now generated whenever the WITH CONSISTENT SNAPSHOT clause is ignored. * InnoDB: The srv_master_thread background thread, which monitors server activity and performs activities such as page flushing when the server is inactive or in a shutdown state, runs on a one second delay loop. srv_master_thread would fail to check if the server is in a shutdown state before sleeping. more...
2013-09-30 20:26:38 +02:00
share/mysql/test/include/have_valgrind.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
share/mysql/test/include/index_merge_ror.inc
share/mysql/test/include/index_merge_ror_cpk.inc
share/mysql/test/include/innodb-index.inc
share/mysql/test/include/innodb_rollback_on_timeout.inc
share/mysql/test/include/innodb_trx_weight.inc
share/mysql/test/include/install_semisync.inc
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/is_embedded.inc
share/mysql/test/include/kill_query.inc
share/mysql/test/include/kill_query_and_diff_master_slave.inc
Changes 5.5.21: * A new CMake option, MYSQL_PROJECT_NAME, can be set on Windows or Mac OS X to be used in the project name. Bugs Fixed * Performance: InnoDB Storage Engine: Memory allocation for InnoDB tables was reorganized to reduce the memory overhead for large numbers of tables or partitions, avoiding situations where the “resident set size” could grow regardless of FLUSH TABLES statements. The problem was most evident for tables with large row size. * Incompatible Change: An earlier change (in MySQL 5.1.62 and 5.5.21) was found to modify date-handling behavior in General Availability-status series (MySQL 5.1 and 5.5). This change has been reverted. * The change was that several functions became more strict when passed a DATE() function value as their argument, thus they rejected incomplete dates with a day part of zero. These functions were affected: CONVERT_TZ(), DATE_ADD(), DATE_SUB(), DAYOFYEAR(), LAST_DAY(), TIMESTAMPDIFF(), TO_DAYS(), TO_SECONDS(), WEEK(), WEEKDAY(), WEEKOFYEAR(), YEARWEEK(). The previous behavior has been restored. * InnoDB Storage Engine: A Valgrind error was fixed in the function os_aio_init(). * InnoDB Storage Engine: The server could crash when creating an InnoDB temporary table under Linux, if the $TMPDIR setting points to a tmpfs filesystem and innodb_use_native_aio is enabled, as it is by default in MySQL 5.5.4 and higher. * InnoDB Storage Engine: References to C preprocessor symbols and macros HAVE_purify, UNIV_INIT_MEM_TO_ZERO, and UNIV_SET_MEM_TO_ZERO were removed from the InnoDB source code. They were only used in debug builds instrumented for Valgrind. They are replaced by calls to the UNIV_MEM_INVALID() macro.
2012-02-23 14:01:03 +01:00
share/mysql/test/include/libdaemon_example.ini
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
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/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/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_print.inc
share/mysql/test/include/ndb_default_cluster.inc
share/mysql/test/include/ndb_master-slave.inc
share/mysql/test/include/ndb_master-slave_2ch.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
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_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_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/one_thread_per_connection.inc
share/mysql/test/include/parser_bug21114.inc
share/mysql/test/include/partition_date_range.inc
share/mysql/test/include/plugin.defs
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/query_cache.inc
share/mysql/test/include/query_cache_sql_prepare.inc
share/mysql/test/include/read_many_rows.inc
Changes 5.5.20: * A new server option, --slow-start-timeout, controls the Windows service control manager's service start timeout. The value is the maximum number of milliseconds that the service control manager waits before trying to kill the MySQL service during startup. The default value is 15000 (15 seconds). If the MySQL service takes too long to start, you may need to increase this value. A value of 0 means there is no timeout. Bugs Fixed: * Important Change: Replication: Setting an empty user in a CHANGE MASTER TO statement caused an invalid internal result and is no longer permitted. Trying to use MASTER_USER='' or setting MASTER_PASSWORD while leaving MASTER_USER unset causes the statement to fail with an error. * Important Change: Replication: Moving the binary log file, relay log file, or both files to a new location, then restarting the server with a new value for --log-bin, --relay-log, or both, caused the server to abort on start. This was because the entries in the index file overrode the new location. In addition, paths were calculated relative to datadir (rather than to the --log-bin or --relay-log values). * InnoDB Storage Engine: When doing a live downgrade from MySQL 5.6.4 or later, with innodb_page_size set to a value other than 16384, now the earlier MySQL version reports that the page size is incompatible with the older version, rather than crashing or displaying a “corruption” error. * InnoDB Storage Engine: Issuing INSERT...ON DUPLICATE KEY statements for InnoDB tables from concurrent threads could cause a deadlock, particularly with the INSERT...ON DUPLICATE KEY UPDATE form. The fix avoids deadlocks caused by the same row being accessed by more than one transaction. Deadlocks could still occur when multiple rows are inserted and updated simultaneously by different transactions in inconsistent order; those types of deadlocks require the standard error handling on the application side, of re-trying the transaction. * An incorrect InnoDB assertion could cause the server to halt. This issue only affected debug builds. The assertion referenced the source file btr0pcur.ic and the variable cursor->pos_state. * Locale information for FORMAT() function instances was lost in view definitions. * The handle_segfault() signal-handler code in mysqld could itself crash due to calling unsafe functions. * Enabling myisam_use_mmap could cause the server to crash. * Concurrent access to ARCHIVE tables could cause corruption.
2012-01-12 17:33:49 +01:00
share/mysql/test/include/relocate_binlogs.inc
share/mysql/test/include/report-features.test
share/mysql/test/include/restart_mysqld.inc
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
share/mysql/test/include/rpl_connection_slave.inc
share/mysql/test/include/rpl_connection_slave1.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_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_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_master_pos.inc
share/mysql/test/include/search_pattern_in_file.inc
share/mysql/test/include/select_ndb_apply_status.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
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_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
Changes 5.5.23: Bugs Fixed * Security Fix: Bug 59533 was fixed. * Performance: Partitioning: InnoDB Storage Engine: The statistics used by the optimizer for queries against partitioned InnoDB tables were based only on the first partition of each such table, leading to use of the wrong execution plan. * References: This bug was introduced by Bug 11756867. * Performance: InnoDB Storage Engine: Improved the performance of the DROP TABLE statement for InnoDB tables, especially on systems with a large buffer pool. The fix speeds up the processing for freeing entries in the adaptive hash index. * InnoDB Storage Engine: Deleting a huge amount of data from InnoDB tables within a short time could cause the purge operation that flushes data from the buffer pool to stall. If this issue occurs, restart the server to work around it. This issue is only likely to occur on 32-bit platforms. * InnoDB Storage Engine: If the server crashed during a TRUNCATE TABLE or CREATE INDEX statement for an InnoDB table, or a DROP DATABASE statement for a database containing InnoDB tables, an index could be corrupted, causing an error message when accessing the table after restart: InnoDB: Error: trying to load index index_name for table table_name InnoDB: but the index tree has been freed! In MySQL 5.1, this fix applies to the InnoDB Plugin, but not the built-in InnoDB storage engine. * InnoDB Storage Engine: When data was removed from an InnoDB table, newly inserted data might not reuse the freed disk blocks, leading to an unexpected size increase for the system tablespace or .ibd file (depending on the setting of innodb_file_per_table. The OPTIMIZE TABLE could compact a .ibd file in some cases but not others. The freed disk blocks would eventually be reused as additional data was inserted. More...
2012-04-14 14:10:05 +02:00
share/mysql/test/include/show_slave_hosts.inc
share/mysql/test/include/show_slave_status.inc
share/mysql/test/include/sp-vars.inc
share/mysql/test/include/start_slave.inc
Changes 5.5.39: CMake support was updated to handle CMake version 3. The timed_mutexes system variable has no effect and is deprecated. Bugs Fixed InnoDB: Opening a parent table that has thousands of child tables could result in a long semaphore wait condition. Partitioning: Selecting from a table having multiple columns in its primary key and partitioned by LIST COLUMNS(R), where R was the last (rightmost) column listed in the primary key definition, returned an incorrect result. Replication: When using row-based replication, updating or deleting a row on the master that did not exist on the slave led to failure of the slave when it tried to process the change. This problem occurred with InnoDB tables lacking a primary key. Replication: Quotation marks were not always handled correctly by LOAD DATA INFILE when written into the binary log. Replication: A group of threads involved in acquiring locks could deadlock when the following events occurred: Dump thread reconnects from slave; on master, a new dump thread tries to kill zombie dump threads; having acquired the thread's LOCK_thd_data, it is about to acquire LOCK_log. Application thread executing show binary logs, having acquired LOCK_log and about to acquire LOCK_index. Application thread executing PURGE BINARY LOGS; having acquired LOCK_index, it is about to acquire LOCK_thread_count. Application thread executing SHOW PROCESSLIST (or SELECT * FROM INFORMATION_SCHEMA.PROCESSLIST), having acquired LOCK_thread_count and about to acquire the zombie dump thread's LOCK_thd_data.
2014-08-10 16:27:40 +02:00
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/sync_io_with_master.inc
share/mysql/test/include/sync_slave_io_with_master.inc
share/mysql/test/include/sync_slave_sql_with_io.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
share/mysql/test/include/uninstall_semisync.inc
share/mysql/test/include/unsafe_binlog.inc
share/mysql/test/include/uses_vardir.inc
share/mysql/test/include/varchar.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
share/mysql/test/include/wait_for_ndb_to_binlog.inc
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
share/mysql/test/include/wait_for_status_var.inc
share/mysql/test/include/wait_show_condition.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/windows.inc
share/mysql/test/include/windows_sys_vars.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/File/Path.pm
share/mysql/test/lib/My/Find.pm
share/mysql/test/lib/My/Handles.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_plugin.result
Changes 5.5.17: * Replication: Previously, replication slaves could connect to the master server only through master accounts that use native authentication. Now replication slaves can also connect through master accounts that use nonnative authentication (except Windows native authentication) if the required client-side plugin is installed on the slave side in the directory named by the slave plugin_dir system variable. * MEMORY table creation time is now available in the CREATE_TIME column of the INFORMATION_SCHEMA.TABLES table and the Create_time column of SHOW TABLE STATUS output. * InnoDB Storage Engine: This fix improves the performance of instrumentation code for InnoDB buffer pool operations. * InnoDB Storage Engine: Data from BLOB columns could be lost if the server crashed at a precise moment when other columns were being updated in an InnoDB table. * InnoDB Storage Engine: Lookups using secondary indexes could give incorrect matches under a specific set of conditions. The conditions involve an index defined on a column prefix, for a BLOB or other long column stored outside the index page, with a table using the Barracuda file format. * InnoDB Storage Engine: This fix corrects cases where the MySQL server could hang or abort with a long semaphore wait message. (This is a different issue than when these symptoms occurred during a CHECK TABLE statement.) * Internal conversion of zero to binary and back could yield a result with incorrect precision. * Valgrind warnings generated by filesort operations were fixed. * mysqld_safe did not properly check for an already running instance of mysqld. * The help message for mysql_install_db did not indicate that it supports the --defaults-file, --defaults-extra-file and --no-defaults options. * An assertion designed to detect zero-length sort keys also was raised when the entire key set fit in memory. * myisampack could create corrupt FULLTEXT indexes when compressing tables. * A linking problem prevented the FEDERATED storage engine plugin from loading.
2011-10-22 12:32:37 +02:00
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
Security Notes * Security Fix: The linked OpenSSL library for the MySQL Commercial Server has been updated to version 1.0.2l. Issues fixed in the new OpenSSL version are described at http://www.openssl.org/news/vulnerabilities.html. This change does not affect the Oracle-produced MySQL Community build of MySQL Server, which uses the yaSSL library instead. Platform-Specific Notes * Linux: The generic Linux build for MySQL 5.6 is now built on Oracle Linux 6 using glibc 2.12. Systems that use the build need to have glibc 2.12 or later installed on them. Functionality Added or Changed * For Windows, MSI installer packages now include a check for the required Visual Studio redistributable package, and produce a message asking the user to install it if it is missing. * The mysql client now supports a --binary-as-hex option that causes display of binary data using hexadecimal notation (0xvalue). Thanks to Daniël van Eeden for the patch. * mysqlaccess now looks for its configuration file only in the SYSCONFDIR directory and /etc. Bugs Fixed * InnoDB: The server allocated memory unnecessarily for an operation that rebuilt the table. * InnoDB: When using an index merge optimizer switch, a SELECT COUNT(*) operation sometimes returned 0. Partitioning code incorrectly performed a memcpy instead of a column copy of columns read by the index, causing the wrong records to be copied. * Replication: A USE statement that followed a SET GTID_NEXT statement sometimes had no effect. * Replication: If the binary log on a master server was rotated and a full disk condition occurred on the partition where the binary log file was being stored, the server could stop unexpectedly. The fix adds a check for the existence of the binary log when the dump thread switches to next binary log file. If the binary log is disabled, all binary logs up to the current active log are transmitted to slave and an error is returned to the receiver thread. * Replication: If a relay log index file named relay log files that did not exist, RESET SLAVE ALL sometimes did not fully clean up properly. * Replication: mysqlbinlog, if invoked with the --raw option, does not flush the output file until the process terminates. But if also invoked with the --stop-never option, the process never terminates, thus nothing is ever written to the output file. Now the output is flushed after each event. * Replication: A memory leak in mysqlbinlog was fixed. The leak happened when processing fake rotate events, or when using --raw and the destination log file could not be created. The leak only occurred when processing events from a remote server. Thanks to Laurynas Biveinis for his contribution to fixing this bug. * Replication: Multi-threaded slaves could not be configured with small queue sizes using slave_pending_jobs_size_max if they ever needed to process transactions larger than that size. Any packet larger than slave_pending_jobs_size_max was rejected with the error ER_MTS_EVENT_BIGGER_PENDING_JOBS_SIZE_MAX, even if the packet was smaller than the limit set by slave_max_allowed_packet. * With this fix, slave_pending_jobs_size_max becomes a soft limit rather than a hard limit. If the size of a packet exceeds slave_pending_jobs_size_max but is less than slave_max_allowed_packet, the transaction is held until all the slave workers have empty queues, and then processed. All subsequent transactions are held until the large transaction has been completed. The queue size for slave workers can therefore be limited while still allowing occasional larger transactions. * mysqldump could write database names in USE statements incorrectly. * If the mysql_stmt_close() C API function was called, it freed memory that later could be accessed if mysql_stmt_error(), mysql_stmt_errno(), or mysql_stmt_sqlstate() was called. To obtain error information after a call to mysql_stmt_close(), call mysql_error(), mysql_errno(), or mysql_sqlstate() instead. * Queries could be cached incorrectly, leading to incorrect query results, under these circumstances: InnoDB table; rows are being inserted but have not yet been committed; a query uses the table as a base table in a derived table; the optimizer chooses to materialize the derived table. * Man pages for a few utilities were missing from Debian/Ubuntu packages. * The field-t unit test failed to run with AddressSanitizer enabled. Thanks to Laurynas Biveinis for the patch. * Debian client packages were missing information about conflicts with native packages. * The Perl path in #! lines at the beginning of Perl scripts has been adjusted to /usr/local/bin/perl for FreeBSD 11. * The server exited abnormally attempting to access invalid memory. * A race condition could occur for CREATE TABLE statements with DATA DIRECTORY or INDEX DIRECTORY clauses. * MySQL compilation in different directories produced different builds to leakage of absolute paths into debug information and __FILE__. * mysqld_failed to start the server if the --datadir option was specified with a relative path name. * With read_only enabled, creation of non-TEMPORARY tables by non-SUPER users was permitted under certain conditions. *Certain stored functions, if used in a query WHERE clause, could be handled using Index Condition Pushdown (which should not happen), resulting in a server exit. * On x86 machines, the uint3korr() macro read 4 bytes of data instead of the intended 3 bytes. * An assertion was raised during a fetch operation by the memcached plugin. * Queries that contained UNION in a subquery and GROUP BY could return incorrect results. * LOAD XML INFILE performance became noticeably slower when the XML file being read contained a great many spaces, such as those introduced by indenting or pretty-printing. Now all leading whitespace is trimmed from each such value before reading it into memory.
2017-07-19 20:48:21 +02:00
share/mysql/test/r/binary_to_hex.result
share/mysql/test/r/binlog_tx_isolation.result
Update mysql55-{client,server} to 5.55.24. Changes (http://dev.mysql.com/doc/refman/5.5/en/news-5-5-24.html): Functionality Added or Changed * Important Change: Replication: INSERT ON DUPLICATE KEY UPDATE is now marked as unsafe for statement-based replication if the target table has more than one primary or unique key. For more information, see Section 16.1.2.3, "Determination of Safe and Unsafe Statements in Binary Logging". Bugs Fixed * Security Fix: Bug #64884 was fixed. * InnoDB: Replication: When binary log statements were replayed on the slave, the Com_insert, Com_update, and Com_delete counters were incremented by BEGIN statements initiating transactions affecting InnoDB tables but not by COMMIT statements ending such transactions. This affected these statements whether they were replicated or they were run using mysqlbinlog. (Bug #12662190) * If the --bind-address option was given a host name value and the host name resolved to more than one IP address, the server failed to start. For example, with --bind-address=localhost, if localhost resolved to both 127.0.0.1 and ::1, startup failed. Now the server prefers the IPv4 address in such cases. (Bug #61713, Bug #12762885) * mysql_store_result() and mysql_use_result() are not for use with prepared statements and are not intended to be called following mysql_stmt_execute(), but failed to return an error when invoked that way in libmysqld. (Bug #62136, Bug #13738989) References: See also Bug #47485. * On Windows, mysqlslap crashed for attempts to connect using shared memory. (Bug #31173, Bug #11747181, Bug #59107, Bug #11766072)
2012-05-13 15:05:33 +02:00
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
Changes 5.5.25: * The --safe-mode server option now is deprecated and will be removed in MySQL 5.6. * Performance: InnoDB: Improved the algorithm related to adaptive flushing. This fix increases the rate of flushing in cases where compression is used and the data set is larger than the buffer pool, leading to eviction. * InnoDB: In a transaction using the REPEATABLE READ isolation level, an UPDATE or DELETE statement for an InnoDB table could sometimes overlook rows recently committed by other transactions. As explained in Section 14.3.9.2, “Consistent Nonlocking Reads”, DML statements within a REPEATABLE READ transaction apply to rows committed by other transactions, even if a query could not see those rows. * InnoDB: The Innodb_buffer_pool_pages_flushed status variable was incorrectly set to twice the value it should be. Its value should never exceed the value of Innodb_pages_written. * InnoDB: The error handling and message was improved for attempting to create a foreign key with a column referencing itself. The message suggested a potential problem with the data dictionary, when no such problem existed. * InnoDB: The CHECK TABLE statement could fail for a large InnoDB table due to a timeout value of 2 hours. For typical storage devices, the issue could occur for tables that exceeded approximately 200 or 350 GB, depending on I/O speed. The fix relaxes the locking performed on the table being checked, which makes the timeout less likely. It also makes InnoDB recognize the syntax CHECK TABLE QUICK, which avoids the possibility of the timeout entirely. * Replication: It was theoretically possible for concurrent execution of more than one instance of SHOW BINLOG EVENTS to crash the MySQL Server. * Replication: Statements using AUTO_INCREMENT, LAST_INSERT_ID(), RAND(), or user variables could be applied in the wrong context on the slave when using statement-based replication and replication filtering server options (see Section 16.2.3, “How Servers Evaluate Replication Filtering Rules”). * Replication: An INSERT into a table that has a composite primary key that includes an AUTO_INCREMENT column that is not the first column of this composite key is not safe for statement-based binary logging or replication. Such statements are now marked as unsafe and fail with an error when using the STATEMENT binary logging format. For more information, see Section 16.1.2.3, “Determination of Safe and Unsafe Statements in Binary Logging”, as well as Section 16.4.1.1, “Replication and AUTO_INCREMENT”.
2012-06-03 00:28:00 +02:00
share/mysql/test/r/bug12427262.result
Changes 5.5.22: * InnoDB Storage Engine: A deprecation warning is now issued when --ignore-builtin-innodb is used. * yaSSL was upgraded from version 1.7.2 to 2.2.0. * Security Fix: Bug 13510739 and Bug 63775 were fixed. * Important Change: InnoDB Storage Engine: When a row grew in size due to an UPDATE operation, other (non-updated) columns could be moved to off-page storage so that information about the row still fit within the constraints of the InnoDB page size. The pointer to the new allocated off-page data was not set up until the pages were allocated and written, potentially leading to lost data if the system crashed while the column was being moved out of the page. The problem was more common with tables using ROW_FORMAT=DYNAMIC or ROW_FORMAT=COMPRESSED along with the Barracuda file format, particularly with the innodb_file_per_table setting enabled, because page allocation operations are more common as the .ibd tablespace files are extended. Still, the problem could occur with any combination of InnoDB version, file format, and row format. * InnoDB Storage Engine: An erroneous assertion could occur, in debug builds only, when creating an index on a column containing zero-length values (that is, ''). * InnoDB Storage Engine: A DDL operation such as ALTER TABLE ... ADD COLUMN could stall, eventually timing out with an Error 1005: Can't create table message referring to fil_rename_tablespace. * InnoDB Storage Engine: A DDL operation for an InnoDB table could cause a busy MySQL server to halt with an assertion error: More...
2012-04-08 20:30:27 +02:00
share/mysql/test/r/bug13633383.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_insensitive_fs.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
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
share/mysql/test/r/consistent_snapshot.result
share/mysql/test/r/constraints.result
share/mysql/test/r/contributors.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/crash_commit_before.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
share/mysql/test/r/ctype_cp932.result
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_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/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/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_partition.require
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/empty_table.result
share/mysql/test/r/enable_cleartext_plugin.result
share/mysql/test/r/endspace.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/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
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_if.result
share/mysql/test/r/func_in.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
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/gcc296.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_no_prot.result
share/mysql/test/r/grant_cache_ps_prot.result
share/mysql/test/r/grant_lowercase_fs.result
share/mysql/test/r/greedy_optimizer.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_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_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/implicit_char_to_num_conversion.result
share/mysql/test/r/implicit_commit.result
share/mysql/test/r/index_merge_innodb.result
share/mysql/test/r/index_merge_myisam.result
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_ignore_builtin.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/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_crash.result
share/mysql/test/r/join_nested.result
share/mysql/test/r/join_optimizer.result
share/mysql/test/r/join_outer.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/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
share/mysql/test/r/log_errchk.result
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.5.46: * yaSSL was upgraded to version 2.3.8. * InnoDB: A data corruption occurred on ARM64. GCC builtins did not issue the correct fences when setting or unsetting the lock word. * InnoDB: In READ COMMITTED mode, a REPLACE operation on a unique secondary index resulted in a constraint violation. Thanks to Alexey Kopytov for the patch. * 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. * Partitioning: CREATE TABLE statements that used an invalid function in a subpartitioning expression did not always fail gracefully as expected. * Partitioning: ALTER TABLE when executed from a stored procedure did not always work correctly with tables partitioned by RANGE. * Certain subqueries as arguments to PROCEDURE ANALYSE() could cause a server exit. * mysql_ssl_rsa_setup could create an unwanted .rnd file in the data directory. (The file is actually created by openssl, which mysql_ssl_ras_setup invokes. mysql_ssl_rsa_setup now cleans up the file.) * An assertion could be raised due to incorrect error handling if a SELECT ... FOR UPDATE subquery resulted in deadlock and caused a rollback. * Servers linked against yaSSL and compiled with GCC 4.8.2 could fail to respond correctly to connection attempts until several seconds after startup. * For tables with subpartitions, the server could exit due to incorrect error handling during partition pruning if the partition could be identified but not the subpartition. * DELETE could check privileges for the wrong database when table aliases were used. * Within a trigger, use of a cursor that accessed OLD or NEW values from a row could cause a server exit. * MySQL sometimes produced no warning when it was unable to interpret a character in a given character set. * For MySQL distributions linked against yaSSL, a corrupt client key file could cause clients to exit. * Execution of certain BINLOG statements while temporary tables were open by HANDLER statements could cause a server exit.
2015-10-03 14:13:29 +02:00
share/mysql/test/r/lowercase_fs_on.result
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_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_recover.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_client_test.result
share/mysql/test/r/mysql_comments.result
share/mysql/test/r/mysql_cp932.result
Changes 5.5.15: * The undocumented --all option for perror is deprecated and will be removed in MySQL 5.6. Bugs Fixed: * InnoDB Storage Engine: A failed CREATE INDEX operation for an InnoDB table could result in some memory being allocated and not freed. This memory leak could affect tables created with the ROW_FORMAT=DYNAMIC and ROW_FORMAT=COMPRESSED settings. * Partitioning: Auto-increment columns of partitioned tables were checked even when they were not being written to. In debug builds, this could lead to a crash of the server. * Partitioning: The UNIX_TIMESTAMP() function was not treated as a monotonic function for purposes of partition pruning. * Replication: If a LOAD DATA INFILE statement—replicated using statement-based replication—featured a SET clause, the name-value pairs were regenerated using a method (Item::print()) intended primarily for generating output for statements such as EXPLAIN EXTENDED, and which cannot be relied on to return valid SQL. This could in certain cases lead to a crash on the slave. * To fix this problem, we now name each value in its original, user-supplied form, and use that to create LOAD DATA INFILE statements for statement-based replication. * Previously, an inappropriate error message was produced if a multiple-table update for an InnoDB table with a clustered primary key would update a table through multiple aliases, and perform an update that may physically move the row in at least one of these aliases. Now the error message is: Primary key/partition key update is not allowed since the table is updated both as 'tbl_name1' and 'tbl_name2' * ALTER TABLE {MODIFY|CHANGE} ... FIRST did nothing except rename columns if the old and new versions of the table had exactly the same structure with respect to column data types. As a result, the mapping of column name to column data was incorrect. The same thing happened for ALTER TABLE DROP COLUMN, ADD COLUMN statements intended to produce a new version of table with exactly the same structure as the old version. * Incorrect handling of metadata locking for FLUSH TABLES WITH READ LOCK for statements requiring prelocking caused two problems: * Execution of any data-changing statement that required prelocking (that is, involved a stored function or trigger) as part of transaction slowed down somewhat all subsequent statements in the transaction. Performance in a transaction that periodically involved such statements gradually degraded over time.
2011-07-28 10:10:29 +02:00
share/mysql/test/r/mysql_embedded.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
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/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_ndb_default.require
share/mysql/test/r/not_openssl.require
share/mysql/test/r/not_partition.require
share/mysql/test/r/not_partition.result
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.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_1.result
share/mysql/test/r/optimizer_switch_eng_cond_pushdown1.result
share/mysql/test/r/optimizer_switch_eng_cond_pushdown2.result
share/mysql/test/r/order_by.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
Changes 5.5.23: Bugs Fixed * Security Fix: Bug 59533 was fixed. * Performance: Partitioning: InnoDB Storage Engine: The statistics used by the optimizer for queries against partitioned InnoDB tables were based only on the first partition of each such table, leading to use of the wrong execution plan. * References: This bug was introduced by Bug 11756867. * Performance: InnoDB Storage Engine: Improved the performance of the DROP TABLE statement for InnoDB tables, especially on systems with a large buffer pool. The fix speeds up the processing for freeing entries in the adaptive hash index. * InnoDB Storage Engine: Deleting a huge amount of data from InnoDB tables within a short time could cause the purge operation that flushes data from the buffer pool to stall. If this issue occurs, restart the server to work around it. This issue is only likely to occur on 32-bit platforms. * InnoDB Storage Engine: If the server crashed during a TRUNCATE TABLE or CREATE INDEX statement for an InnoDB table, or a DROP DATABASE statement for a database containing InnoDB tables, an index could be corrupted, causing an error message when accessing the table after restart: InnoDB: Error: trying to load index index_name for table table_name InnoDB: but the index tree has been freed! In MySQL 5.1, this fix applies to the InnoDB Plugin, but not the built-in InnoDB storage engine. * InnoDB Storage Engine: When data was removed from an InnoDB table, newly inserted data might not reuse the freed disk blocks, leading to an unexpected size increase for the system tablespace or .ibd file (depending on the setting of innodb_file_per_table. The OPTIMIZE TABLE could compact a .ibd file in some cases but not others. The freed disk blocks would eventually be reused as additional data was inserted. More...
2012-04-14 14:10:05 +02:00
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_federated.result
share/mysql/test/r/partition_grant.result
share/mysql/test/r/partition_hash.result
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_key_cache.result
share/mysql/test/r/partition_list.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_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/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_with_views.result
share/mysql/test/r/range.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/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.result
share/mysql/test/r/select_found.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/shm.result
share/mysql/test/r/show_check.result
Changes 5.5.39: CMake support was updated to handle CMake version 3. The timed_mutexes system variable has no effect and is deprecated. Bugs Fixed InnoDB: Opening a parent table that has thousands of child tables could result in a long semaphore wait condition. Partitioning: Selecting from a table having multiple columns in its primary key and partitioned by LIST COLUMNS(R), where R was the last (rightmost) column listed in the primary key definition, returned an incorrect result. Replication: When using row-based replication, updating or deleting a row on the master that did not exist on the slave led to failure of the slave when it tried to process the change. This problem occurred with InnoDB tables lacking a primary key. Replication: Quotation marks were not always handled correctly by LOAD DATA INFILE when written into the binary log. Replication: A group of threads involved in acquiring locks could deadlock when the following events occurred: Dump thread reconnects from slave; on master, a new dump thread tries to kill zombie dump threads; having acquired the thread's LOCK_thd_data, it is about to acquire LOCK_log. Application thread executing show binary logs, having acquired LOCK_log and about to acquire LOCK_index. Application thread executing PURGE BINARY LOGS; having acquired LOCK_index, it is about to acquire LOCK_thread_count. Application thread executing SHOW PROCESSLIST (or SELECT * FROM INFORMATION_SCHEMA.PROCESSLIST), having acquired LOCK_thread_count and about to acquire the zombie dump thread's LOCK_thd_data.
2014-08-10 16:27:40 +02:00
share/mysql/test/r/show_processlist.result
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/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/sql_mode.result
share/mysql/test/r/ssl-big.result
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_ca.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_mode.result
share/mysql/test/r/ssl_mode_no_ssl.result
share/mysql/test/r/status.result
share/mysql/test/r/status2.result
share/mysql/test/r/status_bug17954.result
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/subselect.result
share/mysql/test/r/subselect2.result
share/mysql/test/r/subselect3.result
share/mysql/test/r/subselect4.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/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/tablelock.result
share/mysql/test/r/tablespace.result
share/mysql/test/r/temp_table.result
share/mysql/test/r/testdb_only.require
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/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_time.result
share/mysql/test/r/type_timestamp.result
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/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/xa.result
share/mysql/test/r/xml.result
share/mysql/test/std_data/14897.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
share/mysql/test/std_data/bug11747416_32228_binlog.000001
share/mysql/test/std_data/bug15328.cnf
Changes 5.5.46: * yaSSL was upgraded to version 2.3.8. * InnoDB: A data corruption occurred on ARM64. GCC builtins did not issue the correct fences when setting or unsetting the lock word. * InnoDB: In READ COMMITTED mode, a REPLACE operation on a unique secondary index resulted in a constraint violation. Thanks to Alexey Kopytov for the patch. * 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. * Partitioning: CREATE TABLE statements that used an invalid function in a subpartitioning expression did not always fail gracefully as expected. * Partitioning: ALTER TABLE when executed from a stored procedure did not always work correctly with tables partitioned by RANGE. * Certain subqueries as arguments to PROCEDURE ANALYSE() could cause a server exit. * mysql_ssl_rsa_setup could create an unwanted .rnd file in the data directory. (The file is actually created by openssl, which mysql_ssl_ras_setup invokes. mysql_ssl_rsa_setup now cleans up the file.) * An assertion could be raised due to incorrect error handling if a SELECT ... FOR UPDATE subquery resulted in deadlock and caused a rollback. * Servers linked against yaSSL and compiled with GCC 4.8.2 could fail to respond correctly to connection attempts until several seconds after startup. * For tables with subpartitions, the server could exit due to incorrect error handling during partition pruning if the partition could be identified but not the subpartition. * DELETE could check privileges for the wrong database when table aliases were used. * Within a trigger, use of a cursor that accessed OLD or NEW values from a row could cause a server exit. * MySQL sometimes produced no warning when it was unable to interpret a character in a given character set. * For MySQL distributions linked against yaSSL, a corrupt client key file could cause clients to exit. * Execution of certain BINLOG statements while temporary tables were open by HANDLER statements could cause a server exit.
2015-10-03 14:13:29 +02:00
share/mysql/test/std_data/bug16171518_1.dat
share/mysql/test/std_data/bug16171518_2.dat
share/mysql/test/std_data/bug16266.000001
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/bug47142_master-bin.000001
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/bug49823.CSM
share/mysql/test/std_data/bug49823.CSV
share/mysql/test/std_data/bug49823.frm
share/mysql/test/std_data/ca-cert-verify.pem
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/des_key_file
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/ndb_backup50/BACKUP-1-0.1.Data
share/mysql/test/std_data/ndb_backup50/BACKUP-1-0.2.Data
share/mysql/test/std_data/ndb_backup50/BACKUP-1.1.ctl
share/mysql/test/std_data/ndb_backup50/BACKUP-1.1.log
share/mysql/test/std_data/ndb_backup50/BACKUP-1.2.ctl
share/mysql/test/std_data/ndb_backup50/BACKUP-1.2.log
share/mysql/test/std_data/ndb_backup50/BACKUP-2-0.1.Data
share/mysql/test/std_data/ndb_backup50/BACKUP-2-0.2.Data
share/mysql/test/std_data/ndb_backup50/BACKUP-2.1.ctl
share/mysql/test/std_data/ndb_backup50/BACKUP-2.1.log
share/mysql/test/std_data/ndb_backup50/BACKUP-2.2.ctl
share/mysql/test/std_data/ndb_backup50/BACKUP-2.2.log
share/mysql/test/std_data/ndb_backup51/BACKUP-1-0.1.Data
share/mysql/test/std_data/ndb_backup51/BACKUP-1-0.2.Data
share/mysql/test/std_data/ndb_backup51/BACKUP-1.1.ctl
share/mysql/test/std_data/ndb_backup51/BACKUP-1.1.log
share/mysql/test/std_data/ndb_backup51/BACKUP-1.2.ctl
share/mysql/test/std_data/ndb_backup51/BACKUP-1.2.log
share/mysql/test/std_data/ndb_backup51_data_be/BACKUP-1-0.1.Data
share/mysql/test/std_data/ndb_backup51_data_be/BACKUP-1-0.2.Data
share/mysql/test/std_data/ndb_backup51_data_be/BACKUP-1.1.ctl
share/mysql/test/std_data/ndb_backup51_data_be/BACKUP-1.1.log
share/mysql/test/std_data/ndb_backup51_data_be/BACKUP-1.2.ctl
share/mysql/test/std_data/ndb_backup51_data_be/BACKUP-1.2.log
share/mysql/test/std_data/ndb_backup51_data_le/BACKUP-1-0.1.Data
share/mysql/test/std_data/ndb_backup51_data_le/BACKUP-1-0.2.Data
share/mysql/test/std_data/ndb_backup51_data_le/BACKUP-1.1.ctl
share/mysql/test/std_data/ndb_backup51_data_le/BACKUP-1.1.log
share/mysql/test/std_data/ndb_backup51_data_le/BACKUP-1.2.ctl
share/mysql/test/std_data/ndb_backup51_data_le/BACKUP-1.2.log
share/mysql/test/std_data/ndb_config_config.ini
share/mysql/test/std_data/ndb_config_mycnf1.cnf
share/mysql/test/std_data/ndb_config_mycnf2.cnf
share/mysql/test/std_data/numbers.txt
share/mysql/test/std_data/old_table-323.frm
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/server-cert-verify-fail.pem
share/mysql/test/std_data/server-cert-verify-pass.pem
share/mysql/test/std_data/server-cert.pem
share/mysql/test/std_data/server-key-verify-fail.pem
share/mysql/test/std_data/server-key-verify-pass.pem
share/mysql/test/std_data/server-key.pem
share/mysql/test/std_data/server8k-cert.pem
share/mysql/test/std_data/server8k-key.pem
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/words.dat
share/mysql/test/std_data/words2.dat
share/mysql/test/suite/auth_sec/r/cert_verify.result
share/mysql/test/suite/auth_sec/r/secure_file_priv_error.result
share/mysql/test/suite/auth_sec/r/secure_file_priv_null.result
share/mysql/test/suite/auth_sec/r/secure_file_priv_warnings.result
share/mysql/test/suite/auth_sec/r/secure_file_priv_warnings_not_win.result
share/mysql/test/suite/auth_sec/r/secure_file_priv_warnings_win.result
share/mysql/test/suite/auth_sec/t/cert_verify.test
share/mysql/test/suite/auth_sec/t/secure_file_priv_error.test
share/mysql/test/suite/auth_sec/t/secure_file_priv_null-master.opt
share/mysql/test/suite/auth_sec/t/secure_file_priv_null.test
share/mysql/test/suite/auth_sec/t/secure_file_priv_warnings-master.opt
share/mysql/test/suite/auth_sec/t/secure_file_priv_warnings.test
share/mysql/test/suite/auth_sec/t/secure_file_priv_warnings_not_win.test
share/mysql/test/suite/auth_sec/t/secure_file_priv_warnings_win.test
share/mysql/test/suite/binlog/combinations
share/mysql/test/suite/binlog/r/binlog_base64_flag.result
Changes 5.5.13: * InnoDB Storage Engine: If the server crashed while an XA transaction was prepared but not yet committed, the transaction could remain in the system after restart, and cause a subsequent shutdown to hang. * InnoDB Storage Engine: Similar problem to the foreign key error in bug 11831040 / 60196 / 60909, but with a different root cause and occurring on Mac OS X. With the setting lower_case_table_names=2, inserts into InnoDB tables covered by foreign key constraints could fail after a server restart. * Partitioning: The internal get_partition_set() function did not take into account the possibility that a key specification could be NULL in some cases. * Partitioning: When executing a row-ordered retrieval index merge, the partitioning handler used memory from from that allocated for the table, rather than that allocated to the query, causing table object memory not to be freed until the table was closed. * Replication: A spurious error malformed binlog: it does not contain any Format_description_log_event... was generated when mysqlbinlog was invoked using --base64-output=decode-row and --start-position=pos, where pos is a point in the binary log past the format description log event. However, there is nothing unsafe about not printing the format description log event, so the error has been removed for this case. * Replication: Typographical errors appeared in the text of several replication error messages. (The word “position” was misspelled as “postion”.) * Assignments to NEW.var_name within triggers, where var_name had a BLOB or TEXT type, were not properly handled and produced incorrect results. * XA COMMIT could fail to clean up the error state if it discovered that the current XA transaction had to be rolled back. Consequently, the next XA transaction could raise an assertion when it checked for proper cleanup of the previous transaction. * An internal client macro reference was removed from the client_plugin.h header file. This reference made the file unusable. * The server consumed memory for repeated invocation of some stored procedures, which was not released until the connection terminated. * The server did not check for certain invalid out of order sequences of XA statements, and these sequences raised an assertion. * With the conversion from GNU autotools to CMake for configuring MySQL, the USE_SYMDIR preprocessor symbol was omitted. This caused failure of symbolic links (described at Section 7.11.3.1, “Using Symbolic Links”).
2011-06-15 23:00:05 +02:00
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_database.result
share/mysql/test/suite/binlog/r/binlog_delete_and_flush_index.result
share/mysql/test/suite/binlog/r/binlog_dmls_on_tmp_tables_readonly.result
share/mysql/test/suite/binlog/r/binlog_drop_if_exists.result
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_implicit_commit.result
share/mysql/test/suite/binlog/r/binlog_incident.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_mysqlbinlog2.result
share/mysql/test/suite/binlog/r/binlog_mysqlbinlog_base64.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_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_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_server_id.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
share/mysql/test/suite/binlog/r/binlog_truncate_innodb.result
Changes 5.5.38: Bugs Fixed 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. 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. Certain INFORMATION_SCHEMA queries could cause a server exit. For indexes on prefixes or character string columns, index corruption could occur for assignment of binary data to the column due to improper character counting. Solaris-specific scripts were included in and installed by non-Solaris packages. EXPLAIN on a query with an EXISTS subquery containing a UNION could cause a server exit. Multiple executions of a prepared EXPLAIN on a UNION of subqueries could cause a server exit. Executing a correlated subquery on an ARCHIVE table which has an AUTO_INCREMENT column caused the server to hang. The client library could cause clients to exit due to incorrectly mapping the client error number to the corresponding message, if reallocation of packet buffer memory occurred. Calling mysql_get_server_version() with an invalid connection handler argument caused the client to exit. Now it returns 0 and reports a CR_COMMANDS_OUT_OF_SYNC error. On Windows, calling mysql_thread_init() call without mysql_init() caused the client to exit. windows. Now it returns a nonzero result because it is an error to call mysql_thread_init() before the client library is initialized with mysql_library_init(). CMake produced not-useful warnings about INTERFACE_LINK_LIBRARIES policy. LOAD DATA LOCAL INFILE could use all CPU if import errors occurred when there were no line delimiters. A statement of the following form broke row-based replication because it created a table having a field of data type BIGINT with a display width of 3000, which is beyond the maximum acceptable value of 255: CREATE TABLE t1 AS SELECT REPEAT('A',1000) DIV 1 AS a;
2014-06-02 09:17:31 +02:00
share/mysql/test/suite/binlog/r/binlog_truncate_kill.result
share/mysql/test/suite/binlog/r/binlog_truncate_myisam.result
share/mysql/test/suite/binlog/r/binlog_unsafe.result
share/mysql/test/suite/binlog/r/binlog_write_error.result
share/mysql/test/suite/binlog/std_data/binlog_old_version_4_1.000001
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/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
Changes 5.5.13: * InnoDB Storage Engine: If the server crashed while an XA transaction was prepared but not yet committed, the transaction could remain in the system after restart, and cause a subsequent shutdown to hang. * InnoDB Storage Engine: Similar problem to the foreign key error in bug 11831040 / 60196 / 60909, but with a different root cause and occurring on Mac OS X. With the setting lower_case_table_names=2, inserts into InnoDB tables covered by foreign key constraints could fail after a server restart. * Partitioning: The internal get_partition_set() function did not take into account the possibility that a key specification could be NULL in some cases. * Partitioning: When executing a row-ordered retrieval index merge, the partitioning handler used memory from from that allocated for the table, rather than that allocated to the query, causing table object memory not to be freed until the table was closed. * Replication: A spurious error malformed binlog: it does not contain any Format_description_log_event... was generated when mysqlbinlog was invoked using --base64-output=decode-row and --start-position=pos, where pos is a point in the binary log past the format description log event. However, there is nothing unsafe about not printing the format description log event, so the error has been removed for this case. * Replication: Typographical errors appeared in the text of several replication error messages. (The word “position” was misspelled as “postion”.) * Assignments to NEW.var_name within triggers, where var_name had a BLOB or TEXT type, were not properly handled and produced incorrect results. * XA COMMIT could fail to clean up the error state if it discovered that the current XA transaction had to be rolled back. Consequently, the next XA transaction could raise an assertion when it checked for proper cleanup of the previous transaction. * An internal client macro reference was removed from the client_plugin.h header file. This reference made the file unusable. * The server consumed memory for repeated invocation of some stored procedures, which was not released until the connection terminated. * The server did not check for certain invalid out of order sequences of XA statements, and these sequences raised an assertion. * With the conversion from GNU autotools to CMake for configuring MySQL, the USE_SYMDIR preprocessor symbol was omitted. This caused failure of symbolic links (described at Section 7.11.3.1, “Using Symbolic Links”).
2011-06-15 23:00:05 +02:00
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_database.test
share/mysql/test/suite/binlog/t/binlog_delete_and_flush_index.test
share/mysql/test/suite/binlog/t/binlog_dmls_on_tmp_tables_readonly.test
share/mysql/test/suite/binlog/t/binlog_drop_if_exists.test
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_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_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_mysqlbinlog2.test
share/mysql/test/suite/binlog/t/binlog_mysqlbinlog_base64.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_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_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_server_id.test
share/mysql/test/suite/binlog/t/binlog_sf.test
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
share/mysql/test/suite/binlog/t/binlog_truncate_innodb.test
Changes 5.5.38: Bugs Fixed 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. 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. Certain INFORMATION_SCHEMA queries could cause a server exit. For indexes on prefixes or character string columns, index corruption could occur for assignment of binary data to the column due to improper character counting. Solaris-specific scripts were included in and installed by non-Solaris packages. EXPLAIN on a query with an EXISTS subquery containing a UNION could cause a server exit. Multiple executions of a prepared EXPLAIN on a UNION of subqueries could cause a server exit. Executing a correlated subquery on an ARCHIVE table which has an AUTO_INCREMENT column caused the server to hang. The client library could cause clients to exit due to incorrectly mapping the client error number to the corresponding message, if reallocation of packet buffer memory occurred. Calling mysql_get_server_version() with an invalid connection handler argument caused the client to exit. Now it returns 0 and reports a CR_COMMANDS_OUT_OF_SYNC error. On Windows, calling mysql_thread_init() call without mysql_init() caused the client to exit. windows. Now it returns a nonzero result because it is an error to call mysql_thread_init() before the client library is initialized with mysql_library_init(). CMake produced not-useful warnings about INTERFACE_LINK_LIBRARIES policy. LOAD DATA LOCAL INFILE could use all CPU if import errors occurred when there were no line delimiters. A statement of the following form broke row-based replication because it created a table having a field of data type BIGINT with a display width of 3000, which is beyond the maximum acceptable value of 255: CREATE TABLE t1 AS SELECT REPEAT('A',1000) DIV 1 AS a;
2014-06-02 09:17:31 +02:00
share/mysql/test/suite/binlog/t/binlog_truncate_kill.test
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_write_error.test
share/mysql/test/suite/binlog/t/disabled.def
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.test
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
Changes 5.5.28: The internal interface of the Thread Pool plugin has changed. Old versions of the plugin will work with current versions of the server, but versions of the server older than 5.5.28 will not work with current versions of the plugin. Bugs Fixed InnoDB: Certain information_schema tables originally introduced in MySQL 5.6 are now also available in MySQL 5.5 and MySQL 5.1: INNODB_BUFFER_PAGE, INNODB_BUFFER_PAGE_LRU, and INNODB_BUFFER_POOL_STATS. InnoDB: When a SELECT ... FOR UPDATE, UPDATE, or other SQL statement scanned rows in an InnoDB table using a < or <= operator in a WHERE clause, the next row after the affected range could also be locked. This issue could cause a lock wait timeout for a row that was not expected to be locked. The issue occurred under various isolation levels, such as READ COMMITTED and REPEATABLE READ. Partitioning: For tables using PARTITION BY HASH or PARTITION BY KEY, when the partition pruning mechanism encountered a multi-range list or inequality using a column from the partitioning key, it continued with the next partitioning column and tried to use it for pruning, even if the previous column could not be used. This caused partitions which possibly matched one or more of the previous partitioning columns to be pruned away, leaving partitions that matched only the last column of the partitioning key. This issue was triggered when both of the following conditions were met: The columns making up the table's partitioning key were used in the same order as in the partitioning key definition by a SELECT statement's WHERE clause as in the column definitions; The WHERE condition used with the last column of the partitioning key was satisfied only by a single value, while the condition testing some previous column from the partitioning key was satisfied by a range of values. An example of a statement creating a partitioned table and a query against this for which the issue described above occurred is shown here: CREATE TABLE t1 ( c1 INT, c2 INT, PRIMARY KEY(c2, c1) ) PARTITION BY KEY() # Use primary key as partitioning key PARTITIONS 2; SELECT * FROM t1 WHERE c2 = 2 AND c1 <> 2; This issue is resolved by ensuring that partition pruning skips any remaining partitioning key columns once a partition key column that cannot be used in pruning is encountered. Partitioning: The buffer for the row currently read from each partition used for sorted reads was allocated on open and freed only when the partitioning handler was closed or destroyed. For SELECT statements on tables with many partitions and large rows, this could cause the server to use excessive amounts of memory. This issue has been addressed by allocating buffers for reads from partitioned tables only when they are needed and freeing them immediately once they are no longer needed. As part of this fix, memory is now allocated for reading from rows only in partitions that have not been pruned (see Section 18.4, “Partition Pruning”). Replication: On 64-bit Windows platforms, values greater than 4G for the max_binlog_cache_size and max_binlog_stmt_cache_size system variables were truncated to 4G. This caused LOAD DATA INFILE to fail when trying to load a file larger than 4G in size, even when max_binlog_cache_size was set to a value greater than this. Replication: In master-master replication with --log-slave-updates enabled, setting a user variable and then performing inserts using this variable caused the Exec_master_log_position column in the output of SHOW SLAVE STATUS not to be updated. The RPM spec file now also runs the test suite on the new binaries, before packaging them. The libmysqlclient_r client library exported symbols from yaSSL that conflict with OpenSSL. If a program linked against that library and libcurl, it could crash with a segmentation fault. The argument for LIMIT must be an integer, but if the argument was given by a placeholder in a prepared statement, the server did not reject noninteger values such as '5'. The Thread Pool plugin did not respect the wait_timeout timeout for client sessions. CHECK TABLE and REPAIR TABLE could crash if a key definition differed in the .frm and .MYI files of a MyISAM table. Now the server produces an error. A query for a FEDERATED table could return incorrect results when the underlying table had a compound index on two columns and the query included an AND condition on the columns. mysqlhotcopy failed for databases containing views. The argument to the --ssl-key option was not verified to exist and be a valid key. The resulting connection used SSL, but the key was not used. Adding a LIMIT clause to a query containing GROUP BY and ORDER BY could cause the optimizer to choose an incorrect index for processing the query, and return more rows than required. mysqlbinlog did not accept input on the standard input when the standard input was a pipe.
2012-10-01 17:54:40 +02:00
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.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.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.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
share/mysql/test/suite/innodb/r/add_constraint.result
Changes 5.5.37: Functionality Added or Changed On Solaris, mysql_config --libs now includes -R/path/to/library so that libraries can be found at runtime. Bugs Fixed InnoDB: A regression introduced by Bug 14329288 would result in a performance degradation when a compressed table does not fit into memory. InnoDB: The maximum value for innodb_thread_sleep_delay is now 1000000 microseconds. The previous maximum value (4294967295 microseconds on 32-bit and 18446744073709551615 microseconds on 64-bit) was unnecessarily large. Because the maximum value of innodb_thread_sleep_delay is limited by the value set for innodb_adaptive_max_sleep_delay (when set to a non-zero value), the maximum value for innodb_thread_sleep_delay is now the same as the maximum value for innodb_adaptive_max_sleep_delay. InnoDB: In debug builds, creating a unique index on a binary column, with input data containing duplicate keys, would cause an assertion. InnoDB: InnoDB would fail to start when innodb_data_file_path specified the data file size in kilobytes by appending K to the size value. InnoDB: An insert buffer merge would cause an assertion error due to incorrectly handled ownership information for externally stored BLOBs. InnoDB: Assertion failure in thread thread_num in file ibuf0ibuf.cc line 4080 InnoDB: Failing assertion: rec_get_deleted_flag(rec, page_is_comp(page)) InnoDB: Decreasing the auto_increment_increment value would have no affect on the next auto-increment value. Replication: The server did not handle correctly the insertion of a row larger than 4 GB when using row-based replication. Replication: When using row-based replication, an additional auto-increment column on the slave version of a table was not updated correctly; a zero was inserted instead. Replication: Statements involving the Performance Schema tables should not be written to the binary log, because the content of these tables is applicable only to a given MySQL Server instance, and may differ greatly between different servers in a replication topology. The database administrator should be able to configure (INSERT, UPDATE, or DELETE) or flush (TRUNCATE TABLE) performance schema tables on a single server without affecting others. However, when replicating from a MySQL 5.5 master to a MySQL 5.5 or later slave, warnings about unsafe statements updating Performance Schema tables were elevated to errors. For MySQL 5.6 and later slaves, this prevented the simultaneous use of performance_schema and GTIDs (see Replication with Global Transaction Identifiers, in the MySQL 5.6 Manual). This fix causes all updates on tables in the performance_schema database to be filtered on the master and not replicated, regardless of the type of logging that is in effect. Prior to this fix, statements using were handled by being marked as unsafe for replication, which caused warnings during execution; the statements were nonetheless written to the binary log, regardless of the logging format in effect. Existing replication behavior for tables in the INFORMATION_SCHEMA database is not changed by this fix. For more information, see MySQL Performance Schema. Compilation failed if MySQL was configured with CFLAGS set to include a -Werror option with an argument. A shared libmysqld embedded server library was not built on Linux. While printing the server version, the mysql client did not check for buffer overflow in a string variable. Contraction information in a collation could be mishandled, resulting in incorrect decisions about whether a character is part of a contraction, and miscalculation of contraction weights. DROP TRIGGER succeeded even with the read_only system variable enabled. Updating the Performance Schema setup_instruments table on a replication master caused a slave to exit. Due to a race condition, it was possible for two threads to end up with the same query ID for different queries. When run by root, mysqld --help --verbose exited with a nonzero error code after displaying the help message. MySQL client programs from a Community Edition distribution could not connect using SSL to a MySQL server from an Enterprise Edition. This was due to a difference in certificate handling by yaSSL and OpenSSL (used for Community and Enterprise, respectively). OpenSSL expected a blank certificate to be sent when not all of the --ssl-ca, --ssl-cert, and --ssl-key options were specified, and yaSSL did not do so. To resolve this, yaSSL has been modified to send a blank certificate when an option is missing. A deadlock error occurring during subquery execution could cause an assertion to be raised. The Performance Schema stage/sql/Waiting to get readlock instrument is no longer used and has been removed. For system variables that take a string value, SET statements permitted an unquoted value, but values that contained dots were parsed incorrectly and only part of the value was assigned. For example, SET GLOBAL slow_query_log_file = my_slow.log assigned the value my_slow. Now such values must be quoted or an error occurs. On Windows, mysql_install_db.pl could be run only from within the bin directory under the installation directory.
2014-03-31 10:03:22 +02:00
share/mysql/test/suite/innodb/r/blob-update-debug.result
share/mysql/test/suite/innodb/r/create-index.result
share/mysql/test/suite/innodb/r/dropdb.result
share/mysql/test/suite/innodb/r/foreign-keys.result
2014-11-29 11:01:29 +01:00
share/mysql/test/suite/innodb/r/foreign-keys.result.moved
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
Changes 5.5.22: * InnoDB Storage Engine: A deprecation warning is now issued when --ignore-builtin-innodb is used. * yaSSL was upgraded from version 1.7.2 to 2.2.0. * Security Fix: Bug 13510739 and Bug 63775 were fixed. * Important Change: InnoDB Storage Engine: When a row grew in size due to an UPDATE operation, other (non-updated) columns could be moved to off-page storage so that information about the row still fit within the constraints of the InnoDB page size. The pointer to the new allocated off-page data was not set up until the pages were allocated and written, potentially leading to lost data if the system crashed while the column was being moved out of the page. The problem was more common with tables using ROW_FORMAT=DYNAMIC or ROW_FORMAT=COMPRESSED along with the Barracuda file format, particularly with the innodb_file_per_table setting enabled, because page allocation operations are more common as the .ibd tablespace files are extended. Still, the problem could occur with any combination of InnoDB version, file format, and row format. * InnoDB Storage Engine: An erroneous assertion could occur, in debug builds only, when creating an index on a column containing zero-length values (that is, ''). * InnoDB Storage Engine: A DDL operation such as ALTER TABLE ... ADD COLUMN could stall, eventually timing out with an Error 1005: Can't create table message referring to fil_rename_tablespace. * InnoDB Storage Engine: A DDL operation for an InnoDB table could cause a busy MySQL server to halt with an assertion error: More...
2012-04-08 20:30:27 +02:00
share/mysql/test/suite/innodb/r/innodb-blob.result
Changes 5.5.36: Functionality Added or Changed 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>. Thanks to Honza Horak for the patch. Bugs Fixed InnoDB: Table renaming errors would appear in the LATEST FOREIGN KEY ERROR section of the SHOW ENGINE INNODB STATUS output. Partitioning: Queries using the index_merge optimization (see Index Merge Optimization) could return invalid results when run against tables that were partitioned by HASH. Partitioning: When no partition had returned a row since the last HA_ERR_KEY_NOT_FOUND error, the use of uninitialized memory in the priority queue used for returning rows in sorted order could lead to a crash of the server. Replication: mysqlbinlog --verbose failed when it encountered a corrupt row event in the binary log. Such a row event could also cause the slave to fail. Replication: When log_warnings is greater than 1, the master prints binary log dump thread information—containing the slave server ID, binary log file name, and binary log position—in mysqld.1.err. A slave server ID greater than 2 billion was printed with a negative value in such cases. Replication: Invalid event offsets in the binary log were not always handled correctly, which could lead to replication failure. The cache used for the Index Merge access method was freed only after successful retrieval of all rows. Interruption or failure of the operation led to a file descriptor leak. For utf8 and utf8mb4 strings, handler functions unnecessarily called a Unicode conversion function. Use of a nonmulti-byte algorithm for skipping leading spaces in multi-byte strings could cause a server exit. For the utf8_bin collation, ORDER BY LOWER(col_name) could produce incorrect ordering. On Windows, the --local-service server option did not work, and was not displayed in the --help message. The prototype of the Performance Schema instrumentation API mysql_cond_timedwait() call was fixed to be drop-in compatible with pthread_cond_timedwait(). This fix affects only implementers of third-party plugins. For the path specified with the --basedir option, mysql_plugin attempted to unlink the path rather than free the memory in which the path was stored. COUNT(DISTINCT) sometimes produced an incorrect result when the last read row contained a NULL value. Some scripts displayed out-of-date information regarding where to report bugs. Updating a FEDERATED table with UPDATE... JOIN caused a server exit when the local table contained a single row and that row could be joined to a row in the FEDERATED table. mysql_install_db referred to the obsolete mysqlbug script for reporting problems. It now refers to http://bugs.mysql.com/ instead.
2014-02-01 12:16:03 +01:00
share/mysql/test/suite/innodb/r/innodb-change-buffer-recovery.result
share/mysql/test/suite/innodb/r/innodb-consistent.result
Changes 5.5.39: CMake support was updated to handle CMake version 3. The timed_mutexes system variable has no effect and is deprecated. Bugs Fixed InnoDB: Opening a parent table that has thousands of child tables could result in a long semaphore wait condition. Partitioning: Selecting from a table having multiple columns in its primary key and partitioned by LIST COLUMNS(R), where R was the last (rightmost) column listed in the primary key definition, returned an incorrect result. Replication: When using row-based replication, updating or deleting a row on the master that did not exist on the slave led to failure of the slave when it tried to process the change. This problem occurred with InnoDB tables lacking a primary key. Replication: Quotation marks were not always handled correctly by LOAD DATA INFILE when written into the binary log. Replication: A group of threads involved in acquiring locks could deadlock when the following events occurred: Dump thread reconnects from slave; on master, a new dump thread tries to kill zombie dump threads; having acquired the thread's LOCK_thd_data, it is about to acquire LOCK_log. Application thread executing show binary logs, having acquired LOCK_log and about to acquire LOCK_index. Application thread executing PURGE BINARY LOGS; having acquired LOCK_index, it is about to acquire LOCK_thread_count. Application thread executing SHOW PROCESSLIST (or SELECT * FROM INFORMATION_SCHEMA.PROCESSLIST), having acquired LOCK_thread_count and about to acquire the zombie dump thread's LOCK_thd_data.
2014-08-10 16:27:40 +02:00
share/mysql/test/suite/innodb/r/innodb-fk.result
share/mysql/test/suite/innodb/r/innodb-index.result
share/mysql/test/suite/innodb/r/innodb-index_ucs2.result
share/mysql/test/suite/innodb/r/innodb-lock.result
share/mysql/test/suite/innodb/r/innodb-replace.result
share/mysql/test/suite/innodb/r/innodb-semi-consistent.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.5.37: Functionality Added or Changed On Solaris, mysql_config --libs now includes -R/path/to/library so that libraries can be found at runtime. Bugs Fixed InnoDB: A regression introduced by Bug 14329288 would result in a performance degradation when a compressed table does not fit into memory. InnoDB: The maximum value for innodb_thread_sleep_delay is now 1000000 microseconds. The previous maximum value (4294967295 microseconds on 32-bit and 18446744073709551615 microseconds on 64-bit) was unnecessarily large. Because the maximum value of innodb_thread_sleep_delay is limited by the value set for innodb_adaptive_max_sleep_delay (when set to a non-zero value), the maximum value for innodb_thread_sleep_delay is now the same as the maximum value for innodb_adaptive_max_sleep_delay. InnoDB: In debug builds, creating a unique index on a binary column, with input data containing duplicate keys, would cause an assertion. InnoDB: InnoDB would fail to start when innodb_data_file_path specified the data file size in kilobytes by appending K to the size value. InnoDB: An insert buffer merge would cause an assertion error due to incorrectly handled ownership information for externally stored BLOBs. InnoDB: Assertion failure in thread thread_num in file ibuf0ibuf.cc line 4080 InnoDB: Failing assertion: rec_get_deleted_flag(rec, page_is_comp(page)) InnoDB: Decreasing the auto_increment_increment value would have no affect on the next auto-increment value. Replication: The server did not handle correctly the insertion of a row larger than 4 GB when using row-based replication. Replication: When using row-based replication, an additional auto-increment column on the slave version of a table was not updated correctly; a zero was inserted instead. Replication: Statements involving the Performance Schema tables should not be written to the binary log, because the content of these tables is applicable only to a given MySQL Server instance, and may differ greatly between different servers in a replication topology. The database administrator should be able to configure (INSERT, UPDATE, or DELETE) or flush (TRUNCATE TABLE) performance schema tables on a single server without affecting others. However, when replicating from a MySQL 5.5 master to a MySQL 5.5 or later slave, warnings about unsafe statements updating Performance Schema tables were elevated to errors. For MySQL 5.6 and later slaves, this prevented the simultaneous use of performance_schema and GTIDs (see Replication with Global Transaction Identifiers, in the MySQL 5.6 Manual). This fix causes all updates on tables in the performance_schema database to be filtered on the master and not replicated, regardless of the type of logging that is in effect. Prior to this fix, statements using were handled by being marked as unsafe for replication, which caused warnings during execution; the statements were nonetheless written to the binary log, regardless of the logging format in effect. Existing replication behavior for tables in the INFORMATION_SCHEMA database is not changed by this fix. For more information, see MySQL Performance Schema. Compilation failed if MySQL was configured with CFLAGS set to include a -Werror option with an argument. A shared libmysqld embedded server library was not built on Linux. While printing the server version, the mysql client did not check for buffer overflow in a string variable. Contraction information in a collation could be mishandled, resulting in incorrect decisions about whether a character is part of a contraction, and miscalculation of contraction weights. DROP TRIGGER succeeded even with the read_only system variable enabled. Updating the Performance Schema setup_instruments table on a replication master caused a slave to exit. Due to a race condition, it was possible for two threads to end up with the same query ID for different queries. When run by root, mysqld --help --verbose exited with a nonzero error code after displaying the help message. MySQL client programs from a Community Edition distribution could not connect using SSL to a MySQL server from an Enterprise Edition. This was due to a difference in certificate handling by yaSSL and OpenSSL (used for Community and Enterprise, respectively). OpenSSL expected a blank certificate to be sent when not all of the --ssl-ca, --ssl-cert, and --ssl-key options were specified, and yaSSL did not do so. To resolve this, yaSSL has been modified to send a blank certificate when an option is missing. A deadlock error occurring during subquery execution could cause an assertion to be raised. The Performance Schema stage/sql/Waiting to get readlock instrument is no longer used and has been removed. For system variables that take a string value, SET statements permitted an unquoted value, but values that contained dots were parsed incorrectly and only part of the value was assigned. For example, SET GLOBAL slow_query_log_file = my_slow.log assigned the value my_slow. Now such values must be quoted or an error occurs. On Windows, mysql_install_db.pl could be run only from within the bin directory under the installation directory.
2014-03-31 10:03:22 +02:00
share/mysql/test/suite/innodb/r/innodb-update-insert.result
share/mysql/test/suite/innodb/r/innodb-use-sys-malloc.result
share/mysql/test/suite/innodb/r/innodb.result
share/mysql/test/suite/innodb/r/innodb_autoinc_lock_mode_zero.result
Changes 5.5.22: * InnoDB Storage Engine: A deprecation warning is now issued when --ignore-builtin-innodb is used. * yaSSL was upgraded from version 1.7.2 to 2.2.0. * Security Fix: Bug 13510739 and Bug 63775 were fixed. * Important Change: InnoDB Storage Engine: When a row grew in size due to an UPDATE operation, other (non-updated) columns could be moved to off-page storage so that information about the row still fit within the constraints of the InnoDB page size. The pointer to the new allocated off-page data was not set up until the pages were allocated and written, potentially leading to lost data if the system crashed while the column was being moved out of the page. The problem was more common with tables using ROW_FORMAT=DYNAMIC or ROW_FORMAT=COMPRESSED along with the Barracuda file format, particularly with the innodb_file_per_table setting enabled, because page allocation operations are more common as the .ibd tablespace files are extended. Still, the problem could occur with any combination of InnoDB version, file format, and row format. * InnoDB Storage Engine: An erroneous assertion could occur, in debug builds only, when creating an index on a column containing zero-length values (that is, ''). * InnoDB Storage Engine: A DDL operation such as ALTER TABLE ... ADD COLUMN could stall, eventually timing out with an Error 1005: Can't create table message referring to fil_rename_tablespace. * InnoDB Storage Engine: A DDL operation for an InnoDB table could cause a busy MySQL server to halt with an assertion error: More...
2012-04-08 20:30:27 +02:00
share/mysql/test/suite/innodb/r/innodb_bug11754376.result
Changes 5.5.23: Bugs Fixed * Security Fix: Bug 59533 was fixed. * Performance: Partitioning: InnoDB Storage Engine: The statistics used by the optimizer for queries against partitioned InnoDB tables were based only on the first partition of each such table, leading to use of the wrong execution plan. * References: This bug was introduced by Bug 11756867. * Performance: InnoDB Storage Engine: Improved the performance of the DROP TABLE statement for InnoDB tables, especially on systems with a large buffer pool. The fix speeds up the processing for freeing entries in the adaptive hash index. * InnoDB Storage Engine: Deleting a huge amount of data from InnoDB tables within a short time could cause the purge operation that flushes data from the buffer pool to stall. If this issue occurs, restart the server to work around it. This issue is only likely to occur on 32-bit platforms. * InnoDB Storage Engine: If the server crashed during a TRUNCATE TABLE or CREATE INDEX statement for an InnoDB table, or a DROP DATABASE statement for a database containing InnoDB tables, an index could be corrupted, causing an error message when accessing the table after restart: InnoDB: Error: trying to load index index_name for table table_name InnoDB: but the index tree has been freed! In MySQL 5.1, this fix applies to the InnoDB Plugin, but not the built-in InnoDB storage engine. * InnoDB Storage Engine: When data was removed from an InnoDB table, newly inserted data might not reuse the freed disk blocks, leading to an unexpected size increase for the system tablespace or .ibd file (depending on the setting of innodb_file_per_table. The OPTIMIZE TABLE could compact a .ibd file in some cases but not others. The freed disk blocks would eventually be reused as additional data was inserted. More...
2012-04-14 14:10:05 +02:00
share/mysql/test/suite/innodb/r/innodb_bug11766634.result
Changes 5.5.21: * A new CMake option, MYSQL_PROJECT_NAME, can be set on Windows or Mac OS X to be used in the project name. Bugs Fixed * Performance: InnoDB Storage Engine: Memory allocation for InnoDB tables was reorganized to reduce the memory overhead for large numbers of tables or partitions, avoiding situations where the “resident set size” could grow regardless of FLUSH TABLES statements. The problem was most evident for tables with large row size. * Incompatible Change: An earlier change (in MySQL 5.1.62 and 5.5.21) was found to modify date-handling behavior in General Availability-status series (MySQL 5.1 and 5.5). This change has been reverted. * The change was that several functions became more strict when passed a DATE() function value as their argument, thus they rejected incomplete dates with a day part of zero. These functions were affected: CONVERT_TZ(), DATE_ADD(), DATE_SUB(), DAYOFYEAR(), LAST_DAY(), TIMESTAMPDIFF(), TO_DAYS(), TO_SECONDS(), WEEK(), WEEKDAY(), WEEKOFYEAR(), YEARWEEK(). The previous behavior has been restored. * InnoDB Storage Engine: A Valgrind error was fixed in the function os_aio_init(). * InnoDB Storage Engine: The server could crash when creating an InnoDB temporary table under Linux, if the $TMPDIR setting points to a tmpfs filesystem and innodb_use_native_aio is enabled, as it is by default in MySQL 5.5.4 and higher. * InnoDB Storage Engine: References to C preprocessor symbols and macros HAVE_purify, UNIV_INIT_MEM_TO_ZERO, and UNIV_SET_MEM_TO_ZERO were removed from the InnoDB source code. They were only used in debug builds instrumented for Valgrind. They are replaced by calls to the UNIV_MEM_INVALID() macro.
2012-02-23 14:01:03 +01:00
share/mysql/test/suite/innodb/r/innodb_bug12400341.result
share/mysql/test/suite/innodb/r/innodb_bug12661768.result
Changes 5.5.25: * The --safe-mode server option now is deprecated and will be removed in MySQL 5.6. * Performance: InnoDB: Improved the algorithm related to adaptive flushing. This fix increases the rate of flushing in cases where compression is used and the data set is larger than the buffer pool, leading to eviction. * InnoDB: In a transaction using the REPEATABLE READ isolation level, an UPDATE or DELETE statement for an InnoDB table could sometimes overlook rows recently committed by other transactions. As explained in Section 14.3.9.2, “Consistent Nonlocking Reads”, DML statements within a REPEATABLE READ transaction apply to rows committed by other transactions, even if a query could not see those rows. * InnoDB: The Innodb_buffer_pool_pages_flushed status variable was incorrectly set to twice the value it should be. Its value should never exceed the value of Innodb_pages_written. * InnoDB: The error handling and message was improved for attempting to create a foreign key with a column referencing itself. The message suggested a potential problem with the data dictionary, when no such problem existed. * InnoDB: The CHECK TABLE statement could fail for a large InnoDB table due to a timeout value of 2 hours. For typical storage devices, the issue could occur for tables that exceeded approximately 200 or 350 GB, depending on I/O speed. The fix relaxes the locking performed on the table being checked, which makes the timeout less likely. It also makes InnoDB recognize the syntax CHECK TABLE QUICK, which avoids the possibility of the timeout entirely. * Replication: It was theoretically possible for concurrent execution of more than one instance of SHOW BINLOG EVENTS to crash the MySQL Server. * Replication: Statements using AUTO_INCREMENT, LAST_INSERT_ID(), RAND(), or user variables could be applied in the wrong context on the slave when using statement-based replication and replication filtering server options (see Section 16.2.3, “How Servers Evaluate Replication Filtering Rules”). * Replication: An INSERT into a table that has a composite primary key that includes an AUTO_INCREMENT column that is not the first column of this composite key is not safe for statement-based binary logging or replication. Such statements are now marked as unsafe and fail with an error when using the STATEMENT binary logging format. For more information, see Section 16.1.2.3, “Determination of Safe and Unsafe Statements in Binary Logging”, as well as Section 16.4.1.1, “Replication and AUTO_INCREMENT”.
2012-06-03 00:28:00 +02:00
share/mysql/test/suite/innodb/r/innodb_bug12902967.result
Changes 5.5.22: * InnoDB Storage Engine: A deprecation warning is now issued when --ignore-builtin-innodb is used. * yaSSL was upgraded from version 1.7.2 to 2.2.0. * Security Fix: Bug 13510739 and Bug 63775 were fixed. * Important Change: InnoDB Storage Engine: When a row grew in size due to an UPDATE operation, other (non-updated) columns could be moved to off-page storage so that information about the row still fit within the constraints of the InnoDB page size. The pointer to the new allocated off-page data was not set up until the pages were allocated and written, potentially leading to lost data if the system crashed while the column was being moved out of the page. The problem was more common with tables using ROW_FORMAT=DYNAMIC or ROW_FORMAT=COMPRESSED along with the Barracuda file format, particularly with the innodb_file_per_table setting enabled, because page allocation operations are more common as the .ibd tablespace files are extended. Still, the problem could occur with any combination of InnoDB version, file format, and row format. * InnoDB Storage Engine: An erroneous assertion could occur, in debug builds only, when creating an index on a column containing zero-length values (that is, ''). * InnoDB Storage Engine: A DDL operation such as ALTER TABLE ... ADD COLUMN could stall, eventually timing out with an Error 1005: Can't create table message referring to fil_rename_tablespace. * InnoDB Storage Engine: A DDL operation for an InnoDB table could cause a busy MySQL server to halt with an assertion error: More...
2012-04-08 20:30:27 +02:00
share/mysql/test/suite/innodb/r/innodb_bug13510739.result
Update mysql55-{client,server} to 5.55.24. Changes (http://dev.mysql.com/doc/refman/5.5/en/news-5-5-24.html): Functionality Added or Changed * Important Change: Replication: INSERT ON DUPLICATE KEY UPDATE is now marked as unsafe for statement-based replication if the target table has more than one primary or unique key. For more information, see Section 16.1.2.3, "Determination of Safe and Unsafe Statements in Binary Logging". Bugs Fixed * Security Fix: Bug #64884 was fixed. * InnoDB: Replication: When binary log statements were replayed on the slave, the Com_insert, Com_update, and Com_delete counters were incremented by BEGIN statements initiating transactions affecting InnoDB tables but not by COMMIT statements ending such transactions. This affected these statements whether they were replicated or they were run using mysqlbinlog. (Bug #12662190) * If the --bind-address option was given a host name value and the host name resolved to more than one IP address, the server failed to start. For example, with --bind-address=localhost, if localhost resolved to both 127.0.0.1 and ::1, startup failed. Now the server prefers the IPv4 address in such cases. (Bug #61713, Bug #12762885) * mysql_store_result() and mysql_use_result() are not for use with prepared statements and are not intended to be called following mysql_stmt_execute(), but failed to return an error when invoked that way in libmysqld. (Bug #62136, Bug #13738989) References: See also Bug #47485. * On Windows, mysqlslap crashed for attempts to connect using shared memory. (Bug #31173, Bug #11747181, Bug #59107, Bug #11766072)
2012-05-13 15:05:33 +02:00
share/mysql/test/suite/innodb/r/innodb_bug13635833.result
Changes 5.5.25: * The --safe-mode server option now is deprecated and will be removed in MySQL 5.6. * Performance: InnoDB: Improved the algorithm related to adaptive flushing. This fix increases the rate of flushing in cases where compression is used and the data set is larger than the buffer pool, leading to eviction. * InnoDB: In a transaction using the REPEATABLE READ isolation level, an UPDATE or DELETE statement for an InnoDB table could sometimes overlook rows recently committed by other transactions. As explained in Section 14.3.9.2, “Consistent Nonlocking Reads”, DML statements within a REPEATABLE READ transaction apply to rows committed by other transactions, even if a query could not see those rows. * InnoDB: The Innodb_buffer_pool_pages_flushed status variable was incorrectly set to twice the value it should be. Its value should never exceed the value of Innodb_pages_written. * InnoDB: The error handling and message was improved for attempting to create a foreign key with a column referencing itself. The message suggested a potential problem with the data dictionary, when no such problem existed. * InnoDB: The CHECK TABLE statement could fail for a large InnoDB table due to a timeout value of 2 hours. For typical storage devices, the issue could occur for tables that exceeded approximately 200 or 350 GB, depending on I/O speed. The fix relaxes the locking performed on the table being checked, which makes the timeout less likely. It also makes InnoDB recognize the syntax CHECK TABLE QUICK, which avoids the possibility of the timeout entirely. * Replication: It was theoretically possible for concurrent execution of more than one instance of SHOW BINLOG EVENTS to crash the MySQL Server. * Replication: Statements using AUTO_INCREMENT, LAST_INSERT_ID(), RAND(), or user variables could be applied in the wrong context on the slave when using statement-based replication and replication filtering server options (see Section 16.2.3, “How Servers Evaluate Replication Filtering Rules”). * Replication: An INSERT into a table that has a composite primary key that includes an AUTO_INCREMENT column that is not the first column of this composite key is not safe for statement-based binary logging or replication. Such statements are now marked as unsafe and fail with an error when using the STATEMENT binary logging format. For more information, see Section 16.1.2.3, “Determination of Safe and Unsafe Statements in Binary Logging”, as well as Section 16.4.1.1, “Replication and AUTO_INCREMENT”.
2012-06-03 00:28:00 +02:00
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_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
Changes 5.5.13: * InnoDB Storage Engine: If the server crashed while an XA transaction was prepared but not yet committed, the transaction could remain in the system after restart, and cause a subsequent shutdown to hang. * InnoDB Storage Engine: Similar problem to the foreign key error in bug 11831040 / 60196 / 60909, but with a different root cause and occurring on Mac OS X. With the setting lower_case_table_names=2, inserts into InnoDB tables covered by foreign key constraints could fail after a server restart. * Partitioning: The internal get_partition_set() function did not take into account the possibility that a key specification could be NULL in some cases. * Partitioning: When executing a row-ordered retrieval index merge, the partitioning handler used memory from from that allocated for the table, rather than that allocated to the query, causing table object memory not to be freed until the table was closed. * Replication: A spurious error malformed binlog: it does not contain any Format_description_log_event... was generated when mysqlbinlog was invoked using --base64-output=decode-row and --start-position=pos, where pos is a point in the binary log past the format description log event. However, there is nothing unsafe about not printing the format description log event, so the error has been removed for this case. * Replication: Typographical errors appeared in the text of several replication error messages. (The word “position” was misspelled as “postion”.) * Assignments to NEW.var_name within triggers, where var_name had a BLOB or TEXT type, were not properly handled and produced incorrect results. * XA COMMIT could fail to clean up the error state if it discovered that the current XA transaction had to be rolled back. Consequently, the next XA transaction could raise an assertion when it checked for proper cleanup of the previous transaction. * An internal client macro reference was removed from the client_plugin.h header file. This reference made the file unusable. * The server consumed memory for repeated invocation of some stored procedures, which was not released until the connection terminated. * The server did not check for certain invalid out of order sequences of XA statements, and these sequences raised an assertion. * With the conversion from GNU autotools to CMake for configuring MySQL, the USE_SYMDIR preprocessor symbol was omitted. This caused failure of symbolic links (described at Section 7.11.3.1, “Using Symbolic Links”).
2011-06-15 23:00:05 +02:00
share/mysql/test/suite/innodb/r/innodb_bug59410.result
share/mysql/test/suite/innodb/r/innodb_bug59641.result
Changes 5.5.17: * Replication: Previously, replication slaves could connect to the master server only through master accounts that use native authentication. Now replication slaves can also connect through master accounts that use nonnative authentication (except Windows native authentication) if the required client-side plugin is installed on the slave side in the directory named by the slave plugin_dir system variable. * MEMORY table creation time is now available in the CREATE_TIME column of the INFORMATION_SCHEMA.TABLES table and the Create_time column of SHOW TABLE STATUS output. * InnoDB Storage Engine: This fix improves the performance of instrumentation code for InnoDB buffer pool operations. * InnoDB Storage Engine: Data from BLOB columns could be lost if the server crashed at a precise moment when other columns were being updated in an InnoDB table. * InnoDB Storage Engine: Lookups using secondary indexes could give incorrect matches under a specific set of conditions. The conditions involve an index defined on a column prefix, for a BLOB or other long column stored outside the index page, with a table using the Barracuda file format. * InnoDB Storage Engine: This fix corrects cases where the MySQL server could hang or abort with a long semaphore wait message. (This is a different issue than when these symptoms occurred during a CHECK TABLE statement.) * Internal conversion of zero to binary and back could yield a result with incorrect precision. * Valgrind warnings generated by filesort operations were fixed. * mysqld_safe did not properly check for an already running instance of mysqld. * The help message for mysql_install_db did not indicate that it supports the --defaults-file, --defaults-extra-file and --no-defaults options. * An assertion designed to detect zero-length sort keys also was raised when the entire key set fit in memory. * myisampack could create corrupt FULLTEXT indexes when compressing tables. * A linking problem prevented the FEDERATED storage engine plugin from loading.
2011-10-22 12:32:37 +02:00
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
Changes 5.5.20: * A new server option, --slow-start-timeout, controls the Windows service control manager's service start timeout. The value is the maximum number of milliseconds that the service control manager waits before trying to kill the MySQL service during startup. The default value is 15000 (15 seconds). If the MySQL service takes too long to start, you may need to increase this value. A value of 0 means there is no timeout. Bugs Fixed: * Important Change: Replication: Setting an empty user in a CHANGE MASTER TO statement caused an invalid internal result and is no longer permitted. Trying to use MASTER_USER='' or setting MASTER_PASSWORD while leaving MASTER_USER unset causes the statement to fail with an error. * Important Change: Replication: Moving the binary log file, relay log file, or both files to a new location, then restarting the server with a new value for --log-bin, --relay-log, or both, caused the server to abort on start. This was because the entries in the index file overrode the new location. In addition, paths were calculated relative to datadir (rather than to the --log-bin or --relay-log values). * InnoDB Storage Engine: When doing a live downgrade from MySQL 5.6.4 or later, with innodb_page_size set to a value other than 16384, now the earlier MySQL version reports that the page size is incompatible with the older version, rather than crashing or displaying a “corruption” error. * InnoDB Storage Engine: Issuing INSERT...ON DUPLICATE KEY statements for InnoDB tables from concurrent threads could cause a deadlock, particularly with the INSERT...ON DUPLICATE KEY UPDATE form. The fix avoids deadlocks caused by the same row being accessed by more than one transaction. Deadlocks could still occur when multiple rows are inserted and updated simultaneously by different transactions in inconsistent order; those types of deadlocks require the standard error handling on the application side, of re-trying the transaction. * An incorrect InnoDB assertion could cause the server to halt. This issue only affected debug builds. The assertion referenced the source file btr0pcur.ic and the variable cursor->pos_state. * Locale information for FORMAT() function instances was lost in view definitions. * The handle_segfault() signal-handler code in mysqld could itself crash due to calling unsafe functions. * Enabling myisam_use_mmap could cause the server to crash. * Concurrent access to ARCHIVE tables could cause corruption.
2012-01-12 17:33:49 +01:00
share/mysql/test/suite/innodb/r/innodb_bug60229.result
Changes 5.5.17: * Replication: Previously, replication slaves could connect to the master server only through master accounts that use native authentication. Now replication slaves can also connect through master accounts that use nonnative authentication (except Windows native authentication) if the required client-side plugin is installed on the slave side in the directory named by the slave plugin_dir system variable. * MEMORY table creation time is now available in the CREATE_TIME column of the INFORMATION_SCHEMA.TABLES table and the Create_time column of SHOW TABLE STATUS output. * InnoDB Storage Engine: This fix improves the performance of instrumentation code for InnoDB buffer pool operations. * InnoDB Storage Engine: Data from BLOB columns could be lost if the server crashed at a precise moment when other columns were being updated in an InnoDB table. * InnoDB Storage Engine: Lookups using secondary indexes could give incorrect matches under a specific set of conditions. The conditions involve an index defined on a column prefix, for a BLOB or other long column stored outside the index page, with a table using the Barracuda file format. * InnoDB Storage Engine: This fix corrects cases where the MySQL server could hang or abort with a long semaphore wait message. (This is a different issue than when these symptoms occurred during a CHECK TABLE statement.) * Internal conversion of zero to binary and back could yield a result with incorrect precision. * Valgrind warnings generated by filesort operations were fixed. * mysqld_safe did not properly check for an already running instance of mysqld. * The help message for mysql_install_db did not indicate that it supports the --defaults-file, --defaults-extra-file and --no-defaults options. * An assertion designed to detect zero-length sort keys also was raised when the entire key set fit in memory. * myisampack could create corrupt FULLTEXT indexes when compressing tables. * A linking problem prevented the FEDERATED storage engine plugin from loading.
2011-10-22 12:32:37 +02:00
share/mysql/test/suite/innodb/r/innodb_corrupt_bit.result
share/mysql/test/suite/innodb/r/innodb_file_format.result
share/mysql/test/suite/innodb/r/innodb_gis.result
share/mysql/test/suite/innodb/r/innodb_information_schema.result
Changes 5.5.28: The internal interface of the Thread Pool plugin has changed. Old versions of the plugin will work with current versions of the server, but versions of the server older than 5.5.28 will not work with current versions of the plugin. Bugs Fixed InnoDB: Certain information_schema tables originally introduced in MySQL 5.6 are now also available in MySQL 5.5 and MySQL 5.1: INNODB_BUFFER_PAGE, INNODB_BUFFER_PAGE_LRU, and INNODB_BUFFER_POOL_STATS. InnoDB: When a SELECT ... FOR UPDATE, UPDATE, or other SQL statement scanned rows in an InnoDB table using a < or <= operator in a WHERE clause, the next row after the affected range could also be locked. This issue could cause a lock wait timeout for a row that was not expected to be locked. The issue occurred under various isolation levels, such as READ COMMITTED and REPEATABLE READ. Partitioning: For tables using PARTITION BY HASH or PARTITION BY KEY, when the partition pruning mechanism encountered a multi-range list or inequality using a column from the partitioning key, it continued with the next partitioning column and tried to use it for pruning, even if the previous column could not be used. This caused partitions which possibly matched one or more of the previous partitioning columns to be pruned away, leaving partitions that matched only the last column of the partitioning key. This issue was triggered when both of the following conditions were met: The columns making up the table's partitioning key were used in the same order as in the partitioning key definition by a SELECT statement's WHERE clause as in the column definitions; The WHERE condition used with the last column of the partitioning key was satisfied only by a single value, while the condition testing some previous column from the partitioning key was satisfied by a range of values. An example of a statement creating a partitioned table and a query against this for which the issue described above occurred is shown here: CREATE TABLE t1 ( c1 INT, c2 INT, PRIMARY KEY(c2, c1) ) PARTITION BY KEY() # Use primary key as partitioning key PARTITIONS 2; SELECT * FROM t1 WHERE c2 = 2 AND c1 <> 2; This issue is resolved by ensuring that partition pruning skips any remaining partitioning key columns once a partition key column that cannot be used in pruning is encountered. Partitioning: The buffer for the row currently read from each partition used for sorted reads was allocated on open and freed only when the partitioning handler was closed or destroyed. For SELECT statements on tables with many partitions and large rows, this could cause the server to use excessive amounts of memory. This issue has been addressed by allocating buffers for reads from partitioned tables only when they are needed and freeing them immediately once they are no longer needed. As part of this fix, memory is now allocated for reading from rows only in partitions that have not been pruned (see Section 18.4, “Partition Pruning”). Replication: On 64-bit Windows platforms, values greater than 4G for the max_binlog_cache_size and max_binlog_stmt_cache_size system variables were truncated to 4G. This caused LOAD DATA INFILE to fail when trying to load a file larger than 4G in size, even when max_binlog_cache_size was set to a value greater than this. Replication: In master-master replication with --log-slave-updates enabled, setting a user variable and then performing inserts using this variable caused the Exec_master_log_position column in the output of SHOW SLAVE STATUS not to be updated. The RPM spec file now also runs the test suite on the new binaries, before packaging them. The libmysqlclient_r client library exported symbols from yaSSL that conflict with OpenSSL. If a program linked against that library and libcurl, it could crash with a segmentation fault. The argument for LIMIT must be an integer, but if the argument was given by a placeholder in a prepared statement, the server did not reject noninteger values such as '5'. The Thread Pool plugin did not respect the wait_timeout timeout for client sessions. CHECK TABLE and REPAIR TABLE could crash if a key definition differed in the .frm and .MYI files of a MyISAM table. Now the server produces an error. A query for a FEDERATED table could return incorrect results when the underlying table had a compound index on two columns and the query included an AND condition on the columns. mysqlhotcopy failed for databases containing views. The argument to the --ssl-key option was not verified to exist and be a valid key. The resulting connection used SSL, but the key was not used. Adding a LIMIT clause to a query containing GROUP BY and ORDER BY could cause the optimizer to choose an incorrect index for processing the query, and return more rows than required. mysqlbinlog did not accept input on the standard input when the standard input was a pipe.
2012-10-01 17:54:40 +02:00
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_prefix_index_restart_server.result
Changes 5.5.19: * Performance of metadata locking operations on Windows XP systems was improved by instituting a cache for metadata lock objects. This permits the server to avoid expensive operations for creation and destruction of synchronization objects on XP. A new system variable, metadata_locks_cache_size, permits control over the size of the cache. The default size is 1024. * Replication: Previously, replication slaves could connect to the master server through master accounts that use nonnative authentication, except Windows native authentication. This is now also true for Windows native authentication. Bugs Fixed: * InnoDB Storage Engine: An internal deadlock could occur within InnoDB, on a server doing a substantial amount of change buffering for DML operations, particularly DELETE statements. * Rounding DBL_MAX returned DBL_MAX, not 'inf'. * mysql_upgrade did not upgrade the system tables or create the mysql_upgrade_info file when run with the --write-binlog or --skip-write-binlog option. * If a plugin was uninstalled, thread local variables for plugin variables of string type with wth PLUGIN_VAR_MEMALLOC flag were not freed. * Deadlock could occur when these four things happened at the same time: 1) An old dump thread was waiting for the binary log to grow. 2) The slave server that replicates from the old dump thread tried to reconnect. During reconnection, the new dump thread tried to kill the old dump thread. 3) A KILL statement tried to kill the old dump thread. 4) An INSERT statement caused a binary log rotation.
2011-12-13 13:14:49 +01:00
share/mysql/test/suite/innodb/r/innodb_replace.result
share/mysql/test/suite/innodb/r/innodb_timeout_rollback.result
share/mysql/test/suite/innodb/r/innodb_trx_weight.result
2014-11-29 11:01:29 +01:00
share/mysql/test/suite/innodb/r/insert_debug.result
share/mysql/test/suite/innodb/r/sp_temp_table.result
share/mysql/test/suite/innodb/r/strict_mode.result
Changes 5.5.44: 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: 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: Estimates that were too low for the size of merge chunks in the result sorting algorithm caused a server exit. * SHOW VARIABLES mutexes were being locked twice, resulting in a server exit. * A Provides rule in RPM .spec files misspelled “mysql-embedded” as “mysql-emdedded”. * Under certain conditions, the libedit command-line library could write outside an array boundary and cause a client program crash. * Host value matching for the grant tables could fail to use the most specific of values that contained wildcard characters. * A user with a name of event_scheduler could view the Event Scheduler process list without the PROCESS privilege. * SHOW GRANTS after connecting using a proxy user could display the password hash of the proxied user. * For a prepared statement with an ORDER BY that refers by column number to a GROUP_CONCAT() expression that has an outer reference, repeated statement execution could cause a server exit. * Loading corrupt spatial data into a MyISAM table could cause the server to exit during index building. * Certain queries for the INFORMATION_SCHEMA TABLES and COLUMNS tables could lead to excessive memory use when there were large numbers of empty InnoDB tables. * MySQL failed to compile using OpenSSL 0.9.8e.
2015-06-01 09:40:36 +02:00
share/mysql/test/suite/innodb/r/xa_recovery.result
share/mysql/test/suite/innodb/t/add_constraint.test
Changes 5.5.37: Functionality Added or Changed On Solaris, mysql_config --libs now includes -R/path/to/library so that libraries can be found at runtime. Bugs Fixed InnoDB: A regression introduced by Bug 14329288 would result in a performance degradation when a compressed table does not fit into memory. InnoDB: The maximum value for innodb_thread_sleep_delay is now 1000000 microseconds. The previous maximum value (4294967295 microseconds on 32-bit and 18446744073709551615 microseconds on 64-bit) was unnecessarily large. Because the maximum value of innodb_thread_sleep_delay is limited by the value set for innodb_adaptive_max_sleep_delay (when set to a non-zero value), the maximum value for innodb_thread_sleep_delay is now the same as the maximum value for innodb_adaptive_max_sleep_delay. InnoDB: In debug builds, creating a unique index on a binary column, with input data containing duplicate keys, would cause an assertion. InnoDB: InnoDB would fail to start when innodb_data_file_path specified the data file size in kilobytes by appending K to the size value. InnoDB: An insert buffer merge would cause an assertion error due to incorrectly handled ownership information for externally stored BLOBs. InnoDB: Assertion failure in thread thread_num in file ibuf0ibuf.cc line 4080 InnoDB: Failing assertion: rec_get_deleted_flag(rec, page_is_comp(page)) InnoDB: Decreasing the auto_increment_increment value would have no affect on the next auto-increment value. Replication: The server did not handle correctly the insertion of a row larger than 4 GB when using row-based replication. Replication: When using row-based replication, an additional auto-increment column on the slave version of a table was not updated correctly; a zero was inserted instead. Replication: Statements involving the Performance Schema tables should not be written to the binary log, because the content of these tables is applicable only to a given MySQL Server instance, and may differ greatly between different servers in a replication topology. The database administrator should be able to configure (INSERT, UPDATE, or DELETE) or flush (TRUNCATE TABLE) performance schema tables on a single server without affecting others. However, when replicating from a MySQL 5.5 master to a MySQL 5.5 or later slave, warnings about unsafe statements updating Performance Schema tables were elevated to errors. For MySQL 5.6 and later slaves, this prevented the simultaneous use of performance_schema and GTIDs (see Replication with Global Transaction Identifiers, in the MySQL 5.6 Manual). This fix causes all updates on tables in the performance_schema database to be filtered on the master and not replicated, regardless of the type of logging that is in effect. Prior to this fix, statements using were handled by being marked as unsafe for replication, which caused warnings during execution; the statements were nonetheless written to the binary log, regardless of the logging format in effect. Existing replication behavior for tables in the INFORMATION_SCHEMA database is not changed by this fix. For more information, see MySQL Performance Schema. Compilation failed if MySQL was configured with CFLAGS set to include a -Werror option with an argument. A shared libmysqld embedded server library was not built on Linux. While printing the server version, the mysql client did not check for buffer overflow in a string variable. Contraction information in a collation could be mishandled, resulting in incorrect decisions about whether a character is part of a contraction, and miscalculation of contraction weights. DROP TRIGGER succeeded even with the read_only system variable enabled. Updating the Performance Schema setup_instruments table on a replication master caused a slave to exit. Due to a race condition, it was possible for two threads to end up with the same query ID for different queries. When run by root, mysqld --help --verbose exited with a nonzero error code after displaying the help message. MySQL client programs from a Community Edition distribution could not connect using SSL to a MySQL server from an Enterprise Edition. This was due to a difference in certificate handling by yaSSL and OpenSSL (used for Community and Enterprise, respectively). OpenSSL expected a blank certificate to be sent when not all of the --ssl-ca, --ssl-cert, and --ssl-key options were specified, and yaSSL did not do so. To resolve this, yaSSL has been modified to send a blank certificate when an option is missing. A deadlock error occurring during subquery execution could cause an assertion to be raised. The Performance Schema stage/sql/Waiting to get readlock instrument is no longer used and has been removed. For system variables that take a string value, SET statements permitted an unquoted value, but values that contained dots were parsed incorrectly and only part of the value was assigned. For example, SET GLOBAL slow_query_log_file = my_slow.log assigned the value my_slow. Now such values must be quoted or an error occurs. On Windows, mysql_install_db.pl could be run only from within the bin directory under the installation directory.
2014-03-31 10:03:22 +02:00
share/mysql/test/suite/innodb/t/blob-update-debug.test
share/mysql/test/suite/innodb/t/create-index.test
share/mysql/test/suite/innodb/t/disabled.def
share/mysql/test/suite/innodb/t/dropdb.test
share/mysql/test/suite/innodb/t/foreign-keys.test
2014-11-29 11:01:29 +01:00
share/mysql/test/suite/innodb/t/foreign-keys.test.moved
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
Changes 5.5.22: * InnoDB Storage Engine: A deprecation warning is now issued when --ignore-builtin-innodb is used. * yaSSL was upgraded from version 1.7.2 to 2.2.0. * Security Fix: Bug 13510739 and Bug 63775 were fixed. * Important Change: InnoDB Storage Engine: When a row grew in size due to an UPDATE operation, other (non-updated) columns could be moved to off-page storage so that information about the row still fit within the constraints of the InnoDB page size. The pointer to the new allocated off-page data was not set up until the pages were allocated and written, potentially leading to lost data if the system crashed while the column was being moved out of the page. The problem was more common with tables using ROW_FORMAT=DYNAMIC or ROW_FORMAT=COMPRESSED along with the Barracuda file format, particularly with the innodb_file_per_table setting enabled, because page allocation operations are more common as the .ibd tablespace files are extended. Still, the problem could occur with any combination of InnoDB version, file format, and row format. * InnoDB Storage Engine: An erroneous assertion could occur, in debug builds only, when creating an index on a column containing zero-length values (that is, ''). * InnoDB Storage Engine: A DDL operation such as ALTER TABLE ... ADD COLUMN could stall, eventually timing out with an Error 1005: Can't create table message referring to fil_rename_tablespace. * InnoDB Storage Engine: A DDL operation for an InnoDB table could cause a busy MySQL server to halt with an assertion error: More...
2012-04-08 20:30:27 +02:00
share/mysql/test/suite/innodb/t/innodb-blob.test
Changes 5.5.36: Functionality Added or Changed 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>. Thanks to Honza Horak for the patch. Bugs Fixed InnoDB: Table renaming errors would appear in the LATEST FOREIGN KEY ERROR section of the SHOW ENGINE INNODB STATUS output. Partitioning: Queries using the index_merge optimization (see Index Merge Optimization) could return invalid results when run against tables that were partitioned by HASH. Partitioning: When no partition had returned a row since the last HA_ERR_KEY_NOT_FOUND error, the use of uninitialized memory in the priority queue used for returning rows in sorted order could lead to a crash of the server. Replication: mysqlbinlog --verbose failed when it encountered a corrupt row event in the binary log. Such a row event could also cause the slave to fail. Replication: When log_warnings is greater than 1, the master prints binary log dump thread information—containing the slave server ID, binary log file name, and binary log position—in mysqld.1.err. A slave server ID greater than 2 billion was printed with a negative value in such cases. Replication: Invalid event offsets in the binary log were not always handled correctly, which could lead to replication failure. The cache used for the Index Merge access method was freed only after successful retrieval of all rows. Interruption or failure of the operation led to a file descriptor leak. For utf8 and utf8mb4 strings, handler functions unnecessarily called a Unicode conversion function. Use of a nonmulti-byte algorithm for skipping leading spaces in multi-byte strings could cause a server exit. For the utf8_bin collation, ORDER BY LOWER(col_name) could produce incorrect ordering. On Windows, the --local-service server option did not work, and was not displayed in the --help message. The prototype of the Performance Schema instrumentation API mysql_cond_timedwait() call was fixed to be drop-in compatible with pthread_cond_timedwait(). This fix affects only implementers of third-party plugins. For the path specified with the --basedir option, mysql_plugin attempted to unlink the path rather than free the memory in which the path was stored. COUNT(DISTINCT) sometimes produced an incorrect result when the last read row contained a NULL value. Some scripts displayed out-of-date information regarding where to report bugs. Updating a FEDERATED table with UPDATE... JOIN caused a server exit when the local table contained a single row and that row could be joined to a row in the FEDERATED table. mysql_install_db referred to the obsolete mysqlbug script for reporting problems. It now refers to http://bugs.mysql.com/ instead.
2014-02-01 12:16:03 +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
share/mysql/test/suite/innodb/t/innodb-consistent-master.opt
share/mysql/test/suite/innodb/t/innodb-consistent.test
Changes 5.5.39: CMake support was updated to handle CMake version 3. The timed_mutexes system variable has no effect and is deprecated. Bugs Fixed InnoDB: Opening a parent table that has thousands of child tables could result in a long semaphore wait condition. Partitioning: Selecting from a table having multiple columns in its primary key and partitioned by LIST COLUMNS(R), where R was the last (rightmost) column listed in the primary key definition, returned an incorrect result. Replication: When using row-based replication, updating or deleting a row on the master that did not exist on the slave led to failure of the slave when it tried to process the change. This problem occurred with InnoDB tables lacking a primary key. Replication: Quotation marks were not always handled correctly by LOAD DATA INFILE when written into the binary log. Replication: A group of threads involved in acquiring locks could deadlock when the following events occurred: Dump thread reconnects from slave; on master, a new dump thread tries to kill zombie dump threads; having acquired the thread's LOCK_thd_data, it is about to acquire LOCK_log. Application thread executing show binary logs, having acquired LOCK_log and about to acquire LOCK_index. Application thread executing PURGE BINARY LOGS; having acquired LOCK_index, it is about to acquire LOCK_thread_count. Application thread executing SHOW PROCESSLIST (or SELECT * FROM INFORMATION_SCHEMA.PROCESSLIST), having acquired LOCK_thread_count and about to acquire the zombie dump thread's LOCK_thd_data.
2014-08-10 16:27:40 +02:00
share/mysql/test/suite/innodb/t/innodb-fk.test
share/mysql/test/suite/innodb/t/innodb-index.test
share/mysql/test/suite/innodb/t/innodb-index_ucs2.test
share/mysql/test/suite/innodb/t/innodb-lock.test
share/mysql/test/suite/innodb/t/innodb-master.opt
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
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.5.37: Functionality Added or Changed On Solaris, mysql_config --libs now includes -R/path/to/library so that libraries can be found at runtime. Bugs Fixed InnoDB: A regression introduced by Bug 14329288 would result in a performance degradation when a compressed table does not fit into memory. InnoDB: The maximum value for innodb_thread_sleep_delay is now 1000000 microseconds. The previous maximum value (4294967295 microseconds on 32-bit and 18446744073709551615 microseconds on 64-bit) was unnecessarily large. Because the maximum value of innodb_thread_sleep_delay is limited by the value set for innodb_adaptive_max_sleep_delay (when set to a non-zero value), the maximum value for innodb_thread_sleep_delay is now the same as the maximum value for innodb_adaptive_max_sleep_delay. InnoDB: In debug builds, creating a unique index on a binary column, with input data containing duplicate keys, would cause an assertion. InnoDB: InnoDB would fail to start when innodb_data_file_path specified the data file size in kilobytes by appending K to the size value. InnoDB: An insert buffer merge would cause an assertion error due to incorrectly handled ownership information for externally stored BLOBs. InnoDB: Assertion failure in thread thread_num in file ibuf0ibuf.cc line 4080 InnoDB: Failing assertion: rec_get_deleted_flag(rec, page_is_comp(page)) InnoDB: Decreasing the auto_increment_increment value would have no affect on the next auto-increment value. Replication: The server did not handle correctly the insertion of a row larger than 4 GB when using row-based replication. Replication: When using row-based replication, an additional auto-increment column on the slave version of a table was not updated correctly; a zero was inserted instead. Replication: Statements involving the Performance Schema tables should not be written to the binary log, because the content of these tables is applicable only to a given MySQL Server instance, and may differ greatly between different servers in a replication topology. The database administrator should be able to configure (INSERT, UPDATE, or DELETE) or flush (TRUNCATE TABLE) performance schema tables on a single server without affecting others. However, when replicating from a MySQL 5.5 master to a MySQL 5.5 or later slave, warnings about unsafe statements updating Performance Schema tables were elevated to errors. For MySQL 5.6 and later slaves, this prevented the simultaneous use of performance_schema and GTIDs (see Replication with Global Transaction Identifiers, in the MySQL 5.6 Manual). This fix causes all updates on tables in the performance_schema database to be filtered on the master and not replicated, regardless of the type of logging that is in effect. Prior to this fix, statements using were handled by being marked as unsafe for replication, which caused warnings during execution; the statements were nonetheless written to the binary log, regardless of the logging format in effect. Existing replication behavior for tables in the INFORMATION_SCHEMA database is not changed by this fix. For more information, see MySQL Performance Schema. Compilation failed if MySQL was configured with CFLAGS set to include a -Werror option with an argument. A shared libmysqld embedded server library was not built on Linux. While printing the server version, the mysql client did not check for buffer overflow in a string variable. Contraction information in a collation could be mishandled, resulting in incorrect decisions about whether a character is part of a contraction, and miscalculation of contraction weights. DROP TRIGGER succeeded even with the read_only system variable enabled. Updating the Performance Schema setup_instruments table on a replication master caused a slave to exit. Due to a race condition, it was possible for two threads to end up with the same query ID for different queries. When run by root, mysqld --help --verbose exited with a nonzero error code after displaying the help message. MySQL client programs from a Community Edition distribution could not connect using SSL to a MySQL server from an Enterprise Edition. This was due to a difference in certificate handling by yaSSL and OpenSSL (used for Community and Enterprise, respectively). OpenSSL expected a blank certificate to be sent when not all of the --ssl-ca, --ssl-cert, and --ssl-key options were specified, and yaSSL did not do so. To resolve this, yaSSL has been modified to send a blank certificate when an option is missing. A deadlock error occurring during subquery execution could cause an assertion to be raised. The Performance Schema stage/sql/Waiting to get readlock instrument is no longer used and has been removed. For system variables that take a string value, SET statements permitted an unquoted value, but values that contained dots were parsed incorrectly and only part of the value was assigned. For example, SET GLOBAL slow_query_log_file = my_slow.log assigned the value my_slow. Now such values must be quoted or an error occurs. On Windows, mysql_install_db.pl could be run only from within the bin directory under the installation directory.
2014-03-31 10:03:22 +02:00
share/mysql/test/suite/innodb/t/innodb-update-insert.test
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.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.5.22: * InnoDB Storage Engine: A deprecation warning is now issued when --ignore-builtin-innodb is used. * yaSSL was upgraded from version 1.7.2 to 2.2.0. * Security Fix: Bug 13510739 and Bug 63775 were fixed. * Important Change: InnoDB Storage Engine: When a row grew in size due to an UPDATE operation, other (non-updated) columns could be moved to off-page storage so that information about the row still fit within the constraints of the InnoDB page size. The pointer to the new allocated off-page data was not set up until the pages were allocated and written, potentially leading to lost data if the system crashed while the column was being moved out of the page. The problem was more common with tables using ROW_FORMAT=DYNAMIC or ROW_FORMAT=COMPRESSED along with the Barracuda file format, particularly with the innodb_file_per_table setting enabled, because page allocation operations are more common as the .ibd tablespace files are extended. Still, the problem could occur with any combination of InnoDB version, file format, and row format. * InnoDB Storage Engine: An erroneous assertion could occur, in debug builds only, when creating an index on a column containing zero-length values (that is, ''). * InnoDB Storage Engine: A DDL operation such as ALTER TABLE ... ADD COLUMN could stall, eventually timing out with an Error 1005: Can't create table message referring to fil_rename_tablespace. * InnoDB Storage Engine: A DDL operation for an InnoDB table could cause a busy MySQL server to halt with an assertion error: More...
2012-04-08 20:30:27 +02:00
share/mysql/test/suite/innodb/t/innodb_bug11754376.test
Changes 5.5.23: Bugs Fixed * Security Fix: Bug 59533 was fixed. * Performance: Partitioning: InnoDB Storage Engine: The statistics used by the optimizer for queries against partitioned InnoDB tables were based only on the first partition of each such table, leading to use of the wrong execution plan. * References: This bug was introduced by Bug 11756867. * Performance: InnoDB Storage Engine: Improved the performance of the DROP TABLE statement for InnoDB tables, especially on systems with a large buffer pool. The fix speeds up the processing for freeing entries in the adaptive hash index. * InnoDB Storage Engine: Deleting a huge amount of data from InnoDB tables within a short time could cause the purge operation that flushes data from the buffer pool to stall. If this issue occurs, restart the server to work around it. This issue is only likely to occur on 32-bit platforms. * InnoDB Storage Engine: If the server crashed during a TRUNCATE TABLE or CREATE INDEX statement for an InnoDB table, or a DROP DATABASE statement for a database containing InnoDB tables, an index could be corrupted, causing an error message when accessing the table after restart: InnoDB: Error: trying to load index index_name for table table_name InnoDB: but the index tree has been freed! In MySQL 5.1, this fix applies to the InnoDB Plugin, but not the built-in InnoDB storage engine. * InnoDB Storage Engine: When data was removed from an InnoDB table, newly inserted data might not reuse the freed disk blocks, leading to an unexpected size increase for the system tablespace or .ibd file (depending on the setting of innodb_file_per_table. The OPTIMIZE TABLE could compact a .ibd file in some cases but not others. The freed disk blocks would eventually be reused as additional data was inserted. More...
2012-04-14 14:10:05 +02:00
share/mysql/test/suite/innodb/t/innodb_bug11766634-master.opt
share/mysql/test/suite/innodb/t/innodb_bug11766634.test
Changes 5.5.21: * A new CMake option, MYSQL_PROJECT_NAME, can be set on Windows or Mac OS X to be used in the project name. Bugs Fixed * Performance: InnoDB Storage Engine: Memory allocation for InnoDB tables was reorganized to reduce the memory overhead for large numbers of tables or partitions, avoiding situations where the “resident set size” could grow regardless of FLUSH TABLES statements. The problem was most evident for tables with large row size. * Incompatible Change: An earlier change (in MySQL 5.1.62 and 5.5.21) was found to modify date-handling behavior in General Availability-status series (MySQL 5.1 and 5.5). This change has been reverted. * The change was that several functions became more strict when passed a DATE() function value as their argument, thus they rejected incomplete dates with a day part of zero. These functions were affected: CONVERT_TZ(), DATE_ADD(), DATE_SUB(), DAYOFYEAR(), LAST_DAY(), TIMESTAMPDIFF(), TO_DAYS(), TO_SECONDS(), WEEK(), WEEKDAY(), WEEKOFYEAR(), YEARWEEK(). The previous behavior has been restored. * InnoDB Storage Engine: A Valgrind error was fixed in the function os_aio_init(). * InnoDB Storage Engine: The server could crash when creating an InnoDB temporary table under Linux, if the $TMPDIR setting points to a tmpfs filesystem and innodb_use_native_aio is enabled, as it is by default in MySQL 5.5.4 and higher. * InnoDB Storage Engine: References to C preprocessor symbols and macros HAVE_purify, UNIV_INIT_MEM_TO_ZERO, and UNIV_SET_MEM_TO_ZERO were removed from the InnoDB source code. They were only used in debug builds instrumented for Valgrind. They are replaced by calls to the UNIV_MEM_INVALID() macro.
2012-02-23 14:01:03 +01:00
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_bug12661768.test
Changes 5.5.25: * The --safe-mode server option now is deprecated and will be removed in MySQL 5.6. * Performance: InnoDB: Improved the algorithm related to adaptive flushing. This fix increases the rate of flushing in cases where compression is used and the data set is larger than the buffer pool, leading to eviction. * InnoDB: In a transaction using the REPEATABLE READ isolation level, an UPDATE or DELETE statement for an InnoDB table could sometimes overlook rows recently committed by other transactions. As explained in Section 14.3.9.2, “Consistent Nonlocking Reads”, DML statements within a REPEATABLE READ transaction apply to rows committed by other transactions, even if a query could not see those rows. * InnoDB: The Innodb_buffer_pool_pages_flushed status variable was incorrectly set to twice the value it should be. Its value should never exceed the value of Innodb_pages_written. * InnoDB: The error handling and message was improved for attempting to create a foreign key with a column referencing itself. The message suggested a potential problem with the data dictionary, when no such problem existed. * InnoDB: The CHECK TABLE statement could fail for a large InnoDB table due to a timeout value of 2 hours. For typical storage devices, the issue could occur for tables that exceeded approximately 200 or 350 GB, depending on I/O speed. The fix relaxes the locking performed on the table being checked, which makes the timeout less likely. It also makes InnoDB recognize the syntax CHECK TABLE QUICK, which avoids the possibility of the timeout entirely. * Replication: It was theoretically possible for concurrent execution of more than one instance of SHOW BINLOG EVENTS to crash the MySQL Server. * Replication: Statements using AUTO_INCREMENT, LAST_INSERT_ID(), RAND(), or user variables could be applied in the wrong context on the slave when using statement-based replication and replication filtering server options (see Section 16.2.3, “How Servers Evaluate Replication Filtering Rules”). * Replication: An INSERT into a table that has a composite primary key that includes an AUTO_INCREMENT column that is not the first column of this composite key is not safe for statement-based binary logging or replication. Such statements are now marked as unsafe and fail with an error when using the STATEMENT binary logging format. For more information, see Section 16.1.2.3, “Determination of Safe and Unsafe Statements in Binary Logging”, as well as Section 16.4.1.1, “Replication and AUTO_INCREMENT”.
2012-06-03 00:28:00 +02:00
share/mysql/test/suite/innodb/t/innodb_bug12902967.test
Changes 5.5.22: * InnoDB Storage Engine: A deprecation warning is now issued when --ignore-builtin-innodb is used. * yaSSL was upgraded from version 1.7.2 to 2.2.0. * Security Fix: Bug 13510739 and Bug 63775 were fixed. * Important Change: InnoDB Storage Engine: When a row grew in size due to an UPDATE operation, other (non-updated) columns could be moved to off-page storage so that information about the row still fit within the constraints of the InnoDB page size. The pointer to the new allocated off-page data was not set up until the pages were allocated and written, potentially leading to lost data if the system crashed while the column was being moved out of the page. The problem was more common with tables using ROW_FORMAT=DYNAMIC or ROW_FORMAT=COMPRESSED along with the Barracuda file format, particularly with the innodb_file_per_table setting enabled, because page allocation operations are more common as the .ibd tablespace files are extended. Still, the problem could occur with any combination of InnoDB version, file format, and row format. * InnoDB Storage Engine: An erroneous assertion could occur, in debug builds only, when creating an index on a column containing zero-length values (that is, ''). * InnoDB Storage Engine: A DDL operation such as ALTER TABLE ... ADD COLUMN could stall, eventually timing out with an Error 1005: Can't create table message referring to fil_rename_tablespace. * InnoDB Storage Engine: A DDL operation for an InnoDB table could cause a busy MySQL server to halt with an assertion error: More...
2012-04-08 20:30:27 +02:00
share/mysql/test/suite/innodb/t/innodb_bug13510739.test
Update mysql55-{client,server} to 5.55.24. Changes (http://dev.mysql.com/doc/refman/5.5/en/news-5-5-24.html): Functionality Added or Changed * Important Change: Replication: INSERT ON DUPLICATE KEY UPDATE is now marked as unsafe for statement-based replication if the target table has more than one primary or unique key. For more information, see Section 16.1.2.3, "Determination of Safe and Unsafe Statements in Binary Logging". Bugs Fixed * Security Fix: Bug #64884 was fixed. * InnoDB: Replication: When binary log statements were replayed on the slave, the Com_insert, Com_update, and Com_delete counters were incremented by BEGIN statements initiating transactions affecting InnoDB tables but not by COMMIT statements ending such transactions. This affected these statements whether they were replicated or they were run using mysqlbinlog. (Bug #12662190) * If the --bind-address option was given a host name value and the host name resolved to more than one IP address, the server failed to start. For example, with --bind-address=localhost, if localhost resolved to both 127.0.0.1 and ::1, startup failed. Now the server prefers the IPv4 address in such cases. (Bug #61713, Bug #12762885) * mysql_store_result() and mysql_use_result() are not for use with prepared statements and are not intended to be called following mysql_stmt_execute(), but failed to return an error when invoked that way in libmysqld. (Bug #62136, Bug #13738989) References: See also Bug #47485. * On Windows, mysqlslap crashed for attempts to connect using shared memory. (Bug #31173, Bug #11747181, Bug #59107, Bug #11766072)
2012-05-13 15:05:33 +02:00
share/mysql/test/suite/innodb/t/innodb_bug13635833.test
Changes 5.5.25: * The --safe-mode server option now is deprecated and will be removed in MySQL 5.6. * Performance: InnoDB: Improved the algorithm related to adaptive flushing. This fix increases the rate of flushing in cases where compression is used and the data set is larger than the buffer pool, leading to eviction. * InnoDB: In a transaction using the REPEATABLE READ isolation level, an UPDATE or DELETE statement for an InnoDB table could sometimes overlook rows recently committed by other transactions. As explained in Section 14.3.9.2, “Consistent Nonlocking Reads”, DML statements within a REPEATABLE READ transaction apply to rows committed by other transactions, even if a query could not see those rows. * InnoDB: The Innodb_buffer_pool_pages_flushed status variable was incorrectly set to twice the value it should be. Its value should never exceed the value of Innodb_pages_written. * InnoDB: The error handling and message was improved for attempting to create a foreign key with a column referencing itself. The message suggested a potential problem with the data dictionary, when no such problem existed. * InnoDB: The CHECK TABLE statement could fail for a large InnoDB table due to a timeout value of 2 hours. For typical storage devices, the issue could occur for tables that exceeded approximately 200 or 350 GB, depending on I/O speed. The fix relaxes the locking performed on the table being checked, which makes the timeout less likely. It also makes InnoDB recognize the syntax CHECK TABLE QUICK, which avoids the possibility of the timeout entirely. * Replication: It was theoretically possible for concurrent execution of more than one instance of SHOW BINLOG EVENTS to crash the MySQL Server. * Replication: Statements using AUTO_INCREMENT, LAST_INSERT_ID(), RAND(), or user variables could be applied in the wrong context on the slave when using statement-based replication and replication filtering server options (see Section 16.2.3, “How Servers Evaluate Replication Filtering Rules”). * Replication: An INSERT into a table that has a composite primary key that includes an AUTO_INCREMENT column that is not the first column of this composite key is not safe for statement-based binary logging or replication. Such statements are now marked as unsafe and fail with an error when using the STATEMENT binary logging format. For more information, see Section 16.1.2.3, “Determination of Safe and Unsafe Statements in Binary Logging”, as well as Section 16.4.1.1, “Replication and AUTO_INCREMENT”.
2012-06-03 00:28:00 +02:00
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_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
Changes 5.5.13: * InnoDB Storage Engine: If the server crashed while an XA transaction was prepared but not yet committed, the transaction could remain in the system after restart, and cause a subsequent shutdown to hang. * InnoDB Storage Engine: Similar problem to the foreign key error in bug 11831040 / 60196 / 60909, but with a different root cause and occurring on Mac OS X. With the setting lower_case_table_names=2, inserts into InnoDB tables covered by foreign key constraints could fail after a server restart. * Partitioning: The internal get_partition_set() function did not take into account the possibility that a key specification could be NULL in some cases. * Partitioning: When executing a row-ordered retrieval index merge, the partitioning handler used memory from from that allocated for the table, rather than that allocated to the query, causing table object memory not to be freed until the table was closed. * Replication: A spurious error malformed binlog: it does not contain any Format_description_log_event... was generated when mysqlbinlog was invoked using --base64-output=decode-row and --start-position=pos, where pos is a point in the binary log past the format description log event. However, there is nothing unsafe about not printing the format description log event, so the error has been removed for this case. * Replication: Typographical errors appeared in the text of several replication error messages. (The word “position” was misspelled as “postion”.) * Assignments to NEW.var_name within triggers, where var_name had a BLOB or TEXT type, were not properly handled and produced incorrect results. * XA COMMIT could fail to clean up the error state if it discovered that the current XA transaction had to be rolled back. Consequently, the next XA transaction could raise an assertion when it checked for proper cleanup of the previous transaction. * An internal client macro reference was removed from the client_plugin.h header file. This reference made the file unusable. * The server consumed memory for repeated invocation of some stored procedures, which was not released until the connection terminated. * The server did not check for certain invalid out of order sequences of XA statements, and these sequences raised an assertion. * With the conversion from GNU autotools to CMake for configuring MySQL, the USE_SYMDIR preprocessor symbol was omitted. This caused failure of symbolic links (described at Section 7.11.3.1, “Using Symbolic Links”).
2011-06-15 23:00:05 +02:00
share/mysql/test/suite/innodb/t/innodb_bug59410.test
share/mysql/test/suite/innodb/t/innodb_bug59641.test
Changes 5.5.17: * Replication: Previously, replication slaves could connect to the master server only through master accounts that use native authentication. Now replication slaves can also connect through master accounts that use nonnative authentication (except Windows native authentication) if the required client-side plugin is installed on the slave side in the directory named by the slave plugin_dir system variable. * MEMORY table creation time is now available in the CREATE_TIME column of the INFORMATION_SCHEMA.TABLES table and the Create_time column of SHOW TABLE STATUS output. * InnoDB Storage Engine: This fix improves the performance of instrumentation code for InnoDB buffer pool operations. * InnoDB Storage Engine: Data from BLOB columns could be lost if the server crashed at a precise moment when other columns were being updated in an InnoDB table. * InnoDB Storage Engine: Lookups using secondary indexes could give incorrect matches under a specific set of conditions. The conditions involve an index defined on a column prefix, for a BLOB or other long column stored outside the index page, with a table using the Barracuda file format. * InnoDB Storage Engine: This fix corrects cases where the MySQL server could hang or abort with a long semaphore wait message. (This is a different issue than when these symptoms occurred during a CHECK TABLE statement.) * Internal conversion of zero to binary and back could yield a result with incorrect precision. * Valgrind warnings generated by filesort operations were fixed. * mysqld_safe did not properly check for an already running instance of mysqld. * The help message for mysql_install_db did not indicate that it supports the --defaults-file, --defaults-extra-file and --no-defaults options. * An assertion designed to detect zero-length sort keys also was raised when the entire key set fit in memory. * myisampack could create corrupt FULLTEXT indexes when compressing tables. * A linking problem prevented the FEDERATED storage engine plugin from loading.
2011-10-22 12:32:37 +02:00
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
Changes 5.5.20: * A new server option, --slow-start-timeout, controls the Windows service control manager's service start timeout. The value is the maximum number of milliseconds that the service control manager waits before trying to kill the MySQL service during startup. The default value is 15000 (15 seconds). If the MySQL service takes too long to start, you may need to increase this value. A value of 0 means there is no timeout. Bugs Fixed: * Important Change: Replication: Setting an empty user in a CHANGE MASTER TO statement caused an invalid internal result and is no longer permitted. Trying to use MASTER_USER='' or setting MASTER_PASSWORD while leaving MASTER_USER unset causes the statement to fail with an error. * Important Change: Replication: Moving the binary log file, relay log file, or both files to a new location, then restarting the server with a new value for --log-bin, --relay-log, or both, caused the server to abort on start. This was because the entries in the index file overrode the new location. In addition, paths were calculated relative to datadir (rather than to the --log-bin or --relay-log values). * InnoDB Storage Engine: When doing a live downgrade from MySQL 5.6.4 or later, with innodb_page_size set to a value other than 16384, now the earlier MySQL version reports that the page size is incompatible with the older version, rather than crashing or displaying a “corruption” error. * InnoDB Storage Engine: Issuing INSERT...ON DUPLICATE KEY statements for InnoDB tables from concurrent threads could cause a deadlock, particularly with the INSERT...ON DUPLICATE KEY UPDATE form. The fix avoids deadlocks caused by the same row being accessed by more than one transaction. Deadlocks could still occur when multiple rows are inserted and updated simultaneously by different transactions in inconsistent order; those types of deadlocks require the standard error handling on the application side, of re-trying the transaction. * An incorrect InnoDB assertion could cause the server to halt. This issue only affected debug builds. The assertion referenced the source file btr0pcur.ic and the variable cursor->pos_state. * Locale information for FORMAT() function instances was lost in view definitions. * The handle_segfault() signal-handler code in mysqld could itself crash due to calling unsafe functions. * Enabling myisam_use_mmap could cause the server to crash. * Concurrent access to ARCHIVE tables could cause corruption.
2012-01-12 17:33:49 +01:00
share/mysql/test/suite/innodb/t/innodb_bug60229.test
Changes 5.5.17: * Replication: Previously, replication slaves could connect to the master server only through master accounts that use native authentication. Now replication slaves can also connect through master accounts that use nonnative authentication (except Windows native authentication) if the required client-side plugin is installed on the slave side in the directory named by the slave plugin_dir system variable. * MEMORY table creation time is now available in the CREATE_TIME column of the INFORMATION_SCHEMA.TABLES table and the Create_time column of SHOW TABLE STATUS output. * InnoDB Storage Engine: This fix improves the performance of instrumentation code for InnoDB buffer pool operations. * InnoDB Storage Engine: Data from BLOB columns could be lost if the server crashed at a precise moment when other columns were being updated in an InnoDB table. * InnoDB Storage Engine: Lookups using secondary indexes could give incorrect matches under a specific set of conditions. The conditions involve an index defined on a column prefix, for a BLOB or other long column stored outside the index page, with a table using the Barracuda file format. * InnoDB Storage Engine: This fix corrects cases where the MySQL server could hang or abort with a long semaphore wait message. (This is a different issue than when these symptoms occurred during a CHECK TABLE statement.) * Internal conversion of zero to binary and back could yield a result with incorrect precision. * Valgrind warnings generated by filesort operations were fixed. * mysqld_safe did not properly check for an already running instance of mysqld. * The help message for mysql_install_db did not indicate that it supports the --defaults-file, --defaults-extra-file and --no-defaults options. * An assertion designed to detect zero-length sort keys also was raised when the entire key set fit in memory. * myisampack could create corrupt FULLTEXT indexes when compressing tables. * A linking problem prevented the FEDERATED storage engine plugin from loading.
2011-10-22 12:32:37 +02:00
share/mysql/test/suite/innodb/t/innodb_corrupt_bit.test
share/mysql/test/suite/innodb/t/innodb_file_format-master.opt
share/mysql/test/suite/innodb/t/innodb_file_format.test
share/mysql/test/suite/innodb/t/innodb_gis.test
share/mysql/test/suite/innodb/t/innodb_information_schema.test
Changes 5.5.28: The internal interface of the Thread Pool plugin has changed. Old versions of the plugin will work with current versions of the server, but versions of the server older than 5.5.28 will not work with current versions of the plugin. Bugs Fixed InnoDB: Certain information_schema tables originally introduced in MySQL 5.6 are now also available in MySQL 5.5 and MySQL 5.1: INNODB_BUFFER_PAGE, INNODB_BUFFER_PAGE_LRU, and INNODB_BUFFER_POOL_STATS. InnoDB: When a SELECT ... FOR UPDATE, UPDATE, or other SQL statement scanned rows in an InnoDB table using a < or <= operator in a WHERE clause, the next row after the affected range could also be locked. This issue could cause a lock wait timeout for a row that was not expected to be locked. The issue occurred under various isolation levels, such as READ COMMITTED and REPEATABLE READ. Partitioning: For tables using PARTITION BY HASH or PARTITION BY KEY, when the partition pruning mechanism encountered a multi-range list or inequality using a column from the partitioning key, it continued with the next partitioning column and tried to use it for pruning, even if the previous column could not be used. This caused partitions which possibly matched one or more of the previous partitioning columns to be pruned away, leaving partitions that matched only the last column of the partitioning key. This issue was triggered when both of the following conditions were met: The columns making up the table's partitioning key were used in the same order as in the partitioning key definition by a SELECT statement's WHERE clause as in the column definitions; The WHERE condition used with the last column of the partitioning key was satisfied only by a single value, while the condition testing some previous column from the partitioning key was satisfied by a range of values. An example of a statement creating a partitioned table and a query against this for which the issue described above occurred is shown here: CREATE TABLE t1 ( c1 INT, c2 INT, PRIMARY KEY(c2, c1) ) PARTITION BY KEY() # Use primary key as partitioning key PARTITIONS 2; SELECT * FROM t1 WHERE c2 = 2 AND c1 <> 2; This issue is resolved by ensuring that partition pruning skips any remaining partitioning key columns once a partition key column that cannot be used in pruning is encountered. Partitioning: The buffer for the row currently read from each partition used for sorted reads was allocated on open and freed only when the partitioning handler was closed or destroyed. For SELECT statements on tables with many partitions and large rows, this could cause the server to use excessive amounts of memory. This issue has been addressed by allocating buffers for reads from partitioned tables only when they are needed and freeing them immediately once they are no longer needed. As part of this fix, memory is now allocated for reading from rows only in partitions that have not been pruned (see Section 18.4, “Partition Pruning”). Replication: On 64-bit Windows platforms, values greater than 4G for the max_binlog_cache_size and max_binlog_stmt_cache_size system variables were truncated to 4G. This caused LOAD DATA INFILE to fail when trying to load a file larger than 4G in size, even when max_binlog_cache_size was set to a value greater than this. Replication: In master-master replication with --log-slave-updates enabled, setting a user variable and then performing inserts using this variable caused the Exec_master_log_position column in the output of SHOW SLAVE STATUS not to be updated. The RPM spec file now also runs the test suite on the new binaries, before packaging them. The libmysqlclient_r client library exported symbols from yaSSL that conflict with OpenSSL. If a program linked against that library and libcurl, it could crash with a segmentation fault. The argument for LIMIT must be an integer, but if the argument was given by a placeholder in a prepared statement, the server did not reject noninteger values such as '5'. The Thread Pool plugin did not respect the wait_timeout timeout for client sessions. CHECK TABLE and REPAIR TABLE could crash if a key definition differed in the .frm and .MYI files of a MyISAM table. Now the server produces an error. A query for a FEDERATED table could return incorrect results when the underlying table had a compound index on two columns and the query included an AND condition on the columns. mysqlhotcopy failed for databases containing views. The argument to the --ssl-key option was not verified to exist and be a valid key. The resulting connection used SSL, but the key was not used. Adding a LIMIT clause to a query containing GROUP BY and ORDER BY could cause the optimizer to choose an incorrect index for processing the query, and return more rows than required. mysqlbinlog did not accept input on the standard input when the standard input was a pipe.
2012-10-01 17:54:40 +02:00
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_prefix_index_restart_server.test
Changes 5.5.19: * Performance of metadata locking operations on Windows XP systems was improved by instituting a cache for metadata lock objects. This permits the server to avoid expensive operations for creation and destruction of synchronization objects on XP. A new system variable, metadata_locks_cache_size, permits control over the size of the cache. The default size is 1024. * Replication: Previously, replication slaves could connect to the master server through master accounts that use nonnative authentication, except Windows native authentication. This is now also true for Windows native authentication. Bugs Fixed: * InnoDB Storage Engine: An internal deadlock could occur within InnoDB, on a server doing a substantial amount of change buffering for DML operations, particularly DELETE statements. * Rounding DBL_MAX returned DBL_MAX, not 'inf'. * mysql_upgrade did not upgrade the system tables or create the mysql_upgrade_info file when run with the --write-binlog or --skip-write-binlog option. * If a plugin was uninstalled, thread local variables for plugin variables of string type with wth PLUGIN_VAR_MEMALLOC flag were not freed. * Deadlock could occur when these four things happened at the same time: 1) An old dump thread was waiting for the binary log to grow. 2) The slave server that replicates from the old dump thread tried to reconnect. During reconnection, the new dump thread tried to kill the old dump thread. 3) A KILL statement tried to kill the old dump thread. 4) An INSERT statement caused a binary log rotation.
2011-12-13 13:14:49 +01:00
share/mysql/test/suite/innodb/t/innodb_replace.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
2014-11-29 11:01:29 +01:00
share/mysql/test/suite/innodb/t/insert_debug.test
share/mysql/test/suite/innodb/t/sp_temp_table.test
share/mysql/test/suite/innodb/t/strict_mode.test
Changes 5.5.44: 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: 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: Estimates that were too low for the size of merge chunks in the result sorting algorithm caused a server exit. * SHOW VARIABLES mutexes were being locked twice, resulting in a server exit. * A Provides rule in RPM .spec files misspelled “mysql-embedded” as “mysql-emdedded”. * Under certain conditions, the libedit command-line library could write outside an array boundary and cause a client program crash. * Host value matching for the grant tables could fail to use the most specific of values that contained wildcard characters. * A user with a name of event_scheduler could view the Event Scheduler process list without the PROCESS privilege. * SHOW GRANTS after connecting using a proxy user could display the password hash of the proxied user. * For a prepared statement with an ORDER BY that refers by column number to a GROUP_CONCAT() expression that has an outer reference, repeated statement execution could cause a server exit. * Loading corrupt spatial data into a MyISAM table could cause the server to exit during index building. * Certain queries for the INFORMATION_SCHEMA TABLES and COLUMNS tables could lead to excessive memory use when there were large numbers of empty InnoDB tables. * MySQL failed to compile using OpenSSL 0.9.8e.
2015-06-01 09:40:36 +02:00
share/mysql/test/suite/innodb/t/xa_recovery.test
Changes 5.5.36: Functionality Added or Changed 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>. Thanks to Honza Horak for the patch. Bugs Fixed InnoDB: Table renaming errors would appear in the LATEST FOREIGN KEY ERROR section of the SHOW ENGINE INNODB STATUS output. Partitioning: Queries using the index_merge optimization (see Index Merge Optimization) could return invalid results when run against tables that were partitioned by HASH. Partitioning: When no partition had returned a row since the last HA_ERR_KEY_NOT_FOUND error, the use of uninitialized memory in the priority queue used for returning rows in sorted order could lead to a crash of the server. Replication: mysqlbinlog --verbose failed when it encountered a corrupt row event in the binary log. Such a row event could also cause the slave to fail. Replication: When log_warnings is greater than 1, the master prints binary log dump thread information—containing the slave server ID, binary log file name, and binary log position—in mysqld.1.err. A slave server ID greater than 2 billion was printed with a negative value in such cases. Replication: Invalid event offsets in the binary log were not always handled correctly, which could lead to replication failure. The cache used for the Index Merge access method was freed only after successful retrieval of all rows. Interruption or failure of the operation led to a file descriptor leak. For utf8 and utf8mb4 strings, handler functions unnecessarily called a Unicode conversion function. Use of a nonmulti-byte algorithm for skipping leading spaces in multi-byte strings could cause a server exit. For the utf8_bin collation, ORDER BY LOWER(col_name) could produce incorrect ordering. On Windows, the --local-service server option did not work, and was not displayed in the --help message. The prototype of the Performance Schema instrumentation API mysql_cond_timedwait() call was fixed to be drop-in compatible with pthread_cond_timedwait(). This fix affects only implementers of third-party plugins. For the path specified with the --basedir option, mysql_plugin attempted to unlink the path rather than free the memory in which the path was stored. COUNT(DISTINCT) sometimes produced an incorrect result when the last read row contained a NULL value. Some scripts displayed out-of-date information regarding where to report bugs. Updating a FEDERATED table with UPDATE... JOIN caused a server exit when the local table contained a single row and that row could be joined to a row in the FEDERATED table. mysql_install_db referred to the obsolete mysqlbug script for reporting problems. It now refers to http://bugs.mysql.com/ instead.
2014-02-01 12:16:03 +01:00
share/mysql/test/suite/innodb_zip/r/innodb-create-options.result
share/mysql/test/suite/innodb_zip/r/innodb-zip.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_index_large_prefix.result
share/mysql/test/suite/innodb_zip/r/innodb_prefix_index_liftedlimit.result
share/mysql/test/suite/innodb_zip/t/innodb-create-options.test
share/mysql/test/suite/innodb_zip/t/innodb-zip.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_index_large_prefix.test
share/mysql/test/suite/innodb_zip/t/innodb_prefix_index_liftedlimit.test
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/manual/r/rpl_replication_delay.result
share/mysql/test/suite/manual/t/rpl_replication_delay-slave.opt
share/mysql/test/suite/manual/t/rpl_replication_delay.test
share/mysql/test/suite/ndb/r/ndb_restore_discover.result
share/mysql/test/suite/ndb/t/ndb_restore_discover.test
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_supported_sql_funcs_delete.inc
share/mysql/test/suite/parts/inc/part_supported_sql_funcs_main.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_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_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_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_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/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_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_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_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_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_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.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_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_innodb-master.opt
share/mysql/test/suite/parts/t/partition_debug_innodb.test
share/mysql/test/suite/parts/t/partition_debug_myisam-master.opt
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_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
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_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.test
share/mysql/test/suite/perfschema/include/binlog_common.inc
share/mysql/test/suite/perfschema/include/cleanup_helper.inc
share/mysql/test/suite/perfschema/include/privilege.inc
share/mysql/test/suite/perfschema/include/setup_helper.inc
share/mysql/test/suite/perfschema/include/start_server_common.inc
share/mysql/test/suite/perfschema/include/upgrade_check.inc
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_mix.result
share/mysql/test/suite/perfschema/r/binlog_row.result
share/mysql/test/suite/perfschema/r/binlog_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/ddl_cond_instances.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_instance.result
share/mysql/test/suite/perfschema/r/ddl_ews_by_thread_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_mutex_instances.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_setup_consumers.result
share/mysql/test/suite/perfschema/r/ddl_setup_instruments.result
share/mysql/test/suite/perfschema/r/ddl_setup_timers.result
share/mysql/test/suite/perfschema/r/ddl_threads.result
share/mysql/test/suite/perfschema/r/dml_cond_instances.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_instance.result
share/mysql/test/suite/perfschema/r/dml_ews_by_thread_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_file_summary_by_event_name.result
share/mysql/test/suite/perfschema/r/dml_file_summary_by_instance.result
share/mysql/test/suite/perfschema/r/dml_mutex_instances.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_setup_consumers.result
share/mysql/test/suite/perfschema/r/dml_setup_instruments.result
share/mysql/test/suite/perfschema/r/dml_setup_timers.result
share/mysql/test/suite/perfschema/r/dml_threads.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/information_schema.result
share/mysql/test/suite/perfschema/r/misc.result
share/mysql/test/suite/perfschema/r/myisam_file_io.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/pfs_upgrade.result
share/mysql/test/suite/perfschema/r/privilege.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/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/short_option_1.result
share/mysql/test/suite/perfschema/r/short_option_2.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_file_class.result
share/mysql/test/suite/perfschema/r/start_server_no_file_inst.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_thread_class.result
share/mysql/test/suite/perfschema/r/start_server_no_thread_inst.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/tampered_perfschema_table1.result
share/mysql/test/suite/perfschema/r/thread_cache.result
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_mix.test
share/mysql/test/suite/perfschema/t/binlog_row.test
share/mysql/test/suite/perfschema/t/binlog_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/ddl_cond_instances.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_instance.test
share/mysql/test/suite/perfschema/t/ddl_ews_by_thread_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_mutex_instances.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_setup_consumers.test
share/mysql/test/suite/perfschema/t/ddl_setup_instruments.test
share/mysql/test/suite/perfschema/t/ddl_setup_timers.test
share/mysql/test/suite/perfschema/t/ddl_threads.test
share/mysql/test/suite/perfschema/t/disabled.def
share/mysql/test/suite/perfschema/t/dml_cond_instances.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_instance.test
share/mysql/test/suite/perfschema/t/dml_ews_by_thread_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_file_summary_by_event_name.test
share/mysql/test/suite/perfschema/t/dml_file_summary_by_instance.test
share/mysql/test/suite/perfschema/t/dml_mutex_instances.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_setup_consumers.test
share/mysql/test/suite/perfschema/t/dml_setup_instruments.test
share/mysql/test/suite/perfschema/t/dml_setup_timers.test
share/mysql/test/suite/perfschema/t/dml_threads.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/information_schema.test
share/mysql/test/suite/perfschema/t/misc.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/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/pfs_upgrade.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/query_cache.test
share/mysql/test/suite/perfschema/t/read_only.test
share/mysql/test/suite/perfschema/t/relaylog.test
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/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/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_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_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_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_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/tampered_perfschema_table1-master.opt
share/mysql/test/suite/perfschema/t/tampered_perfschema_table1.test
share/mysql/test/suite/perfschema/t/thread_cache.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/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/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.5.39: CMake support was updated to handle CMake version 3. The timed_mutexes system variable has no effect and is deprecated. Bugs Fixed InnoDB: Opening a parent table that has thousands of child tables could result in a long semaphore wait condition. Partitioning: Selecting from a table having multiple columns in its primary key and partitioned by LIST COLUMNS(R), where R was the last (rightmost) column listed in the primary key definition, returned an incorrect result. Replication: When using row-based replication, updating or deleting a row on the master that did not exist on the slave led to failure of the slave when it tried to process the change. This problem occurred with InnoDB tables lacking a primary key. Replication: Quotation marks were not always handled correctly by LOAD DATA INFILE when written into the binary log. Replication: A group of threads involved in acquiring locks could deadlock when the following events occurred: Dump thread reconnects from slave; on master, a new dump thread tries to kill zombie dump threads; having acquired the thread's LOCK_thd_data, it is about to acquire LOCK_log. Application thread executing show binary logs, having acquired LOCK_log and about to acquire LOCK_index. Application thread executing PURGE BINARY LOGS; having acquired LOCK_index, it is about to acquire LOCK_thread_count. Application thread executing SHOW PROCESSLIST (or SELECT * FROM INFORMATION_SCHEMA.PROCESSLIST), having acquired LOCK_thread_count and about to acquire the zombie dump thread's LOCK_thd_data.
2014-08-10 16:27:40 +02:00
share/mysql/test/suite/rpl/r/rpl_4threads_deadlock.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_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
Changes 5.5.25: * The --safe-mode server option now is deprecated and will be removed in MySQL 5.6. * Performance: InnoDB: Improved the algorithm related to adaptive flushing. This fix increases the rate of flushing in cases where compression is used and the data set is larger than the buffer pool, leading to eviction. * InnoDB: In a transaction using the REPEATABLE READ isolation level, an UPDATE or DELETE statement for an InnoDB table could sometimes overlook rows recently committed by other transactions. As explained in Section 14.3.9.2, “Consistent Nonlocking Reads”, DML statements within a REPEATABLE READ transaction apply to rows committed by other transactions, even if a query could not see those rows. * InnoDB: The Innodb_buffer_pool_pages_flushed status variable was incorrectly set to twice the value it should be. Its value should never exceed the value of Innodb_pages_written. * InnoDB: The error handling and message was improved for attempting to create a foreign key with a column referencing itself. The message suggested a potential problem with the data dictionary, when no such problem existed. * InnoDB: The CHECK TABLE statement could fail for a large InnoDB table due to a timeout value of 2 hours. For typical storage devices, the issue could occur for tables that exceeded approximately 200 or 350 GB, depending on I/O speed. The fix relaxes the locking performed on the table being checked, which makes the timeout less likely. It also makes InnoDB recognize the syntax CHECK TABLE QUICK, which avoids the possibility of the timeout entirely. * Replication: It was theoretically possible for concurrent execution of more than one instance of SHOW BINLOG EVENTS to crash the MySQL Server. * Replication: Statements using AUTO_INCREMENT, LAST_INSERT_ID(), RAND(), or user variables could be applied in the wrong context on the slave when using statement-based replication and replication filtering server options (see Section 16.2.3, “How Servers Evaluate Replication Filtering Rules”). * Replication: An INSERT into a table that has a composite primary key that includes an AUTO_INCREMENT column that is not the first column of this composite key is not safe for statement-based binary logging or replication. Such statements are now marked as unsafe and fail with an error when using the STATEMENT binary logging format. For more information, see Section 16.1.2.3, “Determination of Safe and Unsafe Statements in Binary Logging”, as well as Section 16.4.1.1, “Replication and AUTO_INCREMENT”.
2012-06-03 00:28:00 +02:00
share/mysql/test/suite/rpl/r/rpl_auto_increment_bug45679.result
share/mysql/test/suite/rpl/r/rpl_auto_increment_update_failure.result
share/mysql/test/suite/rpl/r/rpl_autogen_query_multi_byte_char.result
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_grant.result
Changes 5.5.20: * A new server option, --slow-start-timeout, controls the Windows service control manager's service start timeout. The value is the maximum number of milliseconds that the service control manager waits before trying to kill the MySQL service during startup. The default value is 15000 (15 seconds). If the MySQL service takes too long to start, you may need to increase this value. A value of 0 means there is no timeout. Bugs Fixed: * Important Change: Replication: Setting an empty user in a CHANGE MASTER TO statement caused an invalid internal result and is no longer permitted. Trying to use MASTER_USER='' or setting MASTER_PASSWORD while leaving MASTER_USER unset causes the statement to fail with an error. * Important Change: Replication: Moving the binary log file, relay log file, or both files to a new location, then restarting the server with a new value for --log-bin, --relay-log, or both, caused the server to abort on start. This was because the entries in the index file overrode the new location. In addition, paths were calculated relative to datadir (rather than to the --log-bin or --relay-log values). * InnoDB Storage Engine: When doing a live downgrade from MySQL 5.6.4 or later, with innodb_page_size set to a value other than 16384, now the earlier MySQL version reports that the page size is incompatible with the older version, rather than crashing or displaying a “corruption” error. * InnoDB Storage Engine: Issuing INSERT...ON DUPLICATE KEY statements for InnoDB tables from concurrent threads could cause a deadlock, particularly with the INSERT...ON DUPLICATE KEY UPDATE form. The fix avoids deadlocks caused by the same row being accessed by more than one transaction. Deadlocks could still occur when multiple rows are inserted and updated simultaneously by different transactions in inconsistent order; those types of deadlocks require the standard error handling on the application side, of re-trying the transaction. * An incorrect InnoDB assertion could cause the server to halt. This issue only affected debug builds. The assertion referenced the source file btr0pcur.ic and the variable cursor->pos_state. * Locale information for FORMAT() function instances was lost in view definitions. * The handle_segfault() signal-handler code in mysqld could itself crash due to calling unsafe functions. * Enabling myisam_use_mmap could cause the server to crash. * Concurrent access to ARCHIVE tables could cause corruption.
2012-01-12 17:33:49 +01:00
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
Changes 5.5.13: * InnoDB Storage Engine: If the server crashed while an XA transaction was prepared but not yet committed, the transaction could remain in the system after restart, and cause a subsequent shutdown to hang. * InnoDB Storage Engine: Similar problem to the foreign key error in bug 11831040 / 60196 / 60909, but with a different root cause and occurring on Mac OS X. With the setting lower_case_table_names=2, inserts into InnoDB tables covered by foreign key constraints could fail after a server restart. * Partitioning: The internal get_partition_set() function did not take into account the possibility that a key specification could be NULL in some cases. * Partitioning: When executing a row-ordered retrieval index merge, the partitioning handler used memory from from that allocated for the table, rather than that allocated to the query, causing table object memory not to be freed until the table was closed. * Replication: A spurious error malformed binlog: it does not contain any Format_description_log_event... was generated when mysqlbinlog was invoked using --base64-output=decode-row and --start-position=pos, where pos is a point in the binary log past the format description log event. However, there is nothing unsafe about not printing the format description log event, so the error has been removed for this case. * Replication: Typographical errors appeared in the text of several replication error messages. (The word “position” was misspelled as “postion”.) * Assignments to NEW.var_name within triggers, where var_name had a BLOB or TEXT type, were not properly handled and produced incorrect results. * XA COMMIT could fail to clean up the error state if it discovered that the current XA transaction had to be rolled back. Consequently, the next XA transaction could raise an assertion when it checked for proper cleanup of the previous transaction. * An internal client macro reference was removed from the client_plugin.h header file. This reference made the file unusable. * The server consumed memory for repeated invocation of some stored procedures, which was not released until the connection terminated. * The server did not check for certain invalid out of order sequences of XA statements, and these sequences raised an assertion. * With the conversion from GNU autotools to CMake for configuring MySQL, the USE_SYMDIR preprocessor symbol was omitted. This caused failure of symbolic links (described at Section 7.11.3.1, “Using Symbolic Links”).
2011-06-15 23:00:05 +02:00
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_cant_read_event_incident.result
share/mysql/test/suite/rpl/r/rpl_change_master.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_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
Changes 5.5.20: * A new server option, --slow-start-timeout, controls the Windows service control manager's service start timeout. The value is the maximum number of milliseconds that the service control manager waits before trying to kill the MySQL service during startup. The default value is 15000 (15 seconds). If the MySQL service takes too long to start, you may need to increase this value. A value of 0 means there is no timeout. Bugs Fixed: * Important Change: Replication: Setting an empty user in a CHANGE MASTER TO statement caused an invalid internal result and is no longer permitted. Trying to use MASTER_USER='' or setting MASTER_PASSWORD while leaving MASTER_USER unset causes the statement to fail with an error. * Important Change: Replication: Moving the binary log file, relay log file, or both files to a new location, then restarting the server with a new value for --log-bin, --relay-log, or both, caused the server to abort on start. This was because the entries in the index file overrode the new location. In addition, paths were calculated relative to datadir (rather than to the --log-bin or --relay-log values). * InnoDB Storage Engine: When doing a live downgrade from MySQL 5.6.4 or later, with innodb_page_size set to a value other than 16384, now the earlier MySQL version reports that the page size is incompatible with the older version, rather than crashing or displaying a “corruption” error. * InnoDB Storage Engine: Issuing INSERT...ON DUPLICATE KEY statements for InnoDB tables from concurrent threads could cause a deadlock, particularly with the INSERT...ON DUPLICATE KEY UPDATE form. The fix avoids deadlocks caused by the same row being accessed by more than one transaction. Deadlocks could still occur when multiple rows are inserted and updated simultaneously by different transactions in inconsistent order; those types of deadlocks require the standard error handling on the application side, of re-trying the transaction. * An incorrect InnoDB assertion could cause the server to halt. This issue only affected debug builds. The assertion referenced the source file btr0pcur.ic and the variable cursor->pos_state. * Locale information for FORMAT() function instances was lost in view definitions. * The handle_segfault() signal-handler code in mysqld could itself crash due to calling unsafe functions. * Enabling myisam_use_mmap could cause the server to crash. * Concurrent access to ARCHIVE tables could cause corruption.
2012-01-12 17:33:49 +01:00
share/mysql/test/suite/rpl/r/rpl_connection.result
share/mysql/test/suite/rpl/r/rpl_create_database.result
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_delete_no_where.result
share/mysql/test/suite/rpl/r/rpl_do_grant.result
share/mysql/test/suite/rpl/r/rpl_drop.result
share/mysql/test/suite/rpl/r/rpl_drop_db.result
share/mysql/test/suite/rpl/r/rpl_drop_db_fail.result
share/mysql/test/suite/rpl/r/rpl_drop_temp.result
share/mysql/test/suite/rpl/r/rpl_drop_view.result
share/mysql/test/suite/rpl/r/rpl_dual_pos_advance.result
share/mysql/test/suite/rpl/r/rpl_empty_master_host.result
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_failed_optimize.result
share/mysql/test/suite/rpl/r/rpl_filter_tables_not_exist.result
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_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_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_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_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
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
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_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
share/mysql/test/suite/rpl/r/rpl_lost_events_on_rotate.result
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_pos_wait.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
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_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_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
Changes 5.5.25: * The --safe-mode server option now is deprecated and will be removed in MySQL 5.6. * Performance: InnoDB: Improved the algorithm related to adaptive flushing. This fix increases the rate of flushing in cases where compression is used and the data set is larger than the buffer pool, leading to eviction. * InnoDB: In a transaction using the REPEATABLE READ isolation level, an UPDATE or DELETE statement for an InnoDB table could sometimes overlook rows recently committed by other transactions. As explained in Section 14.3.9.2, “Consistent Nonlocking Reads”, DML statements within a REPEATABLE READ transaction apply to rows committed by other transactions, even if a query could not see those rows. * InnoDB: The Innodb_buffer_pool_pages_flushed status variable was incorrectly set to twice the value it should be. Its value should never exceed the value of Innodb_pages_written. * InnoDB: The error handling and message was improved for attempting to create a foreign key with a column referencing itself. The message suggested a potential problem with the data dictionary, when no such problem existed. * InnoDB: The CHECK TABLE statement could fail for a large InnoDB table due to a timeout value of 2 hours. For typical storage devices, the issue could occur for tables that exceeded approximately 200 or 350 GB, depending on I/O speed. The fix relaxes the locking performed on the table being checked, which makes the timeout less likely. It also makes InnoDB recognize the syntax CHECK TABLE QUICK, which avoids the possibility of the timeout entirely. * Replication: It was theoretically possible for concurrent execution of more than one instance of SHOW BINLOG EVENTS to crash the MySQL Server. * Replication: Statements using AUTO_INCREMENT, LAST_INSERT_ID(), RAND(), or user variables could be applied in the wrong context on the slave when using statement-based replication and replication filtering server options (see Section 16.2.3, “How Servers Evaluate Replication Filtering Rules”). * Replication: An INSERT into a table that has a composite primary key that includes an AUTO_INCREMENT column that is not the first column of this composite key is not safe for statement-based binary logging or replication. Such statements are now marked as unsafe and fail with an error when using the STATEMENT binary logging format. For more information, see Section 16.1.2.3, “Determination of Safe and Unsafe Statements in Binary Logging”, as well as Section 16.4.1.1, “Replication and AUTO_INCREMENT”.
2012-06-03 00:28:00 +02:00
share/mysql/test/suite/rpl/r/rpl_parallel_show_binlog_events_purge_logs.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_only.result
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
share/mysql/test/suite/rpl/r/rpl_replicate_ignore_db.result
share/mysql/test/suite/rpl/r/rpl_report.result
Changes 5.5.23: Bugs Fixed * Security Fix: Bug 59533 was fixed. * Performance: Partitioning: InnoDB Storage Engine: The statistics used by the optimizer for queries against partitioned InnoDB tables were based only on the first partition of each such table, leading to use of the wrong execution plan. * References: This bug was introduced by Bug 11756867. * Performance: InnoDB Storage Engine: Improved the performance of the DROP TABLE statement for InnoDB tables, especially on systems with a large buffer pool. The fix speeds up the processing for freeing entries in the adaptive hash index. * InnoDB Storage Engine: Deleting a huge amount of data from InnoDB tables within a short time could cause the purge operation that flushes data from the buffer pool to stall. If this issue occurs, restart the server to work around it. This issue is only likely to occur on 32-bit platforms. * InnoDB Storage Engine: If the server crashed during a TRUNCATE TABLE or CREATE INDEX statement for an InnoDB table, or a DROP DATABASE statement for a database containing InnoDB tables, an index could be corrupted, causing an error message when accessing the table after restart: InnoDB: Error: trying to load index index_name for table table_name InnoDB: but the index tree has been freed! In MySQL 5.1, this fix applies to the InnoDB Plugin, but not the built-in InnoDB storage engine. * InnoDB Storage Engine: When data was removed from an InnoDB table, newly inserted data might not reuse the freed disk blocks, leading to an unexpected size increase for the system tablespace or .ibd file (depending on the setting of innodb_file_per_table. The OPTIMIZE TABLE could compact a .ibd file in some cases but not others. The freed disk blocks would eventually be reused as additional data was inserted. More...
2012-04-14 14:10:05 +02:00
share/mysql/test/suite/rpl/r/rpl_report_port.result
Security Notes * Security Fix: The linked OpenSSL library for the MySQL Commercial Server has been updated to version 1.0.2l. Issues fixed in the new OpenSSL version are described at http://www.openssl.org/news/vulnerabilities.html. This change does not affect the Oracle-produced MySQL Community build of MySQL Server, which uses the yaSSL library instead. Platform-Specific Notes * Linux: The generic Linux build for MySQL 5.6 is now built on Oracle Linux 6 using glibc 2.12. Systems that use the build need to have glibc 2.12 or later installed on them. Functionality Added or Changed * For Windows, MSI installer packages now include a check for the required Visual Studio redistributable package, and produce a message asking the user to install it if it is missing. * The mysql client now supports a --binary-as-hex option that causes display of binary data using hexadecimal notation (0xvalue). Thanks to Daniël van Eeden for the patch. * mysqlaccess now looks for its configuration file only in the SYSCONFDIR directory and /etc. Bugs Fixed * InnoDB: The server allocated memory unnecessarily for an operation that rebuilt the table. * InnoDB: When using an index merge optimizer switch, a SELECT COUNT(*) operation sometimes returned 0. Partitioning code incorrectly performed a memcpy instead of a column copy of columns read by the index, causing the wrong records to be copied. * Replication: A USE statement that followed a SET GTID_NEXT statement sometimes had no effect. * Replication: If the binary log on a master server was rotated and a full disk condition occurred on the partition where the binary log file was being stored, the server could stop unexpectedly. The fix adds a check for the existence of the binary log when the dump thread switches to next binary log file. If the binary log is disabled, all binary logs up to the current active log are transmitted to slave and an error is returned to the receiver thread. * Replication: If a relay log index file named relay log files that did not exist, RESET SLAVE ALL sometimes did not fully clean up properly. * Replication: mysqlbinlog, if invoked with the --raw option, does not flush the output file until the process terminates. But if also invoked with the --stop-never option, the process never terminates, thus nothing is ever written to the output file. Now the output is flushed after each event. * Replication: A memory leak in mysqlbinlog was fixed. The leak happened when processing fake rotate events, or when using --raw and the destination log file could not be created. The leak only occurred when processing events from a remote server. Thanks to Laurynas Biveinis for his contribution to fixing this bug. * Replication: Multi-threaded slaves could not be configured with small queue sizes using slave_pending_jobs_size_max if they ever needed to process transactions larger than that size. Any packet larger than slave_pending_jobs_size_max was rejected with the error ER_MTS_EVENT_BIGGER_PENDING_JOBS_SIZE_MAX, even if the packet was smaller than the limit set by slave_max_allowed_packet. * With this fix, slave_pending_jobs_size_max becomes a soft limit rather than a hard limit. If the size of a packet exceeds slave_pending_jobs_size_max but is less than slave_max_allowed_packet, the transaction is held until all the slave workers have empty queues, and then processed. All subsequent transactions are held until the large transaction has been completed. The queue size for slave workers can therefore be limited while still allowing occasional larger transactions. * mysqldump could write database names in USE statements incorrectly. * If the mysql_stmt_close() C API function was called, it freed memory that later could be accessed if mysql_stmt_error(), mysql_stmt_errno(), or mysql_stmt_sqlstate() was called. To obtain error information after a call to mysql_stmt_close(), call mysql_error(), mysql_errno(), or mysql_sqlstate() instead. * Queries could be cached incorrectly, leading to incorrect query results, under these circumstances: InnoDB table; rows are being inserted but have not yet been committed; a query uses the table as a base table in a derived table; the optimizer chooses to materialize the derived table. * Man pages for a few utilities were missing from Debian/Ubuntu packages. * The field-t unit test failed to run with AddressSanitizer enabled. Thanks to Laurynas Biveinis for the patch. * Debian client packages were missing information about conflicts with native packages. * The Perl path in #! lines at the beginning of Perl scripts has been adjusted to /usr/local/bin/perl for FreeBSD 11. * The server exited abnormally attempting to access invalid memory. * A race condition could occur for CREATE TABLE statements with DATA DIRECTORY or INDEX DIRECTORY clauses. * MySQL compilation in different directories produced different builds to leakage of absolute paths into debug information and __FILE__. * mysqld_failed to start the server if the --datadir option was specified with a relative path name. * With read_only enabled, creation of non-TEMPORARY tables by non-SUPER users was permitted under certain conditions. *Certain stored functions, if used in a query WHERE clause, could be handled using Index Condition Pushdown (which should not happen), resulting in a server exit. * On x86 machines, the uint3korr() macro read 4 bytes of data instead of the intended 3 bytes. * An assertion was raised during a fetch operation by the memcached plugin. * Queries that contained UNION in a subquery and GROUP BY could return incorrect results. * LOAD XML INFILE performance became noticeably slower when the XML file being read contained a great many spaces, such as those introduced by indenting or pretty-printing. Now all leading whitespace is trimmed from each such value before reading it into memory.
2017-07-19 20:48:21 +02:00
share/mysql/test/suite/rpl/r/rpl_reset_slave_fail.result
share/mysql/test/suite/rpl/r/rpl_rewrt_db.result
share/mysql/test/suite/rpl/r/rpl_rotate_logs.result
Changes 5.5.19: * Performance of metadata locking operations on Windows XP systems was improved by instituting a cache for metadata lock objects. This permits the server to avoid expensive operations for creation and destruction of synchronization objects on XP. A new system variable, metadata_locks_cache_size, permits control over the size of the cache. The default size is 1024. * Replication: Previously, replication slaves could connect to the master server through master accounts that use nonnative authentication, except Windows native authentication. This is now also true for Windows native authentication. Bugs Fixed: * InnoDB Storage Engine: An internal deadlock could occur within InnoDB, on a server doing a substantial amount of change buffering for DML operations, particularly DELETE statements. * Rounding DBL_MAX returned DBL_MAX, not 'inf'. * mysql_upgrade did not upgrade the system tables or create the mysql_upgrade_info file when run with the --write-binlog or --skip-write-binlog option. * If a plugin was uninstalled, thread local variables for plugin variables of string type with wth PLUGIN_VAR_MEMALLOC flag were not freed. * Deadlock could occur when these four things happened at the same time: 1) An old dump thread was waiting for the binary log to grow. 2) The slave server that replicates from the old dump thread tried to reconnect. During reconnection, the new dump thread tried to kill the old dump thread. 3) A KILL statement tried to kill the old dump thread. 4) An INSERT statement caused a binary log rotation.
2011-12-13 13:14:49 +01:00
share/mysql/test/suite/rpl/r/rpl_rotate_purge_deadlock.result
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_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
share/mysql/test/suite/rpl/r/rpl_row_corruption.result
Changes 5.5.38: Bugs Fixed 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. 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. Certain INFORMATION_SCHEMA queries could cause a server exit. For indexes on prefixes or character string columns, index corruption could occur for assignment of binary data to the column due to improper character counting. Solaris-specific scripts were included in and installed by non-Solaris packages. EXPLAIN on a query with an EXISTS subquery containing a UNION could cause a server exit. Multiple executions of a prepared EXPLAIN on a UNION of subqueries could cause a server exit. Executing a correlated subquery on an ARCHIVE table which has an AUTO_INCREMENT column caused the server to hang. The client library could cause clients to exit due to incorrectly mapping the client error number to the corresponding message, if reallocation of packet buffer memory occurred. Calling mysql_get_server_version() with an invalid connection handler argument caused the client to exit. Now it returns 0 and reports a CR_COMMANDS_OUT_OF_SYNC error. On Windows, calling mysql_thread_init() call without mysql_init() caused the client to exit. windows. Now it returns a nonzero result because it is an error to call mysql_thread_init() before the client library is initialized with mysql_library_init(). CMake produced not-useful warnings about INTERFACE_LINK_LIBRARIES policy. LOAD DATA LOCAL INFILE could use all CPU if import errors occurred when there were no line delimiters. A statement of the following form broke row-based replication because it created a table having a field of data type BIGINT with a display width of 3000, which is beyond the maximum acceptable value of 255: CREATE TABLE t1 AS SELECT REPEAT('A',1000) DIV 1 AS a;
2014-06-02 09:17:31 +02:00
share/mysql/test/suite/rpl/r/rpl_row_create_select.result
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_find_row.result
Changes 5.5.19: * Performance of metadata locking operations on Windows XP systems was improved by instituting a cache for metadata lock objects. This permits the server to avoid expensive operations for creation and destruction of synchronization objects on XP. A new system variable, metadata_locks_cache_size, permits control over the size of the cache. The default size is 1024. * Replication: Previously, replication slaves could connect to the master server through master accounts that use nonnative authentication, except Windows native authentication. This is now also true for Windows native authentication. Bugs Fixed: * InnoDB Storage Engine: An internal deadlock could occur within InnoDB, on a server doing a substantial amount of change buffering for DML operations, particularly DELETE statements. * Rounding DBL_MAX returned DBL_MAX, not 'inf'. * mysql_upgrade did not upgrade the system tables or create the mysql_upgrade_info file when run with the --write-binlog or --skip-write-binlog option. * If a plugin was uninstalled, thread local variables for plugin variables of string type with wth PLUGIN_VAR_MEMALLOC flag were not freed. * Deadlock could occur when these four things happened at the same time: 1) An old dump thread was waiting for the binary log to grow. 2) The slave server that replicates from the old dump thread tried to reconnect. During reconnection, the new dump thread tried to kill the old dump thread. 3) A KILL statement tried to kill the old dump thread. 4) An INSERT statement caused a binary log rotation.
2011-12-13 13:14:49 +01:00
share/mysql/test/suite/rpl/r/rpl_row_find_row_debug.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_idempotency.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_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
Update mysql55-{client,server} to 5.55.24. Changes (http://dev.mysql.com/doc/refman/5.5/en/news-5-5-24.html): Functionality Added or Changed * Important Change: Replication: INSERT ON DUPLICATE KEY UPDATE is now marked as unsafe for statement-based replication if the target table has more than one primary or unique key. For more information, see Section 16.1.2.3, "Determination of Safe and Unsafe Statements in Binary Logging". Bugs Fixed * Security Fix: Bug #64884 was fixed. * InnoDB: Replication: When binary log statements were replayed on the slave, the Com_insert, Com_update, and Com_delete counters were incremented by BEGIN statements initiating transactions affecting InnoDB tables but not by COMMIT statements ending such transactions. This affected these statements whether they were replicated or they were run using mysqlbinlog. (Bug #12662190) * If the --bind-address option was given a host name value and the host name resolved to more than one IP address, the server failed to start. For example, with --bind-address=localhost, if localhost resolved to both 127.0.0.1 and ::1, startup failed. Now the server prefers the IPv4 address in such cases. (Bug #61713, Bug #12762885) * mysql_store_result() and mysql_use_result() are not for use with prepared statements and are not intended to be called following mysql_stmt_execute(), but failed to return an error when invoked that way in libmysqld. (Bug #62136, Bug #13738989) References: See also Bug #47485. * On Windows, mysqlslap crashed for attempts to connect using shared memory. (Bug #31173, Bug #11747181, Bug #59107, Bug #11766072)
2012-05-13 15:05:33 +02:00
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_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_reset_slave.result
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
share/mysql/test/suite/rpl/r/rpl_semi_sync.result
share/mysql/test/suite/rpl/r/rpl_semi_sync_event.result
Changes 5.5.39: CMake support was updated to handle CMake version 3. The timed_mutexes system variable has no effect and is deprecated. Bugs Fixed InnoDB: Opening a parent table that has thousands of child tables could result in a long semaphore wait condition. Partitioning: Selecting from a table having multiple columns in its primary key and partitioned by LIST COLUMNS(R), where R was the last (rightmost) column listed in the primary key definition, returned an incorrect result. Replication: When using row-based replication, updating or deleting a row on the master that did not exist on the slave led to failure of the slave when it tried to process the change. This problem occurred with InnoDB tables lacking a primary key. Replication: Quotation marks were not always handled correctly by LOAD DATA INFILE when written into the binary log. Replication: A group of threads involved in acquiring locks could deadlock when the following events occurred: Dump thread reconnects from slave; on master, a new dump thread tries to kill zombie dump threads; having acquired the thread's LOCK_thd_data, it is about to acquire LOCK_log. Application thread executing show binary logs, having acquired LOCK_log and about to acquire LOCK_index. Application thread executing PURGE BINARY LOGS; having acquired LOCK_index, it is about to acquire LOCK_thread_count. Application thread executing SHOW PROCESSLIST (or SELECT * FROM INFORMATION_SCHEMA.PROCESSLIST), having acquired LOCK_thread_count and about to acquire the zombie dump thread's LOCK_thd_data.
2014-08-10 16:27:40 +02:00
share/mysql/test/suite/rpl/r/rpl_semi_sync_uninstall_plugin.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_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_slave_hosts.result
share/mysql/test/suite/rpl/r/rpl_show_slave_running.result
share/mysql/test/suite/rpl/r/rpl_skip_error.result
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_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
share/mysql/test/suite/rpl/r/rpl_spec_variables.result
share/mysql/test/suite/rpl/r/rpl_special_charset.result
share/mysql/test/suite/rpl/r/rpl_sporadic_master.result
share/mysql/test/suite/rpl/r/rpl_ssl.result
share/mysql/test/suite/rpl/r/rpl_ssl1.result
Changes 5.5.21: * A new CMake option, MYSQL_PROJECT_NAME, can be set on Windows or Mac OS X to be used in the project name. Bugs Fixed * Performance: InnoDB Storage Engine: Memory allocation for InnoDB tables was reorganized to reduce the memory overhead for large numbers of tables or partitions, avoiding situations where the “resident set size” could grow regardless of FLUSH TABLES statements. The problem was most evident for tables with large row size. * Incompatible Change: An earlier change (in MySQL 5.1.62 and 5.5.21) was found to modify date-handling behavior in General Availability-status series (MySQL 5.1 and 5.5). This change has been reverted. * The change was that several functions became more strict when passed a DATE() function value as their argument, thus they rejected incomplete dates with a day part of zero. These functions were affected: CONVERT_TZ(), DATE_ADD(), DATE_SUB(), DAYOFYEAR(), LAST_DAY(), TIMESTAMPDIFF(), TO_DAYS(), TO_SECONDS(), WEEK(), WEEKDAY(), WEEKOFYEAR(), YEARWEEK(). The previous behavior has been restored. * InnoDB Storage Engine: A Valgrind error was fixed in the function os_aio_init(). * InnoDB Storage Engine: The server could crash when creating an InnoDB temporary table under Linux, if the $TMPDIR setting points to a tmpfs filesystem and innodb_use_native_aio is enabled, as it is by default in MySQL 5.5.4 and higher. * InnoDB Storage Engine: References to C preprocessor symbols and macros HAVE_purify, UNIV_INIT_MEM_TO_ZERO, and UNIV_SET_MEM_TO_ZERO were removed from the InnoDB source code. They were only used in debug builds instrumented for Valgrind. They are replaced by calls to the UNIV_MEM_INVALID() macro.
2012-02-23 14:01:03 +01:00
share/mysql/test/suite/rpl/r/rpl_start_stop_slave.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
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_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_show_relaylog_events.result
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
Changes 5.5.23: Bugs Fixed * Security Fix: Bug 59533 was fixed. * Performance: Partitioning: InnoDB Storage Engine: The statistics used by the optimizer for queries against partitioned InnoDB tables were based only on the first partition of each such table, leading to use of the wrong execution plan. * References: This bug was introduced by Bug 11756867. * Performance: InnoDB Storage Engine: Improved the performance of the DROP TABLE statement for InnoDB tables, especially on systems with a large buffer pool. The fix speeds up the processing for freeing entries in the adaptive hash index. * InnoDB Storage Engine: Deleting a huge amount of data from InnoDB tables within a short time could cause the purge operation that flushes data from the buffer pool to stall. If this issue occurs, restart the server to work around it. This issue is only likely to occur on 32-bit platforms. * InnoDB Storage Engine: If the server crashed during a TRUNCATE TABLE or CREATE INDEX statement for an InnoDB table, or a DROP DATABASE statement for a database containing InnoDB tables, an index could be corrupted, causing an error message when accessing the table after restart: InnoDB: Error: trying to load index index_name for table table_name InnoDB: but the index tree has been freed! In MySQL 5.1, this fix applies to the InnoDB Plugin, but not the built-in InnoDB storage engine. * InnoDB Storage Engine: When data was removed from an InnoDB table, newly inserted data might not reuse the freed disk blocks, leading to an unexpected size increase for the system tablespace or .ibd file (depending on the setting of innodb_file_per_table. The OPTIMIZE TABLE could compact a .ibd file in some cases but not others. The freed disk blocks would eventually be reused as additional data was inserted. More...
2012-04-14 14:10:05 +02:00
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
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_temporary.result
share/mysql/test/suite/rpl/r/rpl_temporary_errors.result
share/mysql/test/suite/rpl/r/rpl_test_framework.result
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
share/mysql/test/suite/rpl/r/rpl_unsafe_statements.result
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.5.39: CMake support was updated to handle CMake version 3. The timed_mutexes system variable has no effect and is deprecated. Bugs Fixed InnoDB: Opening a parent table that has thousands of child tables could result in a long semaphore wait condition. Partitioning: Selecting from a table having multiple columns in its primary key and partitioned by LIST COLUMNS(R), where R was the last (rightmost) column listed in the primary key definition, returned an incorrect result. Replication: When using row-based replication, updating or deleting a row on the master that did not exist on the slave led to failure of the slave when it tried to process the change. This problem occurred with InnoDB tables lacking a primary key. Replication: Quotation marks were not always handled correctly by LOAD DATA INFILE when written into the binary log. Replication: A group of threads involved in acquiring locks could deadlock when the following events occurred: Dump thread reconnects from slave; on master, a new dump thread tries to kill zombie dump threads; having acquired the thread's LOCK_thd_data, it is about to acquire LOCK_log. Application thread executing show binary logs, having acquired LOCK_log and about to acquire LOCK_index. Application thread executing PURGE BINARY LOGS; having acquired LOCK_index, it is about to acquire LOCK_thread_count. Application thread executing SHOW PROCESSLIST (or SELECT * FROM INFORMATION_SCHEMA.PROCESSLIST), having acquired LOCK_thread_count and about to acquire the zombie dump thread's LOCK_thd_data.
2014-08-10 16:27:40 +02:00
share/mysql/test/suite/rpl/t/rpl_4threads_deadlock.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_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
Changes 5.5.25: * The --safe-mode server option now is deprecated and will be removed in MySQL 5.6. * Performance: InnoDB: Improved the algorithm related to adaptive flushing. This fix increases the rate of flushing in cases where compression is used and the data set is larger than the buffer pool, leading to eviction. * InnoDB: In a transaction using the REPEATABLE READ isolation level, an UPDATE or DELETE statement for an InnoDB table could sometimes overlook rows recently committed by other transactions. As explained in Section 14.3.9.2, “Consistent Nonlocking Reads”, DML statements within a REPEATABLE READ transaction apply to rows committed by other transactions, even if a query could not see those rows. * InnoDB: The Innodb_buffer_pool_pages_flushed status variable was incorrectly set to twice the value it should be. Its value should never exceed the value of Innodb_pages_written. * InnoDB: The error handling and message was improved for attempting to create a foreign key with a column referencing itself. The message suggested a potential problem with the data dictionary, when no such problem existed. * InnoDB: The CHECK TABLE statement could fail for a large InnoDB table due to a timeout value of 2 hours. For typical storage devices, the issue could occur for tables that exceeded approximately 200 or 350 GB, depending on I/O speed. The fix relaxes the locking performed on the table being checked, which makes the timeout less likely. It also makes InnoDB recognize the syntax CHECK TABLE QUICK, which avoids the possibility of the timeout entirely. * Replication: It was theoretically possible for concurrent execution of more than one instance of SHOW BINLOG EVENTS to crash the MySQL Server. * Replication: Statements using AUTO_INCREMENT, LAST_INSERT_ID(), RAND(), or user variables could be applied in the wrong context on the slave when using statement-based replication and replication filtering server options (see Section 16.2.3, “How Servers Evaluate Replication Filtering Rules”). * Replication: An INSERT into a table that has a composite primary key that includes an AUTO_INCREMENT column that is not the first column of this composite key is not safe for statement-based binary logging or replication. Such statements are now marked as unsafe and fail with an error when using the STATEMENT binary logging format. For more information, see Section 16.1.2.3, “Determination of Safe and Unsafe Statements in Binary Logging”, as well as Section 16.4.1.1, “Replication and AUTO_INCREMENT”.
2012-06-03 00:28:00 +02:00
share/mysql/test/suite/rpl/t/rpl_auto_increment_bug45679.test
share/mysql/test/suite/rpl/t/rpl_auto_increment_update_failure.test
share/mysql/test/suite/rpl/t/rpl_autogen_query_multi_byte_char.test
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_grant.test
Changes 5.5.20: * A new server option, --slow-start-timeout, controls the Windows service control manager's service start timeout. The value is the maximum number of milliseconds that the service control manager waits before trying to kill the MySQL service during startup. The default value is 15000 (15 seconds). If the MySQL service takes too long to start, you may need to increase this value. A value of 0 means there is no timeout. Bugs Fixed: * Important Change: Replication: Setting an empty user in a CHANGE MASTER TO statement caused an invalid internal result and is no longer permitted. Trying to use MASTER_USER='' or setting MASTER_PASSWORD while leaving MASTER_USER unset causes the statement to fail with an error. * Important Change: Replication: Moving the binary log file, relay log file, or both files to a new location, then restarting the server with a new value for --log-bin, --relay-log, or both, caused the server to abort on start. This was because the entries in the index file overrode the new location. In addition, paths were calculated relative to datadir (rather than to the --log-bin or --relay-log values). * InnoDB Storage Engine: When doing a live downgrade from MySQL 5.6.4 or later, with innodb_page_size set to a value other than 16384, now the earlier MySQL version reports that the page size is incompatible with the older version, rather than crashing or displaying a “corruption” error. * InnoDB Storage Engine: Issuing INSERT...ON DUPLICATE KEY statements for InnoDB tables from concurrent threads could cause a deadlock, particularly with the INSERT...ON DUPLICATE KEY UPDATE form. The fix avoids deadlocks caused by the same row being accessed by more than one transaction. Deadlocks could still occur when multiple rows are inserted and updated simultaneously by different transactions in inconsistent order; those types of deadlocks require the standard error handling on the application side, of re-trying the transaction. * An incorrect InnoDB assertion could cause the server to halt. This issue only affected debug builds. The assertion referenced the source file btr0pcur.ic and the variable cursor->pos_state. * Locale information for FORMAT() function instances was lost in view definitions. * The handle_segfault() signal-handler code in mysqld could itself crash due to calling unsafe functions. * Enabling myisam_use_mmap could cause the server to crash. * Concurrent access to ARCHIVE tables could cause corruption.
2012-01-12 17:33:49 +01:00
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
Changes 5.5.13: * InnoDB Storage Engine: If the server crashed while an XA transaction was prepared but not yet committed, the transaction could remain in the system after restart, and cause a subsequent shutdown to hang. * InnoDB Storage Engine: Similar problem to the foreign key error in bug 11831040 / 60196 / 60909, but with a different root cause and occurring on Mac OS X. With the setting lower_case_table_names=2, inserts into InnoDB tables covered by foreign key constraints could fail after a server restart. * Partitioning: The internal get_partition_set() function did not take into account the possibility that a key specification could be NULL in some cases. * Partitioning: When executing a row-ordered retrieval index merge, the partitioning handler used memory from from that allocated for the table, rather than that allocated to the query, causing table object memory not to be freed until the table was closed. * Replication: A spurious error malformed binlog: it does not contain any Format_description_log_event... was generated when mysqlbinlog was invoked using --base64-output=decode-row and --start-position=pos, where pos is a point in the binary log past the format description log event. However, there is nothing unsafe about not printing the format description log event, so the error has been removed for this case. * Replication: Typographical errors appeared in the text of several replication error messages. (The word “position” was misspelled as “postion”.) * Assignments to NEW.var_name within triggers, where var_name had a BLOB or TEXT type, were not properly handled and produced incorrect results. * XA COMMIT could fail to clean up the error state if it discovered that the current XA transaction had to be rolled back. Consequently, the next XA transaction could raise an assertion when it checked for proper cleanup of the previous transaction. * An internal client macro reference was removed from the client_plugin.h header file. This reference made the file unusable. * The server consumed memory for repeated invocation of some stored procedures, which was not released until the connection terminated. * The server did not check for certain invalid out of order sequences of XA statements, and these sequences raised an assertion. * With the conversion from GNU autotools to CMake for configuring MySQL, the USE_SYMDIR preprocessor symbol was omitted. This caused failure of symbolic links (described at Section 7.11.3.1, “Using Symbolic Links”).
2011-06-15 23:00:05 +02:00
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_cant_read_event_incident.test
share/mysql/test/suite/rpl/t/rpl_change_master.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_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
Changes 5.5.20: * A new server option, --slow-start-timeout, controls the Windows service control manager's service start timeout. The value is the maximum number of milliseconds that the service control manager waits before trying to kill the MySQL service during startup. The default value is 15000 (15 seconds). If the MySQL service takes too long to start, you may need to increase this value. A value of 0 means there is no timeout. Bugs Fixed: * Important Change: Replication: Setting an empty user in a CHANGE MASTER TO statement caused an invalid internal result and is no longer permitted. Trying to use MASTER_USER='' or setting MASTER_PASSWORD while leaving MASTER_USER unset causes the statement to fail with an error. * Important Change: Replication: Moving the binary log file, relay log file, or both files to a new location, then restarting the server with a new value for --log-bin, --relay-log, or both, caused the server to abort on start. This was because the entries in the index file overrode the new location. In addition, paths were calculated relative to datadir (rather than to the --log-bin or --relay-log values). * InnoDB Storage Engine: When doing a live downgrade from MySQL 5.6.4 or later, with innodb_page_size set to a value other than 16384, now the earlier MySQL version reports that the page size is incompatible with the older version, rather than crashing or displaying a “corruption” error. * InnoDB Storage Engine: Issuing INSERT...ON DUPLICATE KEY statements for InnoDB tables from concurrent threads could cause a deadlock, particularly with the INSERT...ON DUPLICATE KEY UPDATE form. The fix avoids deadlocks caused by the same row being accessed by more than one transaction. Deadlocks could still occur when multiple rows are inserted and updated simultaneously by different transactions in inconsistent order; those types of deadlocks require the standard error handling on the application side, of re-trying the transaction. * An incorrect InnoDB assertion could cause the server to halt. This issue only affected debug builds. The assertion referenced the source file btr0pcur.ic and the variable cursor->pos_state. * Locale information for FORMAT() function instances was lost in view definitions. * The handle_segfault() signal-handler code in mysqld could itself crash due to calling unsafe functions. * Enabling myisam_use_mmap could cause the server to crash. * Concurrent access to ARCHIVE tables could cause corruption.
2012-01-12 17:33:49 +01:00
share/mysql/test/suite/rpl/t/rpl_connection.test
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
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_delete_no_where.test
share/mysql/test/suite/rpl/t/rpl_do_grant.test
share/mysql/test/suite/rpl/t/rpl_drop.test
share/mysql/test/suite/rpl/t/rpl_drop_db.test
share/mysql/test/suite/rpl/t/rpl_drop_db_fail.test
share/mysql/test/suite/rpl/t/rpl_drop_temp-slave.opt
share/mysql/test/suite/rpl/t/rpl_drop_temp.test
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
share/mysql/test/suite/rpl/t/rpl_empty_master_host.test
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_failed_optimize.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
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_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_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_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_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.test
share/mysql/test/suite/rpl/t/rpl_insert_id_pk.test
share/mysql/test/suite/rpl/t/rpl_insert_ignore.test
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
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_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
share/mysql/test/suite/rpl/t/rpl_lost_events_on_rotate.test
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_pos_wait.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.test
share/mysql/test/suite/rpl/t/rpl_mix_insert_delayed.test
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.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_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_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
Changes 5.5.25: * The --safe-mode server option now is deprecated and will be removed in MySQL 5.6. * Performance: InnoDB: Improved the algorithm related to adaptive flushing. This fix increases the rate of flushing in cases where compression is used and the data set is larger than the buffer pool, leading to eviction. * InnoDB: In a transaction using the REPEATABLE READ isolation level, an UPDATE or DELETE statement for an InnoDB table could sometimes overlook rows recently committed by other transactions. As explained in Section 14.3.9.2, “Consistent Nonlocking Reads”, DML statements within a REPEATABLE READ transaction apply to rows committed by other transactions, even if a query could not see those rows. * InnoDB: The Innodb_buffer_pool_pages_flushed status variable was incorrectly set to twice the value it should be. Its value should never exceed the value of Innodb_pages_written. * InnoDB: The error handling and message was improved for attempting to create a foreign key with a column referencing itself. The message suggested a potential problem with the data dictionary, when no such problem existed. * InnoDB: The CHECK TABLE statement could fail for a large InnoDB table due to a timeout value of 2 hours. For typical storage devices, the issue could occur for tables that exceeded approximately 200 or 350 GB, depending on I/O speed. The fix relaxes the locking performed on the table being checked, which makes the timeout less likely. It also makes InnoDB recognize the syntax CHECK TABLE QUICK, which avoids the possibility of the timeout entirely. * Replication: It was theoretically possible for concurrent execution of more than one instance of SHOW BINLOG EVENTS to crash the MySQL Server. * Replication: Statements using AUTO_INCREMENT, LAST_INSERT_ID(), RAND(), or user variables could be applied in the wrong context on the slave when using statement-based replication and replication filtering server options (see Section 16.2.3, “How Servers Evaluate Replication Filtering Rules”). * Replication: An INSERT into a table that has a composite primary key that includes an AUTO_INCREMENT column that is not the first column of this composite key is not safe for statement-based binary logging or replication. Such statements are now marked as unsafe and fail with an error when using the STATEMENT binary logging format. For more information, see Section 16.1.2.3, “Determination of Safe and Unsafe Statements in Binary Logging”, as well as Section 16.4.1.1, “Replication and AUTO_INCREMENT”.
2012-06-03 00:28:00 +02:00
share/mysql/test/suite/rpl/t/rpl_parallel_show_binlog_events_purge_logs.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_only.test
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
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_report-slave.opt
share/mysql/test/suite/rpl/t/rpl_report.test
Changes 5.5.25: * The --safe-mode server option now is deprecated and will be removed in MySQL 5.6. * Performance: InnoDB: Improved the algorithm related to adaptive flushing. This fix increases the rate of flushing in cases where compression is used and the data set is larger than the buffer pool, leading to eviction. * InnoDB: In a transaction using the REPEATABLE READ isolation level, an UPDATE or DELETE statement for an InnoDB table could sometimes overlook rows recently committed by other transactions. As explained in Section 14.3.9.2, “Consistent Nonlocking Reads”, DML statements within a REPEATABLE READ transaction apply to rows committed by other transactions, even if a query could not see those rows. * InnoDB: The Innodb_buffer_pool_pages_flushed status variable was incorrectly set to twice the value it should be. Its value should never exceed the value of Innodb_pages_written. * InnoDB: The error handling and message was improved for attempting to create a foreign key with a column referencing itself. The message suggested a potential problem with the data dictionary, when no such problem existed. * InnoDB: The CHECK TABLE statement could fail for a large InnoDB table due to a timeout value of 2 hours. For typical storage devices, the issue could occur for tables that exceeded approximately 200 or 350 GB, depending on I/O speed. The fix relaxes the locking performed on the table being checked, which makes the timeout less likely. It also makes InnoDB recognize the syntax CHECK TABLE QUICK, which avoids the possibility of the timeout entirely. * Replication: It was theoretically possible for concurrent execution of more than one instance of SHOW BINLOG EVENTS to crash the MySQL Server. * Replication: Statements using AUTO_INCREMENT, LAST_INSERT_ID(), RAND(), or user variables could be applied in the wrong context on the slave when using statement-based replication and replication filtering server options (see Section 16.2.3, “How Servers Evaluate Replication Filtering Rules”). * Replication: An INSERT into a table that has a composite primary key that includes an AUTO_INCREMENT column that is not the first column of this composite key is not safe for statement-based binary logging or replication. Such statements are now marked as unsafe and fail with an error when using the STATEMENT binary logging format. For more information, see Section 16.1.2.3, “Determination of Safe and Unsafe Statements in Binary Logging”, as well as Section 16.4.1.1, “Replication and AUTO_INCREMENT”.
2012-06-03 00:28:00 +02:00
share/mysql/test/suite/rpl/t/rpl_report_port-master.opt
Changes 5.5.23: Bugs Fixed * Security Fix: Bug 59533 was fixed. * Performance: Partitioning: InnoDB Storage Engine: The statistics used by the optimizer for queries against partitioned InnoDB tables were based only on the first partition of each such table, leading to use of the wrong execution plan. * References: This bug was introduced by Bug 11756867. * Performance: InnoDB Storage Engine: Improved the performance of the DROP TABLE statement for InnoDB tables, especially on systems with a large buffer pool. The fix speeds up the processing for freeing entries in the adaptive hash index. * InnoDB Storage Engine: Deleting a huge amount of data from InnoDB tables within a short time could cause the purge operation that flushes data from the buffer pool to stall. If this issue occurs, restart the server to work around it. This issue is only likely to occur on 32-bit platforms. * InnoDB Storage Engine: If the server crashed during a TRUNCATE TABLE or CREATE INDEX statement for an InnoDB table, or a DROP DATABASE statement for a database containing InnoDB tables, an index could be corrupted, causing an error message when accessing the table after restart: InnoDB: Error: trying to load index index_name for table table_name InnoDB: but the index tree has been freed! In MySQL 5.1, this fix applies to the InnoDB Plugin, but not the built-in InnoDB storage engine. * InnoDB Storage Engine: When data was removed from an InnoDB table, newly inserted data might not reuse the freed disk blocks, leading to an unexpected size increase for the system tablespace or .ibd file (depending on the setting of innodb_file_per_table. The OPTIMIZE TABLE could compact a .ibd file in some cases but not others. The freed disk blocks would eventually be reused as additional data was inserted. More...
2012-04-14 14:10:05 +02:00
share/mysql/test/suite/rpl/t/rpl_report_port.test
Security Notes * Security Fix: The linked OpenSSL library for the MySQL Commercial Server has been updated to version 1.0.2l. Issues fixed in the new OpenSSL version are described at http://www.openssl.org/news/vulnerabilities.html. This change does not affect the Oracle-produced MySQL Community build of MySQL Server, which uses the yaSSL library instead. Platform-Specific Notes * Linux: The generic Linux build for MySQL 5.6 is now built on Oracle Linux 6 using glibc 2.12. Systems that use the build need to have glibc 2.12 or later installed on them. Functionality Added or Changed * For Windows, MSI installer packages now include a check for the required Visual Studio redistributable package, and produce a message asking the user to install it if it is missing. * The mysql client now supports a --binary-as-hex option that causes display of binary data using hexadecimal notation (0xvalue). Thanks to Daniël van Eeden for the patch. * mysqlaccess now looks for its configuration file only in the SYSCONFDIR directory and /etc. Bugs Fixed * InnoDB: The server allocated memory unnecessarily for an operation that rebuilt the table. * InnoDB: When using an index merge optimizer switch, a SELECT COUNT(*) operation sometimes returned 0. Partitioning code incorrectly performed a memcpy instead of a column copy of columns read by the index, causing the wrong records to be copied. * Replication: A USE statement that followed a SET GTID_NEXT statement sometimes had no effect. * Replication: If the binary log on a master server was rotated and a full disk condition occurred on the partition where the binary log file was being stored, the server could stop unexpectedly. The fix adds a check for the existence of the binary log when the dump thread switches to next binary log file. If the binary log is disabled, all binary logs up to the current active log are transmitted to slave and an error is returned to the receiver thread. * Replication: If a relay log index file named relay log files that did not exist, RESET SLAVE ALL sometimes did not fully clean up properly. * Replication: mysqlbinlog, if invoked with the --raw option, does not flush the output file until the process terminates. But if also invoked with the --stop-never option, the process never terminates, thus nothing is ever written to the output file. Now the output is flushed after each event. * Replication: A memory leak in mysqlbinlog was fixed. The leak happened when processing fake rotate events, or when using --raw and the destination log file could not be created. The leak only occurred when processing events from a remote server. Thanks to Laurynas Biveinis for his contribution to fixing this bug. * Replication: Multi-threaded slaves could not be configured with small queue sizes using slave_pending_jobs_size_max if they ever needed to process transactions larger than that size. Any packet larger than slave_pending_jobs_size_max was rejected with the error ER_MTS_EVENT_BIGGER_PENDING_JOBS_SIZE_MAX, even if the packet was smaller than the limit set by slave_max_allowed_packet. * With this fix, slave_pending_jobs_size_max becomes a soft limit rather than a hard limit. If the size of a packet exceeds slave_pending_jobs_size_max but is less than slave_max_allowed_packet, the transaction is held until all the slave workers have empty queues, and then processed. All subsequent transactions are held until the large transaction has been completed. The queue size for slave workers can therefore be limited while still allowing occasional larger transactions. * mysqldump could write database names in USE statements incorrectly. * If the mysql_stmt_close() C API function was called, it freed memory that later could be accessed if mysql_stmt_error(), mysql_stmt_errno(), or mysql_stmt_sqlstate() was called. To obtain error information after a call to mysql_stmt_close(), call mysql_error(), mysql_errno(), or mysql_sqlstate() instead. * Queries could be cached incorrectly, leading to incorrect query results, under these circumstances: InnoDB table; rows are being inserted but have not yet been committed; a query uses the table as a base table in a derived table; the optimizer chooses to materialize the derived table. * Man pages for a few utilities were missing from Debian/Ubuntu packages. * The field-t unit test failed to run with AddressSanitizer enabled. Thanks to Laurynas Biveinis for the patch. * Debian client packages were missing information about conflicts with native packages. * The Perl path in #! lines at the beginning of Perl scripts has been adjusted to /usr/local/bin/perl for FreeBSD 11. * The server exited abnormally attempting to access invalid memory. * A race condition could occur for CREATE TABLE statements with DATA DIRECTORY or INDEX DIRECTORY clauses. * MySQL compilation in different directories produced different builds to leakage of absolute paths into debug information and __FILE__. * mysqld_failed to start the server if the --datadir option was specified with a relative path name. * With read_only enabled, creation of non-TEMPORARY tables by non-SUPER users was permitted under certain conditions. *Certain stored functions, if used in a query WHERE clause, could be handled using Index Condition Pushdown (which should not happen), resulting in a server exit. * On x86 machines, the uint3korr() macro read 4 bytes of data instead of the intended 3 bytes. * An assertion was raised during a fetch operation by the memcached plugin. * Queries that contained UNION in a subquery and GROUP BY could return incorrect results. * LOAD XML INFILE performance became noticeably slower when the XML file being read contained a great many spaces, such as those introduced by indenting or pretty-printing. Now all leading whitespace is trimmed from each such value before reading it into memory.
2017-07-19 20:48:21 +02:00
share/mysql/test/suite/rpl/t/rpl_reset_slave_fail.test
share/mysql/test/suite/rpl/t/rpl_rewrt_db-slave.opt
share/mysql/test/suite/rpl/t/rpl_rewrt_db.test
share/mysql/test/suite/rpl/t/rpl_rotate_logs.cnf
share/mysql/test/suite/rpl/t/rpl_rotate_logs.test
Changes 5.5.19: * Performance of metadata locking operations on Windows XP systems was improved by instituting a cache for metadata lock objects. This permits the server to avoid expensive operations for creation and destruction of synchronization objects on XP. A new system variable, metadata_locks_cache_size, permits control over the size of the cache. The default size is 1024. * Replication: Previously, replication slaves could connect to the master server through master accounts that use nonnative authentication, except Windows native authentication. This is now also true for Windows native authentication. Bugs Fixed: * InnoDB Storage Engine: An internal deadlock could occur within InnoDB, on a server doing a substantial amount of change buffering for DML operations, particularly DELETE statements. * Rounding DBL_MAX returned DBL_MAX, not 'inf'. * mysql_upgrade did not upgrade the system tables or create the mysql_upgrade_info file when run with the --write-binlog or --skip-write-binlog option. * If a plugin was uninstalled, thread local variables for plugin variables of string type with wth PLUGIN_VAR_MEMALLOC flag were not freed. * Deadlock could occur when these four things happened at the same time: 1) An old dump thread was waiting for the binary log to grow. 2) The slave server that replicates from the old dump thread tried to reconnect. During reconnection, the new dump thread tried to kill the old dump thread. 3) A KILL statement tried to kill the old dump thread. 4) An INSERT statement caused a binary log rotation.
2011-12-13 13:14:49 +01:00
share/mysql/test/suite/rpl/t/rpl_rotate_purge_deadlock-master.opt
share/mysql/test/suite/rpl/t/rpl_rotate_purge_deadlock.test
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_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
share/mysql/test/suite/rpl/t/rpl_row_corruption-slave.opt
share/mysql/test/suite/rpl/t/rpl_row_corruption.test
Changes 5.5.38: Bugs Fixed 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. 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. Certain INFORMATION_SCHEMA queries could cause a server exit. For indexes on prefixes or character string columns, index corruption could occur for assignment of binary data to the column due to improper character counting. Solaris-specific scripts were included in and installed by non-Solaris packages. EXPLAIN on a query with an EXISTS subquery containing a UNION could cause a server exit. Multiple executions of a prepared EXPLAIN on a UNION of subqueries could cause a server exit. Executing a correlated subquery on an ARCHIVE table which has an AUTO_INCREMENT column caused the server to hang. The client library could cause clients to exit due to incorrectly mapping the client error number to the corresponding message, if reallocation of packet buffer memory occurred. Calling mysql_get_server_version() with an invalid connection handler argument caused the client to exit. Now it returns 0 and reports a CR_COMMANDS_OUT_OF_SYNC error. On Windows, calling mysql_thread_init() call without mysql_init() caused the client to exit. windows. Now it returns a nonzero result because it is an error to call mysql_thread_init() before the client library is initialized with mysql_library_init(). CMake produced not-useful warnings about INTERFACE_LINK_LIBRARIES policy. LOAD DATA LOCAL INFILE could use all CPU if import errors occurred when there were no line delimiters. A statement of the following form broke row-based replication because it created a table having a field of data type BIGINT with a display width of 3000, which is beyond the maximum acceptable value of 255: CREATE TABLE t1 AS SELECT REPEAT('A',1000) DIV 1 AS a;
2014-06-02 09:17:31 +02:00
share/mysql/test/suite/rpl/t/rpl_row_create_select.test
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_find_row.test
Changes 5.5.19: * Performance of metadata locking operations on Windows XP systems was improved by instituting a cache for metadata lock objects. This permits the server to avoid expensive operations for creation and destruction of synchronization objects on XP. A new system variable, metadata_locks_cache_size, permits control over the size of the cache. The default size is 1024. * Replication: Previously, replication slaves could connect to the master server through master accounts that use nonnative authentication, except Windows native authentication. This is now also true for Windows native authentication. Bugs Fixed: * InnoDB Storage Engine: An internal deadlock could occur within InnoDB, on a server doing a substantial amount of change buffering for DML operations, particularly DELETE statements. * Rounding DBL_MAX returned DBL_MAX, not 'inf'. * mysql_upgrade did not upgrade the system tables or create the mysql_upgrade_info file when run with the --write-binlog or --skip-write-binlog option. * If a plugin was uninstalled, thread local variables for plugin variables of string type with wth PLUGIN_VAR_MEMALLOC flag were not freed. * Deadlock could occur when these four things happened at the same time: 1) An old dump thread was waiting for the binary log to grow. 2) The slave server that replicates from the old dump thread tried to reconnect. During reconnection, the new dump thread tried to kill the old dump thread. 3) A KILL statement tried to kill the old dump thread. 4) An INSERT statement caused a binary log rotation.
2011-12-13 13:14:49 +01:00
share/mysql/test/suite/rpl/t/rpl_row_find_row_debug.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_idempotency.test
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_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
Update mysql55-{client,server} to 5.55.24. Changes (http://dev.mysql.com/doc/refman/5.5/en/news-5-5-24.html): Functionality Added or Changed * Important Change: Replication: INSERT ON DUPLICATE KEY UPDATE is now marked as unsafe for statement-based replication if the target table has more than one primary or unique key. For more information, see Section 16.1.2.3, "Determination of Safe and Unsafe Statements in Binary Logging". Bugs Fixed * Security Fix: Bug #64884 was fixed. * InnoDB: Replication: When binary log statements were replayed on the slave, the Com_insert, Com_update, and Com_delete counters were incremented by BEGIN statements initiating transactions affecting InnoDB tables but not by COMMIT statements ending such transactions. This affected these statements whether they were replicated or they were run using mysqlbinlog. (Bug #12662190) * If the --bind-address option was given a host name value and the host name resolved to more than one IP address, the server failed to start. For example, with --bind-address=localhost, if localhost resolved to both 127.0.0.1 and ::1, startup failed. Now the server prefers the IPv4 address in such cases. (Bug #61713, Bug #12762885) * mysql_store_result() and mysql_use_result() are not for use with prepared statements and are not intended to be called following mysql_stmt_execute(), but failed to return an error when invoked that way in libmysqld. (Bug #62136, Bug #13738989) References: See also Bug #47485. * On Windows, mysqlslap crashed for attempts to connect using shared memory. (Bug #31173, Bug #11747181, Bug #59107, Bug #11766072)
2012-05-13 15:05:33 +02:00
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_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_reset_slave.test
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.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
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
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.5.39: CMake support was updated to handle CMake version 3. The timed_mutexes system variable has no effect and is deprecated. Bugs Fixed InnoDB: Opening a parent table that has thousands of child tables could result in a long semaphore wait condition. Partitioning: Selecting from a table having multiple columns in its primary key and partitioned by LIST COLUMNS(R), where R was the last (rightmost) column listed in the primary key definition, returned an incorrect result. Replication: When using row-based replication, updating or deleting a row on the master that did not exist on the slave led to failure of the slave when it tried to process the change. This problem occurred with InnoDB tables lacking a primary key. Replication: Quotation marks were not always handled correctly by LOAD DATA INFILE when written into the binary log. Replication: A group of threads involved in acquiring locks could deadlock when the following events occurred: Dump thread reconnects from slave; on master, a new dump thread tries to kill zombie dump threads; having acquired the thread's LOCK_thd_data, it is about to acquire LOCK_log. Application thread executing show binary logs, having acquired LOCK_log and about to acquire LOCK_index. Application thread executing PURGE BINARY LOGS; having acquired LOCK_index, it is about to acquire LOCK_thread_count. Application thread executing SHOW PROCESSLIST (or SELECT * FROM INFORMATION_SCHEMA.PROCESSLIST), having acquired LOCK_thread_count and about to acquire the zombie dump thread's LOCK_thd_data.
2014-08-10 16:27:40 +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
share/mysql/test/suite/rpl/t/rpl_server_id1.test
share/mysql/test/suite/rpl/t/rpl_server_id2-slave.opt
share/mysql/test/suite/rpl/t/rpl_server_id2.test
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_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_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
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_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_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
share/mysql/test/suite/rpl/t/rpl_spec_variables-slave.opt
share/mysql/test/suite/rpl/t/rpl_spec_variables.test
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
share/mysql/test/suite/rpl/t/rpl_sporadic_master-master.opt
share/mysql/test/suite/rpl/t/rpl_sporadic_master.test
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_start_stop_slave-slave.opt
Changes 5.5.21: * A new CMake option, MYSQL_PROJECT_NAME, can be set on Windows or Mac OS X to be used in the project name. Bugs Fixed * Performance: InnoDB Storage Engine: Memory allocation for InnoDB tables was reorganized to reduce the memory overhead for large numbers of tables or partitions, avoiding situations where the “resident set size” could grow regardless of FLUSH TABLES statements. The problem was most evident for tables with large row size. * Incompatible Change: An earlier change (in MySQL 5.1.62 and 5.5.21) was found to modify date-handling behavior in General Availability-status series (MySQL 5.1 and 5.5). This change has been reverted. * The change was that several functions became more strict when passed a DATE() function value as their argument, thus they rejected incomplete dates with a day part of zero. These functions were affected: CONVERT_TZ(), DATE_ADD(), DATE_SUB(), DAYOFYEAR(), LAST_DAY(), TIMESTAMPDIFF(), TO_DAYS(), TO_SECONDS(), WEEK(), WEEKDAY(), WEEKOFYEAR(), YEARWEEK(). The previous behavior has been restored. * InnoDB Storage Engine: A Valgrind error was fixed in the function os_aio_init(). * InnoDB Storage Engine: The server could crash when creating an InnoDB temporary table under Linux, if the $TMPDIR setting points to a tmpfs filesystem and innodb_use_native_aio is enabled, as it is by default in MySQL 5.5.4 and higher. * InnoDB Storage Engine: References to C preprocessor symbols and macros HAVE_purify, UNIV_INIT_MEM_TO_ZERO, and UNIV_SET_MEM_TO_ZERO were removed from the InnoDB source code. They were only used in debug builds instrumented for Valgrind. They are replaced by calls to the UNIV_MEM_INVALID() macro.
2012-02-23 14:01:03 +01:00
share/mysql/test/suite/rpl/t/rpl_start_stop_slave.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_direct-master.opt
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
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_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_show_relaylog_events.test
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
Changes 5.5.23: Bugs Fixed * Security Fix: Bug 59533 was fixed. * Performance: Partitioning: InnoDB Storage Engine: The statistics used by the optimizer for queries against partitioned InnoDB tables were based only on the first partition of each such table, leading to use of the wrong execution plan. * References: This bug was introduced by Bug 11756867. * Performance: InnoDB Storage Engine: Improved the performance of the DROP TABLE statement for InnoDB tables, especially on systems with a large buffer pool. The fix speeds up the processing for freeing entries in the adaptive hash index. * InnoDB Storage Engine: Deleting a huge amount of data from InnoDB tables within a short time could cause the purge operation that flushes data from the buffer pool to stall. If this issue occurs, restart the server to work around it. This issue is only likely to occur on 32-bit platforms. * InnoDB Storage Engine: If the server crashed during a TRUNCATE TABLE or CREATE INDEX statement for an InnoDB table, or a DROP DATABASE statement for a database containing InnoDB tables, an index could be corrupted, causing an error message when accessing the table after restart: InnoDB: Error: trying to load index index_name for table table_name InnoDB: but the index tree has been freed! In MySQL 5.1, this fix applies to the InnoDB Plugin, but not the built-in InnoDB storage engine. * InnoDB Storage Engine: When data was removed from an InnoDB table, newly inserted data might not reuse the freed disk blocks, leading to an unexpected size increase for the system tablespace or .ibd file (depending on the setting of innodb_file_per_table. The OPTIMIZE TABLE could compact a .ibd file in some cases but not others. The freed disk blocks would eventually be reused as additional data was inserted. More...
2012-04-14 14:10:05 +02:00
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
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.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_temporary.test
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
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
share/mysql/test/suite/rpl/t/rpl_unsafe_statements.test
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/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
Changes 5.5.17: * Replication: Previously, replication slaves could connect to the master server only through master accounts that use native authentication. Now replication slaves can also connect through master accounts that use nonnative authentication (except Windows native authentication) if the required client-side plugin is installed on the slave side in the directory named by the slave plugin_dir system variable. * MEMORY table creation time is now available in the CREATE_TIME column of the INFORMATION_SCHEMA.TABLES table and the Create_time column of SHOW TABLE STATUS output. * InnoDB Storage Engine: This fix improves the performance of instrumentation code for InnoDB buffer pool operations. * InnoDB Storage Engine: Data from BLOB columns could be lost if the server crashed at a precise moment when other columns were being updated in an InnoDB table. * InnoDB Storage Engine: Lookups using secondary indexes could give incorrect matches under a specific set of conditions. The conditions involve an index defined on a column prefix, for a BLOB or other long column stored outside the index page, with a table using the Barracuda file format. * InnoDB Storage Engine: This fix corrects cases where the MySQL server could hang or abort with a long semaphore wait message. (This is a different issue than when these symptoms occurred during a CHECK TABLE statement.) * Internal conversion of zero to binary and back could yield a result with incorrect precision. * Valgrind warnings generated by filesort operations were fixed. * mysqld_safe did not properly check for an already running instance of mysqld. * The help message for mysql_install_db did not indicate that it supports the --defaults-file, --defaults-extra-file and --no-defaults options. * An assertion designed to detect zero-length sort keys also was raised when the entire key set fit in memory. * myisampack could create corrupt FULLTEXT indexes when compressing tables. * A linking problem prevented the FEDERATED storage engine plugin from loading.
2011-10-22 12:32:37 +02:00
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/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/rpl_recovery_rank_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
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/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_direct_non_transactional_updates_basic.result
share/mysql/test/suite/sys_vars/r/binlog_format_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
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/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_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/div_precision_increment_basic.result
share/mysql/test/suite/sys_vars/r/div_precision_increment_func.result
share/mysql/test/suite/sys_vars/r/engine_condition_pushdown_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/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/have_compress_basic.result
share/mysql/test/suite/sys_vars/r/have_crypt_basic.result
share/mysql/test/suite/sys_vars/r/have_csv_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_innodb_basic.result
share/mysql/test/suite/sys_vars/r/have_ndbcluster_basic.result
share/mysql/test/suite/sys_vars/r/have_openssl_basic.result
share/mysql/test/suite/sys_vars/r/have_partitioning_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/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/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_hash_index_basic.result
share/mysql/test/suite/sys_vars/r/innodb_additional_mem_pool_size_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
share/mysql/test/suite/sys_vars/r/innodb_buffer_pool_evict_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_size_basic.result
share/mysql/test/suite/sys_vars/r/innodb_change_buffering_basic.result
Changes 5.5.21: * A new CMake option, MYSQL_PROJECT_NAME, can be set on Windows or Mac OS X to be used in the project name. Bugs Fixed * Performance: InnoDB Storage Engine: Memory allocation for InnoDB tables was reorganized to reduce the memory overhead for large numbers of tables or partitions, avoiding situations where the “resident set size” could grow regardless of FLUSH TABLES statements. The problem was most evident for tables with large row size. * Incompatible Change: An earlier change (in MySQL 5.1.62 and 5.5.21) was found to modify date-handling behavior in General Availability-status series (MySQL 5.1 and 5.5). This change has been reverted. * The change was that several functions became more strict when passed a DATE() function value as their argument, thus they rejected incomplete dates with a day part of zero. These functions were affected: CONVERT_TZ(), DATE_ADD(), DATE_SUB(), DAYOFYEAR(), LAST_DAY(), TIMESTAMPDIFF(), TO_DAYS(), TO_SECONDS(), WEEK(), WEEKDAY(), WEEKOFYEAR(), YEARWEEK(). The previous behavior has been restored. * InnoDB Storage Engine: A Valgrind error was fixed in the function os_aio_init(). * InnoDB Storage Engine: The server could crash when creating an InnoDB temporary table under Linux, if the $TMPDIR setting points to a tmpfs filesystem and innodb_use_native_aio is enabled, as it is by default in MySQL 5.5.4 and higher. * InnoDB Storage Engine: References to C preprocessor symbols and macros HAVE_purify, UNIV_INIT_MEM_TO_ZERO, and UNIV_SET_MEM_TO_ZERO were removed from the InnoDB source code. They were only used in debug builds instrumented for Valgrind. They are replaced by calls to the UNIV_MEM_INVALID() macro.
2012-02-23 14:01:03 +01:00
share/mysql/test/suite/sys_vars/r/innodb_change_buffering_debug_basic.result
share/mysql/test/suite/sys_vars/r/innodb_checksums_basic.result
share/mysql/test/suite/sys_vars/r/innodb_commit_concurrency_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_doublewrite_basic.result
share/mysql/test/suite/sys_vars/r/innodb_fast_shutdown_basic.result
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_trx_commit_basic.result
share/mysql/test/suite/sys_vars/r/innodb_flush_method_basic.result
Changes 5.5.17: * Replication: Previously, replication slaves could connect to the master server only through master accounts that use native authentication. Now replication slaves can also connect through master accounts that use nonnative authentication (except Windows native authentication) if the required client-side plugin is installed on the slave side in the directory named by the slave plugin_dir system variable. * MEMORY table creation time is now available in the CREATE_TIME column of the INFORMATION_SCHEMA.TABLES table and the Create_time column of SHOW TABLE STATUS output. * InnoDB Storage Engine: This fix improves the performance of instrumentation code for InnoDB buffer pool operations. * InnoDB Storage Engine: Data from BLOB columns could be lost if the server crashed at a precise moment when other columns were being updated in an InnoDB table. * InnoDB Storage Engine: Lookups using secondary indexes could give incorrect matches under a specific set of conditions. The conditions involve an index defined on a column prefix, for a BLOB or other long column stored outside the index page, with a table using the Barracuda file format. * InnoDB Storage Engine: This fix corrects cases where the MySQL server could hang or abort with a long semaphore wait message. (This is a different issue than when these symptoms occurred during a CHECK TABLE statement.) * Internal conversion of zero to binary and back could yield a result with incorrect precision. * Valgrind warnings generated by filesort operations were fixed. * mysqld_safe did not properly check for an already running instance of mysqld. * The help message for mysql_install_db did not indicate that it supports the --defaults-file, --defaults-extra-file and --no-defaults options. * An assertion designed to detect zero-length sort keys also was raised when the entire key set fit in memory. * myisampack could create corrupt FULLTEXT indexes when compressing tables. * A linking problem prevented the FEDERATED storage engine plugin from loading.
2011-10-22 12:32:37 +02:00
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_io_capacity_basic.result
Changes 5.5.17: * Replication: Previously, replication slaves could connect to the master server only through master accounts that use native authentication. Now replication slaves can also connect through master accounts that use nonnative authentication (except Windows native authentication) if the required client-side plugin is installed on the slave side in the directory named by the slave plugin_dir system variable. * MEMORY table creation time is now available in the CREATE_TIME column of the INFORMATION_SCHEMA.TABLES table and the Create_time column of SHOW TABLE STATUS output. * InnoDB Storage Engine: This fix improves the performance of instrumentation code for InnoDB buffer pool operations. * InnoDB Storage Engine: Data from BLOB columns could be lost if the server crashed at a precise moment when other columns were being updated in an InnoDB table. * InnoDB Storage Engine: Lookups using secondary indexes could give incorrect matches under a specific set of conditions. The conditions involve an index defined on a column prefix, for a BLOB or other long column stored outside the index page, with a table using the Barracuda file format. * InnoDB Storage Engine: This fix corrects cases where the MySQL server could hang or abort with a long semaphore wait message. (This is a different issue than when these symptoms occurred during a CHECK TABLE statement.) * Internal conversion of zero to binary and back could yield a result with incorrect precision. * Valgrind warnings generated by filesort operations were fixed. * mysqld_safe did not properly check for an already running instance of mysqld. * The help message for mysql_install_db did not indicate that it supports the --defaults-file, --defaults-extra-file and --no-defaults options. * An assertion designed to detect zero-length sort keys also was raised when the entire key set fit in memory. * myisampack could create corrupt FULLTEXT indexes when compressing tables. * A linking problem prevented the FEDERATED storage engine plugin from loading.
2011-10-22 12:32:37 +02:00
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
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_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_purge_lag_basic.result
share/mysql/test/suite/sys_vars/r/innodb_mirrored_log_groups_basic.result
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_open_files_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_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_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
share/mysql/test/suite/sys_vars/r/innodb_spin_wait_delay_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_sample_pages_basic.result
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_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
share/mysql/test/suite/sys_vars/r/innodb_trx_purge_view_update_only_debug_basic.result
Changes 5.5.21: * A new CMake option, MYSQL_PROJECT_NAME, can be set on Windows or Mac OS X to be used in the project name. Bugs Fixed * Performance: InnoDB Storage Engine: Memory allocation for InnoDB tables was reorganized to reduce the memory overhead for large numbers of tables or partitions, avoiding situations where the “resident set size” could grow regardless of FLUSH TABLES statements. The problem was most evident for tables with large row size. * Incompatible Change: An earlier change (in MySQL 5.1.62 and 5.5.21) was found to modify date-handling behavior in General Availability-status series (MySQL 5.1 and 5.5). This change has been reverted. * The change was that several functions became more strict when passed a DATE() function value as their argument, thus they rejected incomplete dates with a day part of zero. These functions were affected: CONVERT_TZ(), DATE_ADD(), DATE_SUB(), DAYOFYEAR(), LAST_DAY(), TIMESTAMPDIFF(), TO_DAYS(), TO_SECONDS(), WEEK(), WEEKDAY(), WEEKOFYEAR(), YEARWEEK(). The previous behavior has been restored. * InnoDB Storage Engine: A Valgrind error was fixed in the function os_aio_init(). * InnoDB Storage Engine: The server could crash when creating an InnoDB temporary table under Linux, if the $TMPDIR setting points to a tmpfs filesystem and innodb_use_native_aio is enabled, as it is by default in MySQL 5.5.4 and higher. * InnoDB Storage Engine: References to C preprocessor symbols and macros HAVE_purify, UNIV_INIT_MEM_TO_ZERO, and UNIV_SET_MEM_TO_ZERO were removed from the InnoDB source code. They were only used in debug builds instrumented for Valgrind. They are replaced by calls to the UNIV_MEM_INVALID() macro.
2012-02-23 14:01:03 +01:00
share/mysql/test/suite/sys_vars/r/innodb_trx_rseg_n_slots_debug_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_basic.result
share/mysql/test/suite/sys_vars/r/log_bin_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_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
share/mysql/test/suite/sys_vars/r/log_slow_queries_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/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
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_long_data_size_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
Changes 5.5.19: * Performance of metadata locking operations on Windows XP systems was improved by instituting a cache for metadata lock objects. This permits the server to avoid expensive operations for creation and destruction of synchronization objects on XP. A new system variable, metadata_locks_cache_size, permits control over the size of the cache. The default size is 1024. * Replication: Previously, replication slaves could connect to the master server through master accounts that use nonnative authentication, except Windows native authentication. This is now also true for Windows native authentication. Bugs Fixed: * InnoDB Storage Engine: An internal deadlock could occur within InnoDB, on a server doing a substantial amount of change buffering for DML operations, particularly DELETE statements. * Rounding DBL_MAX returned DBL_MAX, not 'inf'. * mysql_upgrade did not upgrade the system tables or create the mysql_upgrade_info file when run with the --write-binlog or --skip-write-binlog option. * If a plugin was uninstalled, thread local variables for plugin variables of string type with wth PLUGIN_VAR_MEMALLOC flag were not freed. * Deadlock could occur when these four things happened at the same time: 1) An old dump thread was waiting for the binary log to grow. 2) The slave server that replicates from the old dump thread tried to reconnect. During reconnection, the new dump thread tried to kill the old dump thread. 3) A KILL statement tried to kill the old dump thread. 4) An INSERT statement caused a binary log rotation.
2011-12-13 13:14:49 +01:00
share/mysql/test/suite/sys_vars/r/metadata_locks_cache_size_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/performance_schema_basic.result
share/mysql/test/suite/sys_vars/r/pfs_events_waits_history_long_size_basic.result
share/mysql/test/suite/sys_vars/r/pfs_events_waits_history_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
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_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/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_history_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_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_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
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/shared_memory_base_name_basic.result
share/mysql/test/suite/sys_vars/r/shared_memory_basic.result
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_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_skip_errors_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_big_tables_basic.result
share/mysql/test/suite/sys_vars/r/sql_big_tables_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_basic.result
share/mysql/test/suite/sys_vars/r/sql_low_priority_updates_func.result
share/mysql/test/suite/sys_vars/r/sql_max_join_size_basic.result
share/mysql/test/suite/sys_vars/r/sql_max_join_size_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_key_basic.result
share/mysql/test/suite/sys_vars/r/storage_engine_basic.result
Changes 5.5.21: * A new CMake option, MYSQL_PROJECT_NAME, can be set on Windows or Mac OS X to be used in the project name. Bugs Fixed * Performance: InnoDB Storage Engine: Memory allocation for InnoDB tables was reorganized to reduce the memory overhead for large numbers of tables or partitions, avoiding situations where the “resident set size” could grow regardless of FLUSH TABLES statements. The problem was most evident for tables with large row size. * Incompatible Change: An earlier change (in MySQL 5.1.62 and 5.5.21) was found to modify date-handling behavior in General Availability-status series (MySQL 5.1 and 5.5). This change has been reverted. * The change was that several functions became more strict when passed a DATE() function value as their argument, thus they rejected incomplete dates with a day part of zero. These functions were affected: CONVERT_TZ(), DATE_ADD(), DATE_SUB(), DAYOFYEAR(), LAST_DAY(), TIMESTAMPDIFF(), TO_DAYS(), TO_SECONDS(), WEEK(), WEEKDAY(), WEEKOFYEAR(), YEARWEEK(). The previous behavior has been restored. * InnoDB Storage Engine: A Valgrind error was fixed in the function os_aio_init(). * InnoDB Storage Engine: The server could crash when creating an InnoDB temporary table under Linux, if the $TMPDIR setting points to a tmpfs filesystem and innodb_use_native_aio is enabled, as it is by default in MySQL 5.5.4 and higher. * InnoDB Storage Engine: References to C preprocessor symbols and macros HAVE_purify, UNIV_INIT_MEM_TO_ZERO, and UNIV_SET_MEM_TO_ZERO were removed from the InnoDB source code. They were only used in debug builds instrumented for Valgrind. They are replaced by calls to the UNIV_MEM_INVALID() macro.
2012-02-23 14:01:03 +01:00
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/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
share/mysql/test/suite/sys_vars/r/transaction_alloc_block_size_basic.result
share/mysql/test/suite/sys_vars/r/transaction_prealloc_size_basic.result
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/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
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/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_direct_non_transactional_updates_basic.test
share/mysql/test/suite/sys_vars/t/binlog_format_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
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/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_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/div_precision_increment_basic.test
share/mysql/test/suite/sys_vars/t/div_precision_increment_func.test
share/mysql/test/suite/sys_vars/t/engine_condition_pushdown_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/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/have_compress_basic.test
share/mysql/test/suite/sys_vars/t/have_crypt_basic.test
share/mysql/test/suite/sys_vars/t/have_csv_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_innodb_basic.test
share/mysql/test/suite/sys_vars/t/have_ndbcluster_basic.test
share/mysql/test/suite/sys_vars/t/have_openssl_basic.test
share/mysql/test/suite/sys_vars/t/have_partitioning_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/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/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_hash_index_basic.test
share/mysql/test/suite/sys_vars/t/innodb_additional_mem_pool_size_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
share/mysql/test/suite/sys_vars/t/innodb_buffer_pool_evict_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_size_basic.test
share/mysql/test/suite/sys_vars/t/innodb_change_buffering_basic.test
Changes 5.5.21: * A new CMake option, MYSQL_PROJECT_NAME, can be set on Windows or Mac OS X to be used in the project name. Bugs Fixed * Performance: InnoDB Storage Engine: Memory allocation for InnoDB tables was reorganized to reduce the memory overhead for large numbers of tables or partitions, avoiding situations where the “resident set size” could grow regardless of FLUSH TABLES statements. The problem was most evident for tables with large row size. * Incompatible Change: An earlier change (in MySQL 5.1.62 and 5.5.21) was found to modify date-handling behavior in General Availability-status series (MySQL 5.1 and 5.5). This change has been reverted. * The change was that several functions became more strict when passed a DATE() function value as their argument, thus they rejected incomplete dates with a day part of zero. These functions were affected: CONVERT_TZ(), DATE_ADD(), DATE_SUB(), DAYOFYEAR(), LAST_DAY(), TIMESTAMPDIFF(), TO_DAYS(), TO_SECONDS(), WEEK(), WEEKDAY(), WEEKOFYEAR(), YEARWEEK(). The previous behavior has been restored. * InnoDB Storage Engine: A Valgrind error was fixed in the function os_aio_init(). * InnoDB Storage Engine: The server could crash when creating an InnoDB temporary table under Linux, if the $TMPDIR setting points to a tmpfs filesystem and innodb_use_native_aio is enabled, as it is by default in MySQL 5.5.4 and higher. * InnoDB Storage Engine: References to C preprocessor symbols and macros HAVE_purify, UNIV_INIT_MEM_TO_ZERO, and UNIV_SET_MEM_TO_ZERO were removed from the InnoDB source code. They were only used in debug builds instrumented for Valgrind. They are replaced by calls to the UNIV_MEM_INVALID() macro.
2012-02-23 14:01:03 +01:00
share/mysql/test/suite/sys_vars/t/innodb_change_buffering_debug_basic.test
share/mysql/test/suite/sys_vars/t/innodb_checksums_basic.test
share/mysql/test/suite/sys_vars/t/innodb_commit_concurrency_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_doublewrite_basic.test
share/mysql/test/suite/sys_vars/t/innodb_fast_shutdown_basic.test
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.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
Changes 5.5.17: * Replication: Previously, replication slaves could connect to the master server only through master accounts that use native authentication. Now replication slaves can also connect through master accounts that use nonnative authentication (except Windows native authentication) if the required client-side plugin is installed on the slave side in the directory named by the slave plugin_dir system variable. * MEMORY table creation time is now available in the CREATE_TIME column of the INFORMATION_SCHEMA.TABLES table and the Create_time column of SHOW TABLE STATUS output. * InnoDB Storage Engine: This fix improves the performance of instrumentation code for InnoDB buffer pool operations. * InnoDB Storage Engine: Data from BLOB columns could be lost if the server crashed at a precise moment when other columns were being updated in an InnoDB table. * InnoDB Storage Engine: Lookups using secondary indexes could give incorrect matches under a specific set of conditions. The conditions involve an index defined on a column prefix, for a BLOB or other long column stored outside the index page, with a table using the Barracuda file format. * InnoDB Storage Engine: This fix corrects cases where the MySQL server could hang or abort with a long semaphore wait message. (This is a different issue than when these symptoms occurred during a CHECK TABLE statement.) * Internal conversion of zero to binary and back could yield a result with incorrect precision. * Valgrind warnings generated by filesort operations were fixed. * mysqld_safe did not properly check for an already running instance of mysqld. * The help message for mysql_install_db did not indicate that it supports the --defaults-file, --defaults-extra-file and --no-defaults options. * An assertion designed to detect zero-length sort keys also was raised when the entire key set fit in memory. * myisampack could create corrupt FULLTEXT indexes when compressing tables. * A linking problem prevented the FEDERATED storage engine plugin from loading.
2011-10-22 12:32:37 +02:00
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_io_capacity_basic.test
Changes 5.5.17: * Replication: Previously, replication slaves could connect to the master server only through master accounts that use native authentication. Now replication slaves can also connect through master accounts that use nonnative authentication (except Windows native authentication) if the required client-side plugin is installed on the slave side in the directory named by the slave plugin_dir system variable. * MEMORY table creation time is now available in the CREATE_TIME column of the INFORMATION_SCHEMA.TABLES table and the Create_time column of SHOW TABLE STATUS output. * InnoDB Storage Engine: This fix improves the performance of instrumentation code for InnoDB buffer pool operations. * InnoDB Storage Engine: Data from BLOB columns could be lost if the server crashed at a precise moment when other columns were being updated in an InnoDB table. * InnoDB Storage Engine: Lookups using secondary indexes could give incorrect matches under a specific set of conditions. The conditions involve an index defined on a column prefix, for a BLOB or other long column stored outside the index page, with a table using the Barracuda file format. * InnoDB Storage Engine: This fix corrects cases where the MySQL server could hang or abort with a long semaphore wait message. (This is a different issue than when these symptoms occurred during a CHECK TABLE statement.) * Internal conversion of zero to binary and back could yield a result with incorrect precision. * Valgrind warnings generated by filesort operations were fixed. * mysqld_safe did not properly check for an already running instance of mysqld. * The help message for mysql_install_db did not indicate that it supports the --defaults-file, --defaults-extra-file and --no-defaults options. * An assertion designed to detect zero-length sort keys also was raised when the entire key set fit in memory. * myisampack could create corrupt FULLTEXT indexes when compressing tables. * A linking problem prevented the FEDERATED storage engine plugin from loading.
2011-10-22 12:32:37 +02:00
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
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_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_purge_lag_basic.test
share/mysql/test/suite/sys_vars/t/innodb_mirrored_log_groups_basic.test
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_open_files_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_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_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
share/mysql/test/suite/sys_vars/t/innodb_spin_wait_delay_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_sample_pages_basic.test
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_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
share/mysql/test/suite/sys_vars/t/innodb_trx_purge_view_update_only_debug_basic.test
Changes 5.5.21: * A new CMake option, MYSQL_PROJECT_NAME, can be set on Windows or Mac OS X to be used in the project name. Bugs Fixed * Performance: InnoDB Storage Engine: Memory allocation for InnoDB tables was reorganized to reduce the memory overhead for large numbers of tables or partitions, avoiding situations where the “resident set size” could grow regardless of FLUSH TABLES statements. The problem was most evident for tables with large row size. * Incompatible Change: An earlier change (in MySQL 5.1.62 and 5.5.21) was found to modify date-handling behavior in General Availability-status series (MySQL 5.1 and 5.5). This change has been reverted. * The change was that several functions became more strict when passed a DATE() function value as their argument, thus they rejected incomplete dates with a day part of zero. These functions were affected: CONVERT_TZ(), DATE_ADD(), DATE_SUB(), DAYOFYEAR(), LAST_DAY(), TIMESTAMPDIFF(), TO_DAYS(), TO_SECONDS(), WEEK(), WEEKDAY(), WEEKOFYEAR(), YEARWEEK(). The previous behavior has been restored. * InnoDB Storage Engine: A Valgrind error was fixed in the function os_aio_init(). * InnoDB Storage Engine: The server could crash when creating an InnoDB temporary table under Linux, if the $TMPDIR setting points to a tmpfs filesystem and innodb_use_native_aio is enabled, as it is by default in MySQL 5.5.4 and higher. * InnoDB Storage Engine: References to C preprocessor symbols and macros HAVE_purify, UNIV_INIT_MEM_TO_ZERO, and UNIV_SET_MEM_TO_ZERO were removed from the InnoDB source code. They were only used in debug builds instrumented for Valgrind. They are replaced by calls to the UNIV_MEM_INVALID() macro.
2012-02-23 14:01:03 +01:00
share/mysql/test/suite/sys_vars/t/innodb_trx_rseg_n_slots_debug_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_basic.test
share/mysql/test/suite/sys_vars/t/log_bin_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_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
share/mysql/test/suite/sys_vars/t/log_slow_queries_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/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
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_long_data_size_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.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
Changes 5.5.19: * Performance of metadata locking operations on Windows XP systems was improved by instituting a cache for metadata lock objects. This permits the server to avoid expensive operations for creation and destruction of synchronization objects on XP. A new system variable, metadata_locks_cache_size, permits control over the size of the cache. The default size is 1024. * Replication: Previously, replication slaves could connect to the master server through master accounts that use nonnative authentication, except Windows native authentication. This is now also true for Windows native authentication. Bugs Fixed: * InnoDB Storage Engine: An internal deadlock could occur within InnoDB, on a server doing a substantial amount of change buffering for DML operations, particularly DELETE statements. * Rounding DBL_MAX returned DBL_MAX, not 'inf'. * mysql_upgrade did not upgrade the system tables or create the mysql_upgrade_info file when run with the --write-binlog or --skip-write-binlog option. * If a plugin was uninstalled, thread local variables for plugin variables of string type with wth PLUGIN_VAR_MEMALLOC flag were not freed. * Deadlock could occur when these four things happened at the same time: 1) An old dump thread was waiting for the binary log to grow. 2) The slave server that replicates from the old dump thread tried to reconnect. During reconnection, the new dump thread tried to kill the old dump thread. 3) A KILL statement tried to kill the old dump thread. 4) An INSERT statement caused a binary log rotation.
2011-12-13 13:14:49 +01:00
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/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/performance_schema_basic-master.opt
share/mysql/test/suite/sys_vars/t/performance_schema_basic.test
share/mysql/test/suite/sys_vars/t/pfs_events_waits_history_long_size_basic-master.opt
share/mysql/test/suite/sys_vars/t/pfs_events_waits_history_long_size_basic.test
share/mysql/test/suite/sys_vars/t/pfs_events_waits_history_size_basic-master.opt
share/mysql/test/suite/sys_vars/t/pfs_events_waits_history_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
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_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/pid_file_basic.test
Changes 5.5.17: * Replication: Previously, replication slaves could connect to the master server only through master accounts that use native authentication. Now replication slaves can also connect through master accounts that use nonnative authentication (except Windows native authentication) if the required client-side plugin is installed on the slave side in the directory named by the slave plugin_dir system variable. * MEMORY table creation time is now available in the CREATE_TIME column of the INFORMATION_SCHEMA.TABLES table and the Create_time column of SHOW TABLE STATUS output. * InnoDB Storage Engine: This fix improves the performance of instrumentation code for InnoDB buffer pool operations. * InnoDB Storage Engine: Data from BLOB columns could be lost if the server crashed at a precise moment when other columns were being updated in an InnoDB table. * InnoDB Storage Engine: Lookups using secondary indexes could give incorrect matches under a specific set of conditions. The conditions involve an index defined on a column prefix, for a BLOB or other long column stored outside the index page, with a table using the Barracuda file format. * InnoDB Storage Engine: This fix corrects cases where the MySQL server could hang or abort with a long semaphore wait message. (This is a different issue than when these symptoms occurred during a CHECK TABLE statement.) * Internal conversion of zero to binary and back could yield a result with incorrect precision. * Valgrind warnings generated by filesort operations were fixed. * mysqld_safe did not properly check for an already running instance of mysqld. * The help message for mysql_install_db did not indicate that it supports the --defaults-file, --defaults-extra-file and --no-defaults options. * An assertion designed to detect zero-length sort keys also was raised when the entire key set fit in memory. * myisampack could create corrupt FULLTEXT indexes when compressing tables. * A linking problem prevented the FEDERATED storage engine plugin from loading.
2011-10-22 12:32:37 +02:00
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_history_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.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.test
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.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_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_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_recovery_rank_basic_32.test
share/mysql/test/suite/sys_vars/t/rpl_recovery_rank_basic_64.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
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/shared_memory_base_name_basic.test
share/mysql/test/suite/sys_vars/t/shared_memory_basic.test
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_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_skip_errors_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.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_big_tables_basic.test
share/mysql/test/suite/sys_vars/t/sql_big_tables_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_basic.test
share/mysql/test/suite/sys_vars/t/sql_low_priority_updates_func.test
share/mysql/test/suite/sys_vars/t/sql_max_join_size_basic.test
share/mysql/test/suite/sys_vars/t/sql_max_join_size_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_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
Changes 5.5.21: * A new CMake option, MYSQL_PROJECT_NAME, can be set on Windows or Mac OS X to be used in the project name. Bugs Fixed * Performance: InnoDB Storage Engine: Memory allocation for InnoDB tables was reorganized to reduce the memory overhead for large numbers of tables or partitions, avoiding situations where the “resident set size” could grow regardless of FLUSH TABLES statements. The problem was most evident for tables with large row size. * Incompatible Change: An earlier change (in MySQL 5.1.62 and 5.5.21) was found to modify date-handling behavior in General Availability-status series (MySQL 5.1 and 5.5). This change has been reverted. * The change was that several functions became more strict when passed a DATE() function value as their argument, thus they rejected incomplete dates with a day part of zero. These functions were affected: CONVERT_TZ(), DATE_ADD(), DATE_SUB(), DAYOFYEAR(), LAST_DAY(), TIMESTAMPDIFF(), TO_DAYS(), TO_SECONDS(), WEEK(), WEEKDAY(), WEEKOFYEAR(), YEARWEEK(). The previous behavior has been restored. * InnoDB Storage Engine: A Valgrind error was fixed in the function os_aio_init(). * InnoDB Storage Engine: The server could crash when creating an InnoDB temporary table under Linux, if the $TMPDIR setting points to a tmpfs filesystem and innodb_use_native_aio is enabled, as it is by default in MySQL 5.5.4 and higher. * InnoDB Storage Engine: References to C preprocessor symbols and macros HAVE_purify, UNIV_INIT_MEM_TO_ZERO, and UNIV_SET_MEM_TO_ZERO were removed from the InnoDB source code. They were only used in debug builds instrumented for Valgrind. They are replaced by calls to the UNIV_MEM_INVALID() macro.
2012-02-23 14:01:03 +01:00
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/thread_cache_size_basic.test
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
share/mysql/test/suite/sys_vars/t/transaction_alloc_block_size_basic.test
share/mysql/test/suite/sys_vars/t/transaction_prealloc_size_basic.test
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/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_plugin-master.opt
share/mysql/test/t/archive_plugin.test
Changes 5.5.17: * Replication: Previously, replication slaves could connect to the master server only through master accounts that use native authentication. Now replication slaves can also connect through master accounts that use nonnative authentication (except Windows native authentication) if the required client-side plugin is installed on the slave side in the directory named by the slave plugin_dir system variable. * MEMORY table creation time is now available in the CREATE_TIME column of the INFORMATION_SCHEMA.TABLES table and the Create_time column of SHOW TABLE STATUS output. * InnoDB Storage Engine: This fix improves the performance of instrumentation code for InnoDB buffer pool operations. * InnoDB Storage Engine: Data from BLOB columns could be lost if the server crashed at a precise moment when other columns were being updated in an InnoDB table. * InnoDB Storage Engine: Lookups using secondary indexes could give incorrect matches under a specific set of conditions. The conditions involve an index defined on a column prefix, for a BLOB or other long column stored outside the index page, with a table using the Barracuda file format. * InnoDB Storage Engine: This fix corrects cases where the MySQL server could hang or abort with a long semaphore wait message. (This is a different issue than when these symptoms occurred during a CHECK TABLE statement.) * Internal conversion of zero to binary and back could yield a result with incorrect precision. * Valgrind warnings generated by filesort operations were fixed. * mysqld_safe did not properly check for an already running instance of mysqld. * The help message for mysql_install_db did not indicate that it supports the --defaults-file, --defaults-extra-file and --no-defaults options. * An assertion designed to detect zero-length sort keys also was raised when the entire key set fit in memory. * myisampack could create corrupt FULLTEXT indexes when compressing tables. * A linking problem prevented the FEDERATED storage engine plugin from loading.
2011-10-22 12:32:37 +02:00
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
Security Notes * Security Fix: The linked OpenSSL library for the MySQL Commercial Server has been updated to version 1.0.2l. Issues fixed in the new OpenSSL version are described at http://www.openssl.org/news/vulnerabilities.html. This change does not affect the Oracle-produced MySQL Community build of MySQL Server, which uses the yaSSL library instead. Platform-Specific Notes * Linux: The generic Linux build for MySQL 5.6 is now built on Oracle Linux 6 using glibc 2.12. Systems that use the build need to have glibc 2.12 or later installed on them. Functionality Added or Changed * For Windows, MSI installer packages now include a check for the required Visual Studio redistributable package, and produce a message asking the user to install it if it is missing. * The mysql client now supports a --binary-as-hex option that causes display of binary data using hexadecimal notation (0xvalue). Thanks to Daniël van Eeden for the patch. * mysqlaccess now looks for its configuration file only in the SYSCONFDIR directory and /etc. Bugs Fixed * InnoDB: The server allocated memory unnecessarily for an operation that rebuilt the table. * InnoDB: When using an index merge optimizer switch, a SELECT COUNT(*) operation sometimes returned 0. Partitioning code incorrectly performed a memcpy instead of a column copy of columns read by the index, causing the wrong records to be copied. * Replication: A USE statement that followed a SET GTID_NEXT statement sometimes had no effect. * Replication: If the binary log on a master server was rotated and a full disk condition occurred on the partition where the binary log file was being stored, the server could stop unexpectedly. The fix adds a check for the existence of the binary log when the dump thread switches to next binary log file. If the binary log is disabled, all binary logs up to the current active log are transmitted to slave and an error is returned to the receiver thread. * Replication: If a relay log index file named relay log files that did not exist, RESET SLAVE ALL sometimes did not fully clean up properly. * Replication: mysqlbinlog, if invoked with the --raw option, does not flush the output file until the process terminates. But if also invoked with the --stop-never option, the process never terminates, thus nothing is ever written to the output file. Now the output is flushed after each event. * Replication: A memory leak in mysqlbinlog was fixed. The leak happened when processing fake rotate events, or when using --raw and the destination log file could not be created. The leak only occurred when processing events from a remote server. Thanks to Laurynas Biveinis for his contribution to fixing this bug. * Replication: Multi-threaded slaves could not be configured with small queue sizes using slave_pending_jobs_size_max if they ever needed to process transactions larger than that size. Any packet larger than slave_pending_jobs_size_max was rejected with the error ER_MTS_EVENT_BIGGER_PENDING_JOBS_SIZE_MAX, even if the packet was smaller than the limit set by slave_max_allowed_packet. * With this fix, slave_pending_jobs_size_max becomes a soft limit rather than a hard limit. If the size of a packet exceeds slave_pending_jobs_size_max but is less than slave_max_allowed_packet, the transaction is held until all the slave workers have empty queues, and then processed. All subsequent transactions are held until the large transaction has been completed. The queue size for slave workers can therefore be limited while still allowing occasional larger transactions. * mysqldump could write database names in USE statements incorrectly. * If the mysql_stmt_close() C API function was called, it freed memory that later could be accessed if mysql_stmt_error(), mysql_stmt_errno(), or mysql_stmt_sqlstate() was called. To obtain error information after a call to mysql_stmt_close(), call mysql_error(), mysql_errno(), or mysql_sqlstate() instead. * Queries could be cached incorrectly, leading to incorrect query results, under these circumstances: InnoDB table; rows are being inserted but have not yet been committed; a query uses the table as a base table in a derived table; the optimizer chooses to materialize the derived table. * Man pages for a few utilities were missing from Debian/Ubuntu packages. * The field-t unit test failed to run with AddressSanitizer enabled. Thanks to Laurynas Biveinis for the patch. * Debian client packages were missing information about conflicts with native packages. * The Perl path in #! lines at the beginning of Perl scripts has been adjusted to /usr/local/bin/perl for FreeBSD 11. * The server exited abnormally attempting to access invalid memory. * A race condition could occur for CREATE TABLE statements with DATA DIRECTORY or INDEX DIRECTORY clauses. * MySQL compilation in different directories produced different builds to leakage of absolute paths into debug information and __FILE__. * mysqld_failed to start the server if the --datadir option was specified with a relative path name. * With read_only enabled, creation of non-TEMPORARY tables by non-SUPER users was permitted under certain conditions. *Certain stored functions, if used in a query WHERE clause, could be handled using Index Condition Pushdown (which should not happen), resulting in a server exit. * On x86 machines, the uint3korr() macro read 4 bytes of data instead of the intended 3 bytes. * An assertion was raised during a fetch operation by the memcached plugin. * Queries that contained UNION in a subquery and GROUP BY could return incorrect results. * LOAD XML INFILE performance became noticeably slower when the XML file being read contained a great many spaces, such as those introduced by indenting or pretty-printing. Now all leading whitespace is trimmed from each such value before reading it into memory.
2017-07-19 20:48:21 +02:00
share/mysql/test/t/binary_to_hex.test
Update mysql55-{client,server} to 5.55.24. Changes (http://dev.mysql.com/doc/refman/5.5/en/news-5-5-24.html): Functionality Added or Changed * Important Change: Replication: INSERT ON DUPLICATE KEY UPDATE is now marked as unsafe for statement-based replication if the target table has more than one primary or unique key. For more information, see Section 16.1.2.3, "Determination of Safe and Unsafe Statements in Binary Logging". Bugs Fixed * Security Fix: Bug #64884 was fixed. * InnoDB: Replication: When binary log statements were replayed on the slave, the Com_insert, Com_update, and Com_delete counters were incremented by BEGIN statements initiating transactions affecting InnoDB tables but not by COMMIT statements ending such transactions. This affected these statements whether they were replicated or they were run using mysqlbinlog. (Bug #12662190) * If the --bind-address option was given a host name value and the host name resolved to more than one IP address, the server failed to start. For example, with --bind-address=localhost, if localhost resolved to both 127.0.0.1 and ::1, startup failed. Now the server prefers the IPv4 address in such cases. (Bug #61713, Bug #12762885) * mysql_store_result() and mysql_use_result() are not for use with prepared statements and are not intended to be called following mysql_stmt_execute(), but failed to return an error when invoked that way in libmysqld. (Bug #62136, Bug #13738989) References: See also Bug #47485. * On Windows, mysqlslap crashed for attempts to connect using shared memory. (Bug #31173, Bug #11747181, Bug #59107, Bug #11766072)
2012-05-13 15:05:33 +02:00
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
Changes 5.5.25: * The --safe-mode server option now is deprecated and will be removed in MySQL 5.6. * Performance: InnoDB: Improved the algorithm related to adaptive flushing. This fix increases the rate of flushing in cases where compression is used and the data set is larger than the buffer pool, leading to eviction. * InnoDB: In a transaction using the REPEATABLE READ isolation level, an UPDATE or DELETE statement for an InnoDB table could sometimes overlook rows recently committed by other transactions. As explained in Section 14.3.9.2, “Consistent Nonlocking Reads”, DML statements within a REPEATABLE READ transaction apply to rows committed by other transactions, even if a query could not see those rows. * InnoDB: The Innodb_buffer_pool_pages_flushed status variable was incorrectly set to twice the value it should be. Its value should never exceed the value of Innodb_pages_written. * InnoDB: The error handling and message was improved for attempting to create a foreign key with a column referencing itself. The message suggested a potential problem with the data dictionary, when no such problem existed. * InnoDB: The CHECK TABLE statement could fail for a large InnoDB table due to a timeout value of 2 hours. For typical storage devices, the issue could occur for tables that exceeded approximately 200 or 350 GB, depending on I/O speed. The fix relaxes the locking performed on the table being checked, which makes the timeout less likely. It also makes InnoDB recognize the syntax CHECK TABLE QUICK, which avoids the possibility of the timeout entirely. * Replication: It was theoretically possible for concurrent execution of more than one instance of SHOW BINLOG EVENTS to crash the MySQL Server. * Replication: Statements using AUTO_INCREMENT, LAST_INSERT_ID(), RAND(), or user variables could be applied in the wrong context on the slave when using statement-based replication and replication filtering server options (see Section 16.2.3, “How Servers Evaluate Replication Filtering Rules”). * Replication: An INSERT into a table that has a composite primary key that includes an AUTO_INCREMENT column that is not the first column of this composite key is not safe for statement-based binary logging or replication. Such statements are now marked as unsafe and fail with an error when using the STATEMENT binary logging format. For more information, see Section 16.1.2.3, “Determination of Safe and Unsafe Statements in Binary Logging”, as well as Section 16.4.1.1, “Replication and AUTO_INCREMENT”.
2012-06-03 00:28:00 +02:00
share/mysql/test/t/bug12427262.test
Changes 5.5.22: * InnoDB Storage Engine: A deprecation warning is now issued when --ignore-builtin-innodb is used. * yaSSL was upgraded from version 1.7.2 to 2.2.0. * Security Fix: Bug 13510739 and Bug 63775 were fixed. * Important Change: InnoDB Storage Engine: When a row grew in size due to an UPDATE operation, other (non-updated) columns could be moved to off-page storage so that information about the row still fit within the constraints of the InnoDB page size. The pointer to the new allocated off-page data was not set up until the pages were allocated and written, potentially leading to lost data if the system crashed while the column was being moved out of the page. The problem was more common with tables using ROW_FORMAT=DYNAMIC or ROW_FORMAT=COMPRESSED along with the Barracuda file format, particularly with the innodb_file_per_table setting enabled, because page allocation operations are more common as the .ibd tablespace files are extended. Still, the problem could occur with any combination of InnoDB version, file format, and row format. * InnoDB Storage Engine: An erroneous assertion could occur, in debug builds only, when creating an index on a column containing zero-length values (that is, ''). * InnoDB Storage Engine: A DDL operation such as ALTER TABLE ... ADD COLUMN could stall, eventually timing out with an Error 1005: Can't create table message referring to fil_rename_tablespace. * InnoDB Storage Engine: A DDL operation for an InnoDB table could cause a busy MySQL server to halt with an assertion error: More...
2012-04-08 20:30:27 +02:00
share/mysql/test/t/bug13633383.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.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
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
share/mysql/test/t/consistent_snapshot.test
share/mysql/test/t/constraints.test
share/mysql/test/t/contributors.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/crash_commit_before-master.opt
share/mysql/test/t/crash_commit_before.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
share/mysql/test/t/ctype_cp932.test
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_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/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/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/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/empty_table.test
share/mysql/test/t/enable_cleartext_plugin-master.opt
share/mysql/test/t/enable_cleartext_plugin.test
share/mysql/test/t/endspace.test
share/mysql/test/t/error_simulation-master.opt
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/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
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_if.test
share/mysql/test/t/func_in.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.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
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/gcc296.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_no_prot.test
share/mysql/test/t/grant_cache_ps_prot.test
share/mysql/test/t/grant_lowercase_fs.test
share/mysql/test/t/greedy_optimizer.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/implicit_char_to_num_conversion.test
share/mysql/test/t/implicit_commit-master.opt
share/mysql/test/t/implicit_commit.test
share/mysql/test/t/index_merge_innodb.test
share/mysql/test/t/index_merge_myisam.test
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_ignore_builtin-master.opt
share/mysql/test/t/innodb_ignore_builtin.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/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_crash.test
share/mysql/test/t/join_nested.test
share/mysql/test/t/join_optimizer.test
share/mysql/test/t/join_outer.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/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
share/mysql/test/t/log_errchk.test
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.5.46: * yaSSL was upgraded to version 2.3.8. * InnoDB: A data corruption occurred on ARM64. GCC builtins did not issue the correct fences when setting or unsetting the lock word. * InnoDB: In READ COMMITTED mode, a REPLACE operation on a unique secondary index resulted in a constraint violation. Thanks to Alexey Kopytov for the patch. * 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. * Partitioning: CREATE TABLE statements that used an invalid function in a subpartitioning expression did not always fail gracefully as expected. * Partitioning: ALTER TABLE when executed from a stored procedure did not always work correctly with tables partitioned by RANGE. * Certain subqueries as arguments to PROCEDURE ANALYSE() could cause a server exit. * mysql_ssl_rsa_setup could create an unwanted .rnd file in the data directory. (The file is actually created by openssl, which mysql_ssl_ras_setup invokes. mysql_ssl_rsa_setup now cleans up the file.) * An assertion could be raised due to incorrect error handling if a SELECT ... FOR UPDATE subquery resulted in deadlock and caused a rollback. * Servers linked against yaSSL and compiled with GCC 4.8.2 could fail to respond correctly to connection attempts until several seconds after startup. * For tables with subpartitions, the server could exit due to incorrect error handling during partition pruning if the partition could be identified but not the subpartition. * DELETE could check privileges for the wrong database when table aliases were used. * Within a trigger, use of a cursor that accessed OLD or NEW values from a row could cause a server exit. * MySQL sometimes produced no warning when it was unable to interpret a character in a given character set. * For MySQL distributions linked against yaSSL, a corrupt client key file could cause clients to exit. * Execution of certain BINLOG statements while temporary tables were open by HANDLER statements could cause a server exit.
2015-10-03 14:13:29 +02:00
share/mysql/test/t/lowercase_fs_on.test
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/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.test
share/mysql/test/t/mix2_myisam_ucs2.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_recover-master.opt
share/mysql/test/t/myisam_recover.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_client_test-master.opt
share/mysql/test/t/mysql_client_test.test
share/mysql/test/t/mysql_comments.sql
share/mysql/test/t/mysql_comments.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
Changes 5.5.15: * The undocumented --all option for perror is deprecated and will be removed in MySQL 5.6. Bugs Fixed: * InnoDB Storage Engine: A failed CREATE INDEX operation for an InnoDB table could result in some memory being allocated and not freed. This memory leak could affect tables created with the ROW_FORMAT=DYNAMIC and ROW_FORMAT=COMPRESSED settings. * Partitioning: Auto-increment columns of partitioned tables were checked even when they were not being written to. In debug builds, this could lead to a crash of the server. * Partitioning: The UNIX_TIMESTAMP() function was not treated as a monotonic function for purposes of partition pruning. * Replication: If a LOAD DATA INFILE statement—replicated using statement-based replication—featured a SET clause, the name-value pairs were regenerated using a method (Item::print()) intended primarily for generating output for statements such as EXPLAIN EXTENDED, and which cannot be relied on to return valid SQL. This could in certain cases lead to a crash on the slave. * To fix this problem, we now name each value in its original, user-supplied form, and use that to create LOAD DATA INFILE statements for statement-based replication. * Previously, an inappropriate error message was produced if a multiple-table update for an InnoDB table with a clustered primary key would update a table through multiple aliases, and perform an update that may physically move the row in at least one of these aliases. Now the error message is: Primary key/partition key update is not allowed since the table is updated both as 'tbl_name1' and 'tbl_name2' * ALTER TABLE {MODIFY|CHANGE} ... FIRST did nothing except rename columns if the old and new versions of the table had exactly the same structure with respect to column data types. As a result, the mapping of column name to column data was incorrect. The same thing happened for ALTER TABLE DROP COLUMN, ADD COLUMN statements intended to produce a new version of table with exactly the same structure as the old version. * Incorrect handling of metadata locking for FLUSH TABLES WITH READ LOCK for statements requiring prelocking caused two problems: * Execution of any data-changing statement that required prelocking (that is, involved a stored function or trigger) as part of transaction slowed down somewhat all subsequent statements in the transaction. Performance in a transaction that periodically involved such statements gradually degraded over time.
2011-07-28 10:10:29 +02:00
share/mysql/test/t/mysql_embedded.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
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/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.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_switch_eng_cond_pushdown1-master.opt
share/mysql/test/t/optimizer_switch_eng_cond_pushdown1.test
share/mysql/test/t/optimizer_switch_eng_cond_pushdown2-master.opt
share/mysql/test/t/optimizer_switch_eng_cond_pushdown2.test
share/mysql/test/t/order_by.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-master.opt
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
Changes 5.5.23: Bugs Fixed * Security Fix: Bug 59533 was fixed. * Performance: Partitioning: InnoDB Storage Engine: The statistics used by the optimizer for queries against partitioned InnoDB tables were based only on the first partition of each such table, leading to use of the wrong execution plan. * References: This bug was introduced by Bug 11756867. * Performance: InnoDB Storage Engine: Improved the performance of the DROP TABLE statement for InnoDB tables, especially on systems with a large buffer pool. The fix speeds up the processing for freeing entries in the adaptive hash index. * InnoDB Storage Engine: Deleting a huge amount of data from InnoDB tables within a short time could cause the purge operation that flushes data from the buffer pool to stall. If this issue occurs, restart the server to work around it. This issue is only likely to occur on 32-bit platforms. * InnoDB Storage Engine: If the server crashed during a TRUNCATE TABLE or CREATE INDEX statement for an InnoDB table, or a DROP DATABASE statement for a database containing InnoDB tables, an index could be corrupted, causing an error message when accessing the table after restart: InnoDB: Error: trying to load index index_name for table table_name InnoDB: but the index tree has been freed! In MySQL 5.1, this fix applies to the InnoDB Plugin, but not the built-in InnoDB storage engine. * InnoDB Storage Engine: When data was removed from an InnoDB table, newly inserted data might not reuse the freed disk blocks, leading to an unexpected size increase for the system tablespace or .ibd file (depending on the setting of innodb_file_per_table. The OPTIMIZE TABLE could compact a .ibd file in some cases but not others. The freed disk blocks would eventually be reused as additional data was inserted. More...
2012-04-14 14:10:05 +02:00
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_federated.test
share/mysql/test/t/partition_grant.test
share/mysql/test/t/partition_hash.test
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_key_cache.test
share/mysql/test/t/partition_list.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_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.test
share/mysql/test/t/query_cache_28249.test
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.test
share/mysql/test/t/query_cache_notembedded.test
share/mysql/test/t/query_cache_ps_no_prot.test
share/mysql/test/t/query_cache_ps_ps_prot.test
share/mysql/test/t/query_cache_with_views.test
share/mysql/test/t/range.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/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.test
share/mysql/test/t/select_found.test
share/mysql/test/t/select_safe.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.5.39: CMake support was updated to handle CMake version 3. The timed_mutexes system variable has no effect and is deprecated. Bugs Fixed InnoDB: Opening a parent table that has thousands of child tables could result in a long semaphore wait condition. Partitioning: Selecting from a table having multiple columns in its primary key and partitioned by LIST COLUMNS(R), where R was the last (rightmost) column listed in the primary key definition, returned an incorrect result. Replication: When using row-based replication, updating or deleting a row on the master that did not exist on the slave led to failure of the slave when it tried to process the change. This problem occurred with InnoDB tables lacking a primary key. Replication: Quotation marks were not always handled correctly by LOAD DATA INFILE when written into the binary log. Replication: A group of threads involved in acquiring locks could deadlock when the following events occurred: Dump thread reconnects from slave; on master, a new dump thread tries to kill zombie dump threads; having acquired the thread's LOCK_thd_data, it is about to acquire LOCK_log. Application thread executing show binary logs, having acquired LOCK_log and about to acquire LOCK_index. Application thread executing PURGE BINARY LOGS; having acquired LOCK_index, it is about to acquire LOCK_thread_count. Application thread executing SHOW PROCESSLIST (or SELECT * FROM INFORMATION_SCHEMA.PROCESSLIST), having acquired LOCK_thread_count and about to acquire the zombie dump thread's LOCK_thd_data.
2014-08-10 16:27:40 +02:00
share/mysql/test/t/show_processlist.test
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.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/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.test
share/mysql/test/t/sp-lock.test
share/mysql/test/t/sp-no-code.test
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.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/sql_mode.test
share/mysql/test/t/ssl-big.test
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_ca.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_mode.test
share/mysql/test/t/ssl_mode_no_ssl-master.opt
share/mysql/test/t/ssl_mode_no_ssl.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
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/subselect.test
share/mysql/test/t/subselect2.test
share/mysql/test/t/subselect3.test
share/mysql/test/t/subselect4.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.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/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/tablelock.test
share/mysql/test/t/tablespace.test
share/mysql/test/t/temp_table-master.opt
share/mysql/test/t/temp_table.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/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_time.test
share/mysql/test/t/type_timestamp.test
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/varbinary.test
share/mysql/test/t/variables-big.test
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-master.opt
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/xa.test
share/mysql/test/t/xml.test
share/mysql/test/valgrind.supp
share/mysql/ukrainian/errmsg.sys