ER_SQL_SLAVE_SKIP_COUNTER_NOT_SETTABLE_IN_GTID_MODE

Overview

sql_slave_skip_counter can not be set when the server is running with GTID_MODE = ON. Instead, for each transaction that you want to skip, generate an empty transaction with the same GTID as the transaction

See also: Error Codes for MariaDB Enterprise Server 10.6, 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: Error Codes for MariaDB Enterprise Server 10.6, in 10.5 ES, and in 10.4 ES

USAGE

DETAILS

SYNONYMS

SCHEMA

PARAMETERS

SKYSQL

PRIVILEGES

EXAMPLES

ERROR HANDLING

FEATURE INTERACTION

RESPONSES

DIAGNOSIS

ISO 9075:2016

CHANGE HISTORY

Release Series

History

10.6 Enterprise

  • Present starting in MariaDB Enterprise Server 10.6.4-1 as error number 1858

10.6 Community

  • Present starting in MariaDB Community Server 10.6.0 as error number 1858

10.5 Enterprise

  • Present starting in MariaDB Enterprise Server 10.5.3-1 as error number 1858

10.5 Community

  • Present starting in MariaDB Community Server 10.5.0 as error number 1858

10.4 Enterprise

  • Present starting in MariaDB Enterprise Server 10.4.6-1 as error number 1858

10.4 Community

  • Present starting in MariaDB Community Server 10.4.0 as error number 1858

10.3 Enterprise

  • Present starting in MariaDB Enterprise Server 10.3.16-1 as error number 1858

10.3 Community

  • Present starting in MariaDB Community Server 10.3.0 as error number 1858

10.2 Enterprise

  • Present starting in MariaDB Enterprise Server 10.2.25-1 as error number 1858

10.2 Community

  • Present starting in MariaDB Community Server 10.2.0 as error number 1858

Release Series

History

10.6 Enterprise

  • Present starting in MariaDB Enterprise Server 10.6.4-1 as error number 1858

10.5 Enterprise

  • Present starting in MariaDB Enterprise Server 10.5.3-1 as error number 1858

10.4 Enterprise

  • Present starting in MariaDB Enterprise Server 10.4.6-1 as error number 1858

EXTERNAL REFERENCES