> -----Original Message-----
> From: Bruce Dembecki [mailto:bruce@stripped]
> Sent: Thursday, September 22, 2005 11:41
> To: Jeff
> Cc: mysql@stripped
> Subject: Re: MyISAM to InnoDB
> You will need to make sure you have innodb configured in the my.cnf
> file and you have enough space built for it in the shared table
> space. InnoDB also needs it's own memory pool, so make sure you give
> it enough memory. For day to day issues there is no problem doing
> innodb/myisam replication, with a couple of small caveats... an
> "ALTER TABLE" would replicate and thus... may change the table type
> from myisam to innodb or vice versa depending on which server the
> ALTER TABLE came from. To go with that the original conversion from
> myisam to InnoDB would also need to be done in such a way as to not
> be replicated.
True, is there a way to tell a slave to not replicate certain queries
like alter table or would I need to get creative and stop replication
and all writes to the main database, then issue the alter table
statement, then restart replication with a set global
slave_sql_skip_counter=1 so that it skips the alter statemtent?
> Remember that an ALTER TABLE that could have an impact could be as
> simple as adding or dropping an index... although usually
> very simple
> alter table statements like that can be done without defining the
> table engine, some GUIs may however insert that for you on even the
> simplest ALTER TABLE commands.
If I understand what you're saying here, some MySQL front end gui
software will add onto any "Alter table" statement you submit a
statement specifying the type of table like myisam automatically. So if
you used that gui and tried to issue an alter statement to say add an
index to a InnoDB table it would add on a table type = MyISAM and cause
Normally I don't rely on gui tools to do my serious quiries like
altering tables or adding indexes etc. I'll do them logging directly
into mysql server on the linux box itself. In this case there shouldn't
be a problem correct?
> Best Regards, Bruce
> On Sep 22, 2005, at 7:59 AM, Jeff wrote:
> > Hey all,
> > I've got a production database that made up of all MyISAM
> tables. I'd
> > like to change some of the more heavily written to tables
> to InnoDB to
> > take advantage of the record level locking and thus improve write
> > performance of our applications.
> > I currently have a second db server that is replicating from the
> > current production system but not in production yet. I'd like to try
> > to
> > convert
> > it to InnoDB. MySQL version is 4.0.16. It it as symple as just
> > issuing
> > the modify table query or are there problems I should be
> aware of when
> > doing this?
> > Also are there known problems replicating from A -> B -> A (circular
> > replication) when A had Table1= InnoDB and B has Table1=MyISAM?
> > Thanks,
> > Jeff
> > --
> > MySQL General Mailing List
> > For list archives: http://lists.mysql.com/mysql
> > To unsubscribe: http://lists.mysql.com/mysql?
> > unsub=bruce@stripped