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

Implicit rollback by LOAD INDEX or CACHE INDEX should not touch prepared user XA

    XMLWordPrintable

Details

    • Bug
    • Status: Confirmed (View Workflow)
    • Major
    • Resolution: Unresolved
    • 10.4(EOL), 10.5, 10.6, 10.9(EOL), 10.10(EOL), 10.11, 11.0(EOL), 11.1(EOL), 11.2(EOL), 11.3(EOL)
    • 10.5, 10.6, 10.11
    • Server, XA

    Description

      Elaborated MDEV-32347 description test demonstrates how a prepared user XA transaction
      gets rolled back:

      CREATE TABLE ti (c INT KEY) engine=Innodb;
      XA START 'xid_i';
      INSERT INTO ti VALUES (1);
      XA END 'xid_i';
      XA PREPARE 'xid_i';
       
      # --error ER_XAER_RMFAIL
      LOAD INDEX INTO CACHE c KEY(PRIMARY);
       
      XA COMMIT 'xid_i';
       
      SELECT count(*) = 1 FROM ti;
      # => 0 (sic!)
      

      LOAD INDEX INTO CACHE and CACHE INDEX ... must also error out which is not done (by at least LOAD INDEX) either.

      No other sql commands, form either DML:s or DDL:s class, are found to produce similar effect.

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              Elkin Andrei Elkin
              Votes:
              0 Vote for this issue
              Watchers:
              3 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.