Marko Mäkelä 1595189250 MDEV-23897 SIGSEGV on commit with innodb_lock_schedule_algorithm=VATS ... This regression for debug builds was introduced by MDEV-23101 (commit 224c950462). Due to MDEV-16664, the parameter innodb_lock_schedule_algorithm=VATS is not enabled by default. The purpose of the added assertions was to enforce the invariant that Galera replication cannot be enabled together with VATS due to MDEV-12837. However, upon closer inspection, it is obvious that the variable 'lock' may be assigned to the null pointer if no match is found in the previous->hash list. lock_grant_and_move_on_page(), lock_grant_and_move_on_rec(): Assert !lock->trx->is_wsrep() only after ensuring that lock is not a null pointer.		2020-10-06 22:35:43 +03:00
..
include	MDEV-14119 Assertion cmp_rec_rec() in ALTER TABLE	2020-08-11 18:52:38 +03:00
r	Merge 10.1 into 10.2	2020-09-29 10:04:37 +03:00
t	MDEV-23897 SIGSEGV on commit with innodb_lock_schedule_algorithm=VATS	2020-10-06 22:35:43 +03:00
disabled.def	MDEV-23339 innodb_force_recovery=2 may still abort the rollback of recovered transactions	2020-07-30 09:24:36 +03:00