mirror of
https://github.com/MariaDB/server.git
synced 2025-01-28 17:54:16 +01:00
c4cad8d50c
This task is to ensure we have a clear definition and rules of how to
repair or optimize a table.
The rules are:
- REPAIR should be used with tables that are crashed and are
unreadable (hardware issues with not readable blocks, blocks with
'unexpected data' etc)
- OPTIMIZE table should be used to optimize the storage layout for the
table (recover space for delete rows and optimize the index
structure.
- ALTER TABLE table_name FORCE should be used to rebuild the .frm file
(the table definition) and the table (with the original table row
format). If the table is from and older MariaDB/MySQL release with a
different storage format, it will convert the data to the new
format. ALTER TABLE ... FORCE is used as part of mariadb-upgrade
Here follows some more background:
The 3 ways to repair a table are:
1) ALTER TABLE table_name FORCE" (not other options).
As an alias we allow: "ALTER TABLE table_name ENGINE=original_engine"
2) "REPAIR TABLE" (without FORCE)
3) "OPTIMIZE TABLE"
All of the above commands will optimize row space usage (which means that
space will be needed to hold a temporary copy of the table) and
re-generate all indexes. They will also try to replicate the original
table definition as exact as possible.
For ALTER TABLE and "REPAIR TABLE without FORCE", the following will hold:
If the table is from an older MariaDB version and data conversion is
needed (for example for old type HASH columns, MySQL JSON type or new
TIMESTAMP format) "ALTER TABLE table_name FORCE, algorithm=COPY" will be
used.
The differences between the algorithms are
1) Will use the fastest algorithm the engine supports to do a full repair
of the table (except if data conversions are is needed).
2) Will use the storage engine internal REPAIR facility (MyISAM, Aria).
If the engine does not support REPAIR then
"ALTER TABLE FORCE, ALGORITHM=COPY" will be used.
If there was data incompatibilities (which means that FORCE was used)
then there will be a warning after REPAIR that ALTER TABLE FORCE is
still needed.
The reason for this is that REPAIR may be able to go around data
errors (wrong incompatible data, crashed or unreadable sectors) that
ALTER TABLE cannot do.
3) Will use the storage engine internal OPTIMIZE. If engine does not
support optimize, then "ALTER TABLE FORCE" is used.
The above will ensure that ALTER TABLE FORCE is able to
correct almost any errors in the row or index data. In case of
corrupted blocks then REPAIR possible followed by ALTER TABLE is needed.
This is important as mariadb-upgrade executes ALTER TABLE table_name
FORCE for any table that must be re-created.
Bugs fixed with InnoDB tables when using ALTER TABLE FORCE:
- No error for INNODB_DEFAULT_ROW_FORMAT=COMPACT even if row length
would be too wide. (Independent of innodb_strict_mode).
- Tables using symlinks will be symlinked after any of the above commands
(Independent of the setting of --symbolic-links)
If one specifies an algorithm together with ALTER TABLE FORCE, things
will work as before (except if data conversion is required as then
the COPY algorithm is enforced).
ALTER TABLE .. OPTIMIZE ALL PARTITIONS will work as before.
Other things:
- FORCE argument added to REPAIR to allow one to first run internal
repair to fix damaged blocks and then follow it with ALTER TABLE.
- REPAIR will not update frm_version if ha_check_for_upgrade() finds
that table is still incompatible with current version. In this case the
REPAIR will end with an error.
- REPAIR for storage engines that does not have native repair, like InnoDB,
is now using ALTER TABLE FORCE.
- REPAIR csv-table USE_FRM now works.
- It did not work before as CSV tables had extension list in wrong
order.
- Default error messages length for %M increased from 128 to 256 to not
cut information from REPAIR.
- Documented HA_ADMIN_XX variables related to repair.
- Added HA_ADMIN_NEEDS_DATA_CONVERSION to signal that we have to
do data conversions when converting the table (and thus ALTER TABLE
copy algorithm is needed).
- Fixed typo in error message (caused test changes).
116 lines
4.8 KiB
C
116 lines
4.8 KiB
C
#ifndef MYSYS_MY_HANDLER_ERRORS_INCLUDED
|
|
#define MYSYS_MY_HANDLER_ERRORS_INCLUDED
|
|
|
|
/* Copyright (c) 2008, 2013, Oracle and/or its affiliates.
|
|
Copyright (c) 2011, 2013, SkySQL Ab.
|
|
|
|
This program is free software; you can redistribute it and/or modify
|
|
it under the terms of the GNU General Public License as published by
|
|
the Free Software Foundation; version 2 of the License.
|
|
|
|
This program is distributed in the hope that it will be useful,
|
|
but WITHOUT ANY WARRANTY; without even the implied warranty of
|
|
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
|
|
GNU General Public License for more details.
|
|
|
|
You should have received a copy of the GNU General Public License
|
|
along with this program; if not, write to the Free Software Foundation,
|
|
Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1335 USA */
|
|
|
|
/*
|
|
Errors a handler can give you
|
|
*/
|
|
|
|
static const char *handler_error_messages[]=
|
|
{
|
|
/* 120 */
|
|
"Didn't find the key on read or update",
|
|
"Duplicate key on write or update",
|
|
"Internal (unspecified) error in handler",
|
|
"Someone has changed the row since it was read (even though the table was locked to prevent it)",
|
|
"Wrong index given to a function",
|
|
"Undefined handler error 125",
|
|
"Index is corrupted",
|
|
"Table file is corrupted",
|
|
"Out of memory in engine",
|
|
"Undefined handler error 129",
|
|
/* 130 */
|
|
"Incorrect file format",
|
|
"Command not supported by the engine",
|
|
"Old database file",
|
|
"No record read before update",
|
|
"Record was already deleted (or record file crashed)",
|
|
"No more room in record file",
|
|
"No more room in index file",
|
|
"No more records (read after end of file)",
|
|
"Unsupported extension used for table",
|
|
"Too big row",
|
|
/* 140 */
|
|
"Wrong create options",
|
|
"Duplicate unique key on write or update",
|
|
"Unknown character set used in table",
|
|
"Conflicting table definitions in sub-tables of MERGE table",
|
|
"Table is crashed and last repair failed",
|
|
"Table was marked as crashed and should be repaired",
|
|
"Lock timed out; Retry transaction",
|
|
"Lock table is full; Restart program with a larger lock table",
|
|
"Updates are not allowed under a read only transactions",
|
|
"Lock deadlock; Retry transaction",
|
|
/* 150 */
|
|
"Foreign key constraint is incorrectly formed",
|
|
"Cannot add a child row",
|
|
"Cannot delete a parent row",
|
|
"No savepoint with that name",
|
|
"Non unique key block size",
|
|
"The table does not exist in the storage engine",
|
|
"The table already existed in the storage engine",
|
|
"Could not connect to the storage engine",
|
|
"Unexpected null pointer found when using spatial index",
|
|
"The table changed in the storage engine",
|
|
/* 160 */
|
|
"There's no partition in the table for the given value",
|
|
"Row-based binary logging of row failed",
|
|
"Index needed in foreign key constraint",
|
|
"Upholding foreign key constraints would lead to a duplicate key error in some other table",
|
|
"Table needs to be upgraded before it can be used",
|
|
"Table is read only",
|
|
"Failed to get next auto increment value",
|
|
"Failed to set row auto increment value",
|
|
"Unknown (generic) error from engine",
|
|
"Record was not updated. New values were the same as original values",
|
|
/* 170 */
|
|
"It is not possible to log this statement",
|
|
"The event was corrupt, leading to illegal data being read",
|
|
"The table is of a new format not supported by this version",
|
|
"The event could not be processed. No other handler error happened",
|
|
"Fatal error during initialization of handler",
|
|
"File too short; Expected more data in file",
|
|
"Read page with wrong checksum",
|
|
"Too many active concurrent transactions",
|
|
"Record not matching the given partition set",
|
|
"Index column length exceeds limit",
|
|
/* 180 */
|
|
"Index corrupted",
|
|
"Undo record too big",
|
|
"Invalid InnoDB FTS Doc ID",
|
|
"Table is being used in foreign key check",
|
|
"Tablespace already exists",
|
|
"Too many columns",
|
|
"Row in wrong partition",
|
|
"Row is not visible by the current transaction",
|
|
"Operation was interrupted by end user (probably kill command?)",
|
|
"Disk full",
|
|
/* 190 */
|
|
"Incompatible key or row definition between the MariaDB .frm file and the information in the storage engine. You can try REPAIR TABLE ... USE_FRM possibly followed by ALTER TABLE ... FORCE or dump and restore the table to fix this",
|
|
"Too many words in a FTS phrase or proximity search",
|
|
"Table encrypted but decryption failed. This could be because correct encryption management plugin is not loaded, used encryption key is not available or encryption method does not match.",
|
|
"Foreign key cascade delete/update exceeds max depth",
|
|
"Tablespace is missing for a table",
|
|
"Sequence has been run out",
|
|
"Sequence values are conflicting",
|
|
"Error during commit",
|
|
"Cannot select partitions",
|
|
"Cannot initialize encryption. Check that all encryption parameters have been set"
|
|
};
|
|
|
|
#endif /* MYSYS_MY_HANDLER_ERRORS_INCLUDED */
|