Comment 10 for bug 1037711

Revision history for this message
Elena Stepanova (elenst) wrote :

Hi,

Yes, I tried the steps you suggested on 5.3.2 => 5.5.25 Linux binary tarballs, both x86_64 and i686, with no luck.

In the archive you attached, MASTER binary logs are empty.
At the same time, SHOW SLAVE STATUS output you quoted points at a master binary log 000001 pos 934, but there is no such position in MASTER/slave-bin.000001.
So, where do the changes to the slave come from?

Also, lets reconcilie our algorithms to reproduce, just to be sure.

Do I understand correctly that the following set of commands executed on MASTER (5.2.5 or 5.3.2) makes your SLAVE (5.5.25) crash?
(It is the same set that you previously suggested, I only added the schema and table creation).

create database if not exists DB;
drop table if exists DB.a;
create table DB.a (i int) engine=MyISAM;
insert into DB.a values (1);
insert into DB.a values (2);
insert into DB.a values (3);
set @ant=4;
insert into DB.a values (@ant);

If it does crash your slave, please send your my.cnf (or whatever configuration files and/or command-line options you use) for both master and slave.

If it does not crash your slave, could you please point out at a difference between these steps and the way you reproduce the issue?

Thank you.