Hi!
The change of key_buffer_size worked like a charm.
Thank you !
CheHax
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Hi again,
I worked on the problem and found a way to make the LOAD INDEX INTO
CACHE work on my main tables now.
I actually found out that some of my indexes using varchar could be
optimized because they aren't used for search but ordering
(alphabetical and such). So having a index length of 255
One last question, maybe :)
Is there any way to empty the key buffer once the server is started ?
That would be handy :)
Thanks
On Tue, 22 Feb 2005 11:13:29 +0100, HMax [EMAIL PROTECTED] wrote:
Hi again,
I worked on the problem and found a way to make the LOAD INDEX INTO
CACHE work on my
Hello.
Sergei Golubchik said that we can't change the value of the blocksize
of a key (it is chosen in mi_create.c) and there is no workaround
with this LOAD INDEX problem.
HMax [EMAIL PROTECTED] wrote:
Hello there.
OK I'll paste the results of commands you asked right after my
So this means we cannot combine both FULLTEXT and classical indexes if
we want to use a LOAD INDEX INTO CACHE, and that we won't ever be able
to ?
How about being able to specify the indexes we want to load into the
cache. It's supposed to work this way (but it is told in the doc it
doesn't yet).
Hi!
On Feb 21, HMax wrote:
So this means we cannot combine both FULLTEXT and classical indexes if
we want to use a LOAD INDEX INTO CACHE, and that we won't ever be able
to ?
No. FULLTEXT indexes now have small block size (1024) so they should
load ok. Only long varchar indexes will be a
Thank you for your answer Sergei,
It's all clear now, and I'm glad to know where the problem comes from.
Now if I understand correctly, my only solution is to manage to create
indexes in my tables that ALL have the same block size (1024). This
would mean reducing the size of the indexes on my
Hello.
doesn't work. Is there really no workaround ? We have for about 1.5Go
MySQL will store used blocks in memory and minimize a disk I/O,
if your key_buffer_size variable has a sutable value and you
have enough RAM. You may use CACHE INDEX to assign a separate
cache for your table
Hi!
On Feb 21, HMax wrote:
Thank you for your answer Sergei,
It's all clear now, and I'm glad to know where the problem comes from.
Now if I understand correctly, my only solution is to manage to create
indexes in my tables that ALL have the same block size (1024). This
would mean
Hello.
Please send us output of the following statements:
SHOW CREATE TABLE your_table;
SHOW VARIABLES;
SHOW STATUS;
What output does the following command produce:
myisamchk -d -v your_table
HMax [EMAIL PROTECTED] wrote:
Hello there,
We have a problem with the
Hello there.
OK I'll paste the results of commands you asked right after my reply,
because we found out where the problem comes from.
The myisamchk command showed that the index on the VarChar has a block
size of 2048 instead of 1024. However, when I turn this index to a
FULLTEXT one, the block
Hello there,
We have a problem with the LOAD INDEX INTO CACHE command which is
supposed to be fixed in version 4.1.10
It may be fixed, but then we don't get the way to make it work.
We want to load all the indexes of one of our big table into the main key cache.
This table is myISAM, and has
Hi,
I'm trying to load an index into cache hot_cache, but it is not
working. Here is my step to step:
CREATE TABLE GEILSON (CPF VARCHAR(14) NOT NULL, NAME VARCHAR(75) NOT
NULL, PRIMARY KEY (CPF), FULLTEXT (NAME));
INSERT INTO GEILSON (CPF,NAME) VALUES (08238512786, DAVID ESCODINO);
INSERT
13 matches
Mail list logo
