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

Remove trx_sys_t::rw_trx_list

    XMLWordPrintable

Details

    Description

      rw_trx_list contains ACTIVE, PREPARED and recovered COMMITTED transactions.
      Move recovered COMMITTED transactions to purge_list.
      ACTIVE and PREPARED transactions are already available through rw_trx_hash.

      Aim of this task is to improve scalability.

      Attachments

        Issue Links

          causes

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. MDEV-22680 InnoDB trx_sys improvements

          • Major - Major loss of function.
          • Open
          relates to

          Bug - A problem which impairs or prevents the functions of the product. MDEV-8851 innodb.innodb_information_schema fails sporadically in buildbot

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

          Bug - A problem which impairs or prevents the functions of the product. MDEV-21390 lock_print_info_summary() should work even when trx_sys.mutex is locked

          • Major - Major loss of function.
          • Closed

          Activity

            People

              svoj Sergey Vojtovich
              svoj Sergey Vojtovich
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0d
                  0d
                  Logged:
                  Time Spent - 16d 3h
                  16d 3h

                  Git Integration

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