mirror of
https://github.com/MariaDB/server.git
synced 2025-01-28 01:34:17 +01:00
7e916bb86f
Analysis: Problem was that in fil_read_first_page we do find that table has encryption information and that encryption service or used key_id is not available. But, then we just printed fatal error message that causes above assertion. Fix: When we open single table tablespace if it has encryption information (crypt_data) store this crypt data to the table structure. When we open a table and we find out that tablespace is not available, check has table a encryption information and from there is encryption service or used key_id is not available. If it is, add additional warning for SQL-layer. |
||
---|---|---|
.. | ||
aria_tiny.result | ||
create_or_replace.result | ||
debug_key_management.result | ||
encrypt_and_grep.result | ||
encryption_force.result | ||
filekeys_encfile.result | ||
filekeys_encfile_bad.result | ||
filekeys_encfile_badfile.result | ||
filekeys_encfile_file.result | ||
filekeys_encfile_no.result | ||
filekeys_nofile.result | ||
filekeys_syntax.result | ||
filekeys_unencfile.result | ||
innodb-bad-key-change.result | ||
innodb-encr-threads.result | ||
innodb-page_encryption-32k.result | ||
innodb-page_encryption.result | ||
innodb-page_encryption_compression.result | ||
innodb-page_encryption_log_encryption.result | ||
innodb_encryption-page-compression.result | ||
innodb_encryption.result | ||
innodb_encryption_tables.result | ||
innodb_first_page.result | ||
innodb_page_encryption_key_change.result | ||
innodb_scrub.result | ||
innodb_scrub_background.result | ||
innodb_scrub_compressed.result | ||
tempfiles.result |