On Tue, Jun 08, 2010 at 04:57:25PM +0200, V?clav Ovs?k wrote: > Hi Ken, > > On Tue, Jun 08, 2010 at 07:48:15AM -0500, Kenneth Marshall wrote: > > ILIKE is fine on PostgreSQL as long as the search is anchored on > > the left and there is an index. Otherwise it will do a sequential > > scan of the attachments table to find matching records. The wiki > > entries for full-text indexing with PostgreSQL and Oracle can avoid > > the sequential scan through the use of the database's full-text > > thanks for your work on PostgreSQLFullText wiki page! Good starting > point. I'm playing with the fulltext on one instance already. I must > discuss the possibility to use the fulltext on Pg with my leader. The > results are different from those get from ILIKE. I tried to find 'cisco' > for example :). Normal search returned 25 tickets, but fulltext only 15. > Fulltext parser did tokens from URL and www.cisco.com was a lexem as is > (not broken further). I can't say this is fine or not, it is difference. > Users must know this - how to write the query correctly. >
Correct, the results depend on the parsing rules that are used by the full-text configuration. These rules can be adapted to your needs, but I do agree that some explanation about common types of query problems would be worthwhile. Regards, Ken Discover RT's hidden secrets with RT Essentials from O'Reilly Media. Buy a copy at http://rtbook.bestpractical.com