Hi Paolo, Paolo Lucente, 01.05.2006 17:20: >> it seems to be known, that a default MySQL performs a lot better than a >> default PostgreSQL. One difference is, that PostgreSQL is doing an COMMIT > > Not to open a possible flame, but i fully agree with this view. However, we > massively deal with network objects (IP and MAC addresses, network subnets) > > which are handled properly only by PostgreSQL. Do you see chances that this > can re-open the challenge on this scenario ?
what do you mean with properly? Basically these types are just numbers. And these are handled properly by mysql. Sure, doesn't look so nice in a raw table. The problem in the MySQL scheme for me are the strings, especially in ip_proto. For me it looks like PostgreSQL is cool thing if you have complex table relations. But we have plain flat single tables. Maybe even MySQL is an overhead here. ;-) Did you closer look at flowd (http://www.mindrot.org/flowd.html)? It has it's own binary file format for flow data. Maybe this is the right direction? My "dream" is anyway a backend-independent API for accessing the data, where you don't have to know, where and in which format the data is stored. ;-) Cheers, Sven -- Sven Anderson Institute for Informatics - http://www.ifi.informatik.uni-goettingen.de Georg-August-Universitaet Goettingen Lotzestr. 16-18, 37083 Goettingen, Germany _______________________________________________ pmacct-discussion mailing list http://www.pmacct.net/#mailinglists
