Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Duplicate
-
10.3(EOL), 10.4(EOL), 10.5, 10.6, 10.7(EOL), 10.8(EOL), 10.9(EOL)
Description
--source include/have_innodb.inc
|
|
CREATE TABLE t (id INT PRIMARY KEY, s TIMESTAMP(6) AS ROW START, e TIMESTAMP(6) AS ROW END, PERIOD FOR SYSTEM_TIME(s,e)) ENGINE=InnoDB WITH SYSTEM VERSIONING; |
INSERT INTO t (id) VALUES (1),(2); |
DELETE FROM t; |
SET system_versioning_alter_history= KEEP; |
--error ER_DUP_ENTRY
|
ALTER TABLE t ADD UNIQUE (e), ALGORITHM=COPY; |
|
# Cleanup
|
DROP TABLE t; |
10.3 e59c1cef |
mysqld: /data/src/10.3/storage/innobase/row/row0ins.cc:3652: dberr_t row_ins(ins_node_t*, que_thr_t*): Assertion `!strcmp(index->name, "FTS_DOC_ID_INDEX")' failed.
|
201231 19:44:35 [ERROR] mysqld got signal 6 ;
|
|
#7 0x00007f5971a44f36 in __GI___assert_fail (assertion=0x55982180e800 "!strcmp(index->name, \"FTS_DOC_ID_INDEX\")", file=0x55982180cb20 "/data/src/10.3/storage/innobase/row/row0ins.cc", line=3652, function=0x55982180e7b0 "dberr_t row_ins(ins_node_t*, que_thr_t*)") at assert.c:101
|
#8 0x000055982104d50f in row_ins (node=0x7f591c0af848, thr=0x7f591c0afab0) at /data/src/10.3/storage/innobase/row/row0ins.cc:3652
|
#9 0x000055982104dd68 in row_ins_step (thr=0x7f591c0afab0) at /data/src/10.3/storage/innobase/row/row0ins.cc:3788
|
#10 0x0000559821074f14 in row_insert_for_mysql (mysql_rec=0x7f591c127800 "\377\001", prebuilt=0x7f591c0af2d0, ins_mode=ROW_INS_NORMAL) at /data/src/10.3/storage/innobase/row/row0mysql.cc:1421
|
#11 0x0000559820eda0eb in ha_innobase::write_row (this=0x7f591c127c58, record=0x7f591c127800 "\377\001") at /data/src/10.3/storage/innobase/handler/ha_innodb.cc:8023
|
#12 0x0000559820cac1c1 in handler::ha_write_row (this=0x7f591c127c58, buf=0x7f591c127800 "\377\001") at /data/src/10.3/sql/handler.cc:6473
|
#13 0x0000559820a61e7f in copy_data_between_tables (thd=0x7f591c000d90, from=0x7f591c036a00, to=0x7f591c126bb0, create=..., ignore=false, order_num=0, order=0x0, copied=0x7f596c0580d0, deleted=0x7f596c0580d8, keys_onoff=Alter_info::LEAVE_AS_IS, alter_ctx=0x7f596c0588e0) at /data/src/10.3/sql/sql_table.cc:10654
|
#14 0x0000559820a5fd2c in mysql_alter_table (thd=0x7f591c000d90, new_db=0x7f591c005478, new_name=0x7f591c005840, create_info=0x7f596c0594d0, table_list=0x7f591c012bb8, alter_info=0x7f596c059410, order_num=0, order=0x0, ignore=false) at /data/src/10.3/sql/sql_table.cc:10083
|
#15 0x0000559820af003a in Sql_cmd_alter_table::execute (this=0x7f591c0132e8, thd=0x7f591c000d90) at /data/src/10.3/sql/sql_alter.cc:512
|
#16 0x000055982097b069 in mysql_execute_command (thd=0x7f591c000d90) at /data/src/10.3/sql/sql_parse.cc:6052
|
#17 0x00005598209808d0 in mysql_parse (thd=0x7f591c000d90, rawbuf=0x7f591c012ab8 "ALTER TABLE t ADD UNIQUE (e), ALGORITHM=COPY", length=44, parser_state=0x7f596c05a5c0, is_com_multi=false, is_next_command=false) at /data/src/10.3/sql/sql_parse.cc:7840
|
#18 0x000055982096d034 in dispatch_command (command=COM_QUERY, thd=0x7f591c000d90, packet=0x7f591c008f11 "ALTER TABLE t ADD UNIQUE (e), ALGORITHM=COPY", packet_length=44, is_com_multi=false, is_next_command=false) at /data/src/10.3/sql/sql_parse.cc:1852
|
#19 0x000055982096b9d4 in do_command (thd=0x7f591c000d90) at /data/src/10.3/sql/sql_parse.cc:1398
|
#20 0x0000559820ae9ed1 in do_handle_one_connection (connect=0x559823e33870) at /data/src/10.3/sql/sql_connect.cc:1403
|
#21 0x0000559820ae9c2d in handle_one_connection (arg=0x559823e33870) at /data/src/10.3/sql/sql_connect.cc:1308
|
#22 0x00005598214b58ff in pfs_spawn_thread (arg=0x559823e156a0) at /data/src/10.3/storage/perfschema/pfs.cc:1869
|
#23 0x00007f5971f54609 in start_thread (arg=<optimized out>) at pthread_create.c:477
|
#24 0x00007f5971b30293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95
|
The failure started happening after addition of the assertion:
commit 7410ff436e95de09c2f3f0028e7af8b3a043028b
|
Author: Aleksey Midenkov
|
Date: Tue Dec 22 03:33:53 2020 +0300
|
Thus, I can't say whether it's a regression or an old problem revealed by the new assertion.
Currently reproducible on 10.3 and 10.4, the commit is not in 10.5 yet.
No obvious problem on a non-debug build.
Attachments
Issue Links
- duplicates
-
MDEV-25004 Missing row in FTS_DOC_ID_INDEX during DELETE HISTORY
- Closed