hhf/MySQLTuner-perl
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

skip_name_resolve not interpreted properly #675

Browse source
This commit is contained in:
Jean-Marie Renouard 2023-06-17 18:11:00 +02:00
parent aade05cb67
commit 89619dc379
1 changed files with 3 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

5
mysqltuner.pl
View file

@ -3305,6 +3305,7 @@ sub mysql_stats {
} }
# name resolution # name resolution
debugprint "skip name resolve: $result{'Variables'}{'skip_name_resolve'}" if ( defined( $result{'Variables'}{'skip_name_resolve'} ) );
if ( defined( $result{'Variables'}{'skip_networking'} ) if ( defined( $result{'Variables'}{'skip_networking'} )
&& $result{'Variables'}{'skip_networking'} eq 'ON' ) && $result{'Variables'}{'skip_networking'} eq 'ON' )
{ {
@ -3329,8 +3330,8 @@ sub mysql_stats {
push( @adjvars, "skip-name-resolve=0" ); push( @adjvars, "skip-name-resolve=0" );
} }
} }
elsif ( $result{'Variables'}{'skip_name_resolve'} ne 'OFF' elsif ( $result{'Variables'}{'skip_name_resolve'} ne 'ON'
and $result{'Variables'}{'skip_name_resolve'} ne '0' ) and $result{'Variables'}{'skip_name_resolve'} ne '1' )
{ {
badprint badprint
"Name resolution is active: a reverse name resolution is made for each new connection which can reduce performance"; "Name resolution is active: a reverse name resolution is made for each new connection which can reduce performance";