mirror/mariadb
1
0
Fork 0
mirror of https://github.com/MariaDB/server.git synced 2026-05-16 20:07:13 +02:00
Code Issues Projects Releases Packages Wiki Activity

ibuf_set_del_mark(): Do not complain about already delete-marked records.

Browse source 
According to a comment in row_upd_sec_index_entry(), it is a
legitimate situation that can be caused by a lock wait.
This commit is contained in:
Marko Mäkelä 2010-10-19 09:44:38 +03:00
commit 923003f99d
1 changed files with 10 additions and 9 deletions
Download patch file Download diff file Expand all files Collapse all files

21
storage/innobase/ibuf/ibuf0ibuf.c
View file

@ -3997,21 +3997,22 @@ ibuf_set_del_mark(
rec = page_cur_get_rec(&page_cur);
page_zip = page_cur_get_page_zip(&page_cur);
if (UNIV_UNLIKELY
(rec_get_deleted_flag(
rec, dict_table_is_comp(index->table)))) {
ut_print_timestamp(stderr);
fputs(" InnoDB: record is already delete-marked\n",
stderr);
goto failure;
}
/* Delete mark the old index record. According to a
comment in row_upd_sec_index_entry(), it can already
have been delete marked if a lock wait occurred in
row_ins_index_entry() in a previous invocation of
row_upd_sec_index_entry(). */
btr_cur_set_deleted_flag_for_ibuf(rec, page_zip, TRUE, mtr);
if (UNIV_LIKELY
(!rec_get_deleted_flag(
rec, dict_table_is_comp(index->table)))) {
btr_cur_set_deleted_flag_for_ibuf(rec, page_zip,
TRUE, mtr);
}
} else {
ut_print_timestamp(stderr);
fputs(" InnoDB: unable to find a record to delete-mark\n",
stderr);
failure:
fputs("InnoDB: tuple ", stderr);
dtuple_print(stderr, entry);
fputs("\n"