- Original Message -
> From: "Yu Watanabe"
>
> So, which memory corresponds to 'pages' for the MyISAM then?
> It would be helpful if you can help me with this.
None, as Reindl said. This is not a memory issue, it's a function of I/O
optimization. Records are stored in pages, and pages a
you should try to understand what pages are
your data + keys + fragmentation overhead if
deleted records are the size of the files
Am 24.11.2011 10:46, schrieb Yu Watanabe:
> Hi Reindl.
>
> Thanks for the reply.
>
> So, which memory corresponds to 'pages' for the MyISAM then?
> It would be help
Hi Reindl.
Thanks for the reply.
So, which memory corresponds to 'pages' for the MyISAM then?
It would be helpful if you can help me with this.
Thanks,
Yu
Reindl Harald さんは書きました:
>key buffer is memory and has nothing to do with file sizes
>filesize increeases by data and keys
>key buffer is as
key buffer is memory and has nothing to do with file sizes
filesize increeases by data and keys
key buffer is as the name says a memory-buffer for kyes
Am 24.11.2011 10:25, schrieb Yu Watanabe:
> Hello Johan.
>
> Thank you for the reply.
> I see. So it will depend on the key buffer size.
>
> Tha
Hello Johan.
Thank you for the reply.
I see. So it will depend on the key buffer size.
Thanks,
Yu
Johan De Meersman さんは書きました:
>- Original Message -
>> From: "Yu Watanabe"
>>
>> It seems that MYD is the data file but this file size seems to be not
>> increasing after the insert sql.
>
>
At 02:45 AM 11/23/2011, you wrote:
Also,
since MySQL 5.1 MyISAM has an algorythm to detect if you are going to
delete a row without ever reading it,
so when you insert it, it will use the blackhole storage engine instead.
:O (NB: it is a joke)
Claudio
Claudio,
I have been using the bl
Also,
since MySQL 5.1 MyISAM has an algorythm to detect if you are going to
delete a row without ever reading it,
so when you insert it, it will use the blackhole storage engine instead.
:O (NB: it is a joke)
Claudio
2011/11/23 Johan De Meersman
> - Original Message -
> > From: "Yu
- Original Message -
> From: "Yu Watanabe"
>
> It seems that MYD is the data file but this file size seems to be not
> increasing after the insert sql.
That's right, it's an L-space based engine; all the data that has, is and will
ever be created is already in there, so storage never in
Hi !
I would like to ask question regarding to the MyISAM engine.
Is there any physical file that you have to be aware of its size
for disk sizing, like the ibdata1 in innodb storage engine?
It seems that MYD is the data file but this file size seems to be not
increasing after the insert sql.
