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

Feature Request: Convert information_schema.COLUMNS, information_schema.TABLES, ... to a Transactional Engine (Row-Lock, not Table-Lock)

Details

    • Task
    • Status: Closed (View Workflow)
    • Minor
    • Resolution: Won't Fix
    • N/A
    • N/A

    Description

      I would like to suggest that by default some of the mysql or information_schema myisam tables are converted to Transactional Engines (e.g: InnoDB or RocksDB), with Row-Lock (Not Table Lock).

      By default, they shall be InnoDB, but when loading RocksDB engine and disabling InnoDB Engine in my.ini, these could be automatically converted to RocksDB.

      Of particular interest are: information_schema.COLUMNS and information_schema.TABLES

      Thank you!

      Attachments

        Activity

          danblack Daniel Black added a comment -

          Information schema tables aren't really in an engine. Their contents get autopopulated by internal functions.

          Their appearance as an engine, Aria or MEMORY select TABLE_NAME, ENGINE from information_schema.TABLES where TABLE_SCHEMA='information_schema'; is an illusion.

          There are a couple of mysql tables that are innodb because transactional is needed. Other don't have the need for row lock (at least not one that people have strongly justified), or a MVCC model on the state of system tables would be problematic.

          When you disable a storage engine you cannot get data out of it, so auto-conversion isn't an option.

          danblack Daniel Black added a comment - Information schema tables aren't really in an engine. Their contents get autopopulated by internal functions. Their appearance as an engine, Aria or MEMORY select TABLE_NAME, ENGINE from information_schema.TABLES where TABLE_SCHEMA='information_schema'; is an illusion. There are a couple of mysql tables that are innodb because transactional is needed. Other don't have the need for row lock (at least not one that people have strongly justified), or a MVCC model on the state of system tables would be problematic. When you disable a storage engine you cannot get data out of it, so auto-conversion isn't an option.

          People

            Unassigned Unassigned
            Juan Juan Telleria
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Git Integration

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