MARK CALLAGHAN wrote:
On Wed, Oct 7, 2009 at 1:45 PM, Monty Taylor <[email protected]> wrote:
Brian Aker wrote:
Hi!
Should "DROP TABLE IF EXISTS" end up in the replication log even if the
table did not exist on the master?
I do not believe it should. The replication log in Drizzle has been
described to me as being a record of changes made to the master, rather
than being a record of requests made of the master.
If it is a record of changes made, then what should be logged here is
any changes in the state of the master as the result of this statement.
If the table did not exist, then no changes would have been made, and
therefore nothing should go in to the log.
Monty,
If by doing this you are committed to closing the race conditions that
make some actions (including DDL) non-atomic and introduce differences
between master and slave, then I won't mind.
Hi Mark!
Could you elaborate some more please? I'm not intimately familiar with
the race conditions. Can you point me to a MySQL bug report or a piece
of the code we should look at? Is this related to MyISAM/HEAP and not
InnoDB or is it related to all engines? Is the race condition related
to the MySQL binlog? Is it related to the XA code in MySQL?
Any information would be appreciated! We're committed to closing *any*
race conditions that make actions non-atomic. We just need to know
where they are :)
Cheers!
Jay
_______________________________________________
Mailing list: https://launchpad.net/~drizzle-discuss
Post to : [email protected]
Unsubscribe : https://launchpad.net/~drizzle-discuss
More help : https://help.launchpad.net/ListHelp
