Details
-
Bug
-
Status: In Review (View Workflow)
-
Major
-
Resolution: Unresolved
-
25.10.4, 26.10.0
-
None
-
None
Description
Executing SET SESSION TRANSACTION READ ONLY and turning off autocommit breaks the transaction boundary detection and all statements done inside it are treated as if they were outside of a transaction. The transaction remains in read-only mode on all connections but the statements are not necessarily routed to the same backend, like they should be, which breaks transactionality and different states of the database can be observed inside of a single transaction which is wrong under certain isolation modes.
SET SESSION TRANSACTION READ ONLY; |
SET autocommit=0; |
SELECT @@server_id; -- This is not considered to be inside of a transaction |