MySQL 5.1 Reference Manual :: 6 Replication :: 6.3 Replication Notes and Tips :: 6.3.1 Replication Features and Issues :: 6.3.1.9 Replication with MEMORY Table Types
Section Navigation [Toggle]
- 6.3.1 Replication Features and Issues
- 6.3.1.1 Replication and AUTO_INCREMENT
- 6.3.1.2 Replication and Character Sets
- 6.3.1.3 Replication and DIRECTORY Statements
- 6.3.1.4 Replication with Floating Point Values
- 6.3.1.5 Replication and FLUSH
- 6.3.1.6 Replication and System Functions
- 6.3.1.7 Replication during a Master Crash
- 6.3.1.8 Replication during a Master Shutdown
- 6.3.1.9 Replication with MEMORY Table Types
- 6.3.1.10 Replication of the System mysql Database
- 6.3.1.11 Slave Errors during Replication
- 6.3.1.12 Replication during a Slave Shutdown
- 6.3.1.13 Replication and Temporary Tables
- 6.3.1.14 Replication Retries and Timeouts
- 6.3.1.15 Replication and Time zones
- 6.3.1.16 Replication and Transactions
- 6.3.1.17 Replication with More Columns on the Slave
- 6.3.1.18 Replication and Variables
- 6.3.1.19 Replication and Views
When a server shuts down and restarts, its
MEMORY tables become empty. The master
replicates this effect to slaves as follows: The first time that
the master uses each MEMORY table after
startup, it logs an event that notifies the slaves that the
table needs to be emptied by writing a DELETE
statement for that table to the binary log. See
Section 14.7, “The MEMORY (HEAP) Storage Engine”, for more information
about MEMORY tables.
User Comments
Add your own comment.