mirror of
https://github.com/MariaDB/server.git
synced 2025-01-31 11:01:52 +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.
|
||
|---|---|---|
| .. | ||
| buf0buddy.cc | ||
| buf0buf.cc | ||
| buf0checksum.cc | ||
| buf0dblwr.cc | ||
| buf0dump.cc | ||
| buf0flu.cc | ||
| buf0lru.cc | ||
| buf0mtflu.cc | ||
| buf0rea.cc | ||