summaryrefslogtreecommitdiff
path: root/storage/innobase/btr
diff options
context:
space:
mode:
authorMarko Mäkelä <marko.makela@mariadb.com>2019-11-08 11:04:26 +0200
committerMarko Mäkelä <marko.makela@mariadb.com>2019-11-08 11:04:26 +0200
commita6d614fb4ad8df0daa402690b7a0a547a727a04b (patch)
tree7f225e5180cad61fdfcec4966310495a7388460a /storage/innobase/btr
parent5b72e8136fd439b9d297bdf50d5d5d2e8a119665 (diff)
downloadmariadb-git-a6d614fb4ad8df0daa402690b7a0a547a727a04b.tar.gz
MDEV-12353 preparation: Remove redundant writes
fsp_alloc_seg_inode_page(): Ever since commit 3926673ce7149aa223103126b6aeac819b10fab5 all newly allocated pages are zero-initialized. Assert that this is the case for the FSEG_ID fields. (Side note: before that fix, other parts of the pages could contain nonzero garbage.) btr_store_big_rec_extern_fields(): Remove the redundant initialization of the most significant 32 bits of BTR_EXTERN_LEN. InnoDB never supported BLOBs that are longer than 4GiB. In fact, dtuple_convert_big_rec() would write emit an error message if a clustered index record tuple would exceed 1,000,000,000 bytes in length.
Diffstat (limited to 'storage/innobase/btr')
-rw-r--r--storage/innobase/btr/btr0cur.cc4
1 files changed, 2 insertions, 2 deletions
diff --git a/storage/innobase/btr/btr0cur.cc b/storage/innobase/btr/btr0cur.cc
index 72232766e4d..a3fb214cd80 100644
--- a/storage/innobase/btr/btr0cur.cc
+++ b/storage/innobase/btr/btr0cur.cc
@@ -7870,8 +7870,8 @@ next_zip_page:
extern_len -= store_len;
- mlog_write_ulint(field_ref + BTR_EXTERN_LEN, 0,
- MLOG_4BYTES, &mtr);
+ ut_ad(!mach_read_from_4(BTR_EXTERN_LEN
+ + field_ref));
mlog_write_ulint(field_ref
+ BTR_EXTERN_LEN + 4,
big_rec_vec->fields[i].len