| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
LOAD DATA FROM MASTER
LOAD DATA FROM MASTER |
Takes a snapshot of the master and copies it to the slave.
Updates the values of MASTER_LOG_FILE and
MASTER_LOG_POS so that the slave will start replicating from the
correct position. Will honor table and database exclusion rules
specified with replicate-* options.
Use of this statement is subject to the following conditions:
MyISAM tables.
In the future, it is planned to make this statement work with
InnoDB tables and to remove the need for global read lock by using
the non-blocking online backup feature.
If you are loading big tables, you may have to increase the values
of net_read_timeout and net_write_timeout
on both your master and slave.
See SHOW VARIABLES.
Note that LOAD DATA FROM MASTER does NOT copy any
tables from the mysql database. This is to make it easy to have
different users and privileges on the master and the slave.
This statement
requires that the replication account that is used to connect to the master
have RELOAD and SUPER privileges on the master,
SELECT privileges on all master's tables you want to load. All
master's tables on which the user has no SELECT privilege will
be ignored by LOAD DATA FROM MASTER; this is because the
master will hide them to the user: LOAD DATA FROM MASTER calls
SHOW DATABASES to know the master databases to load, but
SHOW DATABASES returns only databases on which the user has
some privilege.
See 13.5.3.1 Retrieving Information about Database, Tables, Columns, and Indexes.
On the slave's side, the user which issues LOAD DATA FROM MASTER should
have grants to drop and create the involved databases and tables.
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |