> Hi, > > in my maddr table are about 400.000 recordsets. Im using mysql 5.0.x and > amavisd-new 2.6.1. > > I realized a different problem: the combination of order by and LIMIT does > not always list the last message. According to > http://dev.mysql.com/doc/refman/5.0/en/limit-optimization.html MySQL ends
On second thought, maybe they 'fixed it' in 5.1, which is why it takes so bloody long now. I suppose, either case, people using 5.0 will get an 'undefined' answer (not what they expect), 5.1 people will get a very long delay. For both, maybe answer is to remove the limit 1 from query, and have amavisd pop the first one off the stack. Maybe a view that creates a temp table, and limit1 by that one? -- Michael Scheidell, CTO >|SECNAP Network Security Winner 2008 Network Products Guide Hot Companies FreeBSD SpamAssassin Ports maintainer _________________________________________________________________________ This email has been scanned and certified safe by SpammerTrap(r). For Information please see http://www.spammertrap.com _________________________________________________________________________ ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ 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/
