Monty 3d241eb948 Improve error reporting in Aria ... This patch fixes the following issues in Aria error reporting in case of read errors & crashed tables: - Added the table name to the most error messages, including in case of read errors or when encrypting/decrypting a table. The format for error messages was changed sligtly to accomodate logging of errors from lower level routines. - If we got an read error from storage (hard disk, ssd, S3 etc) we only reported 'table is crashed'. Now the error number from the storage is reported. - Added checking of read failure from records_in_range() - Calls to ma_set_fatal_error() did not inform the SQL level of errors (to not spam the user with multiple error messages). Now the first error message and any fatal error messages are reported to the user.		2022-06-07 20:43:11 +03:00
..
archive
atomic
binlog
binlog_encryption
client
compat
csv
encryption	MDEV-13542: Crashing on corrupted page is unhelpful	2022-06-06 14:03:22 +03:00
engines
federated
funcs_1
funcs_2
galera
galera_3nodes
galera_3nodes_sr
galera_sr
gcol
handler
heap
innodb	MDEV-25506 fixup: Wait for TRUNCATE recovery	2022-06-07 10:53:33 +03:00
innodb_fts
innodb_gis
innodb_i_s
innodb_zip	MDEV-13542: Crashing on corrupted page is unhelpful	2022-06-06 14:03:22 +03:00
jp
json
large_tests
maria	Improve error reporting in Aria	2022-06-07 20:43:11 +03:00
mariabackup
mtr/t
mtr2
multi_source
optimizer_unfixed_bugs
parts
perfschema
perfschema_stress
period
plugins
roles
rpl
s3
sql_sequence
storage_engine
stress
sys_vars
sysschema
unit
vcol
versioning
wsrep