ER_CANT_SET_GTID_PURGED_WHEN_OWNED_GTIDS_IS_NOT_EMPTY

Overview

GTID_PURGED can only be set when there are no ongoing transactions (not even in other clients)

USAGE

DETAILS

SYNONYMS

SCHEMA

PARAMETERS

SKYSQL

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 as error number 1841

23.07 Enterprise

  • Present starting in MariaDB Enterprise Server 23.07.0 as error number 1841

10.6 Enterprise

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

10.6 Community

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

10.5 Enterprise

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

10.5 Community

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

10.4 Enterprise

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

10.4 Community

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

10.3 Enterprise

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

10.3 Community

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

10.2 Enterprise

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

10.2 Community

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

Release Series

History

23.08 Enterprise

  • Present starting in MariaDB Enterprise Server 23.08.0 as error number 1841

23.07 Enterprise

  • Present starting in MariaDB Enterprise Server 23.07.0 as error number 1841

10.6 Enterprise

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

10.5 Enterprise

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

10.4 Enterprise

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

EXTERNAL REFERENCES