MySQL MSI Installer vs WAMP – Understanding Size Differences

A) Try with

• mysql -h[your IP] -u[username] -P[]port -p
• mysql -h127.0.0.1 -u[username] -p
• mysql -hlocalhost -u[username] -p

Which one works and which does not?

B) Set Log_warnings=2 in my.ini and restart MySQL server and see error log entry when connection gets closed abruptly.

I was looking over the comments from @Federico's answer.

When you ran mysql -V, you got the client program's version. Thus, the mysql client is definitely 32-bit. You need to run mysqld -V. This will give you the server's version (i.e., the version of mysqld)

EXAMPLE

[root@***]# mysqld -V
mysqld  Ver 5.0.81-community-log for unknown-linux-gnu on x86_64 (MySQL Community Edition (GPL))

What you see from mysqld -V should coincide with SHOW VARIABLES LIKE "%version%";.

The fact that

• mysqld runs in the 32-bit OS
• mysql client connects to mysqld

reveals one of three(3) scenarios

1. mysqld is 32-bit and runs good; 32-bit client connects just fine
2. mysqld is 64-bit and runs slow; 32-bit client connects just fine
3. mysqld is 64-bit with the possibility of crashing if code for handling 64-bit addresses was not accounted for, 32-bit client connects fine until it mysql or mysqld crashes

If it is scenario 1, no worries. Otherwise, either code for handling 64-bit addresses exists (chances slim-to-none) or not. There is a possibility that version_comment was a typo left over from a previous 64-bit build.