Under MySQL 3.23, FLUSH LOGS was replicated. Under 4.0.13, this appears to no longer be the case.
Was this intentional? Could it be put back the way it was? We do backups by, at a time of low usage, (1) FLUSH LOGS on the master, (2) Dump the master database, (3) repeat 1 and 2 until there were no updates during the dump. (We've only had to repeat once.) It was useful to know that both the master and the slave had a binlog starting from the time of the dump. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
