On 24/06/13 19:57, Reindl Harald wrote:
Am 24.06.2013 18:47, schrieb Johan De Meersman:
- Original Message -
From: "nixofortune"
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 under
Oops, totally missed that, thanks.
Reindl Harald wrote:
>
>
>Am 24.06.2013 18:47, schrieb Johan De Meersman:
>> - Original Message -
>>> From: "nixofortune"
>>>
>>> Hi guys,
>>> any suggestions? I just repaired 90G MyISAM table with REPAIR TABLE
>>> command. the space on the hard drive g
Am 24.06.2013 18:47, schrieb Johan De Meersman:
> - Original Message -
>> From: "nixofortune"
>>
>> 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
Hello Rafał,
On 6/24/2013 4:26 AM, Rafał Radecki wrote:
As I can see the changes in these values are use by percona cacti
monitoring templates to graph "InnoDB I/O".
Can anyone answer the question finally? ;)
2013/6/21 Hartmut Holzgraefe
On 21.06.2013 13:59, Rafał Radecki wrote:
Hi All.
I
- Original Message -
> From: "nixofortune"
>
> 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 th
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
resta
As I can see the changes in these values are use by percona cacti
monitoring templates to graph "InnoDB I/O".
Can anyone answer the question finally? ;)
2013/6/21 Hartmut Holzgraefe
> On 21.06.2013 13:59, Rafał Radecki wrote:
> > Hi All.
> >
> > I've searched but with no luck... what do exactly
