[MDEV-17794] Do not assign persistent ID for temporary tables - Jira

XML

Word

Printable

Details

Type: Bug
Status: Closed (View Workflow)
Priority: Major
Resolution: Fixed
Affects Version/s: 10.2.2, 10.3.0, 10.4.0
Fix Version/s: 10.4.1
Component/s: Storage Engine - InnoDB
Labels:
- performance
- temporary

Description

InnoDB in MySQL 5.7 introduced two new parameters to the function dict_hdr_get_new_id(), to allow redo logging to be disabled when assigning identifiers to temporary tables or during the backup-unfriendly TRUNCATE TABLE that was replaced in MariaDB by ~~MDEV-13564~~.

Now that MariaDB 10.4.0 removed the crash recovery code for the backup-unfriendly TRUNCATE, one of the two added parameters is constant disable_redo=false.

In MariaDB 10.4, we should use a separate ID pool for temporary tables, and we should be able to assign a constant dummy index ID for indexes of temporary tables.

Attachments

Issue Links

blocks

MDEV-17805 Do not add temporary tables to dict_sys->table_hash

Stalled

relates to

MDEV-19513 Allocate dict_sys statically

Closed

MDEV-26636 Race conditions due to attempted updates of InnoDB defragmentation statistics for temporary tables

Closed

MDEV-13564 TRUNCATE TABLE and undo tablespace truncation are not compatible with Mariabackup

Closed

MDEV-24940 dict_hdr_get_new_id() changes table id in dictionary header, but does not write log record for it

Open

Activity

People

Assignee:: Marko Mäkelä

Reporter:: Marko Mäkelä

Votes:: 0 Vote for this issue

Watchers:: 2 Start watching this issue

Dates

Created:: 2018-11-22 08:18

Updated:: 2021-09-18 07:55

Resolved:: 2018-11-22 14:01

Time Tracking

Estimated:

Not Specified

Remaining:

Logged:

5.5h

Git Integration

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