Instead of storing the client_addr as a VARCHAR(255), how about
storing it instead as a 32bit number in a column of type UNISIGNED
INT? This'll reduce storage and speed queries.
MySQL can convert back and forth using inet_aton and inet_ntoa.
Perhaps there's something similar for postgres and others? If not,
it'd be as simple thing to implement. Using the example in the mysql
docs, SELECT INET_ATON('209.207.224.40') is 3520061480, which is
209*256^3 + 207*256^2 + 224^256 + 40.
-------------------------------------------------------
This SF.Net email is sponsored by the 'Do More With Dual!' webinar happening
July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual
core and dual graphics technology at this free one hour event hosted by HP,
AMD, and NVIDIA. To register visit http://www.hp.com/go/dualwebinar
_______________________________________________
AMaViS-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/amavis-user
AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3
AMaViS-HowTos:http://www.amavis.org/howto/
