Implement COMMIT SYNC/DELAYED
Bug #590289 reported by
Peter Zaitsev
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Percona Server moved to https://jira.percona.com/projects/PS |
Won't Fix
|
Wishlist
|
Unassigned | ||
5.5 |
Won't Fix
|
Wishlist
|
Unassigned |
Bug Description
Currently one can define global commit type with innodb_
In practice however in applications there are different level of durability needed for different transactions - for example money transfer may require durability while in the same system update of view counter does not need one
We could implement COMMIT SYNC and COMMIT DELAYED to force given transaction commit as values 0 (or 2) and 1 independent on global setting.
Changed in percona-server: | |
status: | New → Confirmed |
importance: | Undecided → Wishlist |
Changed in percona-server: | |
milestone: | 5.5-20beta → none |
Changed in percona-server: | |
assignee: | Alexey Kopytov (akopytov) → nobody |
Changed in percona-server: | |
status: | Triaged → Won't Fix |
To post a comment you must log in.
Assigned to Alexey to implement for 5.5