Daniel Kerr wrote:
> I recently noticed replication had stopped between two of our
> MySQL-3.23.27-beta servers in a master/slave relationship. The slave
> aborted replication because of a 'create table' on a temporary table that
> already existed. This table had infact been dropped on the master prior to
> being recreated but the slave hadn't received the drop table message.
That is a bug, DROP TABLE does not get logged if the table is temporary.
However, there is a bigger problem - replication of temporary tables is
currently broken. If you are not doing INSERT INTO .. SELECT FROM tmp_table, a
viable workaround would be to execute SET SQL_LOG_BIN = 0 before CREATE
TEMPORARY TABLE - you must have process priv for this. We will be fixing temp
tables replication shortly...
BTW, mysqlbinlog is the proper (although not yet documented) way to examine the
MySQL Development Team
__ ___ ___ ____ __
/ |/ /_ __/ __/ __ \/ / Sasha Pachev <sasha@stripped>
/ /|_/ / // /\ \/ /_/ / /__ MySQL AB, http://www.mysql.com/
/_/ /_/\_, /___/\___\_\___/ Provo, Utah, USA