mariadb/storage/innobase/trx
Marko Mäkelä c436338d9d Assert that DB_TRX_ID must be set on delete-marked records
This is preparation for MDEV-12288, which would set DB_TRX_ID=0
when purging history. Also with that change in place, delete-marked
records must always refer to an undo log record via a nonzero
DB_TRX_ID column. (The DB_TRX_ID is only present in clustered index
leaf page records.)

btr_cur_parse_del_mark_set_clust_rec(), rec_get_trx_id():
Statically allocate the offsets
(should never use the heap). Add some debug assertions.

Replace some use of rec_get_trx_id() with row_get_rec_trx_id().

trx_undo_report_row_operation(): Add some sanity checks that are
common for all operations that produce undo log.
2017-07-01 11:02:58 +03:00
..
trx0i_s.cc Remove trx_t::has_search_latch and simplify debug code 2017-06-16 13:17:05 +03:00
trx0purge.cc Do allow writes for innodb_force_recovery=2 or 3 2017-06-23 09:54:31 +03:00
trx0rec.cc Assert that DB_TRX_ID must be set on delete-marked records 2017-07-01 11:02:58 +03:00
trx0roll.cc Merge 10.1 into 10.2 2017-05-23 11:09:47 +03:00
trx0rseg.cc Merge 10.1 into 10.2 2017-06-08 12:45:08 +03:00
trx0sys.cc Simplify access to the binlog offset in InnoDB 2017-06-29 23:03:39 +03:00
trx0trx.cc Simplify access to the binlog offset in InnoDB 2017-06-29 23:03:39 +03:00
trx0undo.cc MDEV-12289 Keep 128 persistent rollback segments for compatibility and performance 2017-03-31 18:53:04 +03:00