[DOC] Missing allowed values explanation for innodb_corrupt_table_action variable
Bug #1025705 reported by
Volans
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.5 |
Fix Released
|
Medium
|
Hrvoje Matijakovic | ||
Bug Description
[In:Percona Server Documentation]
In the "Handle Corrupted Tables" ( http://
Please provide a detailed explanation of different behaviour of InnoDB corrupted tables for the "assert" and "warn" values.
Related branches
lp:~hrvojem/percona-server/bug1031410-5.5
- Laurynas Biveinis (community): Approve
-
Diff: 65 lines (+10/-10)3 files modifieddoc/source/diagnostics/slow_extended_55.rst (+4/-4)
doc/source/reliability/innodb_corrupt_table_action.rst (+1/-1)
doc/source/scalability/innodb_insert_buffer.rst (+5/-5)
Revision history for this message
| Raghavendra D Prabhu (raghavendra-prabhu) wrote | #1 |
Revision history for this message
| Laurynas Biveinis (laurynas-biveinis) wrote | #2 |
Revision history for this message
| Volans (volans) wrote | #3 |
Revision history for this message
| Laurynas Biveinis (laurynas-biveinis) wrote | #4 |
Revision history for this message
| Shahriyar Rzayev (rzayev-sehriyar) wrote | #5 |
To post a comment you must log in.
1. Basically assert is 0 (default behavior, to crash) and warn is 1 (warn and disable).
2. Actually there is another value - salvage
=====
const char *corrupt_
{
"assert", /* 0 */
"warn", /* 1 */
"salvage", /* 2 */
NullS
};
=====
From the code I have seen it looks like 'salvage' filters writes (in _fil_io) or to skip a corrupted record (in row_search_