Monty 3691cc1575 MDEV-18187 Aria engine: Redo phase failed with "error 192 when executing record redo_index_new_page" upon startup on a restored datadir ... The issue is that when recovery is about to create a new data or index page it check if the page already exits. If the page does not exists (file is too short) or contains wrong checksum, then the recovery code will recreate the page. The bug was that the code that checked if the page existed didn't take into account encrypted pages. Fixed by adding a check if page could not be encrypted solved the issue. I also added some code to silence decryption errors for new pages. Test case and some inspiration for how to solve this come from the pull request by alexandr.miloslavsky		2021-12-15 16:28:01 +02:00
..
alter_table.result
lock_tables_big.result	This is the downport of	2009-09-11 22:26:35 +02:00
maria_recover_encrypted.result	MDEV-18187 Aria engine: Redo phase failed with "error 192 when executing record redo_index_new_page" upon startup on a restored datadir	2021-12-15 16:28:01 +02:00
rpl_slave_net_timeout.result	MDEV-15253: Default optimizer setting changes for MariaDB 10.4	2018-12-09 09:22:00 +05:30