You are referring to fragmentation. In this case I'm pretty sure it's
just a matter of updating the indexes so that MySQL makes the correct
assumptions about the distribution of data. MySQL assumes data values
have an equal distribution in a database, updating the indexes will
force MySQL to u
when i reimport i usually drop all the indexes first anyway as it takes
forever i have found that a repair table quick usually helps after
reindexing too
-Original Message-
From: Adam Nelson [mailto:[EMAIL PROTECTED]
Sent: Wednesday, August 06, 2003 8:09 AM
To: 'MySQL'
Subject:
Jeff,
- Original Message -
From: "Jeff Mathis" <[EMAIL PROTECTED]>
Newsgroups: mailing.database.mysql
Sent: Thursday, August 07, 2003 9:01 PM
Subject: Re: reindexing
> what is the command to update InnoDB table indexes?
if you mean update index cardinality statis
what is the command to update InnoDB table indexes?
jeff
Brent Baisley wrote:
>
> You are referring to fragmentation. In this case I'm pretty sure it's
> just a matter of updating the indexes so that MySQL makes the correct
> assumptions about the distribution of data. MySQL assumes data values
I was under the impression that InnoDB tables took care of this for you.
You only need to be concerned if you add/delete repeatedly from anywhere
but the end rows of the table.
I'd like to know if I'm wrong about this.
Adam Nelson wrote:
>
> I just did a major insert of new data and now all my
I just did a major insert of new data and now all my selects have slowed
down. The table is innodb. Is there a way to reindex everything
without having to drop anything. Otherwise, I suppose I will have to
drop the indexes and remake them.
--
MySQL General Mailing List
For list archives: http
t;[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Friday, July 18, 2003 11:42 AM
Subject: Re: Faster reindexing
> umm say i reindex after a reimport i usually drop all the indexes first ,
> then a
aul DuBois wrote:
>> At 14:14 +0700 7/9/03, Dominicus Donny wrote:
>> >Sorry, my mistake. It's "reindexing" then.
>> >Once i should add 2 key indexes on a huge table.
>> >But instead of alter the table in 1 single query,
>> >I build each index 1 b
On Wed, Jul 09, 2003 at 11:51:01PM -0500, Paul DuBois wrote:
> At 14:14 +0700 7/9/03, Dominicus Donny wrote:
> >Sorry, my mistake. It's "reindexing" then.
> >Once i should add 2 key indexes on a huge table.
> >But instead of alter the table in 1 single
ian Weimer [mailto:[EMAIL PROTECTED]
Sent: donderdag 10 juli 2003 10:06
To: Dathan Vance Pattishall
Cc: 'Paul DuBois'; [EMAIL PROTECTED]
Subject: Re: Faster reindexing
"Dathan Vance Pattishall" <[EMAIL PROTECTED]> writes:
> Maybe increasing
>
> #use for when my
"Dathan Vance Pattishall" <[EMAIL PROTECTED]> writes:
> Maybe increasing
>
> #use for when mysql is doing a check or repair
> set-variable= myisam_sort_buffer_size=64M
>
> to a higher value will make the index happen faster on the fly.
MySQL doesn't seem to honour this variable. I've set it
At 14:14 +0700 7/9/03, Dominicus Donny wrote:
Sorry, my mistake. It's "reindexing" then.
Once i should add 2 key indexes on a huge table.
But instead of alter the table in 1 single query,
I build each index 1 by 1.
Generally, it is faster to build all your indexes with a sin
t insertion
> for a self balancing tree is a faster in some cases (I believe this is
> the case) then building one on the fly.
I don't think this matters much, as reindexing seems to reload the
database anyway.
> My 2 cents. 100 million rows WOW.
I initially hoped to store even a b
PM
-->To: Florian Weimer; [EMAIL PROTECTED]
-->Subject: Re: Faster reindexing
-->
-->At 9:39 +0200 7/7/03, Florian Weimer wrote:
-->>I've got a table with 100 million rows and need some indexes on it
-->>(one row is 126 bytes).
-->>
-->>I'm currently using M
From: Paul DuBois [mailto:[EMAIL PROTECTED]
Sent: Wednesday, July 09, 2003 5:23 AM
To: Dominicus Donny; [EMAIL PROTECTED]
Subject: Re: Faster reindexing
At 11:23 +0700 7/9/03, Dominicus Donny wrote:
>Try analyze your table(s).
What information will this yield to make indexing faster?
>
&
Sorry, my mistake. It's "reindexing" then.
Once i should add 2 key indexes on a huge table.
But instead of alter the table in 1 single query,
I build each index 1 by 1.
And the responses of the slaves also great, too.
Anyway, im using the standard my-medium.cnf setup.
The hug
"Paul DuBois" <[EMAIL PROTECTED]>; "Florian Weimer" <[EMAIL PROTECTED]>;
<[EMAIL PROTECTED]>
Sent: Wednesday, July 09, 2003 10:23 AM
Subject: RE: Faster reindexing
when reimporting or reinserting or whatever from a huge db i usually drop
all the indexes reimport
t;;
<[EMAIL PROTECTED]>
Sent: Wednesday, July 09, 2003 10:23 AM
Subject: RE: Faster reindexing
> when reimporting or reinserting or whatever from a huge db i usually drop
> all the indexes reimport then create them again much quicker
>
> -Original Message-
> From: Paul DuB
: Faster reindexing
At 9:39 +0200 7/7/03, Florian Weimer wrote:
>I've got a table with 100 million rows and need some indexes on it
>(one row is 126 bytes).
>
>I'm currently using MyISAM and the indexing proceeds at an
>astonishingly low rate: about 200 MB per hour. This is
At 9:39 +0200 7/7/03, Florian Weimer wrote:
I've got a table with 100 million rows and need some indexes on it
(one row is 126 bytes).
I'm currently using MyISAM and the indexing proceeds at an
astonishingly low rate: about 200 MB per hour. This is rate is far
too low; if we had to recover the dat
I've got a table with 100 million rows and need some indexes on it
(one row is 126 bytes).
I'm currently using MyISAM and the indexing proceeds at an
astonishingly low rate: about 200 MB per hour. This is rate is far
too low; if we had to recover the database for some reason, we'd have
to wait fo
On 30-Jul-2001 shawn reed wrote:
> i've tried simply re-creating the index as you suggested ... no luck.
>
> here's a brief summary of my situation: i developed an application on one
> server, after it was developed and ready to go live we started to move it
> to another server. after moving it
i've tried simply re-creating the index as you suggested ... no luck.
here's a brief summary of my situation: i developed an application on one
server, after it was developed and ready to go live we started to move it
to another server. after moving it i noticed my search function wasn't
working
What about issueing first drop index, then add index? Should do
the job. Or repair table. What does check table or myisamchk say?
shawn reed schrieb am Montag, 30. Juli 2001, 07:44:15:
> hi all,
> i apologize for the utterly newbie-ish question, but i've yet to find an
> answer to it after havi
hi all,
i apologize for the utterly newbie-ish question, but i've yet to find an
answer to it after having spent quite some time searching mysql's web site
(especially since half the links i click on now seem to be giving me 404
errors...)
how does one reindex a table containing fulltext indexes
Hi,
How can I reindex any table in mysql.
Thanks
Mucahit
26 matches
Mail list logo
