[MDEV-26833] Missed statement rollback in case transaction drops or create temporary table Created: 2021-10-14 Updated: 2022-03-08 Resolved: 2021-10-28 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Replication |
| Affects Version/s: | 10.2, 10.3, 10.4, 10.5, 10.6 |
| Fix Version/s: | 10.2.41, 10.3.32, 10.4.22, 10.5.13, 10.6.5, 10.7.1 |
| Type: | Bug | Priority: | Blocker |
| Reporter: | Valerii Kravchuk | Assignee: | Andrei Elkin |
| Resolution: | Fixed | Votes: | 1 |
| Labels: | temporary-table-replication | ||
| Description |
|
Consider the following test case (based on real life issue and simplified by Elkin):
You should get error upon INSERT, but the event that causes the problem is in the binary log. Now check this output on master vs slave:
Slave is already out of sync and on every next event it may easily break/hit error that does not happen on master. |
| Comments |
| Comment by Brandon Nesterenko [ 2021-10-25 ] |
|
Added a few comments to 7c318a6. Looks good otherwise to me! |
| Comment by Brandon Nesterenko [ 2021-10-28 ] |
|
d155769 approved to push |
| Comment by Andrei Elkin [ 2021-10-28 ] |
|
To resolve conflicts at merging |
| Comment by Valerii Kravchuk [ 2021-11-10 ] |
|
Why don't we see this bug mentioned in the release notes and even changelogs for the versions where it is supposed to be fixed. It was a blocker! |
| Comment by Alice Sherepa [ 2021-11-10 ] |
|
valerii it is in changelogs in 10.2.41 https://mariadb.com/kb/en/mariadb-10241-changelog/ - and in 10.3+ it has "Includes all fixes from MariaDB 10.2.41" |