Oracle 5.0 Reference Manual page 1492

Replication and Binary Logging Options and Variables
Variable Scope
Dynamic Variable
If a multiple-statement transaction requires more than this many bytes of memory, the
server generates a
Multi-statement transaction required more than
'max_binlog_cache_size' bytes of storage
maximum and default values are 4GB on 32-bit platforms and 16EB (exabytes) on 64-bit platforms.
The maximum recommended value on 64-bit platforms is 4GB; this is due to the fact that MySQL
currently cannot work with binary log positions greater than 4GB.
In MySQL 5.0, a change in
sessions.
•
max_binlog_size
Command-Line Format
Option-File Format
Option Sets Variable
Variable Name
Variable Scope
Dynamic Variable
If a write to the binary log causes the current log file size to exceed the value of this variable, the
server rotates the binary logs (closes the current file and opens the next one). The minimum value is
4096 bytes. The maximum and default value is 1GB.
A transaction is written in one chunk to the binary log, so it is never split between several
binary logs. Therefore, if you have big transactions, you might see binary log files larger than
max_binlog_size
If
max_relay_log_size
as well.
• [1472]
sync_binlog
Version Introduced
Command-Line Format
Option-File Format
Option Sets Variable
Variable Name
Variable Scope
Dynamic Variable
Global
Yes
max_binlog_cache_size
[1472]
--max_binlog_size=#
max_binlog_size
Yes,
max_binlog_size
max_binlog_size
Global
Yes
Permitted Values
Type
numeric
Default
1073741824
Range
4096 .. 1073741824
[1472].
[470] is 0, the value of
5.0.1
--sync-binlog=#
sync_binlog
Yes,
sync_binlog
sync_binlog
Global
Yes
Permitted Values
Platform
32
Bit Size
Type
numeric
Default
0
1472
error. The minimum value is 4096. The
[1471] takes immediate effect for all active
[1472]
[1472]
max_binlog_size
[1472]
applies to relay logs