binlog_row_image

Overview

Controls whether rows should be logged in 'FULL', 'NOBLOB' or 'MINIMAL' formats. 'FULL', means that all columns in the before and after image are logged. 'NOBLOB', means that mysqld avoids logging blob columns whenever possible (e.g., blob column was not changed or is not part of primary key). 'MINIMAL', means that a PK equivalent (PK columns or full row if there is no PK in the table) is logged in the before image, and only changed columns are logged in the after image. (Default: FULL).

See also: System Variables for MariaDB Enterprise Server 23.08, in 23.07 ES, in 10.6 ES, in 10.5 ES, in 10.4 ES, in 10.3 ES, in 10.2 ES, in 10.6 CS, in 10.5 CS, in 10.4 CS, in 10.3 CS, and in 10.2 CS

See also: System Variables for MariaDB Enterprise Server 23.08, in 23.07 ES, in 10.6 ES, in 10.5 ES, and in 10.4 ES

USAGE

DETAILS

SYNONYMS

SCHEMA

PARAMETERS

Command-line

--binlog_row_image={MINIMAL|NOBLOB|FULL}

Configuration file

Supported

Dynamic

Yes

Scope

Global, Session

Data Type

ENUM (MINIMAL, NOBLOB, FULL)

Product Default Value

FULL

SKYSQL

Cloud

SkySQL Topology

ES Ver

Service Default

AWS

Multi-Node Analytics

10.6

FULL

Single Node Analytics

10.6

FULL

Replicated Transactions

10.4

MINIMAL

10.5

MINIMAL

10.6

MINIMAL

Single Node Transactions

10.4

MINIMAL

10.5

MINIMAL

10.6

MINIMAL

GCP

Multi-Node Analytics

10.6

FULL

Single Node Analytics

10.6

FULL

Replicated Transactions

10.4

MINIMAL

10.5

MINIMAL

10.6

MINIMAL

Single Node Transactions

10.4

MINIMAL

10.5

MINIMAL

10.6

MINIMAL

Cloud

SkySQL Topology

ES Ver

Service Default

AWS

ColumnStore Data Warehouse

10.6

FULL

Enterprise Server With Replica(s)

10.4

MINIMAL

10.5

MINIMAL

10.6

MINIMAL

Enterprise Server Single Node

10.4

MINIMAL

10.5

MINIMAL

10.6

MINIMAL

GCP

ColumnStore Data Warehouse

10.6

FULL

Enterprise Server With Replica(s)

10.4

MINIMAL

10.5

MINIMAL

10.6

MINIMAL

Enterprise Server Single Node

10.4

MINIMAL

10.5

MINIMAL

10.6

MINIMAL

PRIVILEGES

EXAMPLES

ERROR HANDLING

FEATURE INTERACTION

RESPONSES

DIAGNOSIS

ISO 9075:2016

CHANGE HISTORY

Release Series

History

23.08 Enterprise

  • Present starting in MariaDB Enterprise Server 23.08.0.

23.07 Enterprise

  • Present starting in MariaDB Enterprise Server 23.07.0.

10.6 Enterprise

  • Present starting in MariaDB Enterprise Server 10.6.4-1.

10.6 Community

  • Present starting in MariaDB Community Server 10.6.0.

10.5 Enterprise

  • Present starting in MariaDB Enterprise Server 10.5.3-1.

10.5 Community

  • Present starting in MariaDB Community Server 10.5.0.

10.4 Enterprise

  • Present starting in MariaDB Enterprise Server 10.4.6-1.

10.4 Community

  • Present starting in MariaDB Community Server 10.4.0.

10.3 Enterprise

  • Present starting in MariaDB Enterprise Server 10.3.16-1.

10.3 Community

  • Present starting in MariaDB Community Server 10.3.0.

10.2 Enterprise

  • Present starting in MariaDB Enterprise Server 10.2.25-1.

10.2 Community

  • Present starting in MariaDB Community Server 10.2.0.

Release Series

History

23.08 Enterprise

  • Present starting in MariaDB Enterprise Server 23.08.0.

23.07 Enterprise

  • Present starting in MariaDB Enterprise Server 23.07.0.

10.6 Enterprise

  • Present starting in MariaDB Enterprise Server 10.6.4-1.

10.5 Enterprise

  • Present starting in MariaDB Enterprise Server 10.5.3-1.

10.4 Enterprise

  • Present starting in MariaDB Enterprise Server 10.4.6-1.

EXTERNAL REFERENCES