--gtid-strict-mode

This page is part of MariaDB's Documentation.

The parent of this page is: mariadbd & mysqld for MariaDB Enterprise Server

Topics on this page:

• Overview

• USAGE

• DETAILS

  • SYNONYMS

  • SCHEMA

  • PARAMETERS

  • SKYSQL

  • PRIVILEGES

• EXAMPLES

• ERROR HANDLING

• FEATURE INTERACTION

• RESPONSES

• DIAGNOSIS

• ISO 9075:2016

• CHANGE HISTORY

• RELATED TOPICS

• EXTERNAL REFERENCES

Overview

This is a command-line option for the mariadbd & mysqld commands.

In 11.4 ES:

Enforce strict seq_no ordering of events in the binary log. Slave stops with an error if it encounters an event that would cause it to generate an out-of-order binlog if executed. When ON the same server-id semisync-replicated transactions that duplicate existing ones in binlog are ignored without error and slave interruption.

In 10.6 ES, 10.6 CS, 10.5 ES, 10.4 ES, 10.3 ES:

Enforce strict seq_no ordering of events in the binary log. Slave stops with an error if it encounters an event that would cause it to generate an out-of-order binlog if executed. When ON the same server-id semisync-replicated transactions that duplicate exising ones in binlog are ignored without error and slave interruption.

In 10.5 CS, 10.4 CS, 10.3 CS, 10.2 ES, 10.2 CS:

Enforce strict seq_no ordering of events in the binary log. Slave stops with an error if it encounters an event that would cause it to generate an out-of-order binlog if executed.

See also: mariadbd & mysqld for MariaDB Enterprise Server 11.4, 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