Mark Martinec schrieb:
> I have now a somewhat more advanced variant of my
previously posted patch,
> which automatically sets partition_tag to a current
ISO8601 week number
> (1..53) if $sql_partition_tag is undef, which will be a
default.
> If anyone is interested please drop me a line.
/me drops a line!!!
Paolo, Robert, Mark: thanks for sharing your ideas /
solutions - that's
absolutely amazing!! Our test environment is up for less
than three
weeks, handling only part of our mail traffic. Db size is ~
15 GB right
now, estimated size once in full production: 50 GB (and
probably soon
even more).
I already encountered some InnoDB Transaction deadlock doing
harmless
queries for some stats (first by doing REPLACE INTO ...
SELECT FROM ...)
and started wondering how "garbage collection"
would behave, once the
first month (I would likt to keep quarantine for 30 days) is
over
MySQL partitioning as shown in your previous mails is REALLY
cool and
exactly what I need. Any concerns about using 5.1 in
production? I'm
still a little bit sceptic...
Thomas
NB (off topic): As MySQL's CHAR() type defaults to latin_xy
I would
suggest to use BINARY(1) instead of CHAR(1) for
msgs.content - I
wrote a little script producing cute "live"
stats for some domains;
and (initially) not using "BINARY content" in
my GROUP BY's drove
me crazy
------------------------------------------------------------
-------------
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/
|