Docs for the log archiving feature are incorrect
Bug #1227611 reported by
Alexey Kopytov
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Percona Server moved to https://jira.percona.com/projects/PS |
Fix Released
|
Medium
|
Hrvoje Matijakovic | ||
| 5.1 |
Invalid
|
Undecided
|
Unassigned | ||
| 5.5 |
Invalid
|
Undecided
|
Unassigned | ||
| 5.6 |
Fix Released
|
Medium
|
Hrvoje Matijakovic | ||
Bug Description
I know that the log archiving documentation is incomplete, but the following statements from http://
"When log archiving is enabled, instead of rotating through log files, XtraDB will create a new one."
It doesn't do log archiving instead of rotating through log files (i.e. normal redo log writing), but it duplicates all redo log writes in a separate set of files in addition to normal redo log writing, creating new files as necessary.
"There will always be one spare log file so that transactions are never stalled at log file rotation."
That was a part of the initial implementation, but does no longer apply.
Related branches
lp:~hrvojem/percona-server/bug1227611-5.6
- Laurynas Biveinis (community): Approve
-
Diff: 172 lines (+107/-2)5 files modifieddoc/source/changed_in_56.rst (+6/-1)
doc/source/flexibility/extended_select_into_outfile.rst (+17/-0)
doc/source/index.rst (+2/-0)
doc/source/management/log_archiving.rst (+6/-1)
doc/source/management/statement_timeout.rst (+76/-0)
| tags: | added: doc |
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:/