At 02:00 PM 9/3/2011 +1200, Chris Cormack wrote:

That script is for the zebraqueue table, truncating the nozebra table is only a good idea if you are using zebra, because you dont need that table with zebra.

And like Robin suggested, you should set file per table or innodb cannot reclaim the space. Or follow Henri-Damiens advice and set the table to myisam. Without doing one of these 2 things, deleting rows or truncating tables does not reclaim space.

We run all our koha with file per table, that way you dont end up with an ever increasing ibdata file.

Chris - thanks ... I'll try and wrap my head around this, but do you know of a detailed description of how zebra is *supposed* to work, vice how it *actually* works, particularly with Koha. [the myisam vice innodb is complex but well documented, but not wrt zebra.] tnx - p.

Chris On 3 Sep 2011 12:53, "Paul" <<mailto:paul.a@aandc.org>paul.a@aandc.org> wrote:

...

At 04:35 PM 9/2/2011 +0200, you wrote:

...

Le 02/09/2011 14:49, sheldon_tappin a écrit :

...

Hi All,

Is it OK to truncate the nozebra table in koha database. The table is too big for a database backup. [snip]

Hi It is ok. In fact, there is/was a cleanup_database script which does that in misc/cronjobs... could be a scheduled task check that the table is MyISAM and not innodb, unless you want to keep a huge innodb file......

Yup - that script seems to have disappeared ... my innodb is now 5.5 Gigabytes ... what on earth is happening? (end of day, I'll have a closer look tomorrow)

Best Paul --- Tired old sys-admin