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

Crash on insert with PARTITION clause after TRUNCATE

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Duplicate
    • 10.4.8, 10.4.10
    • N/A
    • Server
    • AWS Linux from mariadb yum repo
      Docker image 10.4 hash 92495405fc36
      Docker test is also running in AWS Linux

    Description

      Mysqld receives segfault (signal 11) on an insert statement following a truncate partition. It only happens if the insert has a PARTITION clause. If there are any other operations on the table without a PARTITION clause between the truncate and the insert, the crash does not occur.

      I tested in 10.4.8-MariaDB-1:10.4.8+maria~bionic-log in docker container, as well as 10.4.8-MariaDB-log on an Amazon Linux server.

      The error did not occur in version 10.2 which I was running previously in the Amazon Linux server.

      I have attached a sql script which can reproduce the crash on my docker container running 10.4.8 (docker image tagged 10.4 hash 92495405fc36).

      When producing the reproduction script I found that the error only occurred when the table had an AUTO_INCREMENT column. Without the AUTO_INCREMENT, no crash occurred.

      Attachments

        Issue Links

          duplicates

          Bug - A problem which impairs or prevents the functions of the product. MDEV-18244 Server crashes in ha_innobase::update_thd / ... / ha_partition::update_next_auto_inc_val

          • Blocker - Blocks development and/or testing work, production could not run.
          • Closed

          Activity

            Ascending order - Click to sort in descending order
            jacob.williams Jacob Williams created issue -
            jacob.williams Jacob Williams made changes -
            Field Original Value New Value
            Description Mysqld receives segfault (signal 11) on an insert statement following a truncate. It only happens if the insert has a PARTITION clause. If there are any other operations on the table without a PARTITION clause between the truncate and the insert, the crash does not occur.

            I tested in 10.4.8-MariaDB-1:10.4.8+maria~bionic-log in docker container, as well as 10.4.8-MariaDB-log on an Amazon Linux server.

            The error did not occur in version 10.2 which I was running previously in the Amazon Linux server.

            I have attached a sql script which can reproduce the crash on my docker container running 10.4.8 (docker image tagged 10.4 hash 92495405fc36).             		Mysqld receives segfault (signal 11) on an insert statement following a truncate. It only happens if the insert has a PARTITION clause. If there are any other operations on the table without a PARTITION clause between the truncate and the insert, the crash does not occur.

            I tested in 10.4.8-MariaDB-1:10.4.8+maria~bionic-log in docker container, as well as 10.4.8-MariaDB-log on an Amazon Linux server.

            The error did not occur in version 10.2 which I was running previously in the Amazon Linux server.

            I have attached a sql script which can reproduce the crash on my docker container running 10.4.8 (docker image tagged 10.4 hash 92495405fc36).

            When producing the reproduction script I found that the error only occurred when the table had an AUTO_INCREMENT column. Without the AUTO_INCREMENT, no crash occurred.
            jacob.williams Jacob Williams made changes -
            Description Mysqld receives segfault (signal 11) on an insert statement following a truncate. It only happens if the insert has a PARTITION clause. If there are any other operations on the table without a PARTITION clause between the truncate and the insert, the crash does not occur.

            I tested in 10.4.8-MariaDB-1:10.4.8+maria~bionic-log in docker container, as well as 10.4.8-MariaDB-log on an Amazon Linux server.

            The error did not occur in version 10.2 which I was running previously in the Amazon Linux server.

            I have attached a sql script which can reproduce the crash on my docker container running 10.4.8 (docker image tagged 10.4 hash 92495405fc36).

            When producing the reproduction script I found that the error only occurred when the table had an AUTO_INCREMENT column. Without the AUTO_INCREMENT, no crash occurred.             		Mysqld receives segfault (signal 11) on an insert statement following a truncate partition. It only happens if the insert has a PARTITION clause. If there are any other operations on the table without a PARTITION clause between the truncate and the insert, the crash does not occur.

            I tested in 10.4.8-MariaDB-1:10.4.8+maria~bionic-log in docker container, as well as 10.4.8-MariaDB-log on an Amazon Linux server.

            The error did not occur in version 10.2 which I was running previously in the Amazon Linux server.

            I have attached a sql script which can reproduce the crash on my docker container running 10.4.8 (docker image tagged 10.4 hash 92495405fc36).

            When producing the reproduction script I found that the error only occurred when the table had an AUTO_INCREMENT column. Without the AUTO_INCREMENT, no crash occurred.
            alice Alice Sherepa made changes -
            alice Alice Sherepa made changes -
            Fix Version/s N/A [ 14700 ]
            Resolution Duplicate [ 3 ]
            Status Open [ 1 ] Closed [ 6 ]
            jacob.williams Jacob Williams made changes -
            Attachment mariadb-bug-v2.sql [ 49663 ]
            jacob.williams Jacob Williams made changes -
            Affects Version/s 10.4.10 [ 23907 ]
            serg Sergei Golubchik made changes -
            Workflow MariaDB v3 [ 100116 ] MariaDB v4 [ 156807 ]

            People

              Unassigned Unassigned
              jacob.williams Jacob Williams
              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.