[MDEV-30119] INFORMATION_SCHEMA.INNODB_TABLESPACES_ENCRYPTION.NAME is NULL for undo tablespaces Created: 2022-11-29 Updated: 2022-11-29 Resolved: 2022-11-29 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Storage Engine - InnoDB |
| Affects Version/s: | 10.6, 10.7, 10.8, 10.9, 10.10, 10.11 |
| Fix Version/s: | 10.11.2, 10.6.12, 10.7.8, 10.8.7, 10.9.5, 10.10.3 |
| Type: | Bug | Priority: | Blocker |
| Reporter: | Thirunarayanan Balathandayuthapani | Assignee: | Thirunarayanan Balathandayuthapani |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | regression-10.6 | ||
| Issue Links: |
|
||||||||||||||||
| Description |
|
marko encountered that few test cases in encryption and mariabackup suite are hanging
InnoDB:
Mariabackup:
Thanks to marko for finding out the test while working on |
| Comments |
| Comment by Marko Mäkelä [ 2022-11-29 ] |
|
Before To avoid dynamic allocation of strings, it could be better to introduce names like undo001, so that we can simply use a substring of the underlying file name. Regular tablespaces always contain a / in their names. |
| Comment by Marko Mäkelä [ 2022-11-29 ] |
|
In i_s_dict_fill_tablespaces_encryption(), could we allocate a buffer from the stack for the strings like innodb_undo001? In that way, the reported names for undo tablespaces would be the same as they were before |
| Comment by Marko Mäkelä [ 2022-11-29 ] |
|
OK to push. |