Uploaded image for project: 'MariaDB ColumnStore'
  1. MariaDB ColumnStore
  2. MCOL-4780

Intermittent ExeMgr crash for a query involving foreign table UPDATE

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Cannot Reproduce
    • 6.1.1
    • N/A
    • ExeMgr, MDB Plugin
    • None

    Description

      ExeMgr is crashing intermittently for a query involving UPDATE on a foreign table. Below is the reproduction. Note that the crash is happening on Release and Debug builds, but not in RelWithDebInfo builds.

      ExeMgr crashes when the queries are run in a loop:

      ret=0; i=0; while [ $ret -eq 0 ]; do echo $i; mariadb test < exemgr_crash.sql > exemgr_crash.sql.log; ret=$?; ((i=i+1)); done
      

      Here, exemgr_crash.sql is:

      DROP TABLE IF EXISTS cstab1;
      DROP TABLE IF EXISTS innotab1;
       
      CREATE TABLE cstab1 (
        a int(11) DEFAULT NULL,
        b varchar(10) DEFAULT NULL
      ) ENGINE=Columnstore;
      INSERT INTO cstab1 VALUES (1,'cs01');
      INSERT INTO cstab1 VALUES (2,'cs02');
       
      CREATE TABLE innotab1 (
        a int(11) DEFAULT NULL,
        b varchar(10) DEFAULT NULL
      ) ENGINE=InnoDB;
      INSERT INTO innotab1 VALUES (1,'in01');
       
      SELECT * FROM cstab1;
      SELECT * FROM innotab1;
       
      SELECT '--- Updating ---' AS ``;
       
      UPDATE innotab1 SET a=100 WHERE a IN (SELECT a FROM cstab1 WHERE a=1);
      SELECT * FROM cstab1;
      SELECT * FROM innotab1;
       
      DROP TABLE cstab1;
      DROP TABLE innotab1;
      

      Attachments

        Activity

          People

            Unassigned Unassigned
            tntnatbry Gagan Goel (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 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.