Bug #20189 replication fails on cross-database queries
Submitted: 1 Jun 2006 8:34 Modified: 20 Jun 2006 15:45
Reporter: F R Email Updates:
Status: Not a Bug Impact on me:
None 
Category:MySQL Server: Replication Severity:S3 (Non-critical)
Version:4.0.20 OS:Linux (Redhat ES 3)
Assigned to: CPU Architecture:Any

[1 Jun 2006 8:34] F R
Description:
Let's assume 2 databases: db and replicated_db.
Let's also assume that a table t is created in database db and replicated in  replicated_db.
Let's connect a mysql client to replicated_db.
Let's execute the following query: insert into db.t values(...).
Let's check that the new record is inserted in db: use db; select * from t;
Unfortunately, it does appear in replicated_db.t: use replicated_db; select * from t;
A "create table" statement has also the same behaviour.

How to repeat:
cf above

Suggested fix:
Either this is a bug or these cross-db statements should be forbidden.
[1 Jun 2006 19:40] Valeriy Kravchuk
Thank you for a problem report. Please, send your my.cnf file content.
[2 Jun 2006 7:45] F R
# Example mysql config file for medium systems.
#
# This is for a system with little memory (32M - 64M) where MySQL plays
# an important part, or systems up to 128M where MySQL is used together with
# other programs (such as a web server)
#
# You can copy this file to
# /etc/my.cnf to set global options,
# mysql-data-dir/my.cnf to set server-specific options (in this
# installation this directory is /usr/local/mysql/data) or
# ~/.my.cnf to set user-specific options.
#
# One can in this file use all long options that the program supports.
# If you want to know which options a program support, run the program
# with --help option.

# The following options will be passed to all MySQL clients
[client]
#password	= your_password
port		= 3306
socket		= /tmp/mysql.sock

# Here follows entries for some specific programs

# The MySQL server
[mysqld]
port		= 3306
socket		= /tmp/mysql.sock
skip-locking
key_buffer = 16M
max_allowed_packet = 1M
table_cache = 64
sort_buffer_size = 512K
net_buffer_length = 8K
myisam_sort_buffer_size = 8M

# 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
# (via the "enable-named-pipe" option) will render mysqld useless!
# 
#skip-networking

# Replication Master Server (default)
# binary logging is required for replication
#log-bin

# required unique id between 1 and 2^32 - 1
# defaults to 1 if master-host is not set
# but will not function as a master if omitted
#server-id	= 1

# Replication Slave (comment out master section to use this)
#
# To configure this host as a replication slave, you can choose between
# two methods :
#
# 1) Use the CHANGE MASTER TO command (fully described in our manual) -
#    the syntax is:
#
#    CHANGE MASTER TO MASTER_HOST=<host>, MASTER_PORT=<port>,
#    MASTER_USER=<user>, MASTER_PASSWORD=<password> ;
#
#    where you replace <host>, <user>, <password> by quoted strings and
#    <port> by the master's port number (3306 by default).
#
#    Example:
#
#    CHANGE MASTER TO MASTER_HOST='125.564.12.1', MASTER_PORT=3306,
#    MASTER_USER='joe', MASTER_PASSWORD='secret';
#
# OR
#
# 2) Set the variables below. However, in case you choose this method, then
#    start replication for the first time (even unsuccessfully, for example
#    if you mistyped the password in master-password and the slave fails to
#    connect), the slave will create a master.info file, and any later
#    change in this file to the variables' values below will be ignored and
#    overridden by the content of the master.info file, unless you shutdown
#    the slave server, delete master.info and restart the slaver server.
#    For that reason, you may want to leave the lines below untouched
#    (commented) and instead use CHANGE MASTER TO (see above)
#
# required unique id between 2 and 2^32 - 1
# (and different from the master)
# defaults to 2 if master-host is set
# but will not function as a slave if omitted
server-id       = 3
#
# The replication master for this slave - required
master-host     =   dfe-serv-1
#
# The username the slave will use for authentication when connecting
# to the master - required
master-user     =   sitar
#
# The password the slave will authenticate with when connecting to
# the master - required
master-password =   sitar
#
# The port the master is listening on.
# optional - defaults to 3306
#master-port     =  <port>
#
#The number of seconds that the slave thread sleeps before trying to reconnect to the master in case the master goes down or the connection is lost. 
master-connect-retry=1
#
# To rotate the relay log automatically
max-relay-log-size=5
# 
# Database to replicate
binlog-do-db=security
replicate-do-db=security
binlog-do-db=replicated_acg
replicate-do-db=replicated_acg
flush
#
# To be used on slave servers. Usually you can should the default setting of 0, to prevent infinite loops in circular replication
#replicate-same-server-id=0

# binary logging - not required for slaves, but recommended
log-bin

# Point the following paths to different dedicated disks
#tmpdir		= /tmp/		
#log-update 	= /path-to-dedicated-directory/hostname

# Uncomment the following if you are using BDB tables
#bdb_cache_size = 4M
#bdb_max_lock = 10000

# Uncomment the following if you are using InnoDB tables
innodb_data_home_dir = /usr/local/mysql/data/innoDbData
innodb_data_file_path = ibdata1:10M:autoextend
innodb_log_group_home_dir = /usr/local/mysql/data/innoDbData
innodb_log_arch_dir = /usr/local/mysql/data/innoDbData
# You can set .._buffer_pool_size up to 50 - 80 %
# of RAM but beware of setting memory usage too high
innodb_buffer_pool_size = 16M
innodb_additional_mem_pool_size = 2M
# Set .._log_file_size to 25 % of buffer pool size
innodb_log_file_size = 5M
innodb_log_buffer_size = 8M
innodb_flush_log_at_trx_commit = 1
innodb_lock_wait_timeout = 50

[mysqldump]
quick
max_allowed_packet = 16M

[mysql]
no-auto-rehash
# Remove the next comment character if you are not familiar with SQL
#safe-updates

[isamchk]
key_buffer = 20M
sort_buffer_size = 20M
read_buffer = 2M
write_buffer = 2M

[myisamchk]
key_buffer = 20M
sort_buffer_size = 20M
read_buffer = 2M
write_buffer = 2M

[mysqlhotcopy]
interactive-timeout
[20 Jun 2006 15:45] Valeriy Kravchuk
This is not a bug, according to the manual (http://dev.mysql.com/doc/refman/4.1/en/replication-options.html):

"--replicate-do-db=db_name

Tell the slave to restrict replication to statements where the default database (that is, the one selected by USE) is db_name. To specify more than one database, use this option multiple times, once for each database. Note that this does not replicate cross-database statements such as UPDATE some_db.some_table SET foo='bar' while having selected a different database or no database.

..."