mariadb/storage/xtradb/trx
Marko Mäkelä d11001d11b Backport MDEV-13890 from 10.2 (InnoDB/XtraDB shutdown failure)
If InnoDB or XtraDB recovered committed transactions at server
startup, but the processing of recovered transactions was
prevented by innodb_read_only or by innodb_force_recovery,
an assertion would fail at shutdown.

This bug was originally reproduced when Mariabackup executed
InnoDB shutdown after preparing (applying redo log into) a backup.

trx_free_prepared(): Allow TRX_STATE_COMMITTED_IN_MEMORY.

trx_undo_free_prepared(): Allow any undo log state. For transactions
that were resurrected in TRX_STATE_COMMITTED_IN_MEMORY
the undo log state would have been reset by trx_undo_set_state_at_finish().
2017-10-30 18:43:16 +02:00
..
trx0i_s.cc Never pass NULL to innobase_get_stmt() 2017-05-17 08:11:01 +03:00
trx0purge.cc MDEV-12569 InnoDB suggests filing bugs at MySQL bug tracker 2017-10-26 13:29:28 +03:00
trx0rec.cc MDEV-12569 InnoDB suggests filing bugs at MySQL bug tracker 2017-10-26 13:29:28 +03:00
trx0roll.cc Merge branch 'merge-xtradb-5.6' into 10.0 2017-05-17 12:11:12 +03:00
trx0rseg.cc move to storage/xtradb 2015-05-04 19:15:28 +02:00
trx0sys.cc Merge branch 'merge-xtradb-5.6' into 10.0 2017-05-17 12:11:12 +03:00
trx0trx.cc Backport MDEV-13890 from 10.2 (InnoDB/XtraDB shutdown failure) 2017-10-30 18:43:16 +02:00
trx0undo.cc Backport MDEV-13890 from 10.2 (InnoDB/XtraDB shutdown failure) 2017-10-30 18:43:16 +02:00