Hi all, Sven Anderson, 21.04.2006 21:34: > I think the problem is not the updating of the data itself, but updating > the complex primary key. An index of (ip_src, ip_dst, stamp_inserted) is > fast enough to find entries, and easy enough to maintain.
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 after each INSERT/UPDATE, which results in an fsync() call, if fsync = true in postgresql.conf. See this article: http://monstera.man.poznan.pl/wiki/index.php/Mysql_vs_postgres Paolo, are you using transactions in the PostgreSQL plugin, to COMMIT all UPDATES in one bunch? I couldn't clearly see it in the source code. > BTW.: What is the best indexing to make a select with "WHERE > stamp_inserted>=2006-04-21 20:17:55 AND stamp_inserted<2006-04-21 > 21:17:55" fast? I guess a btree index, but maybe there's something better? This question is still open. No DBMS gurus here? ;-) 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
