I'm running MySQL 4.0.14 on Mac OS X 10.2.6 on a development server. We have around 60 tables on the development server and the production servers. 18 tables that exist on the production server are replicated to our development server. We use the replicate-wild-do-table config option to tell it which tables to replicate from the master (production server) to the slave (dev server).

Somehow a REPAIR statement on one of the replicated tables failed on the slave recently. It left the .TMD temporary table file, and the .MYD data file disappeared altogether. I did STOP SLAVE; RESET SLAVE; LOAD DATA FROM MASTER; and it reloaded the 18 replicated tables from the production server. However, it also wiped out the other 44 tables that existed on the dev server.

I looked at the manual page for the LOAD DATA FROM MASTER command (http://www.mysql.com/doc/en/LOAD_DATA_FROM_MASTER.html), and in the first paragraph it states: "Will honor table and database exclusion rules specified with replicate-* options." So, why would it not honor my replicate-wild-do-table configuration and ONLY load those tables? Why would it wipe out everything in the database before doing reloading the replicated tables?

Gabriel Ricard
iMaxSales.net


-- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]



Reply via email to