# POLITICALLY CORRECT ANSWER

You cannot do MySQL Replication from a New Master to an Old Slave

I have written many posts about this:

- `Nov 26, 2012` : https://dba.stackexchange.com/questions/29322/replicate-mysql-5-0-master-to-5-5-slave/29324#29324
- `Feb 08, 2012` : https://dba.stackexchange.com/questions/12509/will-replication-from-5-5-20-to-5-0-xx-server-work/12511#12511
- `Dec 22, 2011` : https://dba.stackexchange.com/questions/9591/what-does-the-base64-binlog-statements-in-mysqlbinlog-output-mean/9621#9621
- `Feb 04, 2011` : https://dba.stackexchange.com/questions/12530/mysql-master-binlog-corruption/12531#12531

In addition, there is the likelihood of dealing with the internal BINLOG magic number being in the wrong place and replication going senile. Here are my posts on the BINLOG magic number:

- `Oct 28, 2012` : https://dba.stackexchange.com/questions/27749/binlog-has-bad-magic-number/27756#27756
- `Dec 26, 2011` : https://dba.stackexchange.com/questions/9736/mysql-emits-binlog-rows-even-though-binlog-format-statement/9738#9738

Since there is nothing in the meantime you can do, please upgrade your Slave to MySQL 5.5

# ALTERNATE PERSPECTIVE

In all fairness, [**@ChristopherSchultz**][1] is correct in that you can implement it. I just yell and scream "RISK !!!" to be more cautious because of the BINLOG magic number's place in the MySQL Replication Universe.


 [1]: https://dba.stackexchange.com/users/19098/christopher-schultz