2004-06-02 12:56:26 -05:00
|
|
|
# Example MySQL config file for small systems.
|
2000-07-31 21:29:14 +02:00
|
|
|
#
|
|
|
|
# This is for a system with little memory (<= 64M) where MySQL is only used
|
2003-10-04 17:41:17 -05:00
|
|
|
# from time to time and it's important that the mysqld daemon
|
2000-07-31 21:29:14 +02:00
|
|
|
# doesn't use much resources.
|
|
|
|
#
|
2010-11-18 18:02:37 +02:00
|
|
|
# MySQL programs look for option files in a set of
|
|
|
|
# locations which depend on the deployment platform.
|
|
|
|
# You can copy this option file to one of those
|
|
|
|
# locations. For information about these locations, see:
|
|
|
|
# http://dev.mysql.com/doc/mysql/en/option-files.html
|
2000-07-31 21:29:14 +02:00
|
|
|
#
|
2004-06-02 12:56:26 -05:00
|
|
|
# In this file, you can use all long options that a program supports.
|
2003-12-01 12:56:29 -06:00
|
|
|
# If you want to know which options a program supports, run the program
|
2004-06-02 12:56:26 -05:00
|
|
|
# with the "--help" option.
|
2000-07-31 21:29:14 +02:00
|
|
|
|
|
|
|
# The following options will be passed to all MySQL clients
|
|
|
|
[client]
|
|
|
|
#password = your_password
|
|
|
|
port = @MYSQL_TCP_PORT@
|
|
|
|
socket = @MYSQL_UNIX_ADDR@
|
|
|
|
|
|
|
|
# Here follows entries for some specific programs
|
|
|
|
|
|
|
|
# The MySQL server
|
|
|
|
[mysqld]
|
|
|
|
port = @MYSQL_TCP_PORT@
|
|
|
|
socket = @MYSQL_UNIX_ADDR@
|
2010-03-03 22:22:02 +03:00
|
|
|
skip-external-locking
|
2009-03-31 11:54:48 +02:00
|
|
|
key_buffer_size = 16K
|
2003-04-23 01:51:28 +02:00
|
|
|
max_allowed_packet = 1M
|
2009-03-31 16:04:01 +02:00
|
|
|
table_open_cache = 4
|
2003-04-23 01:51:28 +02:00
|
|
|
sort_buffer_size = 64K
|
2004-05-10 17:37:38 +03:00
|
|
|
read_buffer_size = 256K
|
|
|
|
read_rnd_buffer_size = 256K
|
2003-04-23 01:51:28 +02:00
|
|
|
net_buffer_length = 2K
|
2008-12-28 07:57:09 +01:00
|
|
|
thread_stack = 128K
|
2003-04-15 17:34:56 +02:00
|
|
|
|
|
|
|
# Don't listen on a TCP/IP port at all. This can be a security enhancement,
|
|
|
|
# if all processes that need to connect to mysqld run on the same host.
|
|
|
|
# All interaction with mysqld must be made via Unix sockets or named pipes.
|
|
|
|
# Note that using this option without enabling named pipes on Windows
|
2003-04-23 01:51:28 +02:00
|
|
|
# (using the "enable-named-pipe" option) will render mysqld useless!
|
2003-04-15 17:34:56 +02:00
|
|
|
#
|
|
|
|
#skip-networking
|
2000-12-07 14:08:48 +02:00
|
|
|
server-id = 1
|
2000-07-31 21:29:14 +02:00
|
|
|
|
2001-02-21 14:33:52 +02:00
|
|
|
# Uncomment the following if you want to log updates
|
2005-01-11 00:16:07 +01:00
|
|
|
#log-bin=mysql-bin
|
2001-02-21 14:33:52 +02:00
|
|
|
|
2008-10-03 15:24:19 +03:00
|
|
|
# binary logging format - mixed recommended
|
|
|
|
#binlog_format=mixed
|
|
|
|
|
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
|
|
|
# Causes updates to non-transactional engines using statement format to be
|
|
|
|
# written directly to binary log. Before using this option make sure that
|
|
|
|
# there are no dependencies between transactional and non-transactional
|
|
|
|
# tables such as in the statement INSERT INTO t_myisam SELECT * FROM
|
|
|
|
# t_innodb; otherwise, slaves may diverge from the master.
|
|
|
|
#binlog_direct_non_transactional_updates=TRUE
|
|
|
|
|
2002-07-12 20:00:15 +03:00
|
|
|
# Uncomment the following if you are using InnoDB tables
|
2010-11-18 18:02:37 +02:00
|
|
|
#innodb_data_home_dir = @localstatedir@
|
2002-07-12 20:00:15 +03:00
|
|
|
#innodb_data_file_path = ibdata1:10M:autoextend
|
2010-11-18 18:02:37 +02:00
|
|
|
#innodb_log_group_home_dir = @localstatedir@
|
2002-07-12 20:00:15 +03:00
|
|
|
# You can set .._buffer_pool_size up to 50 - 80 %
|
|
|
|
# of RAM but beware of setting memory usage too high
|
2003-04-23 01:51:28 +02:00
|
|
|
#innodb_buffer_pool_size = 16M
|
|
|
|
#innodb_additional_mem_pool_size = 2M
|
2002-07-12 20:00:15 +03:00
|
|
|
# Set .._log_file_size to 25 % of buffer pool size
|
2003-04-23 01:51:28 +02:00
|
|
|
#innodb_log_file_size = 5M
|
|
|
|
#innodb_log_buffer_size = 8M
|
|
|
|
#innodb_flush_log_at_trx_commit = 1
|
|
|
|
#innodb_lock_wait_timeout = 50
|
2000-07-31 21:29:14 +02:00
|
|
|
|
|
|
|
[mysqldump]
|
|
|
|
quick
|
2003-04-23 01:51:28 +02:00
|
|
|
max_allowed_packet = 16M
|
2000-07-31 21:29:14 +02:00
|
|
|
|
|
|
|
[mysql]
|
|
|
|
no-auto-rehash
|
2001-02-15 03:43:14 +02:00
|
|
|
# Remove the next comment character if you are not familiar with SQL
|
|
|
|
#safe-updates
|
2000-07-31 21:29:14 +02:00
|
|
|
|
|
|
|
[myisamchk]
|
2009-03-31 11:54:48 +02:00
|
|
|
key_buffer_size = 8M
|
2003-04-23 01:51:28 +02:00
|
|
|
sort_buffer_size = 8M
|
2000-11-20 02:57:02 +02:00
|
|
|
|
|
|
|
[mysqlhotcopy]
|
|
|
|
interactive-timeout
|