Even if you had read the documentation, it is not really clear what interactive_timeout
means.
It means if a connection of an interactive client is idle for too long, the connection is automatically closed. This won't disturb any user interaction, because if they are running queries, by definition the connection is not idle.
The default value of both wait_timeout
and interactive_timeout
is 28800 seconds (8 hours). So the client would have to be doing nothing but holding open the connection for 8 hours before it times out due to inactivity. This is very unlikely to affect any PHP request, which close as soon as the request is done.
It is also not mentioned in the documentation that the only existing client that uses interactive_timeout
is the mysql command-line client.
All connectors for languages like PHP, Java, ODBC, Python, Perl, etc. use the regular wait_timeout
. I have not seen any connector that has an option to use interactive_timeout
. Programmatic connectors are not considered interactive, even though the application they are connecting from accepts user input.
Even the new MySQL Shell client does not enable interactive_timeout
. It relies on the traditional wait_timeout
that other clients use.