Details
-
Bug
-
Status: Closed (View Workflow)
-
Critical
-
Resolution: Fixed
-
10.5.12, 5.5(EOL), 10.0(EOL), 10.1(EOL), 10.2(EOL), 10.3(EOL), 10.4(EOL), 10.5, 10.6
-
OS: Ubuntu-20.04
Description
Under REPEATABLE-READ isolation level, if two transactions concurrently modify the same row to the same value, the transaction that modifies later does not see the modified content.
/* init */ create table t(a int, b int); |
/* init */ insert into t values (0, 0), (1, 1), (2, 2); |
|
/* s1 */ begin; |
/* s1 */ select * from t; -- [(0, 0), (1, 1), (2, 2)] |
/* s2 */ begin; |
/* s2 */ update t set a = 10 where b = 1; |
/* s2 */ commit; |
/* s1 */ select * from t; -- [(0, 0), (1, 1), (2, 2)] |
/* s1 */ update t set a = 10 where true; |
/* s1 */ select * from t; -- [(10, 0), (1, 1), (10, 2)] |
/* s1 */ commit; |
The result of final SELECT should be (10, 0), (10, 1), (10, 2).
I think it is so weird for session 1 to see the second row is still (1, 1) after the successful execution of an UPDATE with the "WHERE TRUE" predicate.
So I think it will be better for s1 to see all records it updates regardless of whether the values before and after the UPDATE are the same.
Attachments
Issue Links
- blocks
-
MDEV-33802 Weird read view after ROLLBACK of other transactions.
-
- Closed
-
- relates to
-
MDEV-32898 Phantom rows caused by UPDATE of PRIMARY KEY
-
- Closed
-
-
MDEV-35124 Set innodb_snapshot_isolation=ON by default
-
- Closed
-
-
MDEV-35262 INT violation when two transactions modify a record to the same value concurrently
-
- Open
-
-
MDEV-14589 InnoDB should not lock a delete-marked record
-
- Closed
-
-
MDEV-26643 Inconsistent behaviors of UPDATE under RU & RC isolation level
-
- Closed
-
-
MDEV-26671 Inconsistent SELECT View when modify a record added by another transaction
-
- Closed
-
-
MDEV-29565 Inconsistent read and write, which use the same predicate (WHERE clause)
-
- Closed
-
-
MDEV-35140 Support innodb-snapshot-isolation in Galera cluster
-
- Stalled
-
Activity
Field | Original Value | New Value |
---|---|---|
Labels | innodb need_feedback | innodb |
Epic/Theme | server |
Fix Version/s | 10.2 [ 14601 ] | |
Fix Version/s | 10.3 [ 22126 ] | |
Fix Version/s | 10.4 [ 22408 ] | |
Fix Version/s | 10.5 [ 23123 ] | |
Fix Version/s | 10.6 [ 24028 ] |
Affects Version/s | 5.5 [ 15800 ] | |
Affects Version/s | 10.0 [ 16000 ] | |
Affects Version/s | 10.1 [ 16100 ] | |
Affects Version/s | 10.2 [ 14601 ] | |
Affects Version/s | 10.3 [ 22126 ] | |
Affects Version/s | 10.4 [ 22408 ] | |
Affects Version/s | 10.5 [ 23123 ] | |
Affects Version/s | 10.6 [ 24028 ] |
Status | Open [ 1 ] | Confirmed [ 10101 ] |
Assignee | Marko Mäkelä [ marko ] |
Link |
This issue relates to |
Assignee | Marko Mäkelä [ marko ] | Ian Gilfillan [ greenman ] |
Link |
This issue relates to |
Link |
This issue relates to |
Workflow | MariaDB v3 [ 125161 ] | MariaDB v4 [ 144409 ] |
Fix Version/s | 10.2 [ 14601 ] |
Link |
This issue relates to |
Fix Version/s | 10.3 [ 22126 ] |
Link |
This issue relates to |
Fix Version/s | 10.6.18 [ 29627 ] | |
Fix Version/s | 10.11.8 [ 29630 ] | |
Fix Version/s | 11.0.6 [ 29628 ] | |
Fix Version/s | 11.2.4 [ 29631 ] | |
Fix Version/s | 11.4.2 [ 29633 ] | |
Fix Version/s | 10.4 [ 22408 ] | |
Fix Version/s | 10.5 [ 23123 ] | |
Fix Version/s | 10.6 [ 24028 ] | |
Assignee | Ian Gilfillan [ greenman ] | Marko Mäkelä [ marko ] |
Resolution | Fixed [ 1 ] | |
Status | Confirmed [ 10101 ] | Closed [ 6 ] |
Fix Version/s | 11.1.5 [ 29629 ] |
Link |
This issue blocks |
Link |
This issue relates to |
Link | This issue relates to MDEV-35262 [ MDEV-35262 ] |
Link | This issue relates to MDEV-35140 [ MDEV-35140 ] |