Replication and Binary Logging Options and Variables SET_VAR  Hint Applies ( ≥  8.0.14) No Type Integer Default Value 8192 Minimum Value 256 Maximum Value (64-bit platforms) 18446744073709551615 Maximum Value (32-bit platforms) 4294967295 When row-based binary logging is used, this setting is a soft limit on the maximum size of a row-based binary log event, in bytes. Where possible, rows stored in the binary log are grouped into events with a size not exceeding the value of this setting. If an event cannot be split, the maximum size can be exceeded. The value must be (or else gets rounded down to) a multiple of 256. The default is 8192 bytes. This global system variable is read-only and can be set only at server startup. Its value can therefore only be modified by using the  PERSIST_ONLY  keyword or the  @@persist_only  qualifier with the  SET statement. • binlog_row_image Command-Line Format --binlog-row-image=image_type System Variable binlog_row_image Scope Global, Session Dynamic Yes SET_VAR  Hint Applies No Type Enumeration Default Value full Valid Values full  (Log all columns) minimal  (Log only changed columns, and columns needed to identify rows) noblob  (Log all columns, except for unneeded BLOB and TEXT columns) For MySQL row-based replication, this variable determines how row images are written to the binary log. Setting the session value of this system variable is a restricted operation. The session user must have privileges sufficient to set restricted session variables. See Section 5.1.9.1, “System Variable Privileges” . In MySQL row-based replication, each row change event contains two images, a “before”  image whose columns are matched against when searching for the row to be updated, and an “after”  image containing the changes. Normally, MySQL logs full rows (that is, all columns) for both the before and after images. However, it is not strictly necessary to include every column in both images, and we can often save disk, memory, and network usage by logging only those columns which are actually required. 3555 Note When deleting a row, only the before image is logged, since there are no changed values to propagate following the deletion. When inserting a row, only the after image is logged, since there is no existing row to be matched. Only