wait_timeout value

[expired user #9604]'s profile image [expired user #9604] posted 8 years ago in General Permalink

If the value for the parameters wait_timeout and interactive_wait_timeout are set differently (for example say 100 and 200) the value shown in the variables list for wait_timeout will be incorrect. wait_timeout appears to always shows the value of interactive_wait_timeout (in the example both will show as 200).

ansgar's profile image ansgar posted 8 years ago Permalink

I guess one of the both variables cannot be lower than the other one. Don't know which of them but the MySQL documentation should shed some light on that.

[expired user #9604]'s profile image [expired user #9604] posted 8 years ago Permalink

I think that because HeidiSQL uses an interactive connection the session value for wait_timeout is set to interactive_timeout. The problem is that then the value displayed for wait_timeout does not match the value set in my.cnf - that might be normal behaviour but it isn't helpful if you want to use HeidiSQL to see the true value.

[expired user #9604]'s profile image [expired user #9604] posted 8 years ago Permalink

I think that it might be clearer to display the result of SHOW GLOBAL VARIABLES perhaps in a second column. It would be more helpful from a DBA perspective to see those settings rather just the session value.

ansgar's profile image ansgar posted 8 years ago Permalink

Global variables already have their own column, at least if you did not hide the column header.

1 attachment(s):
  • host-variables
[expired user #9604]'s profile image [expired user #9604] posted 8 years ago Permalink

That's great thank you. I never saw this column before and I've used heidiSQL for many years.

Please login to leave a reply, or register at first.