- 12.5.2 SQL Statements for Controlling Slave Servers
- 12.5.2.1 CHANGE MASTER TO Syntax
- 12.5.2.2 LOAD DATA FROM MASTER Syntax
- 12.5.2.3 LOAD TABLE tbl_name FROM MASTER Syntax
- 12.5.2.4 MASTER_POS_WAIT() Syntax
- 12.5.2.5 RESET SLAVE Syntax
- 12.5.2.6 SET GLOBAL sql_slave_skip_counter Syntax
- 12.5.2.7 START SLAVE Syntax
- 12.5.2.8 STOP SLAVE Syntax
LOAD TABLE tbl_name FROM MASTER
This feature is deprecated and should be avoided. It is subject to removal in a future version of MySQL.
Since the current implementation of LOAD DATA FROM
MASTER and LOAD TABLE FROM MASTER
is very limited, these statements are deprecated as of MySQL 4.1
and removed in MySQL 5.5.
The recommended alternative solution to using LOAD DATA
FROM MASTER or LOAD TABLE FROM
MASTER is using mysqldump or
mysqlhotcopy. The latter requires Perl and
two Perl modules (DBI and
DBD:mysql) and works for
MyISAM and ARCHIVE tables
only. With mysqldump, you can create SQL
dumps on the master and pipe (or copy) these to a
mysql client on the slave. This has the
advantage of working for all storage engines, but can be quite
slow, since it works using
SELECT.
Transfers a copy of the table from the master to the slave. This
statement is implemented mainly debugging LOAD DATA
FROM MASTER operations. To use LOAD
TABLE, the account used for connecting to the master
server must have the RELOAD and
SUPER privileges on the master
and the SELECT privilege for the
master table to load. On the slave side, the user that issues
LOAD TABLE FROM MASTER must have privileges
for dropping and creating the table.
The conditions for LOAD DATA FROM MASTER
apply here as well. For example, LOAD TABLE FROM
MASTER works only for MyISAM
tables. The timeout notes for LOAD DATA FROM
MASTER apply as well.
User Comments
the the big bold red comment. In my experience:
Works ok from 4.x to 4.x and from 5.0.x to 5.0.x. But will not work at all if you load a table from 4 to 5. It will just create an empty table.
Add your own comment.