On 2013-06-26 18:31, nixofortune wrote:
What would be the best way to convert BIG MyISAM table into InnoDB? We do not
have SLAVE.
I would do it on another computer. Then copy the table to the server and then
add the data that has been added from the original table.
And/or i would experiment
of this being big enough: myisam_sort_buffer_size = 526M
-Original Message-
From: nixofortune [mailto:nixofort...@gmail.com]
Sent: Monday, June 24, 2013 12:35 PM
To: mysql@lists.mysql.com
Subject: Re: space gone after MyISAM REPAIR TABLE
On 24/06/13 19:57, Reindl Harald wrote:
Am 24.06.2013
You can't actually move innodb tables around until 5.6 where you have
transpotable tablespaces.
I suggest having a good hard look at pt-online-schema-change or whatsitcalled.
Jay Ess li...@netrogenic.com wrote:
On 2013-06-26 18:31, nixofortune wrote:
What would be the best way to convert BIG
2013/06/26 17:31 +0100, nixofortune
ALTER TABLE `new_innodb`
ADD KEY `idx1` (`col1`,`col2`),
ADD KEY `idx2` (`col1`,`col2`,`col3`);
Is it really seemly for one index to be a leading part of another?
(or maybe I am really thinking of something else)
--
MySQL General Mailing List
For list
AM
To: li...@netrogenic.com; Jay Ess; mysql@lists.mysql.com
Subject: Re: space gone after MyISAM REPAIR TABLE
You can't actually move innodb tables around until 5.6 where you have
transpotable tablespaces.
I suggest having a good hard look at pt-online-schema-change or
whatsitcalled.
Jay Ess li
. Often it leads to suggesting Summary
Table(s).)
-Original Message-
From: Johan De Meersman [mailto:vegiv...@tuxera.be]
Sent: Wednesday, June 26, 2013 11:46 AM
To: li...@netrogenic.com; Jay Ess; mysql@lists.mysql.com
Subject: Re: space gone after MyISAM REPAIR TABLE
You can't
On 2013-06-27 01:27, nixofortune wrote:
Now importing with Keys in place. It takes longer, much longer but at
least the server is working and customers do not complaint.
Schema design is awful, agree. I try to understand the process so will
redesign it soon, but any suggestions are welcome.
I'
To: li...@netrogenic.com; Jay Ess; mysql@lists.mysql.com
Subject: Re: space gone after MyISAM REPAIR TABLE
You can't actually move innodb tables around until 5.6 where you have
transpotable tablespaces.
I suggest having a good hard look at pt-online-schema-change or
whatsitcalled.
Jay
: myisam_sort_buffer_size
= 526M
-Original Message-
From: nixofortune [mailto:nixofort...@gmail.com]
Sent: Monday, June 24, 2013 12:35 PM
To: mysql@lists.mysql.com
Subject: Re: space gone after MyISAM REPAIR TABLE
On 24/06/13 19:57, Reindl Harald wrote:
Am 24.06.2013 18:47, schrieb Johan De
Hi guys,
any suggestions? I just repaired 90G MyISAM table with REPAIR TABLE
command. the space on the hard drive gone down from 165 Gig to 70 Gig. I
understand that during repair process MySQL creates temp file and remove
it after the job done. Or removal process executes on the server
- Original Message -
From: nixofortune nixofort...@gmail.com
Hi guys,
any suggestions? I just repaired 90G MyISAM table with REPAIR TABLE
command. the space on the hard drive gone down from 165 Gig to 70
Gig. I understand that during repair process MySQL creates temp file and
Am 24.06.2013 18:47, schrieb Johan De Meersman:
- Original Message -
From: nixofortune nixofort...@gmail.com
Hi guys,
any suggestions? I just repaired 90G MyISAM table with REPAIR TABLE
command. the space on the hard drive gone down from 165 Gig to 70
Gig. I understand that during
Oops, totally missed that, thanks.
Reindl Harald h.rei...@thelounge.net wrote:
Am 24.06.2013 18:47, schrieb Johan De Meersman:
- Original Message -
From: nixofortune nixofort...@gmail.com
Hi guys,
any suggestions? I just repaired 90G MyISAM table with REPAIR TABLE
command. the
On 24/06/13 19:57, Reindl Harald wrote:
Am 24.06.2013 18:47, schrieb Johan De Meersman:
- Original Message -
From: nixofortune nixofort...@gmail.com
Hi guys,
any suggestions? I just repaired 90G MyISAM table with REPAIR TABLE
command. the space on the hard drive gone down from 165
14 matches
Mail list logo
