[MDEV-6630] make aria_used_for_temp_tables a modifiable variable Created: 2014-08-22  Updated: 2023-11-30

Status: Open
Project: MariaDB Server
Component/s: None
Fix Version/s: None

Type: New Feature Priority: Critical
Reporter: Sergei Golubchik Assignee: Michael Widenius
Resolution: Unresolved Votes: 9
Labels: None

Issue Links:
Relates
relates to MDEV-6538 aria_used_for_temp_tables cannot be s... Closed

 Description   

Currently aria_used_for_temp_tables is set at compilation time and cannot be changed later. See MDEV-6538 for a description of why it might be useful to make it modifiable (even if only on startup, not run-time).

 Comments   
Comment by Venâncio Ferreira [ 2017-02-16 ]

Hello,

Any news if there is any expectation for this change to be added to MariaDB 10.2?

Regards

Comment by Valerii Kravchuk [ 2020-09-17 ]

There are many bugs related to crashes with Aria temporary tables, Without this feature we do not have a workaround for them.

Comment by Michael Widenius [ 2022-03-22 ]

Why would anyone want to have this changed?
The only options are MyISAM and Aria and only Aria supports encrypted keys.
In addition, thanks to the row caching, Aria is in most cases faster than MyISAM.

I am not aware of a single bug related to crashing temporary tables. If such exists, they should be prioritized and fixed.
Changing to use MyISAM at this point is likely to lead to even more problems. This is not something that is easily configurable run time,
but a compilation option.

Comment by Valerii Kravchuk [ 2022-03-22 ]

What about these:

MDEV-10387
MDEV-26005
MDEV-27225
MDEV-8325
MDEV-28023
MDEV-19318
MDEV-23297

Are you sure none of these applies to implicitly created Aria temporary tables? Why not to give those affected a usable workaround?

Generated at Thu Feb 08 07:13:21 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.