[MDEV-26202] Unexpected failure with query using indirectly a recursive CTE twice Created: 2021-07-21 Updated: 2021-08-03 Resolved: 2021-08-03 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Optimizer - CTE |
| Affects Version/s: | 10.3.30, 10.4.20, 10.5.11, 10.6.3, 10.2, 10.3, 10.4, 10.5, 10.6 |
| Fix Version/s: | 10.2.40, 10.3.31, 10.4.21, 10.5.12, 10.6.4 |
| Type: | Bug | Priority: | Major |
| Reporter: | Miri | Assignee: | Igor Babaev |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | crash, regression | ||
| Environment: |
Windows 10 Professional (different DBs and machines) and Linux x64 unknown Distribution (dbfiddle.uk). |
||
| Attachments: |
|
||||||||||||||||
| Issue Links: |
|
||||||||||||||||
| 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) 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, |
| Comments |
| Comment by Alice Sherepa [ 2021-07-21 ] | |||||||||||||||||||||||||||||||||||||||||||||||
|
Thank you!
on 10.2
10.3-10.6: crash
| |||||||||||||||||||||||||||||||||||||||||||||||
| Comment by Igor Babaev [ 2021-07-22 ] | |||||||||||||||||||||||||||||||||||||||||||||||
|
This bug was caused by the same problem as | |||||||||||||||||||||||||||||||||||||||||||||||
| Comment by Igor Babaev [ 2021-08-03 ] | |||||||||||||||||||||||||||||||||||||||||||||||
|
This bug was fixed by the patch for |