Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-6630

make aria_used_for_temp_tables a modifiable variable

Details

    • New Feature
    • Status: Open (View Workflow)
    • Critical
    • Resolution: Unresolved
    • None
    • None
    • None

    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).

      Attachments

        Issue Links

          relates to

          Bug - A problem which impairs or prevents the functions of the product. MDEV-6538 aria_used_for_temp_tables cannot be set via my.cnf or my.ini file

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Closed

          Activity

            Ascending order - Click to sort in descending order
            Venâncio Ferreira Venâncio Ferreira added a comment -

            Hello,

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

            Regards

            Venâncio Ferreira Venâncio Ferreira added a comment - Hello, Any news if there is any expectation for this change to be added to MariaDB 10.2? Regards
            valerii Valerii Kravchuk added a comment -

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

            valerii Valerii Kravchuk added a comment - There are many bugs related to crashes with Aria temporary tables, Without this feature we do not have a workaround for them.
            monty Michael Widenius added a comment -

            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.

            monty Michael Widenius added a comment - 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.
            valerii Valerii Kravchuk added a comment - - edited

            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?

            valerii Valerii Kravchuk added a comment - - edited 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?

            People

              Unassigned Unassigned
              serg Sergei Golubchik
              Votes:
              9 Vote for this issue
              Watchers:
              16 Start watching this issue

              Dates

                Created:
                Updated:

                Git Integration

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