2:27 PM, James Drabb wrote:
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of
Harald Fuchs
Sent: Tuesday, May 25, 2004 11:18 AM
To: James Drabb
Subject: Re: FULLTEXT and large database
I seem to get inconsistent results when using the FULLTEXT index
speed-wise o
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of
Harald Fuchs
Sent: Tuesday, May 25, 2004 11:18 AM
To: James Drabb
Subject: Re: FULLTEXT and large database
> > I seem to get inconsistent results when using the FULLTEXT index
> > speed-wise
"James Drabb" <[EMAIL PROTECTED]> wrote on 25/05/2004 16:30:07:
> The text 'May' is in the column, yet I get no rows returned? The admins
> are looking
> to be able to search for an arbitrary string in the MsgText field that
> can be anywhere
> in the field not just at the beginning. So
-Original Message-
From: Brent Baisley [mailto:[EMAIL PROTECTED]
Sent: Tuesday, May 25, 2004 9:50 AM
To: James Drabb
Cc: Jigal van Hemert; [EMAIL PROTECTED]
Subject: Re: FULLTEXT and large database
> You may try increasing your sort_buffer_size and key_buffer_size,
> see if that
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Tuesday, May 25, 2004 8:52 AM
To: [EMAIL PROTECTED]
Cc: James Drabb; [EMAIL PROTECTED]
Subject: Re: FULLTEXT and large database
> One thing that ocurs to me is that, if you are using it for syslog
type
>
You may try increasing your sort_buffer_size and key_buffer_size, see
if that speeds up the searching and sorting.
On May 25, 2004, at 9:54 AM, James Drabb wrote:
When I run a FULLTEXT search and view the process list of MySQL in
MySQL,
I see in the state column that MySQL is "sorting results" wh
From: "James Drabb" <[EMAIL PROTECTED]>
> From: Jigal van Hemert [mailto:[EMAIL PROTECTED]
> So is there any way to efficiently search a TEXT field of 5 million rows
> for exact phrases? In this case the MsgText field contains a
> descriptive
> error message that the admins want to search for to h
-Original Message-
From: Jigal van Hemert [mailto:[EMAIL PROTECTED]
Sent: Tuesday, May 25, 2004 7:56 AM
To: [EMAIL PROTECTED]
Subject: Re: FULLTEXT and large database
> > Using Match() Against() showed the Kiwi_MsgText FULLTEXT index
getting
> > used.
>
> Correct. Ful
> >
> > I have a web app to allow admins to search this table. Any searches by
> > MsgDate, MsgTime, MsgPriority or MsgHostname or any combination of them
> > runs
> > pretty fast. When I try to do a search against MsgText, it takes quite
> > a
> > while. I originally tried INSTR(), however
You probably don't have to worry about hitting MySQL limits. Everything
I've read and heard say you hit OS limits first.
For full text searches, you definitely want to use match/against. If
you are only interested in one months worth of data, are you deleting
"old" records on a regular basis
> of data. How big of a DB can MySQL handle? After two days of running
> there
> are 2,160,000 or so records in the database.
Size of database is generally limited by available diskspace.
MyISAM tables are stored in seperate files per table, so the filesystem
might initially limit the size since
11 matches
Mail list logo
