On Thu, Feb 18, 2010 at 7:46 AM, Nahuel ANGELINETTI <nahuel.angelinetti@biblibre.com> wrote:
Hi,
Le 18/02/2010 13:42, Galen Charlton a écrit :
Hi,
On Thu, Feb 18, 2010 at 6:47 AM, Chris Nighswonger <cnighswonger@foundations.edu> wrote:
including not freeing space in the file system even if you truncate the table :(
Ouch! this would seem to be a mysql bug. Is there no way to ensure the drive space is freed up?
It's an issue with the InnoDB storage engine, not MySQL per se. However, reclaiming space is easy enough, since by default a separate InnoDB file is created for each table: just drop and recreate the sessions table. You can also use MyISAM instead of InnoDB for that table.
Usually, in all our installs we change the engine for "session" and "zebraqueue" tables to MyISAM. And add a cronjob that clean the both tables every night.
It sounds to me like we ought to consider changing the engine for these tables in kohastructure.sql. Kind Regards, Chris