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

Unexpected failure with query using indirectly a recursive CTE twice

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • 10.3.30, 10.4.20, 10.5.11, 10.6.3, 10.2(EOL), 10.3(EOL), 10.4(EOL), 10.5, 10.6
    • 10.2.40, 10.3.31, 10.4.21, 10.5.12, 10.6.4
    • Optimizer - CTE
    • Windows 10 Professional (different DBs and machines) and Linux x64 unknown Distribution (dbfiddle.uk).

    Description

      Yesterday I wanted to use an older query for reporting reasons. Every time I run the query there was an error message on the client:

      /* SQL Error (2013): Lost connection to MySQL server during query */

      I tried multiple servers (different versions of MariaDB) but nothing helped. Then I looked on the Windows 10 server event viewer and realized that the MariaDB server has crashed and was restarted every single time! (option on Windows after service crashed)
      I can reproduce that problem after 1 or 2 seconds runtime of my query on all my DB-Versions (10.3.30, 10.4.20, 10.5.11, 10.6.3).

      Then I tried older versions of MariaDB 10.6.3 (crashed) => 10.6.2 (OK) and MariaDB 10.5.11 (crashed) => 10.5.10 (OK), 10.5.5 (OK), 10.5.2 (OK).

      My query has 700 lines and I tried to reduce, strip down and rename everything. I have attached an (hopefully!) working example. The problem is (recursive?) CTE related and my example has no other tables any longer.

      Best,
      Miriam

      Attachments

        Issue Links

          Activity

            People

              igor Igor Babaev
              miridb Miri
              Votes:
              0 Vote for this issue
              Watchers:
              4 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.