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
LOAD TABLE FROM MASTER
is very limited, these statements are deprecated in versions 4.1
of MySQL and above. We will introduce a more advanced technique
(called “online backup”) in a future version. That
technique will have the additional advantage of working with
more storage engines.
For MySQL 5.4 and earlier, the recommended alternative solution
LOAD DATA FROM MASTER or
LOAD TABLE FROM MASTER is using
mysqldump or mysqlhotcopy.
The latter requires Perl and two Perl modules
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
Transfers a copy of the table from the master to the slave. This
statement is implemented mainly debugging
FROM MASTER operations. To use
TABLE, the account used for connecting to the master
server must have the
SUPER privileges on the master
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
tables. The timeout notes for
LOAD DATA FROM
MASTER apply as well.