mariadb/storage/innobase/trx
Vladislav Vaintroub b7fe6179e8 MDEV-29843 Do not use asynchronous log_write_upto() for system THDs
Non-blocking log_write_upto (MDEV-24341) was only designed  for the
client connections. Fix, so it is not be triggered for any system THD.

Previously, an incomplete solution only excluded Innodb purge THDs, but
not  the slave for example.

The hang in MDEV still remains somewhat a mystery though, it is not
immediately clear how exactly condition variable can become corrupted.
But it is clear that it can be avoided.
2022-10-25 19:40:44 +02:00
..
trx0i_s.cc Merge 10.5 into 10.6 2022-01-04 09:26:38 +02:00
trx0purge.cc MDEV-24402: InnoDB CHECK TABLE ... EXTENDED 2022-10-21 10:02:54 +03:00
trx0rec.cc MDEV-24402: InnoDB CHECK TABLE ... EXTENDED 2022-10-21 10:02:54 +03:00
trx0roll.cc MDEV-29081 trx_t::lock.was_chosen_as_deadlock_victim race in lock_wait_end() 2022-08-24 17:06:57 +03:00
trx0rseg.cc MDEV-29321 Percona XtraDB 5.7 can't be upgrade to MariaDB 10.6 or above 2022-08-18 16:02:13 +03:00
trx0sys.cc MDEV-24402: InnoDB CHECK TABLE ... EXTENDED 2022-10-21 10:02:54 +03:00
trx0trx.cc MDEV-29843 Do not use asynchronous log_write_upto() for system THDs 2022-10-25 19:40:44 +02:00
trx0undo.cc MDEV-15020 fixup: Make trx_t::apply_log() truly ATTRIBUTE_COLD 2022-09-20 09:14:04 +03:00