diff options
| author | Marko Mäkelä <marko.makela@mariadb.com> | 2020-10-06 22:35:43 +0300 |
|---|---|---|
| committer | Marko Mäkelä <marko.makela@mariadb.com> | 2020-10-06 22:35:43 +0300 |
| commit | 1595189250e71d5902fc0f378b0e6b14c5b26901 (patch) | |
| tree | e83837dba7f800a4200103dd03465984c14bf1aa /scripts | |
| parent | 2b832151ad66556cb07ed232b139411f4b6defe3 (diff) | |
| download | mariadb-git-1595189250e71d5902fc0f378b0e6b14c5b26901.tar.gz | |
MDEV-23897 SIGSEGV on commit with innodb_lock_schedule_algorithm=VATS
This regression for debug builds was introduced by
MDEV-23101 (commit 224c950462a22e09f4e2e37d19218c9129bccba6).
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.
Diffstat (limited to 'scripts')
0 files changed, 0 insertions, 0 deletions