Details
-
Task
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
None
Description
#3067 and the new parameter innodb_snapshot_isolation need to be documented. The documentation of transaction isolation levels should mention that anything else than READ UNCOMMITTED is not clearly defined unless innodb_snapshot_isolation=ON. With that setting, REPEATABLE READ is Snapshot Isolation.
See also MDEV-29565
Attachments
Issue Links
- relates to
-
MDEV-32898 Phantom rows caused by UPDATE of PRIMARY KEY
-
- Closed
-
Activity
| Field | Original Value | New Value |
|---|---|---|
| Link |
This issue relates to |
| Description | #3067 and the new parameter innodb_snapshot_isolation need to be documented. The documentation of transaction isolation levels should mention that anything else than READ UNCOMMITTED is not clearly defined unless innodb_snapshot_isolation=ON. With that setting, REPEATABLE READ is Snapshot Isolation. |
#3067 and the new parameter innodb_snapshot_isolation need to be documented. The documentation of transaction isolation levels should mention that anything else than READ UNCOMMITTED is not clearly defined unless innodb_snapshot_isolation=ON. With that setting, REPEATABLE READ is Snapshot Isolation.
See also |
| Resolution | Fixed [ 1 ] | |
| Status | Open [ 1 ] | Closed [ 6 ] |