server crash when slow query log is on with additional variables

PR fixing this issue has been pushed to release branch and should appear in Percona Server 8.0.36.

Note the description of the problem from the PR:
When slow log was enabled with --long_query_time option set to 0 (or close value) and with --log_slow_verbosity option including "query_info" mode, server might have crashed when a protocol command other than normal statement execution (COM_QUERY or mysql_query() in C API parlance) was executed in a connection which earlier was used to run some statement. For example, this sometimes happened for COM_QUIT command issue during graceful disconnect.

tried by removing “query_info” from log_slow_verbosity and can confirm that workaround works

Hello!

Quick crash analysis shows that this seems to be Percona specific issue which is regression from .

So one possible way to temporarily workaround this crash should be removing query_info element from value of --log_slow_verbosity option to disable functionality implemented by PS-7046. If this is not possible, then one could try to increase --long_query_time value from 0 as an alternative (to avoid triggering slow log for commands like COM_QUIT and so on).

Hi

Thank you for the report.
Verified as described:

sending the concern to engineering for further review and updates.