Thomas Mueller wrote: > > > But I also have a simpler idea that will still speed things up. It > > > involves using a regexp SQL fulltext search. While it's definitely slow > > > compared to a changed storage (the db won't be able to use indexes), > > > it's still faster because it does not involve any parsing, and uses the > > > well-tuned SQL server code to do fulltext searching. > > That will still be awfully slow because the database has to read every > single page, lot of expensive I/O.
I know. But faster than the read every message-parse-check, which seems to be what's used now. > For PostgreSQL there is Tsearch2 [1], Oracle has built in full text > search as far as I know, what about MySQL? I think it would be better to > use special functions if they are available. The only MySQL special function I know of are fulltext indexes. These are only available on MyISAM tables, and I'm not sure if they're used for this kind of queries. Yours, Mikhail Ramendik
