Re: Changing storage engine in dump file.
Thanks everyone for their reply. Best Regards, Geetanjali Mehra Senior Database Administrator On Wed, Aug 12, 2015 at 7:07 PM, Reindl Harald h.rei...@thelounge.net wrote: Am 12.08.2015 um 15:07 schrieb geetanjali mehra: I am in the process of creating a new slave. On my master, there is a mix of innodb and myisam tables. I want all my tables to be created in innodb on slave. I have planned to change the value of storage engine from innodb to myisam in dump file itself using sed . Running that dump file on the slave will create all my tables with innodb. Is there any implications in doing so. Is this approach correct? Will I face any problem in syncing the slave? if you are asking for trouble do so otherwise replication is designed to be identical how do you imagine that working if there is only a single alter table on the master? how do you imagine row-based replication working in such a setup while statement-based replication is unsafe in many cases? sorry, but that sounds just crazy
Re: Changing storage engine in dump file.
Depending on the version of MySQL and InnoDB engine, the max key length can be 3072 for InnoDB.. On Wed, Aug 12, 2015 at 9:21 AM, Johan De Meersman vegiv...@tuxera.be wrote: - Original Message - From: geetanjali mehra mailtogeetanj...@gmail.com Subject: Changing storage engine in dump file. Is there any implications in doing so. Is this approach correct? Will I face any problem in syncing the slave? The first thing that occurs to me, is that the maximum key lenght for MyISAM is 1000 bytes, but for InnoDB it is only 786 bytes... Depending on your server version, InnoDB may not yet have fulltext indices, and even if it does, the behaviour is different from the MyISAM ones. You are likely to run into a myriad of tiny little differences, and it seems to me like a fairly bad plan. Why do you want this? -- Unhappiness is discouraged and will be corrected with kitten pictures. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
Re: Changing storage engine in dump file.
I have already made this attempt. And really I stucked into some problems. I found lots of full text indexes created on the data directory . I don't know from where they come. We have never created full text indexes for that database. Slave also was not able to sync with its master. Now, I have restored all the things back by restoring mysqldump file as it was. Best Regards, Geetanjali Mehra Senior Database Administrator On Thu, Aug 13, 2015 at 10:31 PM, Singer Wang w...@singerwang.com wrote: Depending on the version of MySQL and InnoDB engine, the max key length can be 3072 for InnoDB.. On Wed, Aug 12, 2015 at 9:21 AM, Johan De Meersman vegiv...@tuxera.be wrote: - Original Message - From: geetanjali mehra mailtogeetanj...@gmail.com Subject: Changing storage engine in dump file. Is there any implications in doing so. Is this approach correct? Will I face any problem in syncing the slave? The first thing that occurs to me, is that the maximum key lenght for MyISAM is 1000 bytes, but for InnoDB it is only 786 bytes... Depending on your server version, InnoDB may not yet have fulltext indices, and even if it does, the behaviour is different from the MyISAM ones. You are likely to run into a myriad of tiny little differences, and it seems to me like a fairly bad plan. Why do you want this? -- Unhappiness is discouraged and will be corrected with kitten pictures. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
