I am using MySQL V4.0.2alpha and I have set MAX_BINLOG_SIZE to 2M in order to not have to run a CRON job or something similar to do a "FLUSH LOGS" intermittently. This should cause the binary log file to be rotated after it has reached 2M according to the documentation. This hasn't been happening as I have binary log files that have reached 240M. It is rotating them but definitely not always at 2M. From what I can work out it seems to rotate the log after it has been idle for a little while and it has an SQL statement that should be written to the binary log. I have been performing load tests on a replicated MySQL database by inserting about 500,000 records into an InnoDB table and the binary log files do not get rotated until after my last insert statement has completed and the database has been idle for a period of time (I have not tested how long it takes) and then I go to do another insert. Is this a 4.0.2alpha feature and is fixed in later versions or is the way it was meant to work in which case the documentation might need a little re-wording.
Regards, Michael Ryan __________________________________________________ Do You Yahoo!? Everything you'll ever need on one web page from News and Sport to Email and Music Charts http://uk.my.yahoo.com --------------------------------------------------------------------- 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
