Brian Wong wrote:
I think this would be fairly difficult to implement. How would a WQMS
access the file in order to display it? The quarantine management
[...]
Right, forget it. We've all already discussed that, and come to the
point that it pointless.
We have a 50GB (fifty GigaB)
On 5/3/06, Paolo Cravero as2594 [EMAIL PROTECTED] wrote:
We have a 50GB (fifty GigaB) quarantine table on the production server,
and the last quarantine purge run took 14 hours to complete. All traffic
was queued because of DB locks and timeouts. We clean every second day
for spam 30 days
Mark Martinec wrote:
/* I am currently filling-up a test database in order to test if the
maintainance is actually faster with these DELETE CASCADE statements.
All 2.4 native. */
Let us know of the results.
Got to 15GB of quarantine so far. I'm heading for 30 at least.
Shortly before a
Paolo Cravero as2594 wrote:
Mark Martinec wrote:
/* I am currently filling-up a test database in order to test if the
maintainance is actually faster with these DELETE CASCADE statements.
All 2.4 native. */
Let us know of the results.
Got to 15GB of quarantine so far. I'm heading for 30
Cami wrote:
Keep far far away from these queries, they are slow.
But probably keep data consistent...
DELETE FROM quarantine WHERE time_num UNIX_TIMESTAMP() - 7*24*60*60;
(make sure you have an index on time_num)
From http://www.ijs.si/software/amavisd/README.sql.txt :
CREATE TABLE
Paolo Cravero as2594 wrote:
Cami wrote:
Keep far far away from these queries, they are slow.
But probably keep data consistent...
They do the same thing really.
DELETE FROM quarantine WHERE time_num UNIX_TIMESTAMP() - 7*24*60*60;
(make sure you have an index on time_num)
From
I don't see any time_num column there. How can that work for you?
I am using a (slightly) patched version of amavisd-new.
The time_num on tables quarantine and msgrcpt was used in
some on the pre-releases of 2.4.0, but I decided not to include
it in the final 2.4.0 in favour of DELETE CASCADE,
Mark Martinec wrote:
I don't see any time_num column there. How can that work for you?
I am using a (slightly) patched version of amavisd-new.
The time_num on tables quarantine and msgrcpt was used in
some on the pre-releases of 2.4.0, but I decided not to include
it in the final 2.4.0 in
On 4/26/06, Cami [EMAIL PROTECTED] wrote:
The time_num on tables quarantine and msgrcpt was used in
some on the pre-releases of 2.4.0, but I decided not to include
it in the final 2.4.0 in favour of DELETE CASCADE, as on
my setup (still at MySQL then) there was no noticeable
advantage of
Hi.
I have read and (probably) understood what has to be done on MySQL
before migrating from 2.3 to 2.4.
/* I am currently filling-up a test database in order to test if the
maintainance is actually faster with these DELETE CASCADE statements.
All 2.4 native. */
I am wondering if any
Paolo,
I have read and (probably) understood what has to be done on MySQL
before migrating from 2.3 to 2.4.
/* I am currently filling-up a test database in order to test if the
maintainance is actually faster with these DELETE CASCADE statements.
All 2.4 native. */
Let us know of the
11 matches
Mail list logo
