MySQL Bugs: #55048: How to set binary log size (Incrementl File) as MAX 250MB.

Bug #55048	How to set binary log size (Incrementl File) as MAX 250MB.
Submitted:	7 Jul 2010 9:55	Modified:	7 Jul 2010 10:15
Reporter:	Anil Alpati	Email Updates:
Status:	Not a Bug	Impact on me:	None
Category:	MySQL Server	Severity:	S5 (Performance)
Version:	5.1.45	OS:	Linux
Assigned to:		CPU Architecture:	Any

Description:
How to set binary log size (Incrementl File) limit upto MAX 250MB.

Give the information where can i set-up it.

How to repeat:
To Limit binary log size upto 250MB - not more that

Please, read the manual, http://dev.mysql.com/doc/refman/5.1/en/binary-log.html:

"The server creates a new file in the series each time it starts or flushes the logs. The server also creates a new binary log file automatically after the current log's size reaches max_binlog_size. A binary log file may become larger than max_binlog_size if you are using large transactions because a transaction is written to the file in one piece, never split between files."

Read http://dev.mysql.com/doc/refman/5.1/en/replication-options-binary-log.html#sysvar_max_binl... also.

We're sorry, but the bug system is not the appropriate forum for asking help on using MySQL products. Your problem is not the result of a bug.

Support on using our products is available both free in our forums at http://forums.mysql.com/ and for a reasonable fee direct from our skilled support engineers at http://www.mysql.com/support/

Thanks for information