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

Server crashes in Field_inet6::store_warning upon updating table statistics

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • 10.5
    • 10.5.0
    • Data types
    • None

    Description

      create table t1 (a inet6);
      insert into t1 values ('1::1'),('2::2');
      analyze table t1 persistent for all;
      insert into t1 values ('3::3');
       
      # cleanup
      drop table t1;
      

      10.5 b37386d8

      #3  <signal handler called>
      #4  0x000055b968454784 in Field_inet6::store_warning (this=0x7fa4ac071358, str=..., level=Sql_state_errno_level::WARN_LEVEL_WARN) at /data/src/10.5/plugin/type_inet/sql_type_inet.cc:613
      #5  0x000055b96845482c in Field_inet6::set_null_with_warn (this=0x7fa4ac071358, str=...) at /data/src/10.5/plugin/type_inet/sql_type_inet.cc:618
      #6  0x000055b968455356 in Field_inet6::store (this=0x7fa4ac071358, str=0x7fa4ac04201d "1::1", length=4, cs=0x55b968fb46c0 <my_charset_bin>) at /data/src/10.5/plugin/type_inet/sql_type_inet.cc:758
      #7  0x000055b967875909 in Column_stat::get_stat_values (this=0x7fa4be509440) at /data/src/10.5/sql/sql_statistics.cc:1140
      #8  0x000055b967870731 in read_statistics_for_table (thd=0x7fa4ac000b10, table=0x7fa4ac194960, stat_tables=0x7fa4be509610) at /data/src/10.5/sql/sql_statistics.cc:3074
      #9  0x000055b9678714cc in read_statistics_for_tables_if_needed (thd=0x7fa4ac000b10, tables=0x7fa4ac013510) at /data/src/10.5/sql/sql_statistics.cc:3362
      #10 0x000055b9676fc8a2 in open_and_lock_tables (thd=0x7fa4ac000b10, options=..., tables=0x7fa4ac013510, derived=true, flags=0, prelocking_strategy=0x7fa4be50aaf8) at /data/src/10.5/sql/sql_base.cc:5244
      #11 0x000055b9676b65c1 in open_and_lock_tables (thd=0x7fa4ac000b10, tables=0x7fa4ac013510, derived=true, flags=0) at /data/src/10.5/sql/sql_base.h:505
      #12 0x000055b96774d9cf in mysql_insert (thd=0x7fa4ac000b10, table_list=0x7fa4ac013510, fields=..., values_list=..., update_fields=..., update_values=..., duplic=DUP_ERROR, ignore=false) at /data/src/10.5/sql/sql_insert.cc:764
      #13 0x000055b96779ba72 in mysql_execute_command (thd=0x7fa4ac000b10) at /data/src/10.5/sql/sql_parse.cc:4474
      #14 0x000055b9677a81c3 in mysql_parse (thd=0x7fa4ac000b10, rawbuf=0x7fa4ac013428 "insert into t1 values ('3::3')", length=30, parser_state=0x7fa4be50b580, is_com_multi=false, is_next_command=false) at /data/src/10.5/sql/sql_parse.cc:7938
      #15 0x000055b9677937a1 in dispatch_command (command=COM_QUERY, thd=0x7fa4ac000b10, packet=0x7fa4ac0083c1 "insert into t1 values ('3::3')", packet_length=30, is_com_multi=false, is_next_command=false) at /data/src/10.5/sql/sql_parse.cc:1845
      #16 0x000055b967791efb in do_command (thd=0x7fa4ac000b10) at /data/src/10.5/sql/sql_parse.cc:1363
      #17 0x000055b96792fcad in do_handle_one_connection (connect=0x55b96b9d9bf0, put_in_cache=true) at /data/src/10.5/sql/sql_connect.cc:1422
      #18 0x000055b96792f9dc in handle_one_connection (arg=0x55b96b9d9bf0) at /data/src/10.5/sql/sql_connect.cc:1319
      #19 0x000055b967e72419 in pfs_spawn_thread (arg=0x55b96b951ce0) at /data/src/10.5/storage/perfschema/pfs.cc:1862
      #20 0x00007fa4c5eae4a4 in start_thread (arg=0x7fa4be50c700) at pthread_create.c:456
      #21 0x00007fa4c43f5d0f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:97
      

      Reproducible with at least MyISAM, InnoDB, Aria.
      Couldn't reproduce with binary instead of inet6.

      Attachments

        Issue Links

          Activity

            People

              bar Alexander Barkov
              elenst Elena Stepanova
              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.