summaryrefslogtreecommitdiff
path: root/storage
diff options
context:
space:
mode:
authorMarko Mäkelä <marko.makela@mariadb.com>2018-10-19 09:29:28 +0300
committerMarko Mäkelä <marko.makela@mariadb.com>2018-10-19 09:31:33 +0300
commitab1ce2204e959bea596817494e932754ab5cbe88 (patch)
treeb61bbcd681d1c8e6081fcb58ec8aa18bf625bd11 /storage
parentabbf169f52e3ec598c37848e11e0d6351cbfb52c (diff)
downloadmariadb-git-ab1ce2204e959bea596817494e932754ab5cbe88.tar.gz
MDEV-17466: Remove the debug assertion
This reverts commit 2d4075e1d9dba3dd8503d65fdb145a6dcc056c51 where the debug assertion was added. There seems to be a potential problem in the purge of indexes that depend on virtual columns. Ultimately, we should change the InnoDB undo log format so that all actual secondary index keys are stored there, also for virtual or spatial indexes. In that way, purge and rollback would be more straightforward.
Diffstat (limited to 'storage')
-rw-r--r--storage/innobase/row/row0row.cc2
1 files changed, 0 insertions, 2 deletions
diff --git a/storage/innobase/row/row0row.cc b/storage/innobase/row/row0row.cc
index 3f4308d4bed..ad4991fb4e9 100644
--- a/storage/innobase/row/row0row.cc
+++ b/storage/innobase/row/row0row.cc
@@ -127,8 +127,6 @@ row_build_index_entry_low(
ut_ad(dfield_is_null(dfield2) ||
dfield_get_len(dfield2) == 0 || dfield2->data);
- ut_ad(dfield2->type.mtype != DATA_MISSING
- || !index->is_committed());
} else {
dfield2 = dtuple_get_nth_field(row, col_no);
ut_ad(dfield_get_type(dfield2)->mtype == DATA_MISSING