on the
slave. this much i know from slaves dying then not restarting due to
the missing temporary table. my current problem is my slaves are
creating myisam temporary tables on disk and alot of them. which
eventualy results in mysqld no longer being able to open any files
with
ERROR: 1 Can't
There is a setting in your my.cnf which specifies the threshold at
which temporary tables will be put to disk instead of being held in
RAM. This has to be a dynamic decision as the system has to consider
available RAM and the size of any given temporary table.. under
normal circumstances, the
Michael Dykman wrote on Fri, Sep 21, 2007 at 01:37:57PM -0400:
There is a setting in your my.cnf which specifies the threshold at
which temporary tables will be put to disk instead of being held in
RAM. This has to be a dynamic decision as the system has to consider
available RAM and the size
according to
http://dev.mysql.com/doc/refman/4.1/en/internal-temporary-tables.html
temporary tables can sometimes be written to disk as myisam. in
replication are these myisam temp tables sent to the slaves as myisam
tables or in memory tables?
--
MySQL General Mailing List
For list
Temporary tables only exist for the length of time that the connection
that created them remains connected and are only visible to that
connection. There is no reason to replicate these to a slave at all,
as no client connecting to that slave would ever be able to see them.
- michael dykman
Michael explained it well, but just to say it a different way, the
temporary table is created as an intermediate step in the table, and is
implicit, not explicit. So it's not sent to the slave -- the query is
sent to the slave, and if the query optimizer makes the same decisions
on the slave
