Bug #119577 Read uncommitted isolation was not work in different transactions

Submitted:	19 Dec 2025 8:15
Reporter:	nie xueying	Email Updates:
Status:	Open	Impact on me:	None
Category:	MySQL Server: XA transactions	Severity:	S3 (Non-critical)
Version:	8.0.43	OS:	Linux
Assigned to:		CPU Architecture:	x86

Description:
Read uncommitted isolation was not work in different transactions. in one transaction, one record was deleted, this record can still be queried by another transition. If even this transaction is committed. 

How to repeat:
1. Data Preparation :

CREATE TABLE t (a INT PRIMARY KEY, b INT);
INSERT INTO t VALUES (1, 2);
INSERT INTO t VALUES (2, 4);

2. The detail operations for the bug:

/*TXN1*/ BEGIN;
SET SESSION TRANSACTION ISOLATION LEVEL READ UNCOMMITTED;
SELECT @@transaction_isolation;
/*TXN2*/ BEGIN;
SET SESSION TRANSACTION ISOLATION LEVEL READ UNCOMMITTED;
SELECT @@transaction_isolation;

/*TXN2*/ DELETE FROM t WHERE a = 1;
/*TXN1*/  SELECT * FROM t WHERE a = 1; /*This record for a=1 should be deleted as expected . however it is not , The query for a=1, b=2 was returned*/
/*TXN2*/  commit;
/*TXN1*/  SELECT * FROM t WHERE a = 1; /*This record for a=1 should be deleted as expected . however it is not , The query for a=1, b=2 was returned*/

Page generated in 0.047 sec. using MySQL 8.4.7-u6-cloud

Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.