Details
-
Bug
-
Status: Open (View Workflow)
-
Major
-
Resolution: Unresolved
-
10.5
-
None
-
None
Description
In case of a rolled back mixed with sequence transaction the effect of the sequence's statement can not be undone. Extend sql_sequence.gtid test's block to see a mismatch
of the use sequence object state between the trx' start and its end times:
begin;
|
insert into t_1 values(3333);
|
select lastval(s_1) as "s_1's transaction start value";
|
+s_1's transaction start value
|
+2
|
insert into t_1 select next value for s_1;
|
...
|
rollback;
|
select lastval(s_1) as "s_1's actual value after rollback";
|
+s_1's actual value after rollback
|
+10
|
|
The correct behavior in the case is expected to display a warning
rollback;
|
+Warnings:
|
+Warning 1196 Some non-transactional changed tables couldn't be rolled back
|
The fixes are part of a broader MDEV-25488.
Attachments
Issue Links
- is part of
-
MDEV-25488 thd::transaction::modified_non_trans_tables isn't set before Rows_log_event caching
- In Progress