Replication and Binary Logging Options and Variables Enabling this variable causes the source to verify events read from the binary log by examining checksums, and to stop with an error in the event of a mismatch.  master_verify_checksum  is disabled by default; in this case, the source uses the event length from the binary log to verify events, so that only complete events are read from the binary log. If a 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  error. The minimum value is 4096. The maximum possible value is 16EiB (exbibytes). The maximum recommended value is 4GB; this is due to the fact that MySQL currently cannot work with binary log positions greater than 4GB. The value must be a multiple of 4096. max_binlog_cache_size  sets the size for the transaction cache only; the upper limit for the statement cache is governed by the  max_binlog_stmt_cache_size  system variable. The visibility to sessions of  max_binlog_cache_size  matches that of the  binlog_cache_size system variable; in other words, changing its value affects only new sessions that are started after the value is changed. 3566 • max_binlog_size • max_binlog_cache_size Default Value OFF Command-Line Format --max-binlog-cache-size=# System Variable max_binlog_cache_size Scope Global Dynamic Yes SET_VAR  Hint Applies No Type Integer Default Value 18446744073709547520 Minimum Value 4096 Maximum Value 18446744073709547520 Block Size 4096 Command-Line Format --max-binlog-size=# System Variable max_binlog_size Scope Global Dynamic Yes SET_VAR  Hint Applies No Type Integer Default Value 1073741824 Minimum Value 4096 Maximum Value 1073741824