On 2013-10-02 11:27, Reindl Harald wrote:
Am 02.10.2013 11:17, schrieb Thomas Raschbacher:
On 2013-10-02 11:01, Reindl Harald wrote:
as it stands now I can't really run this daily anymore :(
the problem is that you may have *a very large* amount because this
was not cleared
in the past from 3.0 until the commit
a40b41d783fde2ff2304dd8bb61a70448be26810
this should be much more relaxed if it runs daily
my homeserver hammered on the RAID10 for some minutes, but only at
the first run
I don't have a problem with some Minutes
but look at my top output .. 1821 Minutes!! that's over 30 Hours !
well, let it hammer a day once :-)
I would but it takes longer than 1 day ^^
and yes i worded that badly I mean until it is done once I can't run
this daily
you can run it daily after that - the problem with no cleanups at all
over a long time is that most likely there are some hundret thousand
records which now get removed
http://dbmail.10918.n7.nabble.com/Housekeeping-dbmail-headervalue-td16954.html
delete from dbmail.dbmail_headername where id not in (select
headername_id from dbmail.dbmail_header) limit 50000;
delete from dbmail.dbmail_headervalue where id not in (select
headervalue_id from dbmail.dbmail_header) limit 50000;
I ran a select query with count(*) (from that post) about 20 minutes
ago... -- it is not done yet O.o
well guess i just have let it run until it is done. Although this might
be good as some extra option like the migration with limit as well so
that it doesn'T take forever ;)
@paul what do you think about putting some limit on this? -- since if
most people run a daily cronjob it would also get done eventually (or
you could run it manually with a higher limit i suppose)
_______________________________________________
DBmail mailing list
DBmail@dbmail.org
http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail
