Details
-
Bug
-
Status: In Review (View Workflow)
-
Critical
-
Resolution: Unresolved
-
N/A
Description
Note: I've made it critical for the feature tentatively, in case it is scalable. I'm not sure it is, I couldn't keep it reproducible with higher values of max-heap-table-size by simply increasing the amount of data. If it turns out to be specific to extremely low values of the option, then of course it is not important and should be demoted.
Run with --mysqld=--max-heap-table-size=32K. I deliberately don't put it inside the test case, so that we are sure that the master and slave run with the same unchanged value from start to end.
# Options: --mysqld=--max-heap-table-size=32K |
|
|
--source include/have_binlog_format_row.inc
|
--source include/have_sequence.inc
|
--source include/master-slave.inc
|
|
|
CREATE TABLE t ( |
pk INT PRIMARY KEY, |
b TEXT,
|
c VARCHAR(8), |
UNIQUE(c) |
) ENGINE=HEAP;
|
INSERT INTO t VALUES (1, 'x', 'foo'); |
REPLACE INTO t SELECT * FROM t; |
|
|
--sync_slave_with_master
|
|
|
--connection master
|
DROP TABLE t; |
|
|
--source include/rpl_end.inc |
|
bb-blob-main-monty 2362eb264048e930dc9eb42da444086d8fce464b |
2026-09-03 13:31:29 7 [ERROR] mariadbd.exe: The table 't' is full
|
2026-09-03 13:31:29 7 [ERROR] Slave SQL: Could not execute Write_rows_v1 event on table test.t; The table 't' is full, Error_code: 1114; handler error HA_ERR_RECORD_FILE_FULL; the event's master log master-bin.000001, end_log_pos 0, Gtid 0-1-3, Internal MariaDB error code: 1114
|
2026-09-03 13:31:29 7 [Warning] Slave: The table 't' is full Error_code: 1114
|
Attachments
Issue Links
- is caused by
-
MDEV-38975 BLOBs in MEMORY (HEAP) Engine
-
- In Testing
-