Report Changes if relay log overwritten
Bug #712163 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 | Status tracked in 5.7 | |||||
| 5.1 |
Won't Fix
|
Wishlist
|
Unassigned | |||
| 5.5 |
Triaged
|
Wishlist
|
Unassigned | |||
| 5.6 |
Invalid
|
Undecided
|
Unassigned | |||
| 5.7 |
Invalid
|
Undecided
|
Unassigned | |||
Bug Description
Right now if overwriting relay log from transactional logs is enabled we get this:
InnoDB: Warning: innodb_
...
InnoDB: relay-log.info was overwritten.
This is not very helpful to check what values have been replaced with which. I would suggest to do either
1) Make it to display the changes done to relay-log.info
2) Make the copy of current relay-log.info which is overwritten so it is easy to validate if change was correct.
| Changed in percona-server: | |
| status: | New → Confirmed |
| importance: | Undecided → Wishlist |
| tags: | added: low-hanging-fruit |
| Changed in percona-server: | |
| status: | Confirmed → Triaged |
| tags: | added: crash-resistant-slave-5.5 |
Revision history for this message
| Shahriyar Rzayev (rzayev-sehriyar) wrote | #1 |
To post a comment you must log in.
Percona now uses JIRA for bug reports so this bug report is migrated to: https:/