Marko Mäkelä b4f6b678a6 MDEV-13520 InnoDB attempts UPDATE with DB_TRX_ID=0 if innodb_force_recovery=3 ... trx_set_rw_mode(): Check the flag high_level_read_only instead of testing srv_force_recovery (innodb_force_recovery) directly. There is no need to prevent the creation of read-write transactions if innodb_force_recovery=3 is used. Yes, in that mode any recovered incomplete transactions will not be rolled back, but these transactions will continue to hold locks on the records that they have modified. If the new read-write transactions hit conflicts with already existing (possibly recovered) transactions, the lock wait timeout mechanism will work just fine.		2017-08-15 10:51:42 +03:00
..
trx0i_s.cc
trx0purge.cc	MDEV-13472 rpl.rpl_semi_sync_wait_point crashes because of thd_destructor_proxy	2017-08-09 08:14:39 +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
trx0rseg.cc
trx0sys.cc	Simplify access to the binlog offset in InnoDB	2017-06-29 23:03:39 +03:00
trx0trx.cc	MDEV-13520 InnoDB attempts UPDATE with DB_TRX_ID=0 if innodb_force_recovery=3	2017-08-15 10:51:42 +03:00
trx0undo.cc