ER_WARN_ONLY_MASTER_LOG_FILE_NO_POS

Overview

CHANGE MASTER TO with a MASTER_LOG_FILE clause but no MASTER_LOG_POS clause may not be safe. The old position value may not be valid for the new binary log file.

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 3023

10.6 Community

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

10.5 Enterprise

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

10.5 Community

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

10.4 Enterprise

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

10.4 Community

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

10.3 Enterprise

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

10.3 Community

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

10.2 Enterprise

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

10.2 Community

  • Added in MariaDB Community Server 10.2.3 as error number 3022

  • Error number changed in MariaDB Community Server 10.2.5 from 3022 to 3023

Release Series

History

10.6 Enterprise

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

10.5 Enterprise

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

10.4 Enterprise

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

EXTERNAL REFERENCES