On Sat, Jun 12, 2004 at 12:25:07AM +0100, Tim Bishop wrote: > > I guess this email is just for information really, unless someone steps > up and finds a bug in SpamAssassin/Perl to attribute this problem to :-) > I'd certainly recommend people use MySQL over Postgresql at this stage. >
For what it's worth I've seen similar results, although with tuning I was able to get PostgreSQL to behave much better. For sure MySQL works better out of the box than PostgreSQL. Granted much of the Bayes/AWL codes was developed using MySQL, but with an eye portability, so it is possible something code related could be involved. In fact, it might be the fact that we do so many row updates. For ACID databases this means that they must insert a whole new row and then mark the old row deleted. Interestingly, the InnoDB table type under MySQL does this, but I've had much better success (along with others) than with PostgreSQL. I'm sure we've got some PostgreSQL experts out there. If any of y'all can see a problem with the code as written or have some tips for tuning PostgreSQL that we can document, feel free to speak up. Michael
