- Documentation Library
- Table of Contents
- MySQL 6.0 Reference Manual
- MySQL 5.1 Reference Manual
- MySQL 5.0 Reference Manual
- MySQL 3.23/4.0/4.1 Manual
- Table of Contents
- 18.3.1 Replication Features and Issues
- 18.3.1.1 Replication and AUTO_INCREMENT
- 18.3.1.2 Replication and Character Sets
- 18.3.1.3 Replication DIRECTORY Statements
- 18.3.1.4 Replication with Floating-Point Values
- 18.3.1.5 Replication and FLUSH
- 18.3.1.6 Replication and Functions
- 18.3.1.7 Replication and LOAD ... Operations
- 18.3.1.8 Replication During a Master Crash
- 18.3.1.9 Replication During a Master Shutdown
- 18.3.1.10 Replication with MEMORY Tables
- 18.3.1.11 Replication and the Query Optimizer
- 18.3.1.12 Replication and Reserved Words
- 18.3.1.13 Slave Errors during Replication
- 18.3.1.14 Replication during a Slave Shutdown
- 18.3.1.15 Replication and Temporary Tables
- 18.3.1.16 Replication Retries and Timeouts
- 18.3.1.17 Replication and Time Zones
- 18.3.1.18 Replication and Transactions
- 18.3.1.19 Replication and Triggers
- 18.3.1.20 Replication and User Privileges
- 18.3.1.21 Replication and Variables
- 18.3.1.22 Replication and Views
Temporary tables are replicated except in the case where you shut down the slave server (not just the slave threads) and you have replicated temporary tables that are used in updates that have not yet been executed on the slave. If you shut down the slave server, the temporary tables needed by those updates are no longer available when the slave is restarted. To avoid this problem, do not shut down the slave while it has temporary tables open. Instead, use the following procedure:
Issue a
STOP SLAVEstatement.Use
SHOW STATUSto check the value of theSlave_open_temp_tablesvariable.If the value is 0, issue a mysqladmin shutdown command to stop the slave.
If the value is not 0, restart the slave SQL thread with
START SLAVE SQL_THREAD.Repeat the procedure later until the
Slave_open_temp_tablesvariable is 0 and you can stop the slave.
User Comments
Add your own comment.