Details
-
Bug
-
Status: Closed (View Workflow)
-
Critical
-
Resolution: Fixed
-
10.2, 10.3, 10.4, 10.5, 10.6, 10.7, 10.8, 10.9, 10.10, 10.11, 11.0, 11.1, 11.2, 11.3, 11.4, 11.2.2
-
Ubuntu 20.04
Description
How to repeat:
/* init */ CREATE TABLE t(a INT PRIMARY KEY, b INT UNIQUE); |
/* init */ INSERT INTO t(a) VALUES (1); |
/* t1 */ SET SESSION TRANSACTION ISOLATION LEVEL SERIALIZABLE; |
/* t2 */ SET SESSION TRANSACTION ISOLATION LEVEL SERIALIZABLE; |
 |
/* t1 */ BEGIN; |
/* t2 */ BEGIN; |
/* t1 */ INSERT INTO t(a) VALUES (2); |
/* t2 */ SELECT a, b FROM t WHERE TRUE; -- [(1, null), (1, null)] |
/* t1 */ ROLLBACK; |
/* t2 */ COMMIT; |
The SELECT statement of t2 was initially blocked by t1. Then it recovered after t1's ROLLBACK, but its query result contained two identical records (1, null). Interestingly, removing the UNIQUE constraint on column b eliminates this anomaly.
Attachments
Issue Links
- is blocked by
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
- is caused by
-
-
- Closed
-