binlog_row_image

Description

binlog_row_image specifies whether to record full-column logs.

Privilege requirements

• Query variables

  • Global level

    The sys tenant and all user tenants can execute the SHOW VARIABLES statement or query the SYS.TENANT_VIRTUAL_GLOBAL_VARIABLE view (Oracle-compatible mode) and information_schema.GLOBAL_VARIABLES view (MySQL-compatible mode) to obtain the value of global system variables.

  • Session level

    The sys tenant and all user tenants can execute the SHOW VARIABLES statement or query the SYS.TENANT_VIRTUAL_SESSION_VARIABLE view (Oracle-compatible mode) and information_schema.SESSION_VARIABLES view (MySQL-compatible mode) to obtain the value of session system variables.

• Modify variables

  • Global level

    • The sys tenant can directly modify the value of global system variables.

    • MySQL user tenants can modify global system variables only if they have the SUPER or ALTER SYSTEM privilege.

    • Oracle user tenants can modify global system variables only if they have the ALTER SYSTEM privilege.

  • Session level

    The sys tenant and all user tenants can directly modify the value of session system variables of their own tenants.

Attributes

Usage

• A full-column log records all the new and old values of columns for UPDATE and DELETE statements on an OBServer node.

A non-full-column log records only the new values of columns.

• After you execute the SET GLOBAL binlog_row_image= 'xxx' statement to modify a variable, the modification does not take effect on any existing session, including the one that issued the modification statement.

Examples

• Global level

  obclient> SET GLOBAL binlog_row_image=FULL;
  

• Session level

  obclient> SET binlog_row_image=FULL;