Details
-
Bug
-
Status: Stalled (View Workflow)
-
Major
-
Resolution: Unresolved
-
10.0.25, 5.5(EOL), 10.0(EOL), 10.1(EOL), 10.2(EOL)
-
None
-
GNU/Linux Lubuntu 16.10, x86_64.
Description
Upon executing a series of SQL statements (see attached file) via JDBC, the server stops responding. The final statement should return just four rows, but does not terminate for at least 20 hours. After the last query all other operations on the server become impossible, and the server consumes 100% of CPU time on one logical processor, even after the query connection is terminated. The only remedy is to kill the server process query.
Executing the same statements directly in the CLI yields the same result.
The exact same sequence of SQL statements complete in a matter of seconds on a stock standard 5.7.16-0ubuntu0.16.10.1 MySQL server running on the same computer. Similar queries also complete in seconds on PostgreSQL, SQLite, HSQLDB, MonetDB, H2, Derby, and Firebird database engines running on the same computer.
The installed version is 10.0.25-MariaDB-1 Ubuntu 16.10, installed via the OS package manager and not configured further except to create a 'test' schema.
Attachments
Issue Links
- relates to
-
MDEV-19532 Query with subqueries hangs for long time with default optimizer_search_depth
- Closed