2009-09-23 23:32:31 +02:00
# ifndef MYSYS_MY_HANDLER_ERRORS_INCLUDED
# define MYSYS_MY_HANDLER_ERRORS_INCLUDED
2008-03-28 18:45:03 +02:00
2013-11-28 12:10:44 +01:00
/* Copyright (c) 2008, 2013, Oracle and/or its affiliates.
Copyright ( c ) 2011 , 2013 , SkySQL Ab .
2011-06-30 17:37:13 +02:00
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
2012-02-27 17:23:56 +05:30
along with this program ; if not , write to the Free Software Foundation ,
2019-05-11 18:08:32 +03:00
Inc . , 51 Franklin Street , Fifth Floor , Boston , MA 02110 - 1335 USA */
2008-03-28 18:45:03 +02:00
/*
Errors a handler can give you
*/
static const char * handler_error_messages [ ] =
{
2016-09-10 16:04:44 +02:00
/* 120 */
2017-09-15 15:05:39 +02:00
" Didn't find the key on read or update " ,
2008-03-28 18:45:03 +02:00
" Duplicate key on write or update " ,
" Internal (unspecified) error in handler " ,
2017-09-15 15:05:39 +02:00
" Someone has changed the row since it was read (even though the table was locked to prevent it) " ,
" Wrong index given to a function " ,
2008-03-28 18:45:03 +02:00
" Undefined handler error 125 " ,
2016-09-10 16:04:44 +02:00
" Index is corrupted " ,
" Table file is corrupted " ,
2008-03-28 18:45:03 +02:00
" Out of memory in engine " ,
" Undefined handler error 129 " ,
2016-09-10 16:04:44 +02:00
/* 130 */
2008-03-28 18:45:03 +02:00
" Incorrect file format " ,
2017-09-15 15:05:39 +02:00
" Command not supported by the engine " ,
2008-03-28 18:45:03 +02:00
" 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 " ,
2016-09-10 16:04:44 +02:00
/* 140 */
2008-03-28 18:45:03 +02:00
" Wrong create options " ,
2017-09-15 15:05:39 +02:00
" Duplicate unique key on write or update " ,
2008-03-28 18:45:03 +02:00
" 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 " ,
2008-04-29 09:26:37 +03:00
" Lock table is full; Restart program with a larger lock table " ,
2008-03-28 18:45:03 +02:00
" Updates are not allowed under a read only transactions " ,
" Lock deadlock; Retry transaction " ,
2016-09-10 16:04:44 +02:00
/* 150 */
2008-03-28 18:45:03 +02:00
" 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 " ,
2017-09-15 15:05:39 +02:00
" The table does not exist in the storage engine " ,
" The table already existed in the storage engine " ,
" Could not connect to the storage engine " ,
2008-03-28 18:45:03 +02:00
" Unexpected null pointer found when using spatial index " ,
2017-09-15 15:05:39 +02:00
" The table changed in the storage engine " ,
2016-09-10 16:04:44 +02:00
/* 160 */
2017-09-15 15:05:39 +02:00
" There's no partition in the table for the given value " ,
2008-04-29 09:26:37 +03:00
" Row-based binary logging of row failed " ,
2008-03-28 18:45:03 +02:00
" Index needed in foreign key constraint " ,
2011-10-19 21:45:18 +02:00
" Upholding foreign key constraints would lead to a duplicate key error in some other table " ,
2008-03-28 18:45:03 +02:00
" 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 " ,
2017-09-15 15:05:39 +02:00
" Record was not updated. New values were the same as original values " ,
2016-09-10 16:04:44 +02:00
/* 170 */
2008-03-28 18:45:03 +02:00
" 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 " ,
2008-05-29 23:56:27 +03:00
" The event could not be processed. No other handler error happened " ,
2017-09-15 15:05:39 +02:00
" Fatal error during initialization of handler " ,
2008-04-29 09:26:37 +03:00
" File too short; Expected more data in file " ,
2009-07-24 12:15:06 +05:30
" Read page with wrong checksum " ,
2009-09-08 00:50:10 +04:00
" Too many active concurrent transactions " ,
2012-05-30 00:37:55 +03:00
" Record not matching the given partition set " ,
2011-07-02 22:12:12 +02:00
" Index column length exceeds limit " ,
2016-09-10 16:04:44 +02:00
/* 180 */
2011-09-01 21:48:04 +03:00
" Index corrupted " ,
2011-11-03 19:17:05 +01:00
" Undo record too big " ,
2012-05-30 00:37:55 +03:00
" Invalid InnoDB FTS Doc ID " ,
2013-03-26 00:03:13 +02:00
" Table is being used in foreign key check " ,
" Tablespace already exists " ,
" Too many columns " ,
2013-11-28 12:10:44 +01:00
" Row in wrong partition " ,
Fix for lp:711565 "Index Condition Pushdown can make a thread hold MyISAM locks as well as be unKILLable for long time"
- In Maria/MyISAM: Release/re-acquire locks to give queries that wait on them a chance to make progress
- In Maria/MyISAM: Change from numeric constants to ICP_RES values.
- In Maria: Do check index condition in maria_rprev() (was lost in the merge/backport?)
- In Maria/MyISAM/XtraDB: Check if the query was killed, and return immediately if it was.
Added new storage engine error: HA_ERR_ABORTED_BY_USER, for handler to signal that it detected a kill of the query and aborted
Authors: Sergey Petrunia & Monty
include/my_base.h:
Added HA_ERR_ABORTED_BY_USER, for handler to signal that it detected a kill of the query and aborted
include/my_handler.h:
Added comment
mysql-test/r/myisam_icp.result:
Updated test
mysql-test/t/myisam_icp.test:
Drop used tables at start of test
Added test case that can help with manual testing of killing index condition pushdown query.
mysys/my_handler_errors.h:
Text for new storage engine error
sql/handler.cc:
If engine got HA_ERR_ABORTED_BY_USER, send kill message.
sql/multi_range_read.cc:
Return error code
storage/maria/ha_maria.cc:
Added ma_killed_in_mariadb() to detect kill.
Ensure that file->external_ref points to TABLE object.
storage/maria/ma_extra.c:
Dummy test-if-killed for standalone
storage/maria/ma_key.c:
If ma_check_index_cond() fails, set my_errno and info->cur_row.lastpos
storage/maria/ma_rkey.c:
Release/re-acquire locks to give queries that wait on them a chance to make progress
Check if the query was killed, and return immediately if it was
storage/maria/ma_rnext.c:
Check if the query was killed, and return immediately if it was
Added missing fast_ma_writeinfo(info)
storage/maria/ma_rnext_same.c:
Check if the query was killed, and return immediately if it was
Added missing fast_ma_writeinfo(info)
storage/maria/ma_rprev.c:
Check if the query was killed, and return immediately if it was
Added missing fast_ma_writeinfo(info) and ma_check_index_cond()
storage/maria/ma_search.c:
Give error message if we find a wrong key
storage/maria/ma_static.c:
Added pointer to test-if-killed function
storage/maria/maria_def.h:
New prototypes
storage/myisam/ha_myisam.cc:
Added mi_killed_in_mariadb()
Ensure that file->external_ref points to TABLE object.
storage/myisam/mi_extra.c:
Dummy test-if-killed for standalone
storage/myisam/mi_key.c:
If ma_check_index_cond() fails, set my_errno and info->lastpos
storage/myisam/mi_rkey.c:
Ensure that info->lastpos= HA_OFFSET_ERROR in case of error
Release/re-acquire locks to give queries that wait on them a chance to make progress
Check if the query was killed, and return immediately if it was
Reorder code to do less things in case of error.
Added missing fast_mi_writeinfo()
storage/myisam/mi_rnext.c:
Check if the query was killed, and return immediately if it was
Simplify old ICP code
Added missing fast_ma_writeinfo(info)
storage/myisam/mi_rnext_same.c:
Check if the query was killed, and return immediately if it was
Added missing fast_mi_writeinfo(info)
storage/myisam/mi_rprev.c:
Check if the query was killed, and return immediately if it was
Simplify error handling of ICP
Added missing fast_mi_writeinfo(info)
storage/myisam/mi_search.c:
Give error message if we find a wrong key
storage/myisam/mi_static.c:
Added pointer to test-if-killed function
storage/myisam/myisamdef.h:
New prototypes
storage/xtradb/handler/ha_innodb.cc:
Added DB_SEARCH_ABORTED_BY_USER and ha_innobase::is_thd_killed()
Check if the query was killed, and return immediately if it was
storage/xtradb/handler/ha_innodb.h:
Added prototype
storage/xtradb/include/db0err.h:
Added DB_SEARCH_ABORTED_BY_USER
storage/xtradb/include/row0mysql.h:
Added possible ICP errors
storage/xtradb/row/row0sel.c:
Use ICP errors instead of constants.
Detect if killed and return B_SEARCH_ABORTED_BY_USER
2011-02-18 17:43:59 +02:00
" Row is not visible by the current transaction " ,
2011-05-18 13:36:12 +03:00
" Operation was interrupted by end user (probably kill command?) " ,
2014-01-22 15:16:57 +02:00
" Disk full " ,
2016-09-10 16:04:44 +02:00
/* 190 */
MDEV-33449 improving repair of tables
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).
2024-01-29 11:52:44 +02:00
" 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 " ,
2015-09-14 08:27:14 +03:00
" Too many words in a FTS phrase or proximity search " ,
2016-09-06 09:43:16 +03:00
" 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 " ,
2017-09-20 17:47:49 +03:00
" Tablespace is missing for a table " ,
MDEV-10139 Support for SEQUENCE objects
Working features:
CREATE OR REPLACE [TEMPORARY] SEQUENCE [IF NOT EXISTS] name
[ INCREMENT [ BY | = ] increment ]
[ MINVALUE [=] minvalue | NO MINVALUE ]
[ MAXVALUE [=] maxvalue | NO MAXVALUE ]
[ START [ WITH | = ] start ] [ CACHE [=] cache ] [ [ NO ] CYCLE ]
ENGINE=xxx COMMENT=".."
SELECT NEXT VALUE FOR sequence_name;
SELECT NEXTVAL(sequence_name);
SELECT PREVIOUS VALUE FOR sequence_name;
SELECT LASTVAL(sequence_name);
SHOW CREATE SEQUENCE sequence_name;
SHOW CREATE TABLE sequence_name;
CREATE TABLE sequence-structure ... SEQUENCE=1
ALTER TABLE sequence RENAME TO sequence2;
RENAME TABLE sequence TO sequence2;
DROP [TEMPORARY] SEQUENCE [IF EXISTS] sequence_names
Missing features
- SETVAL(value,sequence_name), to be used with replication.
- Check replication, including checking that sequence tables are marked
not transactional.
- Check that a commit happens for NEXT VALUE that changes table data (may
already work)
- ALTER SEQUENCE. ANSI SQL version of setval.
- Share identical sequence entries to not add things twice to table list.
- testing insert/delete/update/truncate/load data
- Run and fix Alibaba sequence tests (part of mysql-test/suite/sql_sequence)
- Write documentation for NEXT VALUE / PREVIOUS_VALUE
- NEXTVAL in DEFAULT
- Ensure that NEXTVAL in DEFAULT uses database from base table
- Two NEXTVAL for same row should give same answer.
- Oracle syntax sequence_table.nextval, without any FOR or FROM.
- Sequence tables are treated as 'not read constant tables' by SELECT; Would
be better if we would have a separate list for sequence tables so that
select doesn't know about them, except if refereed to with FROM.
Other things done:
- Improved output for safemalloc backtrack
- frm_type_enum changed to Table_type
- Removed lex->is_view and replaced with lex->table_type. This allows
use to more easy check if item is view, sequence or table.
- Added table flag HA_CAN_TABLES_WITHOUT_ROLLBACK, needed for handlers
that want's to support sequences
- Added handler calls:
- engine_name(), to simplify getting engine name for partition and sequences
- update_first_row(), to be able to do efficient sequence implementations.
- Made binlog_log_row() global to be able to call it from ha_sequence.cc
- Added handler variable: row_already_logged, to be able to flag that the
changed row is already logging to replication log.
- Added CF_DB_CHANGE and CF_SCHEMA_CHANGE flags to simplify
deny_updates_if_read_only_option()
- Added sp_add_cfetch() to avoid new conflicts in sql_yacc.yy
- Moved code for add_table_options() out from sql_show.cc::show_create_table()
- Added String::append_longlong() and used it in sql_show.cc to simplify code.
- Added extra option to dd_frm_type() and ha_table_exists to indicate if
the table is a sequence. Needed by DROP SQUENCE to not drop a table.
2017-03-25 23:36:56 +02:00
" Sequence has been run out " ,
2021-09-15 19:18:11 +03:00
" Sequence values are conflicting " ,
2022-01-30 17:52:15 +01:00
" Error during commit " ,
2023-03-16 17:24:12 +02:00
" Cannot select partitions " ,
MDEV-9101 Limit size of created disk temporary files and tables
Two new variables added:
- max_tmp_space_usage : Limits the the temporary space allowance per user
- max_total_tmp_space_usage: Limits the temporary space allowance for
all users.
New status variables: tmp_space_used & max_tmp_space_used
New field in information_schema.process_list: TMP_SPACE_USED
The temporary space is counted for:
- All SQL level temporary files. This includes files for filesort,
transaction temporary space, analyze, binlog_stmt_cache etc.
It does not include engine internal temporary files used for repair,
alter table, index pre sorting etc.
- All internal on disk temporary tables created as part of resolving a
SELECT, multi-source update etc.
Special cases:
- When doing a commit, the last flush of the binlog_stmt_cache
will not cause an error even if the temporary space limit is exceeded.
This is to avoid giving errors on commit. This means that a user
can temporary go over the limit with up to binlog_stmt_cache_size.
Noteworthy issue:
- One has to be careful when using small values for max_tmp_space_limit
together with binary logging and with non transactional tables.
If a the binary log entry for the query is bigger than
binlog_stmt_cache_size and one hits the limit of max_tmp_space_limit
when flushing the entry to disk, the query will abort and the
binary log will not contain the last changes to the table.
This will also stop the slave!
This is also true for all Aria tables as Aria cannot do rollback
(except in case of crashes)!
One way to avoid it is to use @@binlog_format=statement for
queries that updates a lot of rows.
Implementation:
- All writes to temporary files or internal temporary tables, that
increases the file size, are routed through temp_file_size_cb_func()
which updates and checks the temp space usage.
- Most of the temporary file monitoring is done inside IO_CACHE.
Temporary file monitoring is done inside the Aria engine.
- MY_TRACK and MY_TRACK_WITH_LIMIT are new flags for ini_io_cache().
MY_TRACK means that we track the file usage. TRACK_WITH_LIMIT means
that we track the file usage and we give an error if the limit is
breached. This is used to not give an error on commit when
binlog_stmp_cache is flushed.
- global_tmp_space_used contains the total tmp space used so far.
This is needed quickly check against max_total_tmp_space_usage.
- Temporary space errors are using EE_LOCAL_TMP_SPACE_FULL and
handler errors are using HA_ERR_LOCAL_TMP_SPACE_FULL.
This is needed until we move general errors to it's own error space
so that they cannot conflict with system error numbers.
- Return value of my_chsize() and mysql_file_chsize() has changed
so that -1 is returned in the case my_chsize() could not decrease
the file size (very unlikely and will not happen on modern systems).
All calls to _chsize() are updated to check for > 0 as the error
condition.
- At the destruction of THD we check that THD::tmp_file_space == 0
- At server end we check that global_tmp_space_used == 0
- As a precaution against errors in the tmp_space_used code, one can set
max_tmp_space_usage and max_total_tmp_space_usage to 0 to disable
the tmp space quota errors.
- truncate_io_cache() function added.
- Aria tables using static or dynamic row length are registered in 8K
increments to avoid some calls to update_tmp_file_size().
Other things:
- Ensure that all handler errors are registered. Before, some engine
errors could be printed as "Unknown error".
- Fixed bug in filesort() that causes a assert if there was an error
when writing to the temporay file.
- Fixed that compute_window_func() now takes into account write errors.
- In case of parallel replication, rpl_group_info::cleanup_context()
could call trans_rollback() with thd->error set, which would cause
an assert. Fixed by resetting the error before calling trans_rollback().
- Fixed bug in subselect3.inc which caused following test to use
heap tables with low value for max_heap_table_size
- Fixed bug in sql_expression_cache where it did not overflow
heap table to Aria table.
- Added Max_tmp_disk_space_used to slow query log.
- Fixed some bugs in log_slow_innodb.test
2024-03-14 17:59:00 +01:00
" Cannot initialize encryption. Check that all encryption parameters have been set " ,
/* 200 */
" Local temporary space limit reached " ,
" Global temporary space limit reached "
2008-03-28 18:45:03 +02:00
} ;
2009-09-23 23:32:31 +02:00
# endif /* MYSYS_MY_HANDLER_ERRORS_INCLUDED */
