IP address storage recommended int or varchar (15), is there any difference in efficiency?

See some database structure IP with int storage, and then through Ip2long conversion, but this function seems to have a bug, how do you think?

Reply content:

See some database structure IP with int storage, and then through Ip2long conversion, but this function seems to have a bug, how do you think?

MySQL can refer to this answer.

Postgres directly by network address type, refer here

with varchar or char
Reason:
1. The process of eliminating conversions
2.ipv4 or IPv6 can be saved.

Neither of them can be saved.

The general website just records some information about the user with varchar (15) on the line.
int is generally used for IP libraries, easy to segment records query an IP of the provinces and cities, etc.

Use int to save space, use only 4 bytes, char Word to use 7~15 bytes.
The most important is the convenience of querying comparisons (numeric comparisons), and setting shaping as indexes is also more efficient than char.

