Bug #7723 Multi-Table Updates *not* Replicated in Presence of replicate-ignore-table

• Submitted: 7 Jan 2005 0:58
• Modified: 7 Jan 2005 10:09
• Reporter: Jeremy Cole (Basic Quality Contributor) (OCA)
• Status: Duplicate
• Category: MySQL Server
• Severity: S3 (Non-critical)
• Version: 4.0.19 - 4.0.23?
• OS: Any (All)
• CPU Architecture: Any

[7 Jan 2005 0:58] Jeremy Cole

Description:
This seems to have been broken by guilhem in 4.0.19 @ 1.776.1.1.

It seems like the fix for Bug #3461 (http://bugs.mysql.com/3461) caused this bug.

Multi-table UPDATEs are not replicated if the slave has a replicate-ignore-table line set.  It seems that replicate-ignore-table causes all multi-table updates to be ignored.

The changes do get written to the binary log, but the slave never executes them.

How to repeat:
Have a working replication setup.

Add to SLAVE's my.cnf:

replicate-ignore-table=foo.bar

Execute on master:

drop table if exists s, t;
create table t (a int, b int);
create table s (a int, b int);
insert into t (a, b) values (1, 1), (2, 2), (3, 3);
insert into s (a, b) values (1, 9), (2, 8), (3, 7);

update t,s set t.b=s.b where t.a=s.a and t.a=2;

Check for change propagation:

On master:

mysql> select * from t where a=2 \G
*************************** 1. row ***************************
a: 2
b: 8

On slave:

mysql> select * from t where a=2 \G
*************************** 1. row ***************************
a: 2
b: 2

[7 Jan 2005 10:09] Guilhem Bichot

Hi Jeremy!
Well there have been many bugs around multi-delete UPDATE/DELETE, and some still remain, for example BUG#7011 (to be fixed), 3989 (fixed).
I believe that my fix you're pointing to was a conceptually right fix, but which made some other things later fail, because the other things were buggy. That is, we discovered later that the multi-table UPDATE does NOT set table->updating properly. As my fix modified the behaviour of tables_ok() towards table->updating, the bug moved from multi-DELETE to multi-UPDATE...
I think yours is BUG#7011, for which Antony has submitted a patch - I'm marking it a duplicate of 7011 for now.

[7 Jan 2005 17:41] Jeremy Cole

Can I get the patch for this bug?

Isn't this a "critical" bug for a stable release?  Will there be a new release made?