Pelletier, Robert wrote:
> Wouldn't the simplest way to handle that kind of load
to use the
> partitionning fonctionnality of MySQL 5.1?
Excellent shot Robert!
I had looked into MySQL documentation but for the wrong
keyword. Unfortunately
we're still at MySQL 4.1.x and my suggested patch is a quick
and not-so-dirty
workaround.
So probably Mark will mention this possibility in the
documentation rather
than think of how to implement my suggested feature. No
problem.
> I've got a 81GB / 0.5G rows log database set up like
that giving me good
> speed and stability. MySQL does the whole job for you,
nothing to change in
> the application.
Nice to meet someone that has a large database too!
Paolo
------------------------------------------------------------
-------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and
a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
AMaViS-user mailing list
AMaViS-user lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/amavis-user
AMaViS-FAQ:http://www.amav
is.org/amavis-faq.php3
AMaViS-HowTos:http://www.amavis.org/ho
wto/
|