IIRC, "localhost" is seen by the client as a magic word to mean "use the
UNIX socket, not 127.0.0.1".
So, yes, that would make the connection not show up in netstat :-)
On Tue, Nov 23, 2010 at 11:11 AM, Brent Clark <brentgclarklist@stripped>wrote:
> Is there a difference if someone had to make the connection string the a
> domain (hosts file entry makes the machine look at its ip) as opposed to
> just using localhost.
> If so would a performance hit be incurred?
> I have this client that has used the domain and in netstat im seeing all
> tcp 0 0 own.ex.ip:50340 own.ex.ip:3306 ESTABLISHED
> tcp 0 0 own.ex.ip:50287 own.ex.ip:3306 ESTABLISHED
> tcp 0 0 own.ex.ip:3306 own.ex.ip:50287 ESTABLISHED
> tcp 0 0 own.ex.ip:50357 own.ex.ip:3306 ESTABLISHED
> tcp 0 0 own.ex.ip:3306 own.ex.ip:50335 ESTABLISHED
> But I have another client that is using localhost and netstat is quiet as a
> This actually never dawned on me. Hence the reason im asking
> But the real reason is that the first clients machine is under heavy load
> and we are trying to see what can be improved.
> Kind Regards
> Brent Clark
> MySQL General Mailing List
> For list archives: http://lists.mysql.com/mysql
> To unsubscribe: http://lists.mysql.com/mysql?unsub=1
Bier met grenadyn
Is als mosterd by den wyn
Sy die't drinkt, is eene kwezel
Hy die't drinkt, is ras een ezel