Bug #18607 LOAD DATA FROM MASTER fails because of INFORMATION_SCHEMA database

Description:
In 5.0 if you try to use LOAD DATA FROM MASTER, it tries to load INFORMATION_SCHEMA database as well and fails:

mysql> load data from master;
Query OK, 0 rows affected, 1 warning (0.04 sec)

mysql> show warnings;
+-------+------+-------------------------------------------------------------+
| Level | Code | Message                                                     |
+-------+------+-------------------------------------------------------------+
| Error | 1007 | Can't create database 'information_schema'; database exists |
+-------+------+-------------------------------------------------------------+
1 row in set (0.01 sec)

If I add replicate-ignore-db=information_schema, it works fine.

INFORMATION_SCHEMA is a system database and I think it should not be copied at all during LOAD DATA FROM MASTER.

How to repeat:
1. setup replication between 5.0.X servers
2. run LOAD DATA FROM MASTER on the slave.
3. Check warnings.

I am having the same problem. However, adding "replicate-ignore-db=information_schema" to  my.cnf doesn't seem to help. 
Executing the "show slave status" command shows that there is now replication database defined. (Replicate_Do_DB: )

Operating System: CentOS 4.3
Slave: MySQL 5.0.19 community edition
Master: MySQL 5.0.18 pro

Sorry, that was supposed to be "NO replication database defined"

A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/commits/5330

Looks ok to me(after seconds review).

Fixed in 5.0.22 and 5.1.10.

Documented in 5.0 and 5.1 changelog.

<literal>LOAD DATA FROM MASTER</literal> would fail when trying to load the <literal>INFORMATION_SCHEMA</literal> database from the master, because the <literal>INFORMATION_SCHEMA</literal> system database would already exist on the slave. (Bug #18607)