diff options
| author | Dmitry Lenev <Dmitry.Lenev@oracle.com> | 2013-08-26 14:43:12 +0400 |
|---|---|---|
| committer | Dmitry Lenev <Dmitry.Lenev@oracle.com> | 2013-08-26 14:43:12 +0400 |
| commit | 4582478214e81d789d23442ad169654d9c96ef0c (patch) | |
| tree | 10178054c07e2065d920b42ed3a51f5b4e0f1b8d /VERSION | |
| parent | 45daf55a551226fa22b5057ad8e894fe8f0b53d9 (diff) | |
| download | mariadb-git-4582478214e81d789d23442ad169654d9c96ef0c.tar.gz | |
Fix for bug #17356954 "CANNOT USE SAVEPOINTS AFTER ER_LOCK_DEADLOCK OR
ER_LOCK_WAIT_TIMEOUT".
The problem was that after changes caused by fix bug 14188793 "DEADLOCK
CAUSED BY ALTER TABLE DOEN'T CLEAR STATUS OF ROLLBACKED TRANSACTION"/
bug 17054007 "TRANSACTION IS NOT FULLY ROLLED BACK IN CASE OF INNODB
DEADLOCK implicit rollback of transaction which occurred on ER_LOCK_DEADLOCK
(and ER_LOCK_WAIT_TIMEOUT if innodb_rollback_on_timeout option was set)
didn't start new transaction in @@autocommit=1 mode.
Such behavior although consistent with behavior of explicit ROLLBACK has
broken expectations of users and backward compatibility assumptions.
This patch fixes problem by reverting to starting new transaction
in 5.5/5.6.
The plan is to keep new behavior in trunk so the code change from this
patch is to be null-merged there.
Diffstat (limited to 'VERSION')
0 files changed, 0 insertions, 0 deletions