InnoDB deadlock output does not always include the full SQL statement

The recent release of MySQL 8.0.35 includes the following change:
Bug #23036096 - INNODB LAST DETECTED DEADLOCK NOT SHOWING FULL QUERY

The function innobase_mysql_print_thd() reserves a 1024-byte buffer for the output of a function that in MariaDB has been renamed to thd_get_error_context_description(). At most 600 first bytes of the SQL string will be copied to the buffer. The above fix is increasing that limit to 3000 bytes.

In MariaDB, at least starting with the fix of MDEV-15359, it is possible that no SQL statement will be output at all. In some MariaDB releases, there also was a lock order inversion problem that caused server hangs; see MDEV-13983 for some details.

In MariaDB Server 10.6, the locking subsystem was greatly refactored by MDEV-20612, MDEV-24738 and other changes. Therefore, it could make sense to not fix this bug in earlier major versions.