Aaron,
I have a dpatch ready for commitment that backports the transaction support in the insertion chain from
cvs-head to 2.0
It's in the 2.0.2-0.20041212 debian packages, but I can commit it *now*.
Aaron Stone wrote:
DBMail 2 hammers PostgreSQL pretty hard because each message is first
delivered to the internal delivery user, processed if needed, and then
messages and physmessages are created for each real recipient. Finally the
message and physmessage for the delivery user is deleted. This means that
each message causes at least one DELETE. I believe this is what causes the
need for heavy vacuuming in PostgreSQL.
So, a detail that I hope a PostgreSQL person can answer definitively: will
wrapping the delivery into a transaction prevent rows that are eventually
deleted from even hitting the database? That would probably completely
alleviate the need for heavy vacuuming.
Aaron
_______________________________________________
Dbmail-dev mailing list
Dbmail-dev@dbmail.org
http://twister.fastxs.net/mailman/listinfo/dbmail-dev
--
________________________________________________________________
Paul Stevens mailto:[EMAIL PROTECTED]
NET FACILITIES GROUP PGP: finger [EMAIL PROTECTED]
The Netherlands________________________________http://www.nfg.nl
