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

Server crashes in Item_cond::get_mm_tree/prune_partitions

    XMLWordPrintable

Details

    • Bug
    • Status: Stalled (View Workflow)
    • Major
    • Resolution: Unresolved
    • 10.3, 10.4, 10.5
    • 10.4, 10.5
    • Partitioning
    • None

    Description

      Server crashes in Item_cond::get_mm_tree/prune_partitions

      --source include/have_partition.inc
       
      CREATE TABLE t1 (i1 int) ;
      INSERT INTO t1 VALUES (1),(2),(3);
       
      CREATE TABLE t2 (pk int NOT NULL, i int, PRIMARY KEY (pk)) PARTITION BY KEY (pk) PARTITIONS 2;
      INSERT INTO t2 VALUES (1,1),(2,1),(3,1);
       
      UPDATE (t1 JOIN t2 ON (t2.pk = t1.i1 OR 0))
      SET t2.i = 5;
      

      Reproducible with Myisam/Aria/Innodb, debug/non-debug, reproducible on 10.3-10.5:

      10.3 affe7fabc7baa36083e7632eb

      Thread 1 (Thread 0x7f5407583700 (LWP 17954)):
      #0  __pthread_kill (threadid=<optimized out>, signo=11) at ../sysdeps/unix/sysv/linux/pthread_kill.c:62
      #1  0x000055898abc33e2 in my_write_core (sig=11) at /10.3/mysys/stacktrace.c:481
      #2  0x000055898a34480f in handle_fatal_signal (sig=11) at /10.3/sql/signal_handler.cc:343
      #3  <signal handler called>
      #4  0x000055898a4c7903 in Item_cond::get_mm_tree (this=0x7f53f00141c8, param=0x7f5407581460, cond_ptr=0x7f54075813a8) at /10.3/sql/opt_range.cc:7660
      #5  0x000055898a4bd945 in prune_partitions (thd=0x7f53f0000af0, table=0x7f53f0076340, pprune_cond=0x7f53f00141c8) at /10.3/sql/opt_range.cc:3528
      #6  0x000055898a06e4e4 in JOIN::optimize_inner (this=0x7f53f0014d18) at /10.3/sql/sql_select.cc:1830
      #7  0x000055898a06cfcb in JOIN::optimize (this=0x7f53f0014d18) at /10.3/sql/sql_select.cc:1488
      #8  0x000055898a0770c8 in mysql_select (thd=0x7f53f0000af0, tables=0x7f53f0013010, wild_num=0, fields=..., conds=0x0, og_num=0, order=0x0, group=0x0, having=0x0, proc_param=0x0, select_options=1342177408, result=0x7f53f0014c40, unit=0x7f53f00049b8, select_lex=0x7f53f0005140) at /10.3/sql/sql_select.cc:4283
      #9  0x000055898a12f002 in mysql_multi_update (thd=0x7f53f0000af0, table_list=0x7f53f0013010, fields=0x7f53f0005268, values=0x7f53f0005770, conds=0x0, options=0, handle_duplicates=DUP_ERROR, ignore=false, unit=0x7f53f00049b8, select_lex=0x7f53f0005140, result=0x7f5407581e60) at /10.3/sql/sql_update.cc:1805
      #10 0x000055898a02857e in mysql_execute_command (thd=0x7f53f0000af0) at /10.3/sql/sql_parse.cc:4369
      #11 0x000055898a034246 in mysql_parse (thd=0x7f53f0000af0, rawbuf=0x7f53f0012818 "UPDATE (t1 JOIN t2 ON (t2.pk = t1.i1 OR 0))\nSET t2.i = 5", length=56, parser_state=0x7f5407582460, is_com_multi=false, is_next_command=false) at /10.3/sql/sql_parse.cc:7817
      #12 0x000055898a020d6d in dispatch_command (command=COM_QUERY, thd=0x7f53f0000af0, packet=0x7f53f0123221 "UPDATE (t1 JOIN t2 ON (t2.pk = t1.i1 OR 0))\nSET t2.i = 5", packet_length=56, is_com_multi=false, is_next_command=false) at /10.3/sql/sql_parse.cc:1856
      #13 0x000055898a01f67b in do_command (thd=0x7f53f0000af0) at /10.3/sql/sql_parse.cc:1402
      #14 0x000055898a19838c in do_handle_one_connection (connect=0x55898c98c610) at /10.3/sql/sql_connect.cc:1403
      #15 0x000055898a1980c8 in handle_one_connection (arg=0x55898c98c610) at /10.3/sql/sql_connect.cc:1308
      #16 0x000055898ab49af0 in pfs_spawn_thread (arg=0x55898c8d86f0) at /10.3/storage/perfschema/pfs.cc:1869
      #17 0x00007f5412e176ba in start_thread (arg=0x7f5407583700) at pthread_create.c:333
      #18 0x00007f54122ac41d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109
      

      Attachments

        Activity

          People

            psergei Sergei Petrunia
            alice Alice Sherepa
            Votes:
            0 Vote for this issue
            Watchers:
            5 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.