MySQL Bugs: #8297: non-replicated tables are written to the general query log on slave

Bug #8297	non-replicated tables are written to the general query log on slave
Submitted:	3 Feb 2005 17:57	Modified:	7 Mar 2005 21:39
Reporter:	Victoria Reznichenko	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Server: Replication	Severity:	S3 (Non-critical)
Version:	4.1.10	OS:	Linux (Linux)
Assigned to:	Lars Thalmann	CPU Architecture:	Any

Description:
Statements that should not be replicated according replicate-* rules are written to the slave's general log.

How to repeat:
1. set up relication with --replicate-wild-do-table=test.t% and --log options on slave.
2. create 3 tables on the master: 
use test;
create table tt1(id int); 
create table a(id int);
create table tt2(id int);
3. Check on the slave that tables were replicated properly
4. Look into slave's general log: you can see 3 create table statements.

This has now been pushed into 4.1 tree and will most likely be included 
in the next 4.1.11 release.

This fix introduced a new semantics of the general log (filtered queries are 
no longer visible in the general log).  This should be documented in the 
"functionality added or changed" section of the manual.

ChangeSet@1.2165.11.1, 2005-02-17 00:28:04+01:00, lars@mysql.com
  BUG#8297: If query is filtered on slave, do not put it in general log.

Noted in 4.1.11 changelog.