Skip to main content

ER_STMT_CACHE_FULL

This page is part of MariaDB's MariaDB Documentation.

The parent of this page is: Error Codes

Topics on this page:

Overview
CHANGE HISTORY

Overview

In 10.6 ES, 10.6 CS, 10.5 ES, 10.5 CS:: Multi-row statements required more than 'max_binlog_stmt_cache_size' bytes of storage.

In 10.6 ES, 10.5 ES:: Multi-row statements required more than 'max_binlog_stmt_cache_size' bytes of storage.

In 10.4 ES, 10.4 CS, 10.3 ES, 10.3 CS, 10.2 ES, 10.2 CS:: Multi-row statements required more than 'max_binlog_stmt_cache_size' bytes of storage; increase this mysqld variable and try again

In 10.4 ES:: Multi-row statements required more than 'max_binlog_stmt_cache_size' bytes of storage; increase this mysqld variable and try again

See also: Error Codes 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

See also: Error Codes in 10.6 ES, in 10.5 ES, and in 10.4 ES

CHANGE HISTORY

Release Series	History
10.6 Enterprise	Present starting in MariaDB Enterprise Server 10.6.4-1 as error number 1705
10.6 Community	Present starting in MariaDB Community Server 10.6.0 as error number 1705
10.5 Enterprise	Present starting in MariaDB Enterprise Server 10.5.3-1 as error number 1705
10.5 Community	Present starting in MariaDB Community Server 10.5.0 as error number 1705
10.4 Enterprise	Present starting in MariaDB Enterprise Server 10.4.6-1 as error number 1705
10.4 Community	Present starting in MariaDB Community Server 10.4.0 as error number 1705
10.3 Enterprise	Present starting in MariaDB Enterprise Server 10.3.16-1 as error number 1705
10.3 Community	Present starting in MariaDB Community Server 10.3.0 as error number 1705
10.2 Enterprise	Present starting in MariaDB Enterprise Server 10.2.25-1 as error number 1705
10.2 Community	Present starting in MariaDB Community Server 10.2.0 as error number 1705

Release Series	History
10.6 Enterprise	Present starting in MariaDB Enterprise Server 10.6.4-1 as error number 1705
10.5 Enterprise	Present starting in MariaDB Enterprise Server 10.5.3-1 as error number 1705
10.4 Enterprise	Present starting in MariaDB Enterprise Server 10.4.6-1 as error number 1705