summaryrefslogtreecommitdiff
path: root/strings
diff options
context:
space:
mode:
authorAndrei Elkin <andrei.elkin@mariadb.com>2021-10-25 18:25:03 +0300
committerAndrei Elkin <andrei.elkin@mariadb.com>2021-10-28 19:54:03 +0300
commit42ae765960869a7ce381341d7b98c1e8aa157b29 (patch)
tree3dff06a0dccc6473a8baf05fdb1cdf265659da88 /strings
parent4e5cf34819f80b5184cce371d2ec95f83e597ef8 (diff)
downloadmariadb-git-42ae765960869a7ce381341d7b98c1e8aa157b29.tar.gz
MDEV-26833 Missed statement rollback in case transaction drops or create temporary tablebb-10.2-andrei
When transaction creates or drops temporary tables and afterward its statement faces an error even the transactional table statement's cached ROW format events get involved into binlog and are visible after the transaction's commit. Fixed with proper analysis of whether the errored-out statement needs to be rolled back in binlog. For instance a fact of already cached CREATE or DROP for temporary tables by previous statements alone does not cause to retain the being errored-out statement events in the cache. Conversely, if the statement creates or drops a temporary table itself it can't be rolled back - this rule remains.
Diffstat (limited to 'strings')
0 files changed, 0 insertions, 0 deletions