Hello all,
Does anyone know if this procedure has been documented anywhere?
Best,
Adam
jurgen wrote:
One thing to watch out for is the innodb_data_file_path sting. That
controls how big individual innodb files are allowed to get, and if
they're allowed to grow. The default on my system
One thing to watch out for is the innodb_data_file_path sting. That
controls how big individual innodb files are allowed to get, and if
they're allowed to grow. The default on my system (Gentoo 2006.0) was
an unreasonably small number, and importing my initial load of
messages would always fail
Hi There,
I am running MyISAM tables in mysql 4.1 with dbmail 2.0.9-1 on debian
sarge. I am reaching a 4GB limit on the messageblks table and am going
to move from MyISAM to innodb tables. As instructed i should do the
following:
set unique_checks=0;
alter table dbmail_users type=innodb;
alter
Simon,
Simon wrote:
set unique_checks=0;
alter table dbmail_users type=innodb;
... etc ...
set unique_checks=1;
This seems to have worked fine on my dev server, shutting down dbmail
before doing so... My question is: Is there any small tweaks needed
within mysql before doing this?
On 7/10/06, Paul J Stevens [EMAIL PROTECTED] wrote:
Simon,
Simon wrote:
set unique_checks=0;
alter table dbmail_users type=innodb;
... etc ...
set unique_checks=1;
This seems to have worked fine on my dev server, shutting down dbmail
before doing so... My question is: Is there any
DecimalHi,
There's no problem to set dbmail tables from MyISAM to InnoDB directly?
Jorge Bastos
On Mon, Mar 20, 2006 at 07:27:03PM -, Jorge Bastos wrote:
I see, i'll just stop postfix and dbmail when i'll do it
Just one more question to make sure i do the right thing, how do you advise
to do it?
This is the normal procedure right?
ALTER TABLE table_name ENGINE = InnoDB;
As far
