[MDEV-27752] main.alter_table does not work with MSAN with ER_OPTION_PREVENTS_STATEMENT Created: 2022-02-05  Updated: 2022-02-05

Status: Open
Project: MariaDB Server
Component/s: Tests
Affects Version/s: 10.5, 10.6
Fix Version/s: 10.5, 10.6

Type: Bug Priority: Minor
Reporter: Elena Stepanova Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: not-10.7


 Description   

10.5 fb40a2fa

main.alter_table 'innodb,innodb'         w1 [ fail ]
        Test ended at 2022-02-04 02:28:51
 
CURRENT_TEST: main.alter_table
mysqltest: At line 2678: query 'LOCK TABLE t1 WRITE' failed: 1290: The MariaDB server is running with the --max-thread-mem-used=8192 option so it cannot execute this statement
 
The result from queries just before the failure was:
< snip >
#
create table t1 (a int, key idx1(a), key idx2 using btree(a)) engine=memory;
alter table t1 rename index idx1 to idx3, algorithm=inplace;
delete from t1 where a = 10;
alter table t1 drop key idx3, add key idx1(a), algorithm=inplace;
ERROR 0A000: ALGORITHM=INPLACE is not supported for this operation. Try ALGORITHM=COPY
delete from t1 where a = 11;
drop table t1;
#
# MDEV-23836: Assertion `! is_set() || m_can_overwrite_status' in
# Diagnostics_area::set_error_status (interrupted ALTER TABLE under LOCK)
#
SET @max_session_mem_used_save= @@max_session_mem_used;
CREATE TABLE t1 (a INT);
SELECT * FROM t1;
a
ALTER TABLE x MODIFY xx INT;
ERROR 42S02: Table 'test.x' doesn't exist
SET SESSION max_session_mem_used= 8192;
LOCK TABLE t1 WRITE;


Generated at Thu Feb 08 09:55:19 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.