[MDEV-18798] InnoDB: No matching column for `DB_ROW_HASH_1`and server crash in ha_innobase::commit_inplace_alter_table upon ALTER on table with UNIQUE key Created: 2019-03-03  Updated: 2022-09-29  Resolved: 2019-03-17

Status: Closed
Project: MariaDB Server
Component/s: Data Definition - Alter Table, Storage Engine - InnoDB
Affects Version/s: 10.4
Fix Version/s: 10.4.4

Type: Bug Priority: Critical
Reporter: Elena Stepanova Assignee: Sergei Golubchik
Resolution: Fixed Votes: 0
Labels: regression

Issue Links:
Problem/Incident
is caused by MDEV-371 Unique indexes for blobs Closed

 Description   

Note: The problem appeared in 10.4 tree with the first MDEV-371 revision, even though there are no BLOBs in the scenario.

--source include/have_innodb.inc
 
CREATE TABLE t1 (a INT, UNIQUE ind USING HASH (a)) ENGINE=InnoDB;
ALTER TABLE t1 CHANGE COLUMN IF EXISTS b a INT;
 
# Cleanup
DROP TABLE t1;

2019-03-03  1:59:12 9 [ERROR] InnoDB: No matching column for `DB_ROW_HASH_1` in index `ind` of table `test`.`t1`
190303  1:59:12 [ERROR] mysqld got signal 11 ;
 
#3  <signal handler called>
#4  0x0000563fefefc41e in ha_innobase::commit_inplace_alter_table (this=0x7fbb6414fd98, altered_table=0x7fbb641539e0, ha_alter_info=0x7fbbbc09a900, commit=true) at /data/src/10.4/storage/innobase/handler/handler0alter.cc:11131
#5  0x0000563fefb77e9a in handler::ha_commit_inplace_alter_table (this=0x7fbb6414fd98, altered_table=0x7fbb641539e0, ha_alter_info=0x7fbbbc09a900, commit=true) at /data/src/10.4/sql/handler.cc:4677
#6  0x0000563fef90e63b in mysql_inplace_alter_table (thd=0x7fbb64000b00, table_list=0x7fbb640155b0, table=0x7fbb6400c960, altered_table=0x7fbb641539e0, ha_alter_info=0x7fbbbc09a900, inplace_supported=HA_ALTER_INPLACE_INSTANT, target_mdl_request=0x7fbbbc09ab30, alter_ctx=0x7fbbbc09b0e0) at /data/src/10.4/sql/sql_table.cc:7695
#7  0x0000563fef914caf in mysql_alter_table (thd=0x7fbb64000b00, new_db=0x7fbb64005290, new_name=0x7fbb64005690, create_info=0x7fbbbc09bcd0, table_list=0x7fbb640155b0, alter_info=0x7fbbbc09bc10, order_num=0, order=0x0, ignore=false) at /data/src/10.4/sql/sql_table.cc:9922
#8  0x0000563fef9a30ee in Sql_cmd_alter_table::execute (this=0x7fbb64015d88, thd=0x7fbb64000b00) at /data/src/10.4/sql/sql_alter.cc:499
#9  0x0000563fef83448e in mysql_execute_command (thd=0x7fbb64000b00) at /data/src/10.4/sql/sql_parse.cc:6346
#10 0x0000563fef839636 in mysql_parse (thd=0x7fbb64000b00, rawbuf=0x7fbb640154a8 "ALTER TABLE t1 CHANGE COLUMN IF EXISTS b a INT", length=46, parser_state=0x7fbbbc09d180, is_com_multi=false, is_next_command=false) at /data/src/10.4/sql/sql_parse.cc:8157
#11 0x0000563fef824d24 in dispatch_command (command=COM_QUERY, thd=0x7fbb64000b00, packet=0x7fbb64139fd1 "ALTER TABLE t1 CHANGE COLUMN IF EXISTS b a INT", packet_length=46, is_com_multi=false, is_next_command=false) at /data/src/10.4/sql/sql_parse.cc:1829
#12 0x0000563fef8234f8 in do_command (thd=0x7fbb64000b00) at /data/src/10.4/sql/sql_parse.cc:1358
#13 0x0000563fef99d003 in do_handle_one_connection (connect=0x563ff30a4d10) at /data/src/10.4/sql/sql_connect.cc:1399
#14 0x0000563fef99cd74 in handle_one_connection (arg=0x563ff30a4d10) at /data/src/10.4/sql/sql_connect.cc:1302
#15 0x0000563fefe93d17 in pfs_spawn_thread (arg=0x563ff30eab80) at /data/src/10.4/storage/perfschema/pfs.cc:1862
#16 0x00007fbbc33f9494 in start_thread (arg=0x7fbbbc09e700) at pthread_create.c:333
#17 0x00007fbbc17df93f in clone () from /lib/x86_64-linux-gnu/libc.so.6



 Comments   
Comment by Sachin Setiya (Inactive) [ 2019-03-04 ]

Patch for mdev-18799 also solves this

Generated at Thu Feb 08 08:46:49 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.