I was looking at the code for trunk/2.3.x and it looks like the vacuum
switch is calling a function to do nothing. From the descriptions of
what the -c flag should do, i think this is the function that used to do
this and should be populated with the optimization of the tables code.
Or make a new switch like -o to do the optimize table calls. It may also
be advantageous to break the optimization into 2 parts - the caching and
message link tables, and then the partlists and mimeparts. The time it
takes to do all the tables on a larger set of data may make it easier to
clean up the caching and message tables to keep operations running
faster with a daily or 2 day interval run on those tables, then a
cleaning of the mimeparts and partlists tables every 2 weeks.
-Jon
Uwe Kiewel wrote:
Jorge Bastos schrieb:
Is it an option to include the "OPTIMIZE TABLE" parts into the code of
dbmail-util? Let's discuss about advantages and disadvantages!
I think it can be an idea, but only with plus one switch for it.
Of course. Only with an additional switch - not per default.
Uwe
_______________________________________________
DBmail mailing list
[email protected]
https://mailman.fastxs.nl/mailman/listinfo/dbmail
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
_______________________________________________
DBmail mailing list
[email protected]
https://mailman.fastxs.nl/mailman/listinfo/dbmail
