mirror of
https://github.com/MariaDB/server.git
synced 2026-05-04 14:15:33 +02:00
Bug #13933132: [ERROR] GOT ERROR -1 WHEN READING TABLE APPEARED
WHEN KILLING Suppose there is a query waiting for a lock. If the user kills this query, then "Got error -1 when reading table" error message must not be logged in the server log file. Since this is a user requested interruption, no spurious error message must be logged in the server log. This patch will remove the error message from the log. approved by joh and tatjana
This commit is contained in:
parent
2ebd927ec0
commit
a28a2ca798
2 changed files with 3 additions and 1 deletions
|
|
@ -11791,7 +11791,8 @@ int report_error(TABLE *table, int error)
|
|||
Locking reads can legally return also these errors, do not
|
||||
print them to the .err log
|
||||
*/
|
||||
if (error != HA_ERR_LOCK_DEADLOCK && error != HA_ERR_LOCK_WAIT_TIMEOUT)
|
||||
if (error != HA_ERR_LOCK_DEADLOCK && error != HA_ERR_LOCK_WAIT_TIMEOUT
|
||||
&& !table->in_use->killed)
|
||||
sql_print_error("Got error %d when reading table '%s'",
|
||||
error, table->s->path.str);
|
||||
table->file->print_error(error,MYF(0));
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue