t. Reduce your key buffer to 1700 or you will eventually crash.
>
>
> Then type repair table PC1_Text quick, or ALTER TABLE PC1_TEXT
> ENGINE=myISAM. This helps with rebuilding full text indexes.
>
>
> DVP
>
> Dathan Vance Pattishall http://www.friendster.com
>
&g
Hello all,
I'm having a bit of trouble with a full-text query being slow. At first I
thought it was a problem with a join, then I thought it was a problem with a
sort - but I've boiled down the query and it seems like plain-old slowness.
This is the table:
CREATE TABLE `PC1_Text` (
`AssetID` i
So I don't think this is a mysql issue, but I wanted to bounce it off the
group anyways and see if anyone had seen similar behavior.
I'm running MySQL 4.1.10 on a Dell Poweredge 1850 with 2 EM64T Xeons and
2GB of memory running Redhat Enterprise 3 ES. I've been trying to address
some slowness i
I have the following table:
> CREATE TABLE `Article_Search` (
> `ArticleID` int(11) NOT NULL default '0',
> `Content` text NOT NULL,
> PRIMARY KEY (`ArticleID`),
> FULLTEXT KEY `Content` (`Content`)
> ) ENGINE=MyISAM DEFAULT CHARSET=latin1
This table has several million rows, but I only want t
ten duplicate 'a'
> > and 'b' sections which polutes the key buffer.
> >
> > -Eric
> >
> > Dathan Pattishall wrote:
> >
> > >Use 10 smaller tables and perform a union. It's faster to look up in
> > >smaller tables then
Hi everyone,
I have a question regarding the performance of UNION queries:
I need to do a full-text search against a large number of rows. Is it
faster to have one table with 10,000,000 text rows and perform one
full-text search. Or, am I better off having 10 smaller more managable
tables and per
