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

Server crashes on SELECT from I_S table

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Duplicate
    • 10.0.6
    • None
    • None

    Description

      It might be the same as MDEV-5415, MDEV-5416, MDEV-5417 but the stack trace is different again. It needs to be re-checked after MDEV-5415 is fixed.

      Preliminary test case:

      SET optimizer_use_condition_selectivity=3;
      SELECT * FROM INFORMATION_SCHEMA . `INNODB_SYS_DATAFILES` AS table1 WHERE  table1 . `PATH` <> 'se'   ORDER BY table1 . `PATH` , table1 . `PATH` LIMIT 14;

      If it's run via MTR, should be run as

      perl ./mtr bug.t1 --mysqld=--plugin-innodb-sys-datafiles

      #3  <signal handler called>
      #4  0x000000000094fa51 in step_down_to (arg=0x7fc2723dd6b0, key_tree=0x7fc267f4c368) at 10.0/sql/opt_range_mrr.cc:100
      #5  0x000000000094fbea in sel_arg_range_seq_next (rseq=0x7fc2723dd6b0, range=0x7fc2723dd660) at 10.0/sql/opt_range_mrr.cc:165
      #6  0x00000000009551ce in records_in_column_ranges (param=0x7fc2723ddca0, idx=0, tree=0x7fc267f4c0a8) at 10.0/sql/opt_range.cc:3360
      #7  0x00000000009554fc in calculate_cond_selectivity_for_table (thd=0x7fc26ab3d070, table=0x7fc267c15088, cond=0x7fc267dd8b90) at 10.0/sql/opt_range.cc:3478
      #8  0x0000000000000000 in ?? ()

      revision-id: bar@mnogosearch.org-20131206150255-und2j89f85by7imn
      revno: 3915
      branch-nick: 10.0

      Attachments

        Issue Links

          Activity

            People

              elenst Elena Stepanova
              elenst Elena Stepanova
              Votes:
              0 Vote for this issue
              Watchers:
              2 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.