[MDEV-28752] Rollback of RENAME is broken if innodb_file_per_table=0 - Jira

Details

Type: Bug
Status: Closed (View Workflow)
Priority: Major
Resolution: Fixed
Affects Version/s: 10.8.0, 10.6.1, 10.7.0, 10.9.0
Fix Version/s: 10.6.9, 10.7.5, 10.8.4, 10.9.2
Component/s: Storage Engine - InnoDB
Labels:
- regression-10.6

Description

In ~~MDEV-25524~~, the logic of rolling back RENAME operations was broken for tables that are stored in the system tablespace (created while the non-default setting innodb_file_per_table=0 was in effect). Any rename operations in the file system (dict_table_t::rename_tablespace()) are only applicable to tables that are stored in .ibd files.

Attachments

Issue Links

is caused by

MDEV-25524 AddressSanitizer: heap-use-after-free in fil0fil.cc:2074 in fil_space_t::rename(char const*, bool, bool)

Closed

Activity

There are no comments yet on this issue.

People

Assignee:: Marko Mäkelä

Reporter:: Marko Mäkelä

Votes:: 0 Vote for this issue

Watchers:: 1 Start watching this issue

Dates

Created:: 2022-06-06 06:58

Updated:: 2022-06-06 14:57

Resolved:: 2022-06-06 14:57

Git Integration

Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.

MariaDB Server