Comments on: InnoDB in self-compiled MySQL 5.1

By: Bimal

Bimal — Thu, 29 Oct 2009 12:13:27 +0000

Normally, I backup the database, and restore it again, to flush off the old innodb logs – by this way, all my indices are recreated, and the overall system increases.

I do this once a month – talking around an hour of database performance management job.

By: Bimal Poudel

Bimal Poudel — Fri, 23 May 2008 10:03:10 +0000

I have a very big innodb database on linux. I am now, doubtful, if its log/archives are causing some slow-ness in the database’s performances. Since a cron script takes the full-database backup everyday, I now want to remove these archivals. How can I do this?

By: Phil Hildebrand

Phil Hildebrand — Tue, 16 Oct 2007 21:43:21 +0000

I messed with this forever, then finally looked at the config options, and sure enough, the ./configure expects innobase:

from: http://www.innodb.com/support/tips

On MySQL 5.1, ./configure expects a different parameter:

$ ./configure –with-plugins=innobase

By: Martin Tsachev

Martin Tsachev — Thu, 13 Sep 2007 13:25:13 +0000

You can with sql_mode = NO_ENGINE_SUBSTITUTION. It’s just that it’s not the default.

create table test (id int) engine=blackhole;
ERROR 1289 (HY000): The ‘BLACKHOLE’ feature is disabled; you need MySQL built with ‘BLACKHOLE’ to have it working