Time Back machine for Innodb
Bug #301925 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 |
Triaged
|
Wishlist
|
Unassigned | ||
| Percona patches |
Won't Fix
|
Wishlist
|
Unassigned | ||
Bug Description
Innodb has a feature of providing state of data as it was before so we can add functionality to fetch the data at the former stage.
In particular we can do something like:
- Add a variable to keep history
innodb_
Track history for 600 seconds. Only data older than that will be purged.
- Add the trxid to time mapping so we can understand where each trx belongs (optional)
- Add ability to recover to given trx-id on point in time recovery (all newer transactions will be rolled back)
NOTE: This can be a bit complicated as transactions do not commit in the order they are started.
- Add ability yo read the data at the given time/transaction id within history.
| Changed in percona-patches: | |
| importance: | Undecided → Wishlist |
| status: | New → Confirmed |
Revision history for this message
| Stewart Smith (stewart) wrote | #1 |
| Changed in percona-server: | |
| status: | New → Triaged |
| importance: | Undecided → Wishlist |
| Changed in percona-patches: | |
| status: | Confirmed → Won't Fix |
Revision history for this message
| Shahriyar Rzayev (rzayev-sehriyar) wrote | #2 |
To post a comment you must log in.
Development has moved to Percona Server.