summaryrefslogtreecommitdiff
path: root/win
diff options
context:
space:
mode:
authorMarko Mäkelä <marko.makela@mariadb.com>2017-08-23 13:03:13 +0300
committerMarko Mäkelä <marko.makela@mariadb.com>2017-08-23 13:03:13 +0300
commitb8b3ba632b8596bb483420dc6da46925f1c9b094 (patch)
tree77d5ddab55ed16f46840fd15d038a90da44740fd /win
parentce6c0e584e35b516297f2afdaea5b31e508b7570 (diff)
downloadmariadb-git-b8b3ba632b8596bb483420dc6da46925f1c9b094.tar.gz
MDEV-13606 XA PREPARE transactions should survive innodb_force_recovery=1 or 2
When MySQL 5.0.3 introduced InnoDB support for two-phase commit, it also introduced the questionable logic to roll back XA PREPARE transactions on startup when innodb_force_recovery is 1 or 2. Remove this logic in order to avoid unwanted side effects when innodb_force_recovery is being set for other reasons. That is, XA PREPARE transactions will always remain in that state until InnoDB receives an explicit XA ROLLBACK or XA COMMIT request from the upper layer. At the time the logic was introduced in MySQL 5.0.3, there already was a startup parameter that is the preferred way of achieving the behaviour: --tc-heuristic-recover=ROLLBACK.
Diffstat (limited to 'win')
0 files changed, 0 insertions, 0 deletions