[MDEV-17794] Do not assign persistent ID for temporary tables Created: 2018-11-22  Updated: 2021-09-18  Resolved: 2018-11-22

Status: Closed
Project: MariaDB Server
Component/s: Storage Engine - InnoDB
Affects Version/s: 10.2.2, 10.3.0, 10.4.0
Fix Version/s: 10.4.1

Type: Bug Priority: Major
Reporter: Marko Mäkelä Assignee: Marko Mäkelä
Resolution: Fixed Votes: 0
Labels: performance, temporary

Issue Links:
Blocks
blocks MDEV-17805 Do not add temporary tables to dict_s... Stalled
Relates
relates to MDEV-19513 Allocate dict_sys statically Closed
relates to MDEV-26636 Race conditions due to attempted upda... Closed
relates to MDEV-13564 TRUNCATE TABLE and undo tablespace tr... Closed
relates to MDEV-24940 dict_hdr_get_new_id() changes table i... Open

 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.
Generated at Thu Feb 08 08:39:09 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.