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

Too large scale in DECIMAL dynamic column getter crashes mysqld

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 10.0.15, 5.5
    • Fix Version/s: 5.5.44, 10.0.20, 10.1.6
    • Component/s: Dynamic Columns
    • Labels:
      None
    • Environment:
      Darwin 13.4.0 Darwin Kernel Version 13.4.0: Sun Aug 17 19:50:11 PDT 2014; root:xnu-2422.115.4~1/RELEASE_X86_64 x86_64
    • Sprint:
      5.5.44

      Description

          CREATE TABLE `product` (
              `id` INT(11) NOT NULL AUTO_INCREMENT,
              `name` VARCHAR(128),
              `dynamic_columns` BLOB,
              PRIMARY KEY (`id`)
          ) ENGINE =InnoDB DEFAULT CHARSET =utf8;
          INSERT INTO `product` (name, dynamic_columns) VALUES (
              'name1',
              COLUMN_CREATE(
                  'str', 'value1',
                  'int', 123,
                  'float', 123.456,
                  'bool', true,
                  'null', null,
                  'children', COLUMN_CREATE(
                      'str', 'value1',
                      'int', 123,
                      'float', 123.456,
                      'bool', true,
                      'null', null)));
          SELECT COLUMN_GET(`dynamic_columns`, 'float' AS DECIMAL(6,34)) FROM `product`;
      
      150126 16:50:38 [ERROR] mysqld got signal 11 ;
      This could be because you hit a bug. It is also possible that this binary
      or one of the libraries it was linked against is corrupt, improperly built,
      or misconfigured. This error can also be caused by malfunctioning hardware.
      
      To report this bug, see http://kb.askmonty.org/en/reporting-bugs
      
      We will try our best to scrape up some info that will hopefully help
      diagnose the problem, but since we have already crashed, 
      something is definitely wrong and this may fail.
      
      Server version: 10.0.15-MariaDB
      key_buffer_size=2147483648
      read_buffer_size=131072
      max_used_connections=3
      max_threads=153
      thread_count=3
      It is possible that mysqld could use up to 
      key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 2433222 K  bytes of memory
      Hope that's ok; if not, decrease some variables in the equation.
      
      Thread pointer: 0x0x7f9d21841408
      Attempting backtrace. You can use the following information to find out
      where mysqld died. If you see no messages after this, something went
      terribly wrong...
      stack_bottom = 0x21b408e90 thread_stack 0x48000
      0   mysqld                              0x0000000107a9482d my_print_stacktrace + 60
      0   mysqld                              0x000000010757b2cd handle_fatal_signal + 602
      0   libsystem_platform.dylib            0x00007fff8cf625aa _sigtramp + 26
      0   libsystem_malloc.dylib              0x00007fff8e922868 malloc_zone_malloc + 71
      0   mysqld                              0x000000010774cd8c _ZN6String6appendEPKcj + 194
      0   mysqld                              0x00000001075dd587 _ZN15Item_dyncol_get5printEP6String15enum_query_type + 43
      0   mysqld                              0x00000001075b4a60 _ZL9item_nameP4ItemP6String + 40
      0   mysqld                              0x00000001075ab0cf _ZL21wrong_precision_errorjP4Itemym + 135
      0   mysqld                              0x00000001075ab00f _Z20get_length_and_scaleyyPmPjjjP4Item + 59
      0   mysqld                              0x00000001075b46e6 _Z16create_func_castP3THDP4Item11Cast_targetPKcS5_PK15charset_info_st + 1018
      0   mysqld                              0x00000001077fc207 _Z10MYSQLparseP3THD + 58895
      0   mysqld                              0x00000001076e3a2f _Z9parse_sqlP3THDP12Parser_stateP19Object_creation_ctxb + 124
      0   mysqld                              0x00000001076db751 _Z11mysql_parseP3THDPcjP12Parser_state + 164
      0   mysqld                              0x00000001076d9131 _Z16dispatch_command19enum_server_commandP3THDPcj + 1003
      0   mysqld                              0x00000001076db408 _Z10do_commandP3THD + 231
      0   mysqld                              0x00000001077a1883 _Z24do_handle_one_connectionP3THD + 383
      0   mysqld                              0x00000001077a16f7 handle_one_connection + 59
      0   libsystem_pthread.dylib             0x00007fff8f2d0899 _pthread_body + 138
      0   libsystem_pthread.dylib             0x00007fff8f2d072a _pthread_struct_init + 0
      0   libsystem_pthread.dylib             0x00007fff8f2d4fc9 thread_start + 13
      
      Trying to get some variables.
      Some pointers may be invalid and cause the dump to abort.
      Query (0x7f9d21038220): is an invalid pointer
      Connection ID (thread ID): 2
      Status: NOT_KILLED
      
      Optimizer switch: index_merge=on,index_merge_union=on,index_merge_sort_union=on,index_merge_intersection=on,index_merge_sort_intersection=off,engine_condition_pushdown=off,index_condition_pushdown=on,derived_merge=on,derived_with_keys=on,firstmatch=on,loosescan=on,materialization=on,in_to_exists=on,semijoin=on,partial_match_rowid_merge=on,partial_match_table_scan=on,subquery_cache=on,mrr=off,mrr_cost_based=off,mrr_sort_keys=off,outer_join_with_cache=on,semijoin_with_cache=on,join_cache_incremental=on,join_cache_hashed=on,join_cache_bka=on,optimize_join_buffer_size=off,table_elimination=on,extended_keys=on,exists_to_in=on
      
      The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
      information that should help you find out what is causing the crash.
      150126 16:50:38 mysqld_safe mysqld restarted
      

      my.cnf is:

      [clint-server]
      socket = /tmp/mysql.sock
      max_allowed_packet = 1024M
      
      [mysqld]
      user = fsb
      datadir = /Volumes/RAIDv2/mysql
      key_buffer_size = 2G
      innodb_buffer_pool_size = 2G
      net_write_timeout = 3600
      net_read_timeout = 3600
      max_allowed_packet = 1024M
      
      [mysqlhotcopy]
      interactive-timeout
      

        Attachments

          Issue links

            Activity

              People

              • Assignee:
                svoj Sergey Vojtovich
                Reporter:
                thefsb thefsb
              • Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0 minutes
                  0m
                  Logged:
                  Time Spent - 10 minutes
                  10m