Description:
After most recent merge from trunk, test rpl.rpl_slave_load_remove_tmpfile fails. Message written by mysqltest:
**** Slave stopped with wrong error code: 1290 (expected 29, 13) ****
From slave log:
110209 13:11:05 [ERROR] LOAD DATA INFILE in the slave SQL Thread can only read from --slave-load-tmpdir. Please, report a bug.
110209 13:11:05 [ERROR] Slave SQL: Error 'The MySQL server is running with the --slave-load-tmpdir option so it cannot execute this statement' on query. Default database: 'test'. Query: 'LOAD DATA INFILE '../../tmp/SQL_LOAD-2-1-1.data' INTO TABLE `t1` FIELDS TERMINATED BY '\t' ENCLOSED BY '' ESCAPED BY '\\' LINES TERMINATED BY '\n' (`a`, `b`)', Error_code: 1290
110209 13:11:05 [Warning] Slave: The MySQL server is running with the --slave-load-tmpdir option so it cannot execute this statement Error_code: 1290
110209 13:11:05 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'master-bin.000001' position 260
How to repeat:
./mtr --mem rpl.rpl_slave_load_remove_tmpfile.
Seems caused by some recent merge/fix to trunk.
Without --mem it works fine.
This was fixed by Bug #51190, but now appears again.
Suggested fix:
May be circumvented by putting this in the test:
--source include/not_var_link.inc
This won't solve the problem, but skips the test where it doesn't work.
