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

SIGSEGV in `rename_columns_in_stat_table`

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Duplicate
    • 12.0.2
    • N/A
    • N/A
    • None
    • 12.0.2
    • Not for Release Notes

    Description

      Description
      Modifying `mysql.column_stats` table structure causes a segmentation fault.

      Reproduction Steps
      CREATE DATABASE IF NOT EXISTS HuangHe;
      USE HuangHe;
      CREATE TABLE tab (c INT KEY, c2 POINT, c3 LINESTRING, c4 POLYGON, c5 GEOMETRY);
      ALTER TABLE mysql.column_stats RENAME TO mysql.column_stats1;
      CREATE TABLE t (a INT, b CHAR(1), c FLOAT);
      ALTER TABLE t RENAME mysql.column_stats;
      ALTER TABLE tab CHANGE COLUMN c3 c33 LINESTRING;

      Stack Trace
      [ERROR] Column count of mysql.column_stats is wrong. Expected 11, found 3. The table is probably corrupted
      [ERROR] mariadbd got signal 11 ;
      mariadbd(_Z28rename_columns_in_stat_tableP3THDP5TABLEP4ListIN10Alter_info25RENAME_COLUMN_STAT_PARAMSEE+0x584)[0x55d1f753f654]
      mariadbd(_ZN10Alter_info32apply_statistics_deletes_renamesEP3THDP5TABLE+0x69)[0x55d1f760f399]
      mariadbd(+0x118df48)[0x55d1f7da7f48]
      mariadbd(_Z17mysql_alter_tableP3THDPK25st_mysql_const_lex_stringS3_P22Table_specification_stP10TABLE_LISTP13Recreate_infoP10Alter_infojP8st_orderbb+0x4cae)[0x55d1f758624e]
      mariadbd(_ZN19Sql_cmd_alter_table7executeEP3THD+0x362)[0x55d1f7619882]

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              maohaogang maohaogang
              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.