2013-09-06 22:31:30 +02:00
|
|
|
# Copyright (c) 2007, 2013, Oracle and/or its affiliates
|
2019-10-28 17:11:10 +02:00
|
|
|
# Copyright (c) 2010, 2019, MariaDB Corporation
|
2010-01-11 18:47:27 -07:00
|
|
|
#
|
|
|
|
|
# This program is free software; you can redistribute it and/or modify
|
|
|
|
|
# it under the terms of the GNU General Public License as published by
|
|
|
|
|
# the Free Software Foundation; version 2 of the License.
|
|
|
|
|
#
|
|
|
|
|
# This program is distributed in the hope that it will be useful,
|
|
|
|
|
# but WITHOUT ANY WARRANTY; without even the implied warranty of
|
|
|
|
|
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
|
|
|
|
|
# GNU General Public License for more details.
|
|
|
|
|
#
|
|
|
|
|
# You should have received a copy of the GNU General Public License
|
|
|
|
|
# along with this program; if not, write to the Free Software
|
2019-05-11 21:29:06 +03:00
|
|
|
# Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1335 USA
|
2010-01-11 18:47:27 -07:00
|
|
|
|
2007-12-12 18:19:24 +01:00
|
|
|
# Default values that applies to all MySQL Servers
|
|
|
|
|
[mysqld]
|
2015-01-07 12:13:21 +01:00
|
|
|
disable-getopt-prefix-matching
|
2017-11-24 21:56:13 +00:00
|
|
|
plugin-maturity=unknown
|
2007-12-12 18:19:24 +01:00
|
|
|
open-files-limit= 1024
|
|
|
|
|
local-infile
|
2010-02-17 10:18:17 +01:00
|
|
|
character-set-server= latin1
|
2007-12-12 18:19:24 +01:00
|
|
|
|
|
|
|
|
# Increase default connect_timeout to avoid intermittent
|
|
|
|
|
# disconnects when test servers are put under load see BUG#28359
|
|
|
|
|
connect-timeout= 60
|
|
|
|
|
|
2012-03-05 17:44:26 +01:00
|
|
|
secure-file-priv= @ENV.MYSQLTEST_VARDIR
|
2011-07-02 22:12:12 +02:00
|
|
|
|
2011-10-19 23:01:15 +02:00
|
|
|
log-basename=mysqld
|
2011-12-12 23:58:40 +01:00
|
|
|
debug-no-sync
|
2011-10-19 23:01:15 +02:00
|
|
|
|
2012-02-23 07:50:11 +01:00
|
|
|
# Retry bind as this may fail on busy server
|
|
|
|
|
port-open-timeout=10
|
|
|
|
|
|
2007-12-12 18:19:24 +01:00
|
|
|
log-bin-trust-function-creators=1
|
|
|
|
|
key_buffer_size= 1M
|
2013-06-26 12:19:02 +03:00
|
|
|
sort_buffer_size= 256K
|
2007-12-12 18:19:24 +01:00
|
|
|
max_heap_table_size= 1M
|
2013-06-05 23:53:35 +03:00
|
|
|
loose-aria-pagecache-buffer-size=8M
|
2007-12-12 18:19:24 +01:00
|
|
|
|
2011-10-04 16:51:39 +02:00
|
|
|
loose-feedback-user-info= mysql-test
|
2015-11-18 10:58:51 +01:00
|
|
|
loose-feedback-debug-startup-interval=20
|
|
|
|
|
loose-feedback-debug-first-interval=60
|
|
|
|
|
loose-feedback-debug-interval=60
|
2010-08-17 11:14:46 +04:00
|
|
|
|
2016-07-26 12:34:04 +02:00
|
|
|
loose-pam-debug
|
|
|
|
|
|
2013-11-04 21:46:16 +01:00
|
|
|
loose-innodb_data_file_path= ibdata1:12M:autoextend
|
2009-08-12 15:48:47 +02:00
|
|
|
loose-innodb_buffer_pool_size= 8M
|
fixes for test failures
and small collateral changes
mysql-test/lib/My/Test.pm:
somehow with "print" we get truncated writes sometimes
mysql-test/suite/perfschema/r/digest_table_full.result:
md5 hashes of statement digests differ, because yacc token codes are different in mariadb
mysql-test/suite/perfschema/r/dml_handler.result:
host table is not ported over yet
mysql-test/suite/perfschema/r/information_schema.result:
host table is not ported over yet
mysql-test/suite/perfschema/r/nesting.result:
this differs, because we don't rewrite general log queries, and multi-statement
packets are logged as a one entry. this result file is identical to what mysql-5.6.5
produces with the --log-raw option.
mysql-test/suite/perfschema/r/relaylog.result:
MariaDB modifies the binlog index file directly, while MySQL 5.6 has a feature "crash-safe binlog index" and modifies a special "crash-safe" shadow copy of the index file and then moves it over. That's why this test shows "NONE" index file writes in MySQL and "MANY" in MariaDB.
mysql-test/suite/perfschema/r/server_init.result:
MariaDB initializes the "manager" resources from the "manager" thread, and starts this thread only when --flush-time is not 0. MySQL 5.6 initializes "manager" resources unconditionally on server startup.
mysql-test/suite/perfschema/r/stage_mdl_global.result:
this differs, because MariaDB disables query cache when query_cache_size=0. MySQL does not
do that, and this causes useless mutex locks and waits.
mysql-test/suite/perfschema/r/statement_digest.result:
md5 hashes of statement digests differ, because yacc token codes are different in mariadb
mysql-test/suite/perfschema/r/statement_digest_consumers.result:
md5 hashes of statement digests differ, because yacc token codes are different in mariadb
mysql-test/suite/perfschema/r/statement_digest_long_query.result:
md5 hashes of statement digests differ, because yacc token codes are different in mariadb
mysql-test/suite/rpl/r/rpl_mixed_drop_create_temp_table.result:
will be updated to match 5.6 when alfranio.correia@oracle.com-20110512172919-c1b5kmum4h52g0ni and anders.song@greatopensource.com-20110105052107-zoab0bsf5a6xxk2y are merged
mysql-test/suite/rpl/r/rpl_non_direct_mixed_mixing_engines.result:
will be updated to match 5.6 when anders.song@greatopensource.com-20110105052107-zoab0bsf5a6xxk2y is merged
2012-09-27 20:09:46 +02:00
|
|
|
loose-innodb_lru_scan_depth= 100
|
2009-08-11 18:35:22 +02:00
|
|
|
loose-innodb_write_io_threads= 2
|
|
|
|
|
loose-innodb_read_io_threads= 2
|
2009-08-12 15:48:47 +02:00
|
|
|
loose-innodb_log_buffer_size= 1M
|
2019-10-28 17:11:10 +02:00
|
|
|
loose-innodb_log_file_size= 10M
|
2013-07-13 09:22:00 +02:00
|
|
|
loose-innodb-stats-persistent= OFF
|
2007-12-12 18:19:24 +01:00
|
|
|
|
2008-03-12 12:35:30 +01:00
|
|
|
slave-net-timeout=120
|
2007-12-19 17:16:22 +01:00
|
|
|
|
2013-06-15 18:32:08 +03:00
|
|
|
# MAINTAINER:
|
|
|
|
|
# the loose- syntax is to make sure the cnf file is also
|
|
|
|
|
# valid when building without the performance schema.
|
|
|
|
|
|
2010-01-11 18:47:27 -07:00
|
|
|
# Run tests with the performance schema instrumentation
|
|
|
|
|
loose-enable-performance-schema
|
2010-09-08 12:01:12 -06:00
|
|
|
# Run tests with a small number of instrumented objects
|
|
|
|
|
# to limit memory consumption with MTR
|
2013-06-15 18:32:08 +03:00
|
|
|
loose-performance-schema-accounts-size=100
|
|
|
|
|
loose-performance-schema-digests-size=200
|
|
|
|
|
loose-performance-schema-hosts-size=100
|
|
|
|
|
loose-performance-schema-users-size=100
|
fixes for test failures
and small collateral changes
mysql-test/lib/My/Test.pm:
somehow with "print" we get truncated writes sometimes
mysql-test/suite/perfschema/r/digest_table_full.result:
md5 hashes of statement digests differ, because yacc token codes are different in mariadb
mysql-test/suite/perfschema/r/dml_handler.result:
host table is not ported over yet
mysql-test/suite/perfschema/r/information_schema.result:
host table is not ported over yet
mysql-test/suite/perfschema/r/nesting.result:
this differs, because we don't rewrite general log queries, and multi-statement
packets are logged as a one entry. this result file is identical to what mysql-5.6.5
produces with the --log-raw option.
mysql-test/suite/perfschema/r/relaylog.result:
MariaDB modifies the binlog index file directly, while MySQL 5.6 has a feature "crash-safe binlog index" and modifies a special "crash-safe" shadow copy of the index file and then moves it over. That's why this test shows "NONE" index file writes in MySQL and "MANY" in MariaDB.
mysql-test/suite/perfschema/r/server_init.result:
MariaDB initializes the "manager" resources from the "manager" thread, and starts this thread only when --flush-time is not 0. MySQL 5.6 initializes "manager" resources unconditionally on server startup.
mysql-test/suite/perfschema/r/stage_mdl_global.result:
this differs, because MariaDB disables query cache when query_cache_size=0. MySQL does not
do that, and this causes useless mutex locks and waits.
mysql-test/suite/perfschema/r/statement_digest.result:
md5 hashes of statement digests differ, because yacc token codes are different in mariadb
mysql-test/suite/perfschema/r/statement_digest_consumers.result:
md5 hashes of statement digests differ, because yacc token codes are different in mariadb
mysql-test/suite/perfschema/r/statement_digest_long_query.result:
md5 hashes of statement digests differ, because yacc token codes are different in mariadb
mysql-test/suite/rpl/r/rpl_mixed_drop_create_temp_table.result:
will be updated to match 5.6 when alfranio.correia@oracle.com-20110512172919-c1b5kmum4h52g0ni and anders.song@greatopensource.com-20110105052107-zoab0bsf5a6xxk2y are merged
mysql-test/suite/rpl/r/rpl_non_direct_mixed_mixing_engines.result:
will be updated to match 5.6 when anders.song@greatopensource.com-20110105052107-zoab0bsf5a6xxk2y is merged
2012-09-27 20:09:46 +02:00
|
|
|
loose-performance-schema-max-mutex-instances=5000
|
|
|
|
|
loose-performance-schema-max-rwlock-instances=5000
|
2013-06-15 18:32:08 +03:00
|
|
|
loose-performance-schema-max-cond-instances=1000
|
|
|
|
|
loose-performance-schema-max-file-instances=10000
|
|
|
|
|
loose-performance-schema-max-socket-instances=1000
|
2010-09-08 12:01:12 -06:00
|
|
|
loose-performance-schema-max-table-instances=500
|
2020-02-15 18:25:57 +01:00
|
|
|
loose-performance-schema-max-table-lock-stat=500
|
|
|
|
|
loose-performance-schema-max-index-stat=5000
|
2010-09-08 12:01:12 -06:00
|
|
|
loose-performance-schema-max-table-handles=1000
|
2020-02-15 18:25:57 +01:00
|
|
|
loose-performance-schema-max-prepared-statements-instances=100
|
|
|
|
|
loose-performance-schema-max-program-instances=5000
|
|
|
|
|
loose-performance-schema-setup-actors-size=100
|
|
|
|
|
loose-performance-schema-setup-objects-size=100
|
2010-01-11 18:47:27 -07:00
|
|
|
|
2013-06-15 18:32:08 +03:00
|
|
|
loose-performance-schema-events-waits-history-size=10
|
|
|
|
|
loose-performance-schema-events-waits-history-long-size=10000
|
|
|
|
|
loose-performance-schema-events-stages-history-size=10
|
fixes for test failures
and small collateral changes
mysql-test/lib/My/Test.pm:
somehow with "print" we get truncated writes sometimes
mysql-test/suite/perfschema/r/digest_table_full.result:
md5 hashes of statement digests differ, because yacc token codes are different in mariadb
mysql-test/suite/perfschema/r/dml_handler.result:
host table is not ported over yet
mysql-test/suite/perfschema/r/information_schema.result:
host table is not ported over yet
mysql-test/suite/perfschema/r/nesting.result:
this differs, because we don't rewrite general log queries, and multi-statement
packets are logged as a one entry. this result file is identical to what mysql-5.6.5
produces with the --log-raw option.
mysql-test/suite/perfschema/r/relaylog.result:
MariaDB modifies the binlog index file directly, while MySQL 5.6 has a feature "crash-safe binlog index" and modifies a special "crash-safe" shadow copy of the index file and then moves it over. That's why this test shows "NONE" index file writes in MySQL and "MANY" in MariaDB.
mysql-test/suite/perfschema/r/server_init.result:
MariaDB initializes the "manager" resources from the "manager" thread, and starts this thread only when --flush-time is not 0. MySQL 5.6 initializes "manager" resources unconditionally on server startup.
mysql-test/suite/perfschema/r/stage_mdl_global.result:
this differs, because MariaDB disables query cache when query_cache_size=0. MySQL does not
do that, and this causes useless mutex locks and waits.
mysql-test/suite/perfschema/r/statement_digest.result:
md5 hashes of statement digests differ, because yacc token codes are different in mariadb
mysql-test/suite/perfschema/r/statement_digest_consumers.result:
md5 hashes of statement digests differ, because yacc token codes are different in mariadb
mysql-test/suite/perfschema/r/statement_digest_long_query.result:
md5 hashes of statement digests differ, because yacc token codes are different in mariadb
mysql-test/suite/rpl/r/rpl_mixed_drop_create_temp_table.result:
will be updated to match 5.6 when alfranio.correia@oracle.com-20110512172919-c1b5kmum4h52g0ni and anders.song@greatopensource.com-20110105052107-zoab0bsf5a6xxk2y are merged
mysql-test/suite/rpl/r/rpl_non_direct_mixed_mixing_engines.result:
will be updated to match 5.6 when anders.song@greatopensource.com-20110105052107-zoab0bsf5a6xxk2y is merged
2012-09-27 20:09:46 +02:00
|
|
|
loose-performance-schema-events-stages-history-long-size=1000
|
2013-06-15 18:32:08 +03:00
|
|
|
loose-performance-schema-events-statements-history-size=10
|
fixes for test failures
and small collateral changes
mysql-test/lib/My/Test.pm:
somehow with "print" we get truncated writes sometimes
mysql-test/suite/perfschema/r/digest_table_full.result:
md5 hashes of statement digests differ, because yacc token codes are different in mariadb
mysql-test/suite/perfschema/r/dml_handler.result:
host table is not ported over yet
mysql-test/suite/perfschema/r/information_schema.result:
host table is not ported over yet
mysql-test/suite/perfschema/r/nesting.result:
this differs, because we don't rewrite general log queries, and multi-statement
packets are logged as a one entry. this result file is identical to what mysql-5.6.5
produces with the --log-raw option.
mysql-test/suite/perfschema/r/relaylog.result:
MariaDB modifies the binlog index file directly, while MySQL 5.6 has a feature "crash-safe binlog index" and modifies a special "crash-safe" shadow copy of the index file and then moves it over. That's why this test shows "NONE" index file writes in MySQL and "MANY" in MariaDB.
mysql-test/suite/perfschema/r/server_init.result:
MariaDB initializes the "manager" resources from the "manager" thread, and starts this thread only when --flush-time is not 0. MySQL 5.6 initializes "manager" resources unconditionally on server startup.
mysql-test/suite/perfschema/r/stage_mdl_global.result:
this differs, because MariaDB disables query cache when query_cache_size=0. MySQL does not
do that, and this causes useless mutex locks and waits.
mysql-test/suite/perfschema/r/statement_digest.result:
md5 hashes of statement digests differ, because yacc token codes are different in mariadb
mysql-test/suite/perfschema/r/statement_digest_consumers.result:
md5 hashes of statement digests differ, because yacc token codes are different in mariadb
mysql-test/suite/perfschema/r/statement_digest_long_query.result:
md5 hashes of statement digests differ, because yacc token codes are different in mariadb
mysql-test/suite/rpl/r/rpl_mixed_drop_create_temp_table.result:
will be updated to match 5.6 when alfranio.correia@oracle.com-20110512172919-c1b5kmum4h52g0ni and anders.song@greatopensource.com-20110105052107-zoab0bsf5a6xxk2y are merged
mysql-test/suite/rpl/r/rpl_non_direct_mixed_mixing_engines.result:
will be updated to match 5.6 when anders.song@greatopensource.com-20110105052107-zoab0bsf5a6xxk2y is merged
2012-09-27 20:09:46 +02:00
|
|
|
loose-performance-schema-events-statements-history-long-size=1000
|
2020-02-15 18:25:57 +01:00
|
|
|
loose-performance-schema-events-transactions-history-size=10
|
|
|
|
|
loose-performance-schema-events-transactions-history-long-size=1000
|
fixes for test failures
and small collateral changes
mysql-test/lib/My/Test.pm:
somehow with "print" we get truncated writes sometimes
mysql-test/suite/perfschema/r/digest_table_full.result:
md5 hashes of statement digests differ, because yacc token codes are different in mariadb
mysql-test/suite/perfschema/r/dml_handler.result:
host table is not ported over yet
mysql-test/suite/perfschema/r/information_schema.result:
host table is not ported over yet
mysql-test/suite/perfschema/r/nesting.result:
this differs, because we don't rewrite general log queries, and multi-statement
packets are logged as a one entry. this result file is identical to what mysql-5.6.5
produces with the --log-raw option.
mysql-test/suite/perfschema/r/relaylog.result:
MariaDB modifies the binlog index file directly, while MySQL 5.6 has a feature "crash-safe binlog index" and modifies a special "crash-safe" shadow copy of the index file and then moves it over. That's why this test shows "NONE" index file writes in MySQL and "MANY" in MariaDB.
mysql-test/suite/perfschema/r/server_init.result:
MariaDB initializes the "manager" resources from the "manager" thread, and starts this thread only when --flush-time is not 0. MySQL 5.6 initializes "manager" resources unconditionally on server startup.
mysql-test/suite/perfschema/r/stage_mdl_global.result:
this differs, because MariaDB disables query cache when query_cache_size=0. MySQL does not
do that, and this causes useless mutex locks and waits.
mysql-test/suite/perfschema/r/statement_digest.result:
md5 hashes of statement digests differ, because yacc token codes are different in mariadb
mysql-test/suite/perfschema/r/statement_digest_consumers.result:
md5 hashes of statement digests differ, because yacc token codes are different in mariadb
mysql-test/suite/perfschema/r/statement_digest_long_query.result:
md5 hashes of statement digests differ, because yacc token codes are different in mariadb
mysql-test/suite/rpl/r/rpl_mixed_drop_create_temp_table.result:
will be updated to match 5.6 when alfranio.correia@oracle.com-20110512172919-c1b5kmum4h52g0ni and anders.song@greatopensource.com-20110105052107-zoab0bsf5a6xxk2y are merged
mysql-test/suite/rpl/r/rpl_non_direct_mixed_mixing_engines.result:
will be updated to match 5.6 when anders.song@greatopensource.com-20110105052107-zoab0bsf5a6xxk2y is merged
2012-09-27 20:09:46 +02:00
|
|
|
loose-performance-schema-max-thread-instances=200
|
2013-06-15 18:32:08 +03:00
|
|
|
loose-performance-schema-session-connect-attrs-size=2048
|
2020-02-15 18:25:57 +01:00
|
|
|
loose-performance-schema-max-metadata-locks=10000
|
2013-06-15 18:32:08 +03:00
|
|
|
|
|
|
|
|
# Enable everything, for maximun code exposure during testing
|
fixes for test failures
and small collateral changes
mysql-test/lib/My/Test.pm:
somehow with "print" we get truncated writes sometimes
mysql-test/suite/perfschema/r/digest_table_full.result:
md5 hashes of statement digests differ, because yacc token codes are different in mariadb
mysql-test/suite/perfschema/r/dml_handler.result:
host table is not ported over yet
mysql-test/suite/perfschema/r/information_schema.result:
host table is not ported over yet
mysql-test/suite/perfschema/r/nesting.result:
this differs, because we don't rewrite general log queries, and multi-statement
packets are logged as a one entry. this result file is identical to what mysql-5.6.5
produces with the --log-raw option.
mysql-test/suite/perfschema/r/relaylog.result:
MariaDB modifies the binlog index file directly, while MySQL 5.6 has a feature "crash-safe binlog index" and modifies a special "crash-safe" shadow copy of the index file and then moves it over. That's why this test shows "NONE" index file writes in MySQL and "MANY" in MariaDB.
mysql-test/suite/perfschema/r/server_init.result:
MariaDB initializes the "manager" resources from the "manager" thread, and starts this thread only when --flush-time is not 0. MySQL 5.6 initializes "manager" resources unconditionally on server startup.
mysql-test/suite/perfschema/r/stage_mdl_global.result:
this differs, because MariaDB disables query cache when query_cache_size=0. MySQL does not
do that, and this causes useless mutex locks and waits.
mysql-test/suite/perfschema/r/statement_digest.result:
md5 hashes of statement digests differ, because yacc token codes are different in mariadb
mysql-test/suite/perfschema/r/statement_digest_consumers.result:
md5 hashes of statement digests differ, because yacc token codes are different in mariadb
mysql-test/suite/perfschema/r/statement_digest_long_query.result:
md5 hashes of statement digests differ, because yacc token codes are different in mariadb
mysql-test/suite/rpl/r/rpl_mixed_drop_create_temp_table.result:
will be updated to match 5.6 when alfranio.correia@oracle.com-20110512172919-c1b5kmum4h52g0ni and anders.song@greatopensource.com-20110105052107-zoab0bsf5a6xxk2y are merged
mysql-test/suite/rpl/r/rpl_non_direct_mixed_mixing_engines.result:
will be updated to match 5.6 when anders.song@greatopensource.com-20110105052107-zoab0bsf5a6xxk2y is merged
2012-09-27 20:09:46 +02:00
|
|
|
|
|
|
|
|
loose-performance-schema-instrument='%=ON'
|
|
|
|
|
|
|
|
|
|
loose-performance-schema-consumer-events-stages-current=ON
|
|
|
|
|
loose-performance-schema-consumer-events-stages-history=ON
|
|
|
|
|
loose-performance-schema-consumer-events-stages-history-long=ON
|
|
|
|
|
loose-performance-schema-consumer-events-statements-current=ON
|
|
|
|
|
loose-performance-schema-consumer-events-statements-history=ON
|
|
|
|
|
loose-performance-schema-consumer-events-statements-history-long=ON
|
2020-02-15 18:25:57 +01:00
|
|
|
loose-performance-schema-consumer-events-transactions-current=ON
|
|
|
|
|
loose-performance-schema-consumer-events-transactions-history=ON
|
|
|
|
|
loose-performance-schema-consumer-events-transactions-history-long=ON
|
fixes for test failures
and small collateral changes
mysql-test/lib/My/Test.pm:
somehow with "print" we get truncated writes sometimes
mysql-test/suite/perfschema/r/digest_table_full.result:
md5 hashes of statement digests differ, because yacc token codes are different in mariadb
mysql-test/suite/perfschema/r/dml_handler.result:
host table is not ported over yet
mysql-test/suite/perfschema/r/information_schema.result:
host table is not ported over yet
mysql-test/suite/perfschema/r/nesting.result:
this differs, because we don't rewrite general log queries, and multi-statement
packets are logged as a one entry. this result file is identical to what mysql-5.6.5
produces with the --log-raw option.
mysql-test/suite/perfschema/r/relaylog.result:
MariaDB modifies the binlog index file directly, while MySQL 5.6 has a feature "crash-safe binlog index" and modifies a special "crash-safe" shadow copy of the index file and then moves it over. That's why this test shows "NONE" index file writes in MySQL and "MANY" in MariaDB.
mysql-test/suite/perfschema/r/server_init.result:
MariaDB initializes the "manager" resources from the "manager" thread, and starts this thread only when --flush-time is not 0. MySQL 5.6 initializes "manager" resources unconditionally on server startup.
mysql-test/suite/perfschema/r/stage_mdl_global.result:
this differs, because MariaDB disables query cache when query_cache_size=0. MySQL does not
do that, and this causes useless mutex locks and waits.
mysql-test/suite/perfschema/r/statement_digest.result:
md5 hashes of statement digests differ, because yacc token codes are different in mariadb
mysql-test/suite/perfschema/r/statement_digest_consumers.result:
md5 hashes of statement digests differ, because yacc token codes are different in mariadb
mysql-test/suite/perfschema/r/statement_digest_long_query.result:
md5 hashes of statement digests differ, because yacc token codes are different in mariadb
mysql-test/suite/rpl/r/rpl_mixed_drop_create_temp_table.result:
will be updated to match 5.6 when alfranio.correia@oracle.com-20110512172919-c1b5kmum4h52g0ni and anders.song@greatopensource.com-20110105052107-zoab0bsf5a6xxk2y are merged
mysql-test/suite/rpl/r/rpl_non_direct_mixed_mixing_engines.result:
will be updated to match 5.6 when anders.song@greatopensource.com-20110105052107-zoab0bsf5a6xxk2y is merged
2012-09-27 20:09:46 +02:00
|
|
|
loose-performance-schema-consumer-events-waits-current=ON
|
|
|
|
|
loose-performance-schema-consumer-events-waits-history=ON
|
|
|
|
|
loose-performance-schema-consumer-events-waits-history-long=ON
|
|
|
|
|
loose-performance-schema-consumer-global-instrumentation=ON
|
|
|
|
|
loose-performance-schema-consumer-thread-instrumentation=ON
|
|
|
|
|
|
Manual merge of patch for Bug#46364 from mysql-next-mr-bugfixing.
Conflicts:
- mysql-test/r/mysqld--help-win.result
- sql/sys_vars.cc
Original revsion (in next-mr-bugfixing):
------------------------------------------------------------
revno: 2971 [merge]
revision-id: alfranio.correia@sun.com-20100121210527-rbuheu5rnsmcakh1
committer: Alfranio Correia <alfranio.correia@sun.com>
branch nick: mysql-next-mr-bugfixing
timestamp: Thu 2010-01-21 21:05:27 +0000
message:
BUG#46364 MyISAM transbuffer problems (NTM problem)
It is well-known that due to concurrency issues, a slave can become
inconsistent when a transaction contains updates to both transaction and
non-transactional tables.
In a nutshell, the current code-base tries to preserve causality among the
statements by writing non-transactional statements to the txn-cache which
is flushed upon commit. However, modifications done to non-transactional
tables on behalf of a transaction become immediately visible to other
connections but may not immediately get into the binary log and therefore
consistency may be broken.
In general, it is impossible to automatically detect causality/dependency
among statements by just analyzing the statements sent to the server. This
happen because dependency may be hidden in the application code and it is
necessary to know a priori all the statements processed in the context of
a transaction such as in a procedure. Moreover, even for the few cases that
we could automatically address in the server, the computation effort
required could make the approach infeasible.
So, in this patch we introduce the option
- "--binlog-direct-non-transactional-updates" that can be used to bypass
the current behavior in order to write directly to binary log statements
that change non-transactional tables.
Besides, it is used to enable the WL#2687 which is disabled by default.
------------------------------------------------------------
revno: 2970.1.1
revision-id: alfranio.correia@sun.com-20100121131034-183r4qdyld7an5a0
parent: alik@sun.com-20100121083914-r9rz2myto3tkdya0
committer: Alfranio Correia <alfranio.correia@sun.com>
branch nick: mysql-next-mr-bugfixing
timestamp: Thu 2010-01-21 13:10:34 +0000
message:
BUG#46364 MyISAM transbuffer problems (NTM problem)
It is well-known that due to concurrency issues, a slave can become
inconsistent when a transaction contains updates to both transaction and
non-transactional tables.
In a nutshell, the current code-base tries to preserve causality among the
statements by writing non-transactional statements to the txn-cache which
is flushed upon commit. However, modifications done to non-transactional
tables on behalf of a transaction become immediately visible to other
connections but may not immediately get into the binary log and therefore
consistency may be broken.
In general, it is impossible to automatically detect causality/dependency
among statements by just analyzing the statements sent to the server. This
happen because dependency may be hidden in the application code and it is
necessary to know a priori all the statements processed in the context of
a transaction such as in a procedure. Moreover, even for the few cases that
we could automatically address in the server, the computation effort
required could make the approach infeasible.
So, in this patch we introduce the option
- "--binlog-direct-non-transactional-updates" that can be used to bypass
the current behavior in order to write directly to binary log statements
that change non-transactional tables.
Besides, it is used to enable the WL#2687 which is disabled by default.
2010-02-02 10:56:42 +03:00
|
|
|
binlog-direct-non-transactional-updates
|
2012-02-23 07:50:11 +01:00
|
|
|
|
2012-04-19 04:02:28 +02:00
|
|
|
default-storage-engine=myisam
|
2018-12-09 13:25:27 +05:30
|
|
|
use_stat_tables=preferably
|
2012-04-19 04:02:28 +02:00
|
|
|
|
2017-04-26 17:55:27 +02:00
|
|
|
loose-ssl-ca=@ENV.MYSQL_TEST_DIR/std_data/cacert.pem
|
|
|
|
|
loose-ssl-cert=@ENV.MYSQL_TEST_DIR/std_data/server-cert.pem
|
|
|
|
|
loose-ssl-key=@ENV.MYSQL_TEST_DIR/std_data/server-key.pem
|
|
|
|
|
|
2012-02-23 07:50:11 +01:00
|
|
|
# here, at the end of [mysqld] group mtr will automatically disable
|
|
|
|
|
# all optional plugins.
|
|
|
|
|
|
|
|
|
|
[embedded]
|
|
|
|
|
# mtr automatically adds [embedded] group at the end and copies [mysqld]
|
|
|
|
|
# and [mysqld.1] groups into it.
|
|
|
|
|
# but we want [server] group to be after [mysqld] (and its copies).
|
|
|
|
|
# create a non-empty [embedded] group here, to force it before [server]
|
|
|
|
|
local-infile
|
|
|
|
|
|
|
|
|
|
[server]
|
|
|
|
|
# Aria is optional, but it must be enabled if it's used for temporary
|
|
|
|
|
# tables. Let's enable it in the [server] group, because this group
|
|
|
|
|
# is read after [mysqld] and [embedded]
|
|
|
|
|
loose-aria
|