Readers of the mailing list, when I was writing about recovery in the upcoming Innobase manual, I realized that a logical log used in MySQL in the roll-forward recovery from a backup does not work properly. The problem is that the log does not contain enough information on the snapshot a consistent read in complex SQL statements like INSERT INTO T SELECT * FROM S see of the database. There are also some subtler similar problems in cases where an SQL statement results in an error. Therefore I have to advise you not to rely on a roll-forward recovery from a backup currently with Innobase. A roll-forward may work, but in some cases you may end up with a database which is not identical to the one which was lost. Fixing the problem is not very difficult but we have to discuss with Monty which approach should be taken. It will probably take 2 weeks to fix the problem. Regards, Heikki Tuuri Innobase Oy --------------------------------------------------------------------- Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail <[EMAIL PROTECTED]> To unsubscribe, e-mail <[EMAIL PROTECTED]> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
