Jinsheng Ba
Jinsheng Ba
It may be randomly generated by my application when converting external data to SQL query.
Unfortunately, I cannot remember exactly which concrete line of code it refers to as it is a manually simplified query. I believe there are many other similar issues in [PQS](https://github.com/sqlancer/sqlancer/blob/master/src/sqlancer/sqlite3/oracle/SQLite3PivotedQuerySynthesisOracle.java)....
/label fuzz/sqlancer
It seems SQLancer triggers another issue in MariaDB?
1: I think it can be solved by checking whether the table uses the InnoDB storage engine. If it is difficult, we can simply ignore it as it is not...
1 I guess only innodb engines can not use optimization, so perhaps you can use storage engine to identify it. 2 Is it the full log? Sometimes the column data...
Seems it is a flaky issue that cannot be reproduced stably. Can you look into the root reason of this issue? It's definitely ideal to avoid this error message. If...
It looks like a deadlock bug. If so, it is hard to bypass this bug in the CI.
If you can produce a minimal test case to reproduce the issue, say executing several SQL statements triggers this deadlock, you can report it to MySQL.