Bug #115435 | Interactive interface new connection session wait_timeout value error | ||
---|---|---|---|
Submitted: | 26 Jun 2024 10:13 | Modified: | 27 Jun 2024 10:33 |
Reporter: | li liu | Email Updates: | |
Status: | Not a Bug | Impact on me: | |
Category: | MySQL Server | Severity: | S3 (Non-critical) |
Version: | 5.7.44 | OS: | CentOS |
Assigned to: | CPU Architecture: | x86 |
[26 Jun 2024 10:13]
li liu
[26 Jun 2024 10:24]
MySQL Verification Team
HI Mr. liu, Thank you for your bug report. However, there are two issues with your report. First one is that version 5.7 is no longer maintained. Current supported versions are 8.0 and 8.4. Second one is that wait and interactive timeout are two distinct timeouts in MySQL for the last 20 (twenty) years and one or the other is applied, depending on whether it is an interactive or batch program. This behaviour will not change. Unsupported.
[27 Jun 2024 8:14]
Tsubasa Tanaka
FYI. This behavior is same on 8.0 and 8.4, not only 5.7. But it has been already written in Document. > On thread startup, the session wait_timeout value is initialized from the global wait_timeout value or from the global interactive_timeout value, depending on the type of client (as defined by the CLIENT_INTERACTIVE connect option to mysql_real_connect()). See also interactive_timeout. https://dev.mysql.com/doc/refman/8.0/en/server-system-variables.html#sysvar_wait_timeout
[27 Jun 2024 10:33]
MySQL Verification Team
Thank you, Mr. Tanaka, for your contribution. This is truly not a bug.