mirror of
https://github.com/MariaDB/server.git
synced 2025-01-26 16:54:15 +01:00
b9f5793176
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
119 lines
4.9 KiB
C
119 lines
4.9 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",
|
|
/* 200 */
|
|
"Local temporary space limit reached",
|
|
"Global temporary space limit reached"
|
|
};
|
|
|
|
#endif /* MYSYS_MY_HANDLER_ERRORS_INCLUDED */
|