Document SERIALIZABLE is not supported by PXC
Bug #1500551 reported by
Percona
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Percona XtraDB Cluster moved to https://jira.percona.com/projects/PXC |
Fix Released
|
Medium
|
Alexey Zhebel |
Bug Description
We need clearly document that SERIALIZABLE isolation level is not supported by Percona XtraDB Cluster 5.6. Plus we need to explain what
kind of locks are used when one specify SERIALIZABLE and run competing transactions on different nodes.
For 5.7 we need to disable (by default, but optionally enable) SERIALIZABLE level.
We need to document what practically it means for developers, that is what behavior will not work and propose workarounds
Changed in percona-xtradb-cluster: | |
status: | New → Confirmed |
description: | updated |
Changed in percona-xtradb-cluster: | |
assignee: | nobody → Hrvoje Matijakovic (hrvojem) |
Changed in percona-xtradb-cluster: | |
importance: | Undecided → High |
importance: | High → Medium |
Changed in percona-xtradb-cluster: | |
assignee: | Hrvoje Matijakovic (hrvojem) → Alexey Zhebel (alexey-zhebel) |
To post a comment you must log in.
This is documented as a PXC strict mode validation https:/ /www.percona. com/doc/ percona- xtradb- cluster/ LATEST/ features/ pxc-strict- mode.html# explicit- table-locking